← All scenarios

Legacy replacement

The system being replaced has no documentation

The real model lives in a database nobody wrote and a drawer of paper forms, and the rebuild has to start from that.

Teams with data that keeps changing shape

These are illustrative scenarios showing how the products are used, not customer case studies.

The same sequence, twice

The same sequence today, and with SynaptaGrid.

Today

  1. No documentation to work from
  2. Discovery by interview
  3. Model transcribed by hand
  4. Wrong shape found late

With SynaptaGrid

  1. Read the existing database
  2. Infer from a paper form
  3. Review the proposal
  4. Create the model

The situation

Discovery produces a spreadsheet of guesses. The paper forms are the actual specification, and they get transcribed by hand into a data model that is wrong in ways nobody finds until the users arrive.

How it is approached

The existing database is registered and read directly: pick a table, follow its relationships, preview what would be created, then create it. A sample document infers a model the same way. A photographed or scanned form produces a proposed schema, and a completed form has its values extracted against a published one. Every proposal is a draft to review, regenerate or discard before anything exists.

What changes

Discovery starts from a proposal taken out of the real system rather than from a blank document. What the forms actually captured becomes visible early, while changing the model is still cheap.