lean-ux-canvas

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: 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 /       │
│