lean-ux-canvas

Guides teams through Lean UX Canvas v2 to frame business problems and test assumptions.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill lean-ux-canvas-brunol28
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lean-ux-canvas
Source: https://github.com/BrunoL28/product-onboarding-skill/tree/main/skills/lean-ux-canvas
Command: npx skills add https://github.com/BrunoL28/product-onboarding-skill --skill lean-ux-canvas-brunol28

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight to building solutions without framing the underlying business problem, surfacing risky assumptions, or defining what to learn first. This Skill structures that conversation using Jeff Gothelf's Lean UX Canvas v2, turning assumptions into cheap experiments before development begins. ## Core Features & Use Cases - Eight-box guided facilitation: Walks through Business Problem, Business Outcomes, Users, User Outcomes, Solutions, Hypotheses, Riskiest Assumption, and Smallest Experiment, with a checkpoint gate after each box. - Upstream artifact collapse: When PROBLEM_STATEMENT.md and PROTO_PERSONA.md exist, it pre-fills Boxes 1, 3, and 4 and starts the real conversation at Box 2. - Experiment contract enforcement: Box 8 is only complete with a method, a pre-stated pass/fail signal, and a timebox, and Boxes 7-8 loop until confidence is high enough to build. - Use Case: A product team debating a new in-app dispute feature uses the canvas to discover their riskiest assumption is a value assumption (does visible status deflect calls?), then designs a two-week IVR experiment with no engineering build to test it. ## Quick Start Ask the assistant to run a Lean UX Canvas session for your initiative, starting from the business problem and your target user.

Frequently Asked Questions about lean-ux-canvas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a Lean UX Canvas session with my team?▼

Start with the business problem and target user, then work through the eight boxes in order, gating after each one. The skill asks at most three targeted questions when context is missing and proceeds with clearly labelled assumptions.

What is the difference between Box 2 and Box 4 in Lean UX Canvas?▼

Box 2 captures measurable business outcomes as numbers with direction, while Box 4 captures user outcomes as feelings or benefits with no metrics. If Box 4 contains a percentage it belongs in Box 2, and if Box 2 contains an adjective it is wrong.

Can Lean UX Canvas reuse existing problem statements or personas?▼

Yes. When PROBLEM_STATEMENT.md and PROTO_PERSONA.md exist upstream, Boxes 1, 3, and 4 are pre-populated from those artifacts with sources shown, and the conversation starts at Box 2 where new decisions are needed.

How do I identify the riskiest assumption in Box 7?▼

Ask which assumption, if false, would waste the most work, then classify it as value, usability, feasibility, or viability. Teams typically name a comfortable usability assumption when the value assumption is the one that would sink the initiative.

What makes a valid Box 8 experiment in Lean UX?▼

A valid Box 8 entry requires three things: the method, a pass/fail signal stated in advance, and a timebox. Running a survey is not an experiment; the result must be able to change the plan, such as promoting a different solution on a fail signal.

When is a Lean UX Canvas considered finished?▼

The canvas is finished when the Box 8 experiment is cheap enough to run this sprint, not when all eight boxes contain text. Boxes 7 and 8 loop until confidence is high enough to build or the assumption is cheap enough to risk.