Lean Inception

---

Origins

Lean Inception was developed by Paulo Caroli at Thoughtworks and published in his 2018 book Lean Inception: How to Align People and Build the Right Product¹. Caroli built it from a recurring problem he saw on new product engagements: teams were eager to start building, but rarely shared a clear, common understanding of what the product was, who it was for, or what the smallest worthwhile version would actually contain.

Lean Inception combines ideas from Design Thinking, Lean Startup, and Agile delivery into a structured five-day workshop. Rather than asking the team to write a long product specification upfront, it produces a tight set of artifacts — product vision, personas, user journeys, a feature canvas, and an MVP canvas — through collaborative exercises with the people who will actually build and use the product.

What Lean Inception Produces

The output of a Lean Inception is not a document. It is a shared understanding, captured in a small set of visible artifacts that the team and stakeholders agreed to in the room. By the end of the week, the team has answered four practical questions:

• What are we building? A clear product vision, refined with the team rather than handed to them.
• Who is it for? Personas grounded in real users, with the journeys they care about laid out step by step.
• What goes in the MVP? A feature list scoped to the smallest version worth shipping, with explicit trade-offs.
• How will we know it worked? Success criteria, metrics, and the next learning cycle planned.

The Five-Day Agenda

Caroli's canonical Lean Inception runs over five days, with each day building on the previous one. The exact agenda is flexible — remote teams often spread it across two weeks, and smaller scopes can compress it — but the sequence matters.

Day 1: Vision and Alignment

• Kickoff: framing the inception, agreeing on goals, surfacing existing assumptions.
• Product Vision: collaborative writing of a one-paragraph vision statement that everyone in the room can quote without reading it.
• Is — Is Not, Does — Does Not: a four-quadrant exercise that defines the product by what it is, isn't, does, and doesn't do. Often the most clarifying hour of the week.

Day 2: Users and Goals

• Personas: building 3–5 personas with goals, behaviors, and needs. Each persona is grounded in a real user where possible.
• Goals and Business Outcomes: making explicit what success looks like from the business side, not just the user side.
• Brainstorming Features: divergent generation of every possible feature that might serve the personas and goals.

Day 3: Journeys and Features

• User Journeys: mapping the step-by-step experience of each persona, often using sticky notes on a wall.
• Feature Refinement: each feature is described and sized using the Feature Canvas, a one-page template covering value, users, criteria, and dependencies.

Day 4: Sequencing and Trade-offs

• Sequencer: features arranged on a timeline by sequence and effort. The result is a visible MVP-versus-later split, debated openly.
• Technical, UX, and Business Reviews: each discipline scrutinizes the proposed MVP for feasibility, viability, and desirability.

Day 5: MVP Canvas and Commitments

• MVP Canvas: the inception's primary deliverable. A single-page summary of the MVP — vision, personas, journeys, features, success metrics, and the next learning cycle — that the team can carry forward into delivery.
• Showcase & Commitments: presenting the result to stakeholders, capturing decisions, and agreeing on next steps.

Who Should Be in the Room

The participant list matters as much as the agenda. A Lean Inception is most useful when it brings together:

• The Product Owner or sponsor who owns the outcome.
• The delivery team — developers, designers, testers — who will actually build the product.
• Key stakeholders whose decisions will affect scope, funding, or release.
• A facilitator who has run inceptions before. The format depends on disciplined facilitation, especially at the trade-off conversations.

Workshops attended only by the development team produce great team alignment and weak business alignment. Workshops attended only by stakeholders produce great roadmaps and weak engineering buy-in. The format works because all sides are in the room when the trade-offs get made.

Coaching Tips

Resist the Urge to Pre-Bake

Teams that arrive at the inception with vision and personas "already done" rarely get the alignment value. Let the workshop do the work it is designed to do, even if it feels slower.

Insist on the Right Room

Without stakeholders and engineers both present at the trade-off conversations, the MVP either over-commits scope or quietly excludes the people who have to deliver it.

Time-Box Hard

Each exercise has a recommended duration. Honor it. The discipline of timeboxing is what keeps the week from turning into a sequence of unresolved discussions.

Capture Decisions, Not Just Outputs

The artifacts (MVP Canvas, personas, journeys) matter, but so does the trail of trade-offs behind them. Note what was rejected and why so the decisions can be revisited.

Plan the First Sprint Inside the Inception

End the week with the team knowing what they will start on Monday. Without a concrete next step, the energy and alignment of the workshop fade fast.

Plan for Re-Inception

The MVP Canvas is a snapshot, not a contract. Schedule a checkpoint — six weeks, three months — to revisit assumptions with the evidence the team has now gathered.

Summary

Lean Inception is a tool for the moment between strategic intent and team commitment. It replaces the long inception of upfront documents with a fast, collaborative week that produces just enough shared understanding for the team to start building with confidence and just enough explicit scope to avoid the early sprints disappearing into endless framing conversations.

It is not the right tool for every situation. For products with strong existing direction or teams already deep into delivery, the format is overkill. But for new products, major pivots, or any time the question "are we sure what we're building?" feels uncomfortable, the cost of a Lean Inception week is small compared to the cost of finding out later that the team and the stakeholders were never quite aligned.

Back to Discovery Workshops Hub