Shop/Sprints/Ideas & experimentation

Prototype & validate

Before the big build, ask a better question.

Make an important uncertainty tangible. Develop a prototype, put it in front of relevant people and use what happens to inform the next investment decision.

Sprints / Prototype & validate Choose a format

Sounds like

The proposal is convincing because nobody has had to use it.

A team is about to commit real resources to assumptions it could examine more cheaply. “We need a pilot” has become the plan rather than the start of a learning design.

What you might be hearing

  • A new idea is gathering commitment before evidence.
  • The team disagrees about what customers or users need.
  • The next investment is much larger than the learning so far.

How it works.

Choose the assumption that most affects the decision, then design the smallest credible way to examine it. A prototype is selected for the evidence it can create, not its visual polish.

  1. Choose the uncertainty

    Frame the user need, the idea and the decision ahead. Rank assumptions and choose the one worth examining first.

  2. Make something testable

    Build an appropriate prototype: paper, role-play, service walkthrough or interactive model. Agree the test method and what observations matter.

  3. Listen, interpret and decide

    Run the agreed tests, separate observation from interpretation and compare the evidence with the original assumption. Decide whether to continue, change, stop or investigate further.

What you leave with.

  • A prioritised assumption map
  • A prototype suited to the learning question
  • An evidence summary and a next investment recommendation
Who it’s for
Product teams, service owners, founders and internal innovators before a significant commitment.
What to bring
Access to relevant users or stakeholders, a clear decision owner and agreement on test boundaries.
Example pageINSO

The evidence readout

A decision-focused summary of what the test actually showed.

  1. What we expected and who we tested with.
  2. What we observed, including contradictory signals.
  3. What the evidence supports, what it does not and what to do next.

Choose your format.

This builds a line in your brief. Scope and fees are agreed with you before anything is booked.

1Format
2Delivery
3Roughly how many people?

Before we talk.

The questions people usually ask first. Ask a different one

Will the prototype be production ready?

Usually not. Its purpose is to learn. Production development, integrations and ongoing support require a separate scope.

Can you prove market demand in a week?

A small test provides bounded evidence. We state the limits and avoid treating a few responses as proof of a whole market.

What if testing takes longer?

Recruitment and evidence readiness shape timing. We agree the test plan before promising a schedule.