Skip to content

Private draft · Not published · For internal review

How Concepts Advance

Four stages. Four decision gates. One standard of evidence.

Each stage has a defined purpose, a gate to advance, and the option to stop. A concept can advance, change direction, or end at any gate, and not every concept advances through every stage.

Durations are proposed planning ranges, not commitments · Stage four timing is set by leadership decision

The stage-gate timeline.

Purpose, duration, and gate criteria for each stage, as proposed in the November 19 meeting brief.

Stage 01

Thesis

Proposed planning range

2–4 weeks

Purpose

  • Name the problem.

  • Identify the user, buyer, and budget owner.

  • Describe why the issue matters now.

  • Identify the likely workflow and affected decision.

Gate to advance

A credible buyer confirms the problem and indicates a plausible budget path.

Questions to answer

  • Who experiences the problem?
  • Who can purchase a solution?
  • What happens today?
  • What makes this problem urgent?
  • What evidence supports the hypothesis?

Stage 02

Validate

Proposed planning range

6–8 weeks

Purpose

  • Conduct buyer interviews.

  • Map the current workflow.

  • Identify unmet needs and alternative solutions.

  • Confirm data, access, procurement, and regulatory dependencies.

  • Seek a signed design partnership or other written validation arrangement.

Gate to advance

A design partner commits to defined participation and the buyer evidence supports continued work.

Stage 03

Build

Proposed planning range

10–12 weeks

Purpose

  • Define the initial product and user workflows.

  • Establish architecture, security, privacy, and data boundaries.

  • Build and test a bounded first product.

  • Document acceptance criteria and unresolved risks.

  • Review whether intended users can complete the agreed first task.

Gate to advance

The design partner accepts the pilot against written criteria and there is evidence of user engagement or repeat use, as defined for that concept.

Stage 04

Spin Out

Timing

Set by leadership decision and the specific concept

Purpose

  • Recruit a dedicated founding CEO.

  • Define ownership, governance, and company structure with counsel.

  • Establish a separate operating plan, team, budget, and funding path.

  • Set transition terms for shared resources and any licensed technology.

  • Wind down shared Studio support according to written agreements.

Gate to advance

The company has its own accountable leader, approved formation plan, defined resources, and an agreed path to operate independently.

Planning ranges describe intent, not a schedule. A gate may be revisited if the underlying evidence changes, and any change of direction is recorded with the decision.

Inertia break

What stops a concept.

Stopping preserves resources for concepts with stronger evidence. Each condition below is sufficient on its own, and the decision is recorded at the gate.

  1. 01

    No buyer with a budget confirms the problem

    Interest without purchasing authority is not evidence of a market.

  2. 02

    No design partner can commit to access and participation

    Without defined participation, the work cannot be tested with real users.

  3. 03

    Required data, workflow access, or procurement path cannot be established

    A product that cannot reach its users cannot be validated responsibly.

  4. 04

    The regulatory or clinical path cannot be responsibly funded or supported

    Some problems need a path the team cannot carry at this stage.

  5. 05

    The economics do not justify continued work

    A real problem still needs a workable commercial model.

  6. 06

    The concept depends on another organization’s confidential information, code, or intellectual property without written permission

    No amount of demand justifies using what we are not authorized to use.

Abstract concept imagery. A joint, not a portfolio company.

Bring a problem to the first gate.

The Thesis stage begins with the buyer, the workflow, and the evidence behind the problem.