Start a conversation
WH/ / DECISION SYSTEM

Validation & Prototype / Evidence before build

Make the critical assumption visible before it becomes an expensive commitment.

Validation & Prototype is a focused evidence cycle for a product or AI direction that looks plausible but hasn't been tested. We make the riskiest assumption tangible and test it with the right people. The recommendation says what to advance, change, narrow, or stop.

Discuss the risk to validate

The moment to use this engagement

When to run a validation cycle

You have a direction. The risk is whether it survives contact with reality.

  • A product or AI concept has executive attention, but customer value is still an assertion.
  • A workflow appears efficient on paper, but adoption, trust, or exceptions remain unclear.
  • Technical, security, or operating constraints may materially change the experience.
  • Stakeholders need a shared artifact instead of another abstract debate.

Not the right fit when

If the central decision is still undefined, begin with an Innovation Working Session.

What it is

What the validation cycle includes

A focused way to change the next decision.

  • A focused evidence cycle built around one consequential decision.
  • A way to make a proposition, workflow, or AI interaction tangible enough to test.
  • A written recommendation that links evidence, limits, and next action.

What it is not

What it doesn't include

Clear scope is part of the value.

  • A full product build presented as prototyping.
  • A visual-design engagement without a decision question.
  • A generic innovation lab or unbounded research program.

How the work unfolds

How the cycle runs

One important question. One credible test. One clear recommendation.

01

Frame the decision

Clarify the decision, risk owner, and conditions that would change the call.

02

Define the evidence threshold

Agree on the signal that would be meaningful enough to act on.

03

Make the question tangible

Create the prototype, scenario, workflow, or decision artifact needed to test.

04

Gather the right signal

Test with relevant people, constraints, or operating conditions.

05

Produce the recommendation

Convert evidence into a decision brief and a sequenced next move.

What you keep

What you keep

The prototype is not the deliverable. The decision it enables is.

01

Validation plan

02

Decision prototype or test artifact

03

Evidence log

04

Findings synthesis

05

Decision recommendation

06

Next-step roadmap

Possible outcomes

Possible outcomes

Better evidence creates more than one valid answer.

Advance to buildChange the propositionNarrow the workflowRun a deeper constraint testPause or stop

The value is not a preselected answer. It is an answer the team can explain, act on, and carry into the next decision.

Start with the decision

Name the risk that is still too expensive to ignore.

In a 30-minute fit conversation, we will clarify the decision, the assumption most likely to change it, and whether a focused validation cycle is the right next move.

Discuss the risk to validate