lean-ux-canvas
Guide teams through Lean UX Canvas v2
Install / Use
npx skills add deanpeters/Product-Manager-Skills --skill lean-ux-canvasInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
DesignSupported Platforms
Tags
Our assessment of lean-ux-canvas
lean-ux-canvas scores 88/100 on our quality scale, 111th of 260 Design skills we index (top 43%).
Its SKILL.md is 24 KB long, well organised into 33 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so lean-ux-canvas is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
lean-ux-canvas compared with similar skills
All 4 of these similar skills score higher than lean-ux-canvas; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| lean-ux-canvas (this skill)by deanpeters | 88 | 7.1k | 3mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install lean-ux-canvas?
- Run
npx skills add deanpeters/Product-Manager-Skills --skill lean-ux-canvas. The install tabs above show the steps for each supported agent. - Which AI agents does lean-ux-canvas work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is lean-ux-canvas safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is lean-ux-canvas still maintained?
- The repository was last updated about 3 months ago, so lean-ux-canvas is actively maintained.
Skill content
View source on GitHubname: lean-ux-canvas argument-hint: "[business problem]" description: Guide teams through Lean UX Canvas v2. Use when framing a business problem, surfacing assumptions, and defining what to learn next. intent: >- Guide product managers through creating Jeff Gothelf's Lean UX Canvas (v2)—a one-page facilitation tool that frames work around a business problem to solve, not a solution to implement. Use this to align cross-functional teams around core assumptions, craft testable hypotheses, and ensure learning happens every sprint by exposing gaps in understanding (problem, users, value, and why the solution should work). type: interactive best_for:
- "Framing a business problem before solutioning"
- "Surfacing assumptions in a cross-functional workshop"
- "Turning a vague initiative into hypotheses and learning goals" scenarios:
- "Help me run a Lean UX Canvas workshop for onboarding drop-off"
- "Use Lean UX Canvas to frame a new AI product idea"
- "We have a business problem but too many assumptions. Run a Lean UX Canvas session." theme: validation-experiments estimated_time: "30-45 min"
Purpose
Guide product managers through creating Jeff Gothelf's Lean UX Canvas (v2)—a one-page facilitation tool that frames work around a business problem to solve, not a solution to implement. Use this to align cross-functional teams around core assumptions, craft testable hypotheses, and ensure learning happens every sprint by exposing gaps in understanding (problem, users, value, and why the solution should work).
This is not a roadmap or feature list—it's an "insurance policy" that turns assumptions into experiments before committing to full development. The canvas shifts conversations from outputs to outcomes and ensures teams build the right thing, not just build things right.
Input
Works best with: The business problem you're framing — or the solution idea you're being handed, which the canvas will reframe as a problem. Also useful: Known users, evidence so far, and what the team already believes (assumptions to surface).
Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended ARGUMENTS: line — counts as answers already given. Use it and skip whatever it covers; don't re-ask.
Arriving empty-handed? That works too. The skill opens with Box 1: what business problem are you trying to solve?
Example invocation: Fill a Lean UX canvas: leadership wants 'an AI chatbot' — underlying problem seems to be support ticket volume growing 3x faster than the team.
Key Concepts
What is the Lean UX Canvas?
The Lean UX Canvas (v2) is a structured, one-page template designed to help teams frame their work around a business problem, not a solution. It aligns cross-functional teams on:
- What problem exists (and why it matters now)
- What measurable outcomes indicate success
- Who we're solving for
- What assumptions we're making
- What we need to learn first
- What experiments will test those assumptions
Origin: Created by Jeff Gothelf, author of Lean UX (O'Reilly, 2013). Version 2 was released to improve clarity around business vs. user outcomes.
Key Insight: The canvas acts like an insurance policy—it exposes gaps in understanding before you build, ensuring you don't waste sprints on the wrong thing.
Canvas Structure (8 Boxes)
Layout (3 columns × 3 rows):
┌─────────────────────┬──────────────┬───────────────────────┐
│ 1. Business Problem │ │ 2. Business Outcomes │
│ │ │ │
├─────────────────────┤ 5. Solutions ├───────────────────────┤
│ 3. Users │ (tall box │ 4. User Outcomes │
│ │ spanning │ & Benefits │
├─────────────────────┤ rows 1-2) ├───────────────────────┤
│ 6. Hypotheses │──────────────┤ 8. Least Work / │
│ │ 7. Learn │ Experiments │
│ │ First │ │
└─────────────────────┴──────────────┴───────────────────────┘
The 8 Boxes (fill in this order):
- Business Problem — What changed in the world that created a problem worth solving?
- Business Outcomes — What measurable behavior change indicates success?
- Users — Which persona(s) should you focus on first?
- User Outcomes & Benefits — Why would users seek this? What benefit do they gain?
- Solutions — What features/initiatives might solve the problem and meet user needs?
- Hypotheses — Testable assumptions combining boxes 2-5 (If/Then format)
- What's Most Important to Learn First? — The single riskiest assumption right now
- What's the Least Work to Learn Next? — Smallest experiment to validate/invalidate that assumption
Why This Works
Problem-First, Not Solution-First: Starts with "what changed in the world?" not "we should build X." This prevents solution-driven thinking.
Assumption-Driven: Makes hypotheses explicit before building. Every discipline surfaces their risks (technical feasibility, user value, business viability).
Experiment-Focused: Tests assumptions before committing resources. Small experiments beat big bets.
Cross-Functional Alignment: Shared canvas creates common language. Everyone sees the same gaps in understanding.
Key Distinctions (Avoid Confusion)
Box 2 (Business Outcomes) vs. Box 4 (User Outcomes):
- Box 2: Measurable behavior change (retention rate, time on site, average order value)
- Box 4: Goals, benefits, emotions, empathy (save money, get promoted, spend time with family)
Box 2 is metrics. Box 4 is human.
Solutions (Box 5) Are Hypotheses, Not Commitments: List candidate solutions (features, policies, even business model shifts). You're not committing to build all of them—you're exploring the solution space.
Hypotheses (Box 6) Are Testable: Use the template: "We believe [business outcome] will be achieved if [user] attains [benefit] with [solution]." Each hypothesis focuses on one solution.
Anti-Patterns (What This Is NOT)
- Not a feature list: Solutions are ideas to test, not a backlog
- Not a project plan: Canvas frames learning, not delivery timelines
- Not a replacement for strategy: Canvas executes strategy; it doesn't create it
- Not a one-time exercise: Re-visit as you learn; update assumptions
When to Use This
✅ Use this when:
- Starting a new product initiative or feature
- Reframing an existing project (suspect you're building the wrong thing)
- Aligning cross-functional teams on assumptions and experiments
- Planning discovery sprints or MVPs
- Stakeholders are solution-driven ("we need to build X") and you need to expose assumptions
❌ Don't use this when:
- Problem and solution are already validated (move to execution)
- Tactical bug fixes or technical debt (no learning needed)
- Stakeholders have committed to a solution regardless of evidence (address alignment first)
Facilitation Source of Truth
Use workshop-facilitation as the default interaction protocol for this skill.
It defines:
- session heads-up + entry mode (Guided, Context dump, Best guess)
- one-question turns with plain-language prompts
- progress labels (for example, Context Qx/8 and Scoring Qx/5)
- interruption handling and pause/resume behavior
- numbered recommendations at decision points
- quick-select numbered response options for regular questions (include
Other (specify)when useful)
This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
Application
Use template.md for the full fill-in structure.
This interactive skill walks through 8 adaptive questions (one per canvas box) in sequence. At each step, the agent offers guidance, examples, and options to help you fill the box correctly.
Step 0: Gather Context
Agent asks:
Before we fill out the Lean UX Canvas, let's gather context. Please share:
Business Context:
- Stakeholder request, product brief, or initiative description
- Business metrics (revenue, churn, growth targets, KPIs)
- Strategic goals (OKRs, roadmap priorities)
User Context:
- Customer research, personas, JTBD insights
- User feedback, support tickets, churn reasons
- Competitor analysis, market trends
You can paste:
- PRD or product brief
- Stakeholder memo
- User research summary
- Just describe the initiative briefly
Question 1: Business Problem (Box 1)
Agent asks:
What problem does the business have that you are trying to solve?
Describe:
- Current state: How does the business deliver value today?
- What changed: Market shift, competitive threat, customer behavior change, new delivery channel
- Why it matters: Why isn't the current situation meeting expectations?
Good examples:
- "Our checkout conversion rate dropped 15% after mobile traffic surpassed desktop. Our checkout flow wasn't designed for mobile, and competitors have one-tap checkout."
- "Enterprise customers are churning after 6 months because our onboarding process requires 3+ weeks of manual configuration. Competitors offer self-service onboarding."
Bad examples (too vague):
- "We need to increase revenue" (no context on what changed)
- "Users want more features" (no business problem stated)
Agent offers 3 options:
- I'll describe the business problem — [Paste or write your description]
- Help me identify the business problem — [Agent asks follow-up questions: What changed? What metrics are affected? What are competitors doing?]
- I'm not sure what the business problem is — [Agent suggests starting with
skills/problem-statement/SKILL.mdorskills/problem-framing-canvas/SKILL.mdfirst]
User response: [Selection or description]
Agent validates: Does this describe what changed and why it creates a problem? If not, ask clarifying questions.
Question 2: Business Outcomes (Box 2)
Agent asks:
How will you know you solved the business problem? What will you measure?
Focus on measurable behavior change (leading indicators welcome). Ask yourself: "What will people be doing differently if the solution works?"
Examples of business outcomes:
- Increase mobile checkout conversion rate from 45% to 60%
- Reduce enterprise onboarding time from 3 weeks to 3 days
- Increase average order value from $50 to $75
- Reduce customer support tickets by 30%
- Increase free-to-paid conversion rate from 5% to 10%
Important: This is Box 2 (behavior change), not Box 4 (user benefits/empathy). Metrics go here. Emotions go in Box 4.
Agent offers 3 options:
- I have specific metrics in mind — [State your business outcomes]
- Help me define measurable outcomes — [Agent suggests metrics based on the business problem]
- I only have lagging indicators (revenue, profit) — [Agent helps identify leading indicators that predict those outcomes]
User response: [Selection or description]
Agent validates: Are these measurable? Observable? Do they indicate behavior change (not just "increase revenue")?
Question 3: Users (Box 3)
Agent asks:
What types (i.e., personas) of users and customers should you focus on first?
Consider:
- Who buys it?
- Who uses it?
- Who configures it?
- Who administers it?
Why this matters: Teams tend to shortcut here ("everyone"). The canvas wants a shared vision of the user—and it's not always "the customer."
Examples:
- "SMB owners (1-10 employees) in professional services (consultants, accountants, lawyers)"
- "Enterprise IT admins who configure SSO for 500+ employees"
- "Mobile-first millennials (25-35) who order takeout 3+ times per week"
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
