Before we build, we S.I.T.

Structured. Iterative. Transparent.

Structured means modelling the real problem. Iterative means building and testing in useful stages. Transparent means you can see what is being decided, what stage the work has reached and what remains. The method applies from discovery and prototype through to V1, deployment and later refinement.

01

Discover

Start with the real problem, the people affected, the tools already in use, the constraints and what a useful result would look like. No technical specification is required.

02

Architect

Turn the agreed scope into clear rules, boundaries, data, states, decisions and dependencies before weak assumptions become expensive.

03

Build

Build the agreed stage: perhaps a focused prototype, an internal tool, a bespoke operational system or a live V1 product.

04

Validate

Test the workflow, assumptions and edge cases against the agreed success criteria. Resolve contradictions, refine the build and make trade-offs explicit.

05

Deploy & Iterate

When the scope supports it, deploy the tested product with clear documentation, then continue into later stages or refinements where they add value.

Discovery without the form-filling

A useful conversation, structured behind the scenes.

You are not expected to complete a long questionnaire or describe the problem in software language. Discovery happens as a natural phone, video or face-to-face conversation while Constellation Highway works through a structured framework internally.

S.I.T. UP — Structured Internally. Typed Up. Afterwards, the answers are reconstructed and organised into a clear consultation record and proposed scope for you to confirm. It is a structured record of what was learned, not a claimed verbatim transcript.

Stu Robertson on a client call, taking notes at a laptop
01

Natural conversation

02

Structured discovery

03

Written record

04

Proposed scope

05

Client confirmation

06

Build authority

Working philosophy

“Protect the invariant, find the source of discrepancy, and improve the method rather than weakening the acceptance standard.”

That principle keeps ambitious systems coherent while they change, grow and meet edge cases.

Start a conversation

Have a problem, process or product that needs its next stage?

Bring the complicated version. We’ll define what needs to work, agree a sensible scope and identify whether the right next step is discovery, prototype, build or deployment.

Email Stu