Skip to content

A practical routefrom idea to live.

Five stages, each with a clear purpose, visible output and a decision point — so you always know what is being built and why.

  1. 01

    Frame

    Clarify the business problem, users, constraints and what success should look like.

    Strategist in an orange coat taking notes in a notebook.
  2. 02

    Shape

    Map flows, system boundaries and the smallest product that proves the right thing.

    Product manager placing sticky notes on a planning board.
  3. 03

    Design

    Turn the system into a clear interface with a coherent visual language.

    Designer in an orange sweater sketching wireframes on a whiteboard.
  4. 04

    Engineer

    Build in short loops with testing, review and working software throughout.

    Bearded engineer coding on a laptop while sitting on a block.
  5. 05

    Ship

    Deploy, observe, improve and hand over with the documentation needed to keep moving.

    Engineer on a video call with the team, waving.

stage 01

Frame

Clarify the business problem, users, constraints and what success should look like.

Strategist in an orange coat taking notes in a notebook.

Typical activities

  • Problem and goal conversations
  • User and context mapping
  • Constraint and risk review

Deliverables

  • A written problem frame
  • Agreed success criteria
  • Known constraints and open questions

Collaboration

Direct sessions with the people who own the problem — no layers of account management.

Decision checkpoint

We agree on what problem is being solved and how we will recognise success.

stage 02

Shape

Map flows, system boundaries and the smallest product that proves the right thing.

Product manager placing sticky notes on a planning board.

Typical activities

  • User flow mapping
  • System boundary and integration sketching
  • Scope reduction to the smallest useful product

Deliverables

  • Flow maps
  • A first-release scope
  • A technical outline

Collaboration

Shared working sessions to trade scope against value openly.

Decision checkpoint

We agree on the first release and what is deliberately left out.

stage 03

Design

Turn the system into a clear interface with a coherent visual language.

Designer in an orange sweater sketching wireframes on a whiteboard.

Typical activities

  • Interface structure and hierarchy
  • Visual language
  • Interactive prototypes for key flows

Deliverables

  • Interface designs
  • Prototypes
  • Reusable components and styles

Collaboration

Regular reviews on real screens rather than abstract decks.

Decision checkpoint

Key flows are reviewed and approved before they are engineered.

stage 04

Engineer

Build in short loops with testing, review and working software throughout.

Bearded engineer coding on a laptop while sitting on a block.

Typical activities

  • Short build loops
  • Code review and testing
  • Continuous working builds

Deliverables

  • Working software at each loop
  • Tested, reviewed code
  • Environments to review progress

Collaboration

You see working software throughout, not only at the end.

Decision checkpoint

Each loop is reviewed in working software before the next begins.

stage 05

Ship

Deploy, observe, improve and hand over with the documentation needed to keep moving.

Engineer on a video call with the team, waving.

Typical activities

  • Deployment
  • Observation after launch
  • Improvements and handover

Deliverables

  • A live product
  • Documentation
  • A clear handover

Collaboration

Handover is planned with your team so the product can keep moving.

Decision checkpoint

The product is live, observed, documented and handed over.

Every project is scoped individually. Durations and the depth of each stage depend on the problem, so we agree them together during Frame and Shape rather than quoting fixed timelines here.

Have something to build?
Tell us about it.

Start a project