foundation-lean-canvas

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Lean Canvas

精益画布

A lean canvas is a one-page business thesis that makes your assumptions about problem, customer, solution, and viability explicit and testable. Developed by Ash Maurya from Alex Osterwalder's Business Model Canvas, it is specifically adapted for startups and product teams operating under uncertainty. Nine interlocking blocks force you to articulate the whole picture at once so that changing one block's assumptions surfaces the ripple effect on the others.

This skill is a strategic hub, not a specialist tool. It produces the integrated one-page artifact and cross-links to deeper PM skills (

/problem-statement

/persona

/jtbd-canvas

/solution-brief

/competitive-analysis

/experiment-design

) for single-block depth when needed.

精益画布是一种单页商业假设工具，能让你关于问题、客户、解决方案和可行性的假设变得明确且可测试。它由Ash Maurya在Alex Osterwalder的商业模式画布基础上开发而成，专门为处于不确定性环境中的初创企业和产品团队量身定制。九个相互关联的模块会促使你一次性阐述完整的商业模式图景，这样当某个模块的假设发生变化时，就能凸显其对其他模块的连锁影响。

此技能是一个战略枢纽，而非专业工具。它生成一体化的单页成果，并可交叉链接到更深入的PM技能（

/problem-statement

、

/persona

、

/jtbd-canvas

、

/solution-brief

、

/competitive-analysis

、

/experiment-design

），以便在需要时深入单个模块。

Supported Modes

支持模式

```
content
```
(default) produces the nine-block canvas as structured markdown.
```
visual
```
produces the markdown canvas AND writes a self-contained, attractive
```
.html
```
file to disk using
```
references/html-template.html
```
as the layout scaffold. The HTML renders the canonical Maurya nine-block layout with polished typography, subtle per-column color accents, confidence badges per block, and print-ready A3 landscape styling. No external assets or CDN dependencies: the file opens correctly in a browser with no network access.

If mode is omitted, default to

content

and state that fallback explicitly.

```
content
```
（默认模式）生成结构化Markdown格式的九模块画布。
```
visual
```
模式生成Markdown格式的画布，并使用
```
references/html-template.html
```
作为布局框架，在磁盘上生成一个独立、美观的
```
.html
```
文件。该HTML文件会呈现标准的Maurya九模块布局，配有精致的排版、微妙的每列颜色点缀、每个模块的置信度徽章，以及适合打印的A3横向样式。无外部资源或CDN依赖：无需网络连接，文件即可在浏览器中正常打开。

如果未指定模式，则默认使用

content

模式，并明确说明这一 fallback 选择。

When to Use

适用场景

Framing a new product, feature, or business thesis on one page
Stress-testing an existing business by making implicit assumptions explicit
Comparing two or more strategic options side-by-side (run the skill once per option, then diff)
Onboarding new team members into the strategic thesis in a single artifact
Mid-phase reality check: does the thesis still hold given what we have learned?
Pairing with
```
/experiment-design
```
to prioritize which block assumptions to test first

在单页上构建新产品、新功能或新商业假设
通过将隐性假设显性化，对现有业务进行压力测试
并排比较两个或多个战略选项（针对每个选项运行一次该技能，然后对比差异）
用单个成果向新团队成员介绍战略假设
中期现状核查：根据已掌握的信息，原假设是否仍然成立？
与
```
/experiment-design
```
搭配使用，优先确定需要测试哪些模块的假设

When NOT to Use

不适用场景

You need deep research on a single block (persona detail, problem framing, competitive landscape). Use the specialist skill (
```
/persona
```
,
```
/problem-statement
```
,
```
/competitive-analysis
```
) instead.
You are drafting a PRD, user stories, or acceptance criteria. Use
```
/prd
```
,
```
/user-stories
```
,
```
/acceptance-criteria
```
; lean canvas is strategy, not specification.
You want to brainstorm solutions without a customer-problem anchor. Start with
```
/problem-statement
```
or
```
/jtbd-canvas
```
and return to lean canvas once the problem is framed.
You need a Business Model Canvas for an established enterprise with known customers and channels. Maurya designed lean canvas specifically for high-uncertainty early-stage ventures; a BMC is a better fit for steady-state analysis.

你需要对单个模块进行深入研究（如用户画像细节、问题构建、竞争格局）。请改用专业技能（
```
/persona
```
、
```
/problem-statement
```
、
```
/competitive-analysis
```
）。
你正在撰写PRD、用户故事或验收标准。请使用
```
/prd
```
、
```
/user-stories
```
、
```
/acceptance-criteria
```
；精益画布是战略工具，而非规范文档工具。
你想在没有客户-问题锚点的情况下 brainstorm 解决方案。请先从
```
/problem-statement
```
或
```
/jtbd-canvas
```
开始，待问题明确后再返回使用精益画布。
你需要为拥有已知客户和渠道的成熟企业使用商业模式画布。Maurya设计精益画布专门针对高不确定性的早期创业项目；对于稳态分析，商业模式画布（BMC）更合适。

Instructions

操作步骤

When asked to create a lean canvas, follow these steps:

Resolve mode and intent Determine whether the request is
```
content
```
or
```
visual
```
. If mode is omitted, default to
```
content
```
and state the fallback. Clarify the target: new product thesis, existing-business stress test, or side-by-side comparison of options. If unclear, ask once before proceeding.
Collect context and evidence Use user-provided context first: product name, market, target customer, any research already done, existing alternatives users are hiring today, known constraints. If evidence is thin, continue generation but mark gaps in the Evidence & Confidence section and calibrate per-block confidence accordingly. For existing businesses, distinguish current assumptions from validated data explicitly.
Fill the nine blocks in recommended order Fill in this order because each block's answer constrains the next. Do not skip ahead.

a. Problem . Top 3 problems, ranked by pain intensity and frequency. Include Existing Alternatives (what customers do today, including workarounds and non-consumption, not just direct competitors). b. Customer Segments . Who has these problems most acutely? Name Early Adopters as a distinct subset you will reach first. Early Adopters are more painful, more reachable, and more willing to try a new solution than the broader segment. c. Unique Value Proposition (UVP) . One sentence that makes a clear, testable promise. Include a High-Level Concept ("X for Y" analogy) that accelerates understanding for busy readers. d. Solution . Top 3 features that address the top 3 problems. Map 1:1 to the Problem block. Keep it concrete but do not over-engineer; this is a hypothesis, not a spec. e. Channels . Free and paid paths to your early adopters. Distinguish compounding channels (content, SEO, community) from traction-demonstrating channels (outbound, paid ads). f. Revenue Streams . Model (subscription, transaction, freemium, services), price point, expected volume, and LTV. Show the math so the revenue thesis is inspectable. g. Cost Structure . CAC, fixed vs variable, and the cost driver that shapes the growth curve. h. Key Metrics . The 3 to 5 leading indicators that signal whether the model is working. AARRR (Acquisition, Activation, Retention, Revenue, Referral) is a useful default frame. i. Unfair Advantage . What cannot be easily copied or bought. Empty is acceptable if framed as an open question; never fabricate a moat.
Apply evidence and confidence policy Tag each block with
```
High
```
,
```
Medium
```
, or
```
Low
```
confidence plus a one-line rationale. Populate the Evidence & Confidence section:
```
Validated
```
(assumptions with named sources),
```
Assumed
```
(no data yet),
```
Open Questions
```
(what you would need to learn to raise confidence),
```
Governance
```
(who owns the canvas and when it is revisited). A block marked "High" must name a specific evidence source, not a generic claim.
Render and write the visual file (visual mode only) Read
```
references/html-template.html
```
. It is a complete, self-contained HTML5 document using CSS Grid to express the canonical Maurya nine-block layout, with per-column color accents, confidence badges, and A3 landscape print styling. Fill every
```
{{PLACEHOLDER}}
```
token in the template with content from the markdown canvas:
- ```
{{PRODUCT_NAME}}
```
  ,
```
{{CREATED_DATE}}
```
  ,
```
{{PURPOSE}}
```
  ,
```
{{OVERALL_CONFIDENCE}}
```
  from the canvas header.
- ```
{{PROBLEM_CONTENT}}
```
  ,
```
{{EXISTING_ALTERNATIVES}}
```
  ,
```
{{SOLUTION_CONTENT}}
```
  ,
```
{{UVP_CONTENT}}
```
  ,
```
{{HIGH_LEVEL_CONCEPT}}
```
  ,
```
{{ADVANTAGE_CONTENT}}
```
  ,
```
{{CUSTOMER_CONTENT}}
```
  ,
```
{{EARLY_ADOPTERS}}
```
  ,
```
{{METRICS_CONTENT}}
```
  ,
```
{{CHANNELS_CONTENT}}
```
  ,
```
{{COST_CONTENT}}
```
  ,
```
{{REVENUE_CONTENT}}
```
  from the respective blocks. Use a
```
<ul><li>
```
  list for multi-item blocks; keep cell content concise (one-line summaries, not the full markdown detail) so the visual stays scannable.
- ```
{{CONF_PROBLEM}}
```
  ,
```
{{CONF_SOLUTION}}
```
  ,
```
{{CONF_UVP}}
```
  ,
```
{{CONF_ADVANTAGE}}
```
  ,
```
{{CONF_CUSTOMER}}
```
  ,
```
{{CONF_METRICS}}
```
  ,
```
{{CONF_CHANNELS}}
```
  ,
```
{{CONF_COST}}
```
  ,
```
{{CONF_REVENUE}}
```
  with the single letter
```
H
```
  ,
```
M
```
  , or
```
L
```
  matching each block's confidence tag. Each appears twice in the template (once in the class attribute for styling, once as visible text).
- ```
{{VALIDATED_COUNT}}
```
  ,
```
{{ASSUMED_COUNT}}
```
  ,
```
{{OPEN_QUESTIONS_COUNT}}
```
  ,
```
{{OWNER}}
```
  ,
```
{{NEXT_REVIEW}}
```
  in the footer evidence strip. Write the filled document to disk at a user-specified path, or default to
```
./lean-canvas-{slug}.html
```
  in the current working directory (where
```
{slug}
```
  is the product name lowercased with non-alphanumeric characters replaced by hyphens). Do not introduce external font or CSS links; the template is intentionally self-contained. In content mode, skip this step entirely.
Finalize for direct use Remove all template guidance blockquotes (
```
>
```
notes) from the final artifact. Verify UVP is decision-changing and testable, not marketing fluff. Confirm Early Adopters is a distinct subset (not a restatement of Customer Segments). Confirm Solution block items map 1:1 to Problem block items.

当被要求创建精益画布时，请遵循以下步骤：

确定模式与意图 判断请求是使用
```
content
```
还是
```
visual
```
模式。如果未指定模式，则默认使用
```
content
```
模式，并说明这一 fallback 选择。明确目标：新产品假设、现有业务压力测试，还是选项的并排比较。如果不明确，在继续前询问一次。
收集背景与证据 优先使用用户提供的背景信息：产品名称、市场、目标客户、已完成的研究、当前用户选择的替代方案、已知约束条件。如果证据不足，继续生成内容，但在“证据与置信度”部分标记空白，并相应调整每个模块的置信度。对于现有业务，要明确区分当前假设与已验证的数据。
按推荐顺序填充九个模块 按以下顺序填充，因为每个模块的答案会约束下一个模块的内容。请勿跳过。

a. 问题：按痛苦程度和频率排序的前3个问题。包括现有替代方案（客户当前的做法，包括变通方法和非消费行为，而非仅直接竞争对手）。 b. 客户细分：哪些群体受这些问题的影响最严重？将早期采用者（Early Adopters）列为你首先接触的独特子集。早期采用者比更广泛的用户群体更痛苦、更容易触达，也更愿意尝试新解决方案。 c. 独特价值主张（UVP）：一句清晰、可测试的承诺。包含一个高水平概念（“为Y打造的X”类比），以便忙碌的读者快速理解。 d. 解决方案：针对前3个问题的前3个功能。与“问题”模块一一对应。内容要具体但不要过度设计；这是一个假设，而非规范。 e. 渠道：触达早期采用者的免费和付费路径。区分复利渠道（内容、SEO、社区）与展示牵引力的渠道（ outbound、付费广告）。 f. 收入流：模式（订阅、交易、免费增值、服务）、价格点、预期数量和LTV。列出计算过程，以便收入假设可被核查。 g. 成本结构：CAC、固定成本与可变成本，以及影响增长曲线的成本驱动因素。 h. 关键指标：3到5个能表明模型是否有效的领先指标。AARRR（获客、激活、留存、收入、推荐）是一个实用的默认框架。 i. 不公平优势：无法轻易复制或购买的优势。如果是开放性问题，留空也可以；切勿编造护城河。
应用证据与置信度规则 为每个模块标记
```
High
```
（高）、
```
Medium
```
（中）或
```
Low
```
（低）置信度，并附上一行理由。填充“证据与置信度”部分：
```
Validated
```
（有明确来源的假设）、
```
Assumed
```
（尚无数据）、
```
Open Questions
```
（提升置信度所需了解的内容）、
```
Governance
```
（画布所有者及复查时间）。标记为“High”的模块必须指明具体的证据来源，而非泛泛而谈。
渲染并写入可视化文件（仅visual模式） 读取
```
references/html-template.html
```
。这是一个完整的独立HTML5文档，使用CSS Grid呈现标准的Maurya九模块布局，配有每列颜色点缀、置信度徽章和A3横向打印样式。将模板中的每个
```
{{PLACEHOLDER}}
```
标记替换为Markdown画布中的内容：
- 画布标题中的
```
{{PRODUCT_NAME}}
```
  、
```
{{CREATED_DATE}}
```
  、
```
{{PURPOSE}}
```
  、
```
{{OVERALL_CONFIDENCE}}
```
  。
- 各个模块中的
```
{{PROBLEM_CONTENT}}
```
  、
```
{{EXISTING_ALTERNATIVES}}
```
  、
```
{{SOLUTION_CONTENT}}
```
  、
```
{{UVP_CONTENT}}
```
  、
```
{{HIGH_LEVEL_CONCEPT}}
```
  、
```
{{ADVANTAGE_CONTENT}}
```
  、
```
{{CUSTOMER_CONTENT}}
```
  、
```
{{EARLY_ADOPTERS}}
```
  、
```
{{METRICS_CONTENT}}
```
  、
```
{{CHANNELS_CONTENT}}
```
  、
```
{{COST_CONTENT}}
```
  、
```
{{REVENUE_CONTENT}}
```
  。多项目模块使用
```
<ul><li>
```
  列表；保持单元格内容简洁（单行摘要，而非完整的Markdown细节），以便可视化内容易于扫描。
- ```
{{CONF_PROBLEM}}
```
  、
```
{{CONF_SOLUTION}}
```
  、
```
{{CONF_UVP}}
```
  、
```
{{CONF_ADVANTAGE}}
```
  、
```
{{CONF_CUSTOMER}}
```
  、
```
{{CONF_METRICS}}
```
  、
```
{{CONF_CHANNELS}}
```
  、
```
{{CONF_COST}}
```
  、
```
{{CONF_REVENUE}}
```
  使用与每个模块置信度标签对应的单个字母
```
H
```
  、
```
M
```
  或
```
L
```
  。每个标记在模板中出现两次（一次在class属性中用于样式，一次作为可见文本）。
- 页脚证据栏中的
```
{{VALIDATED_COUNT}}
```
  、
```
{{ASSUMED_COUNT}}
```
  、
```
{{OPEN_QUESTIONS_COUNT}}
```
  、
```
{{OWNER}}
```
  、
```
{{NEXT_REVIEW}}
```
  。将填充后的文档写入用户指定路径，或默认写入当前工作目录下的
```
./lean-canvas-{slug}.html
```
  （其中
```
{slug}
```
  是产品名称小写，非字母数字字符替换为连字符）。请勿引入外部字体或CSS链接；模板特意设计为独立式。在content模式下，完全跳过此步骤。
优化以便直接使用 从最终成果中移除所有模板指导引用块（
```
>
```
注释）。验证UVP具有决策价值且可测试，而非营销空话。确认早期采用者是一个独特的子集（而非客户细分的重复表述）。确认解决方案模块的内容与问题模块一一对应。

Output Contract (v1.0.0)

输出协议（v1.0.0）

All nine blocks present in the canonical order (Problem, Customer Segments, UVP, Solution, Channels, Revenue Streams, Cost Structure, Key Metrics, Unfair Advantage)
Each block contains content, a confidence tag (
```
High|Medium|Low
```
), and a one-line rationale
Evidence & Confidence section present with
```
Validated
```
,
```
Assumed
```
,
```
Open Questions
```
, and
```
Governance
```
subsections populated (even if a subsection is intentionally empty, mark it "None" rather than removing it)
Content mode: the markdown canvas is the single output.
Visual mode: in addition to the markdown canvas, a self-contained HTML file is written to disk at
```
./lean-canvas-{slug}.html
```
(or a user-specified path). The HTML is derived from
```
references/html-template.html
```
with every placeholder filled and no external dependencies. After writing, report the file path to the user.
Foundation classification: no
```
phase:
```
field in frontmatter; uses
```
classification: foundation
```

所有九个模块均按标准顺序呈现（问题、客户细分、UVP、解决方案、渠道、收入流、成本结构、关键指标、不公平优势）
每个模块包含内容、置信度标签（
```
High|Medium|Low
```
）和一行理由
包含“证据与置信度”部分，其中
```
Validated
```
、
```
Assumed
```
、
```
Open Questions
```
和
```
Governance
```
子部分已填充（即使某个子部分有意留空，也要标记为“无”，而非删除）
Content模式：仅输出Markdown画布。
Visual模式：除Markdown画布外，还会在
```
./lean-canvas-{slug}.html
```
（或用户指定路径）生成一个独立的HTML文件。该HTML文件基于
```
references/html-template.html
```
，所有占位符均已替换，无外部依赖。写入完成后，向用户报告文件路径。
基础分类：前置元数据中无
```
phase:
```
字段；使用
```
classification: foundation
```

Quality Checklist

质量检查清单

Before finalizing, verify:

All nine blocks are present and ordered correctly (Problem, Customer Segments, UVP, Solution, Channels, Revenue Streams, Cost Structure, Key Metrics, Unfair Advantage)
Problem lists the top 3 problems AND includes an Existing Alternatives subsection
Customer Segments names Early Adopters as a distinct subset, not a restatement
UVP is one sentence AND includes a High-Level Concept analogy ("X for Y")
Solution maps 1:1 to the Problem block (top 3 features for top 3 problems)
Channels distinguishes compounding from traction-demonstrating paths
Revenue Streams shows the math (model, price, volume, LTV)
Cost Structure names CAC and identifies the cost driver
Key Metrics lists 3 to 5 leading indicators
Unfair Advantage is either specific OR explicitly flagged as an open question
Each block has a confidence tag (
```
High|Medium|Low
```
) with a one-line rationale
Evidence & Confidence section has all four subsections populated
Template guidance blockquotes are removed from the final artifact
Visual mode: the generated
```
.html
```
file opens successfully in a browser with no network access; every
```
{{PLACEHOLDER}}
```
has been replaced; confidence badges render with correct color; the canonical Maurya nine-block arrangement is visible; print-preview at A3 landscape fits the canvas on one page;
```
role="img"
```
and
```
aria-label
```
are present; the file path is reported back to the user
Content mode: no
```
.html
```
file is written and no visual section appears in the markdown

最终确定前，请验证：

所有九个模块均存在且顺序正确（问题、客户细分、UVP、解决方案、渠道、收入流、成本结构、关键指标、不公平优势）
问题模块列出了前3个问题，并包含“现有替代方案”子部分
客户细分模块将早期采用者列为独特子集，而非重复表述
UVP为一句话，并包含高水平概念类比（“为Y打造的X”）
解决方案与问题模块一一对应（前3个功能对应前3个问题）
渠道模块区分了复利渠道与展示牵引力的路径
收入流模块列出了计算过程（模式、价格、数量、LTV）
成本结构模块指明了CAC和成本驱动因素
关键指标模块列出了3到5个领先指标
不公平优势要么具体明确，要么明确标记为开放性问题
每个模块都有置信度标签（
```
High|Medium|Low
```
）和一行理由
“证据与置信度”部分的四个子部分均已填充
最终成果中已移除模板指导引用块
Visual模式：生成的
```
.html
```
文件无需网络即可在浏览器中成功打开；所有
```
{{PLACEHOLDER}}
```
均已替换；置信度徽章颜色显示正确；可见标准的Maurya九模块布局；A3横向打印预览可将画布放在一页上；包含
```
role="img"
```
和
```
aria-label
```
；已向用户报告文件路径
Content模式：未生成
```
.html
```
文件，Markdown中无可视化部分

Examples

示例

See

references/EXAMPLE.md

for a completed lean canvas in content mode with a realistic B2B SaaS scenario. The HTML template scaffold for visual mode lives at

references/html-template.html

查看

references/EXAMPLE.md

获取content模式下完成的精益画布示例，基于真实的B2B SaaS场景。Visual模式的HTML模板框架位于

references/html-template.html

。",