Lean UX Canvas
beta · Family discovery-docs · Phase discover · Sizes lean · ~5,200 tokens
The one-page canvas that frames one initiative’s business problem, the outcomes the business wants, the users affected, the outcomes those users want, and candidate solutions, then turns those links into testable hypotheses and names what to learn first and the least work that will learn it, before anyone commits to building.
An operator card. Read it before a first pass and again every time the team loops back through it.
The reasoning behind every rule here lives in
lean-ux-canvas_companion.md.
When to use this document
Section titled “When to use this document”Open a canvas when an initiative is about to start and nobody has yet written down the business problem, the outcomes, the users, or a candidate solution for it. Gothelf’s own walkthrough starts here, before any other box is touched, and the book calls the canvas “a great way to start an initiative,” filled by the whole team with stakeholders and clients joining “as much as possible.” A first pass rarely takes less than half a day, and some teams spread it across a series of meetings over a couple of weeks; either is normal, and the spread reflects the initiative’s own scope, not disagreement about the method.
Treat the canvas as a facilitation tool first. Its originators call it exactly that, “a facilitation tool for cross-functional teams designed to create a customer-centric conversation,” and the filled page is the record of that conversation, not the thing of value on its own. If no cross-functional conversation is happening, a page of boxes filled in alone by one person has not done this document’s job, whatever it says.
Is this the right document at all?
Section titled “Is this the right document at all?”| If the real question is | Write this instead |
|---|---|
| Which problem is worth solving, before anyone names a solution? | problem-statement |
| We have chosen one concept; who will design it? | design-brief |
| We need to plan one test of one hypothesis, with variants, allocation, and a decision rule | experiment-design-doc |
| Where is the whole product going, over years? | product-vision |
| Who exactly are we building for, researched rather than guessed? | user-persona |
| What does the whole business look like: channels, revenue, cost structure? | lean-canvas, Ash Maurya’s Lean Canvas; this canvas asks nothing about revenue or cost (2026-10-30: this cell said the bundle was planned and not yet built; it is built now) |
When NOT to use this document
Section titled “When NOT to use this document”- The problem is already chosen and so is the concept. A canvas names candidate solutions in Box 5 and turns them into hypotheses in Box 6; it has not chosen one. Once a concept is chosen, hand it to the people who will design it in a design brief instead.
- The team already knows exactly which test it is running. Box 8 only sketches the shape of a test: the smallest thing that would learn whether the riskiest assumption holds. It does not plan one, with variants, an allocation, metrics, and a decision rule. If the team already knows those, it needs an experiment-design-doc, not another pass of this canvas.
- Nobody from outside the writer will read or discuss it. The canvas earns its name as “a facilitation tool,” and its own book lists communicating the work “broadly beyond the team” among what a filled canvas is for. A canvas written and filed by one person, with no conversation and no wider reader, has skipped the half of its job a document alone cannot do.
- The initiative is actually the whole product’s direction for years, not one initiative for weeks. That scale is a product vision’s job.
Picking a variant
Section titled “Picking a variant”There is nothing to pick. This bundle ships one size, lean, with no full variant: Gothelf
publishes the canvas as a single one-page shape in both the 2019 and 2024 versions, and this
research found no source that splits a short form of the canvas from a longer one. Do not invent a
full-size version by adding sections the originators never wrote; a team that needs more structure
than the canvas itself offers is better served by experiment-design-doc once Box 8’s smallest
experiment becomes a real test, or by design-brief once the team has chosen a concept, than by an
invented longer canvas. See the companion’s Variants and sizing section.
The rubric
Section titled “The rubric”Below 12 out of 18, the canvas reads as filled-in homework rather than the record of a conversation. A reader cannot tell what the team actually believes about any box, and the facilitator ends up walking every reader through it live instead of letting the page carry the conversation on its own.
Each row’s test is the same: could someone satisfy this cell without actually improving the box? If a cell can be cleared by adding words rather than evidence, it is written wrong, and no row here is scored by counting items.
| # | Criterion | 0 | 1 | 2 |
|---|---|---|---|---|
| 1 | Problem, not a solution | The box names a feature or a solution, or no evidence is given for what changed | A problem is named, but you cannot point to the evidence behind it, or it never closes on a how-might-we question | You can point at the sentence naming what changed, the evidence that it is real, and the closing how-might-we question |
| 2 | Outcome is a behavior | A revenue figure, an output count, or a feeling, with no stated magnitude | A behavior is named, but with no stated magnitude or timeframe, or it reads as a feeling rather than a measured change | You can state who does what, by how much, and by when, as a measured behavior change, not a number on a report or a feeling |
| 3 | Users named specifically | Only “users” or a single buyer is named | A group is named, but a stranger to the project could not picture a member of it, or only the buyer appears | You can name a group a stranger could picture, and it includes anyone who configures the product or is affected by it beyond the buyer |
| 4 | A distinct user outcome | The user outcome restates the business outcome’s measured behavior in different words | A user’s own reason is attempted, but it still reads as a measurable, business-shaped target | You can point to a reason stated in the user’s own language, distinct from Box 2’s measured behavior, even if it is not itself measurable |
| 5 | Genuinely different candidates | A single solution appears, with no non-technical option | Several candidates appear, but they are variations of one software feature | You can point to candidates that take different approaches to the problem, one of them a non-technical option that is not a thinner version of a software one |
| 6 | One feature per hypothesis | A row spans more than one feature, or a slot (outcome, user, benefit, feature) is missing | One hypothesis per row, but a slot is vague enough that you could not design a test from it alone | Each row names the business outcome, the user, the benefit, and exactly one feature, specific enough to test on its own |
| 7 | One named riskiest assumption | A list of risks appears, with no single one chosen | An assumption is implied, but several are named with no stated priority among them | You can point to one named assumption, and the sentence states it as the one most important to learn right now |
| 8 | Learning, not a release | The box describes building a smaller version of the eventual product | An activity is named, but you cannot tell whether it tests the named assumption or only previews the feature | You can point to a specific test that would prove or disprove the named assumption, with no feature actually built |
| 9 | Dated revision outcomes | No dated row exists, or a row states only that something was “tested,” with no outcome | A dated row exists, but you cannot tell whether the assumption held or which boxes changed as a result | You can point to a dated row naming the assumption tested, whether it held, and which boxes changed; once the canvas stops changing, a successor document is named |
Anti-patterns
Section titled “Anti-patterns”Starting from a solution rather than a problem. Box 1 asks what changed in the world, not what to build. A community pitfalls list puts this first among six recurring failures, and the canvas’s own structure makes it visible immediately: nothing in Box 1 should read like Box 5.
Writing a vague business outcome. A revenue figure, an output count, or a sentiment in Box 2 fails Gothelf’s own test that an outcome is a measured change in human behavior. A vague outcome in Box 2 also breaks Box 6, since the hypotheses table pulls its business-outcome slot straight from this box.
Naming a user segment too broadly to act on. “Users” or “fleet managers” cannot be pictured by a stranger to the project, and Gothelf tightened Box 3’s wording in 2019 specifically because teams were taking this shortcut. Naming only the buyer and skipping everyone who configures or is affected by the product is the same failure in a different shape.
Confusing the business outcomes box with the user outcomes box. This is the canvas’s best-documented point of confusion: Gothelf names it directly, and an independent podcast discussion of the same revision reports that Box 4 was the part of the canvas with the most confusion. Business outcomes are measured behavior; user outcomes are why users seek the product out in the first place, and they are often not measurable at all. Writing one box’s content into the other is the confusion Gothelf rewrote Box 4 to remove, and a community pitfalls list names it as one of its six recurring failures.
Filling the solutions box with only one idea. Box 5 was explicitly widened in 2019 to admit new systems, business models, and non-technical solutions, not only software features. A single idea here undercuts that widening before the team ever reaches Box 6.
Bundling more than one feature into a single hypothesis. The canvas’s own rule is one feature per hypothesis; a sentence spanning several features cannot be tested cleanly, because a result would not say which feature caused it.
Skipping the experiment step entirely. A canvas that reaches Box 6 and stops, with no riskiest assumption named in Box 7 and no smallest test designed in Box 8, has stopped short of the reason the canvas exists: to find out whether the hypotheses are true before anyone commits to building.
Leaving the revisions section blank because a first pass feels finished. The canvas is revised while its experiments run: after Box 8 returns a result, the team asks Box 7’s question again, and evidence can even send the team back to Box 1. A canvas revised with no record of what changed cannot show what the team actually learned, which is exactly why this section exists.
Before you share it
Section titled “Before you share it”Self-grade against the rubric above, then delete every HTML comment; they are guidance, not content. Remember that a canvas is not finished when you first fill it. It stays open while the initiative’s experiments run, and it is finished only when the team commits to building, changes course, or stops the initiative, at which point the final row of the revisions section should name what takes over.
The artifacts
Section titled “The artifacts”lean-ux-canvas_template-lean.md · ~5,200 tokens
---title: "{{initiative_name}} Lean UX Canvas"initiative_name: "{{initiative_name}}"facilitator: "{{facilitator}}"status: "{{status}}"date: "{{date}}"iteration: "{{iteration}}"doc_type: lean-ux-canvassize: leansource_template: lean-ux-canvassource_template_version: 0.1.0---
<!--LEAN UX CANVAS. This bundle ships one size, deliberately: Gothelf publishes the canvas as a singleone-page shape in both the 2019 and 2024 versions, and this research found no source that splits ashort form of the canvas from a longer one. See lean-ux-canvas_companion.md section 4 (Variants andsizing).
WHAT THIS DOCUMENT IS, AND IS NOT. A Lean UX Canvas frames one initiative's business problem, theoutcomes the business wants, the users affected, the outcomes those users want, and candidatesolutions, then turns those links into testable hypotheses. It closes on the single most importantthing the team needs to learn right now and the smallest piece of work that would learn it. It is afacilitation tool first: its originators call it a facilitation tool for cross-functional teamsdesigned to create a customer-centric conversation, and the filled page is the record of thatconversation, not the thing of value by itself. See lean-ux-canvas_companion.md section 1(Orientation).
It is NOT a problem statement (that names which problem is worth solving, before anyone names asolution; this canvas names candidate solutions in Box 5 and links them to outcomes in Box 6 - aproblem statement, where one exists, can feed Box 1, but nothing this research read makes that arule). It is NOT an experiment-design-doc (that plans one test of one hypothesis, with variants,allocation, metrics and a decision rule; this canvas only picks which hypothesis to test next andsketches the least work in a single box, Box 8). It is NOT a design-brief (that hands one chosenconcept to the people who will design it; this canvas has not chosen a concept, only namedcandidates in Box 5). It is NOT a product-vision (that states a whole product's direction foryears; this canvas frames one initiative for weeks). It is NOT a user-persona (Box 3 names theusers in a line and may point to a persona; it is not the researched portrait itself). It is NOTAsh Maurya's lean-canvas (that models a whole business - channels, revenue, cost structure - whilethis canvas frames one initiative's hypotheses and asks nothing about revenue or cost). Where thiscanvas sits relative to each of these neighbors is this library's own POSITION in places, not asourced sequence; see lean-ux-canvas_companion.md section 8 (Relationships to other artifacts) forwhich lines are sourced and which are not.
THIS DOCUMENT IS REVISED WHILE THE INITIATIVE'S EXPERIMENTS RUN. After the smallest experiment inBox 8 returns a result, the team asks Box 7's question again, and the evidence can even send theteam back to Box 1 if it shows the wrong problem, the wrong audience, or the wrong measure ofsuccess was in play. It is finished when the team commits to building, changes course, or stops theinitiative, not on a calendar. Box 9 below exists to keep that history visible, rather than lettingthe canvas go stale with no record of what changed. See lean-ux-canvas_companion.md section 3 (Box9: Revisions and What Takes Over).
HOW TO FILL THIS IN1. Read the comment under each heading: WHAT it wants, WHY it matters (with a pointer into lean-ux-canvas_companion.md), guiding questions to ASK, a GOOD and a WEAK example, and the TRAP to avoid. For the two table sections, PRIORITY explains how to use the table and ROW HINT says what a good row contains.2. Fill the boxes roughly in the order below on a first pass: Gothelf's own walkthrough starts at Box 1, and Box 6 cannot be written before Boxes 2 through 5 exist. Once the canvas is underway, any box can be revisited on its own.3. If a section does not apply to this initiative, write "N/A" and one line of why, rather than deleting it.4. This canvas is not finished when you first fill it; it is revised as experiments return results (see above). Before you first share a pass: self-grade against lean-ux-canvas_guide.md, then DELETE every HTML comment. They are guidance, not content.-->
# {{initiative_name}} Lean UX Canvas
## Business Problem
<!-- WHAT What changed in the world and why it makes this a problem worth the organization's attention right now, closing on a "how might we" question. Not a solution or a feature idea. WHY Gothelf's own walkthrough of how to use the canvas starts here, naming the business problem statement before touching any other box. The box's closing "how might we" question also supplies the objective half of an OKR built from the canvas, with Box 2 supplying the key results half. Deep dive: lean-ux-canvas_companion.md section 3 (Box 1) and section 8 (Relationships to other artifacts). ASK What changed in the world that makes this worth the organization's attention now? What evidence shows this is a real problem rather than an assumption? If you ended this statement with "how might we," what question would it ask? GOOD "Dispatchers at single-site depots phone every driver each morning to confirm status, after three depots reported drivers marked absent in error last quarter. How might we confirm a driver's status without a phone call?" (names what changed, cites evidence, ends on a how-might-we question) WEAK "We should build an automated check-in feature." (a solution, not a problem, and no evidence of what changed) TRAP Writing a solution or a feature idea into this box instead of the problem it would solve. That is Box 5's job, not Box 1's, and starting from a solution rather than a problem is the first of a community skill file's named pitfalls. -->
{{business_problem_statement}}
## Business Outcomes
<!-- WHAT The measurable change in human behavior the business wants, stated as who does what, by how much. Not a revenue figure or an output count. WHY Gothelf defines a business outcome as a measure of human behavior, not a number on a report, and has separately called this box perhaps the most critical one in the whole canvas, because its outcomes become the success criteria Box 6's hypotheses are later tested against. The 2024 prompt made that discipline more explicit by asking for the same who-does-what-by-how-much format his and Seiden's OKR book uses. Deep dive: lean-ux-canvas_companion.md section 3 (Box 2) and section 6 (Business outcomes against user outcomes). ASK What will people do differently if this business problem is solved? Can you state it as who does what, by how much, and by when? Is this a behavior you can actually measure, not a sentiment or a revenue figure? GOOD "Dispatchers who use the check-in feature make 80% fewer manual confirmation calls within 60 days of rollout." (a measured behavior, a magnitude, a timeframe) WEAK "Dispatchers feel more confident in their fleet's status." (a feeling, not a measured change in behavior) TRAP Writing a revenue figure or an output count here instead of a behavior change. Confusing this box with Box 4 is the canvas's best-documented point of confusion, and Gothelf's own revision of both boxes exists to draw that line. -->
{{business_outcome}}
## Users
<!-- WHAT Who the team is solving for, named specifically enough that someone unfamiliar with the initiative could picture them, including anyone who configures the product or is affected by it, not only the person who buys or approves it. WHY The 2024 wording widens this box past paying customers to anyone who configures the product or is affected by its use, and Gothelf tightened the box in 2019 because teams were taking a shortcut on it, treating it too casually. The book's own practice fills this box with proto-personas where the team has them. Deep dive: lean-ux-canvas_companion.md section 3 (Box 3). ASK Who specifically uses or is affected by this, beyond whoever buys or approves it? Could someone outside the team picture this user from your description? Does a researched persona already exist that this box should point to, rather than inventing a thinner sketch for the canvas? GOOD "Dispatchers at single-site depots who coordinate 15-40 drivers each morning, and the drivers themselves, who are affected by the check-in process even though they do not choose it." (names more than one affected group, specific enough to picture) WEAK "Fleet managers." (too broad to act on, and skips the affected drivers entirely) TRAP Naming only the buyer and skipping everyone else who configures or is affected by the product. Treating this box as a formality is exactly the shortcut Gothelf tightened the wording to stop. -->
{{users}}
## User Outcomes and Benefits
<!-- WHAT What users want to achieve and how they want to feel, in language a user would recognize, not a restatement of the business outcome in different words. The 2024 prompt adds jobs-to-be-done language. WHY Gothelf names this box as the part of the canvas with the most confusion, and resolves it directly against Box 2: business outcomes are measured behavior, while user outcomes are the reasons users seek out a product in the first place, often not measurable goals at all but intangible states of being. Deep dive: lean-ux-canvas_companion.md section 3 (Box 4) and section 6, which also records a minority "ethics box" reading that Gothelf's own pages do not use. ASK Why does this user actually seek this out, independent of what the business wants from them? What job are they trying to get done? How do they want to feel afterward, in language they would recognize? GOOD "Dispatchers want to trust that a driver's status is accurate without double-checking it themselves, so they can start the day's routing without delay." (a reason to seek the product out, in the user's own language, distinct from the business's measured behavior) WEAK "Dispatchers make 80% fewer calls." (this restates Box 2's business outcome, not a user outcome) TRAP Writing the business outcome again in different words. Box 2 against Box 4 is the canvas's best-documented point of confusion, and filling either box with language that belongs in the other is, by Gothelf's own account, the single most common way a team's canvas becomes hard for anyone else to read. -->
{{user_outcomes_and_benefits}}
## Solutions
<!-- WHAT Candidate solutions, listed as widely as the box invites, including at least one non-technical option, before narrowing to anything specific. WHY The 2019 widening explicitly admits new systems, business models, and non-technical solutions, not only software features, and Gothelf's own guidance calls for ideas that can be big, small, innovative, or even a little unconventional. Naming a solution here does not commit the team to building it. Deep dive: lean-ux-canvas_companion.md section 3 (Box 5). ASK What candidate solutions, technical and non-technical, could address the user and business outcomes above? Have you listed more than one, or stopped at the first idea? Does at least one candidate not involve building new software? GOOD "An automated SMS check-in; a geofence that logs arrival automatically; or, non-technically, a shared paper log the depot's shift lead photographs each morning." (more than one candidate, including a non-technical option) WEAK "Build an automated check-in app." (a single idea; the box's own widening to several, non-technical candidates goes unused) TRAP Stopping at one solution. A single idea in this box undercuts the box's own 2019 widening and is one of six pitfalls a community skill file names. -->
{{candidate_solutions}}
## Hypotheses
<!-- WHAT A table, one row per candidate hypothesis, each combining the business outcome, the user, the benefit, and the feature into a single sentence. WHY This box combines Boxes 2 through 5 into one sentence carrying four slots: the business outcome, the user, the benefit the user attains, and the feature or solution that attains it. Each hypothesis should address exactly one feature; a hypothesis spanning several cannot be tested cleanly. Deep dive: lean-ux-canvas_companion.md section 3 (Box 6) and section 7 (Anti-patterns and failure modes). ASK For each candidate solution, what single hypothesis sentence links it to one business outcome and one user benefit? Does each row name exactly one feature, or has more than one been bundled into the same sentence? PRIORITY One row per feature, never one row bundling several features into a single sentence; a bundled hypothesis cannot be tested cleanly. Rows are candidates, not ranked by this table; Box 7 is where the team picks one to test first. ROW HINT A good row names the business outcome, the user, the benefit, and exactly one feature. A weak row omits a slot, or bundles two features into one sentence. GOOD | H-01 | We believe 80% fewer manual confirmation calls will follow if dispatchers get confidence in driver status from an automated SMS check-in. | WEAK | H-01 | We believe check-ins will improve if we build the SMS feature and the geofence feature. | (two features bundled into one sentence that cannot be tested cleanly) TRAP Bundling more than one feature into a single hypothesis. The canvas's own rule is one feature per hypothesis, and a sentence spanning several features cannot be tested cleanly. -->
| ID | Hypothesis (business outcome, user, benefit, one feature) ||---|---|| {{hypothesis_id}} | We believe {{hypothesis_business_outcome}} will follow if {{hypothesis_user}} gets {{hypothesis_benefit}} from {{hypothesis_feature}}. |
## What We Need to Learn First
<!-- WHAT One hypothesis chosen from the table above, the ways it might fail, and the single riskiest assumption behind it. Not a list of everything that could go wrong. WHY Gothelf is pointed about scope here: the job is not to list every risk a hypothesis carries, but to identify the one thing that matters most to learn right now. In a hypothesis's early stages, the guidance favors risks to value over risks to feasibility. This box is revisited, not answered once: after an experiment from Box 8 returns, the team asks this box's question again. Deep dive: lean-ux-canvas_companion.md section 3 (Box 7). ASK Of all the ways this hypothesis could fail, which one matters most to learn about right now? Is this risk about whether users value the outcome, or only about whether the team can build it? After the last experiment returned, has this answer changed? GOOD "The riskiest assumption behind the SMS check-in hypothesis is that dispatchers would actually trust a text reply over a phone call, not whether the SMS platform is technically feasible." (one named assumption, about value rather than feasibility) WEAK "There are a lot of risks: cost, timeline, driver adoption, SMS reliability, and whether dispatchers like it." (a list, not a single named priority) TRAP Listing every risk a hypothesis carries instead of naming the one thing most important to learn right now. That is exactly the shortcut Gothelf's own guidance warns against. -->
{{riskiest_assumption}}
## The Least Work to Learn It
<!-- WHAT The smallest experiment that would show whether the riskiest assumption named above is true or false. Not a smaller version of the finished product. WHY "MVP" in this context means a small and fast way of learning something, not a stripped-down release meant to ship. This box sketches the shape of a test; it does not plan one in the detail an experiment-design-doc would. Deep dive: lean-ux-canvas_companion.md section 3 (Box 8) and section 8 (Relationships to other artifacts). ASK What is the cheapest, fastest way to learn whether the assumption above holds? Does this design actually test the assumption, or does it quietly become a smaller version of the final feature? If this needs a full test plan with variants and a decision rule, does experiment-design-doc need to take over from here? GOOD "Ask five dispatchers to try replying to one manual SMS check-in for a week, with no app built, and track how many replies come back and whether dispatchers say they would trust it." (a fast way of learning, not a smaller release) WEAK "Build a stripped-down version of the SMS app with only the core check-in feature." (a smaller release, not a fast way of learning) TRAP Designing a smaller version of the eventual product instead of the fastest way to learn the answer. The originators are explicit that MVP here means a way of learning, not a release. -->
{{smallest_experiment}}
## Revisions and What Takes Over
<!-- WHAT A dated row for each pass through the two boxes above, recording what was learned, whether the assumption held, and which boxes changed as a result. Then, once the canvas stops changing, the document that takes over. WHY This section is this library's own addition. Its dated, iterative half is sourced: the canvas's own header carries date and iteration fields, and a community skill file treats the canvas explicitly as not a one-time exercise, to be revisited as the team learns. The successor half is this library's POSITION, not sourced: no source this research read names which document takes over once a canvas has served its purpose. This library names one, informed by one named consultancy's account of the canvas being abandoned in favor of other tools once a project reached enough definition, together with this family's own successor obligation. Deep dive: lean-ux-canvas_companion.md section 3 (Box 9) and section 8 (Relationships to other artifacts). ASK What did the last experiment tell you, and did the assumption it tested hold? Which boxes did you change because of it, and what does Box 7 name now? Has the canvas stopped changing, and if so, did the team commit, change course or stop? PRIORITY Add one row every time the team loops back through the two boxes above; do not overwrite an earlier row. Fill "What takes over" only once the canvas stops changing, not on a first pass. ROW HINT A good row names the date, which assumption was tested, whether it held, and which boxes changed as a result. A weak row says only "tested" with no stated outcome. GOOD | 2026-04-10 | Tested whether dispatchers would trust an SMS reply over a phone call | Held: 5 of 5 dispatchers replied within the pilot week and said they trusted it more than expected | Box 7 now names geofence reliability as the next riskiest assumption | WEAK | | Tested the SMS idea | Went fine | | (no date, no clearly stated outcome, nothing named as having changed) TRAP Leaving this section blank because a first pass feels finished. A canvas revised without a record cannot show what the team actually learned, which is exactly why this family's cadence exception requires one. -->
| Date | Assumption tested | What was learned | Boxes changed ||---|---|---|---|| {{revision_date}} | {{assumption_tested}} | {{outcome_learned}} | {{boxes_changed}} |
**What takes over when this canvas is finished**, because the team committed to building, changedcourse, or stopped the initiative: {{successor_document}}.---title: "Collaborative Analysis Lean UX Canvas"initiative_name: "Collaborative Analysis"facilitator: "Priya Nair, PM, Reporting"status: "active"date: "2026-09-24"iteration: "2"doc_type: lean-ux-canvassize: leansource_template: lean-ux-canvassource_template_version: 0.1.0---
> **Worked example.** A filled `lean-ux-canvas`, the bundle's only size, for the same Acme Analytics> product used throughout this library's examples. It frames the FY26 product roadmap's Later-lane item> 6, "Collaborative analysis" (`../product-roadmap/product-roadmap_example.md`), which that roadmap,> dated 2026-02-11, carries unshaped and names as possibly not even a problem for this product to solve.> This canvas's first pass is dated 2026-09-09; the row below records its one revision so far, dated> 2026-09-24, well before the roadmap's own 15 October 2026 review trigger, and it cites no document> dated after itself. It draws on the> [FY26 product strategy](../product-strategy/product-strategy_example.md) (2026-01-28) for the> Recurring Analyst and for the second-view metric this canvas's own outcome deliberately does not> ladder to, and on the internal announcement> (`../announcement-internal-comms/announcement-internal-comms_example.md`, 2026-07-18) for Saved Views> sharing already being live for Acme's own Reporting squad. Per the `discovery-docs` family contract's> second cadence exception, this canvas stays open while its own experiments run; it has not yet> committed to building, changed course, or stopped the initiative.>> All figures are illustrative. They are internally consistent with the other examples in this library> and are not drawn from a real company.
# Collaborative Analysis Lean UX Canvas
## Business Problem
Acme's FY26 roadmap has carried "Collaborative analysis" in its Later lane since February, unshaped,with a line admitting it might not even be this product's problem to solve. Since then, Support has keptbringing back the same pattern: an analyst at an account works out an answer, and weeks later a differentanalyst at the same account asks Support the identical question, with neither one aware the other alreadydid the work. In a two-week sample Jordan Ames, Support Lead, pulled in late August, 9 of the26 "how do I read this" tickets Support closed turned out, on a second look, to be a questionsomeone else at the same account had already answered on the same dashboard (illustrative counts fromthat one sample). Nothing about any single dashboard causes this; it is the same quiet gap, repeated,account after account, and nobody has owned finding out whether fixing it is worth the effort. How mightwe let an analyst find out that a teammate already has their answer, before either one spends time on itagain?
## Business Outcomes
This outcome does not ladder to the roadmap's own headline measure, the share of new accounts that builda second view within 14 days, from a 31 percent baseline to 50 percent: that number is about a newaccount's first two weeks, and every account in Jordan Ames's sample above had already cleared 14 days,most of them by months. The behavior this initiative wants instead: at an account where a fix has shipped,an analyst who hits a question a teammate already answered reuses that earlier answer, rather than openinga new Support ticket or redoing the analysis from scratch, in at least 70 percent of such repeats within 30days of the fix going live (illustrative target; no fix exists yet to measure a baseline against).
## Users
The Recurring Analyst, the person the FY26 product strategy describes by what they lack, someone who ownsa number, answers questions about it weekly, and has no data team behind them, and whom documents afterit, this one included, name by behavior. Specifically, that analyst on the day they ask aquestion a teammate at their own account already answered. And that teammate, also a Recurring Analyst,whose earlier answer nobody currently surfaces to anyone else. Also affected: Acme's own Support team, whofield the escalation today when neither analyst finds the earlier answer on their own, and who absorb therepeated work this initiative exists to remove.
## User Outcomes and Benefits
An analyst who half-recognizes a question wants one thing before anything else: to find out fast whetherthis has already been worked out, so they can trust that earlier answer and move straight to acting on it,rather than feel like they are starting from zero or interrupting a teammate to ask something that teammatemay not even remember answering. The job is not "get an answer" in the abstract; it is "stop redoing worksomeone at my own company already did," and the small embarrassment of asking a colleague a question theyalready answered once is, if anything, a bigger push toward checking first than the time it would save.
## Solutions
- A searchable log of previously answered questions, tied to the dashboard they came from, that an analyst can check before asking anyone else. Acme has no index like this today.- A prompt inside the dashboard itself, shown when an analyst's typed question looks close to one already on file for that account, pointing at the earlier answer instead of letting the analyst start writing a new one from a blank state.- Not duplicating Saved Views: that capability, live for Acme's own Reporting squad since July, lets one person hand a teammate their exact filter state, but it depends on the second analyst already knowing a saved view exists and going looking for it. The pattern Support brings us shows that second step is exactly the one that is not happening.- Non-technical: route repeat questions through Support's own triage instead of building anything new. Jordan Ames's team already checks whether a question has come in before when they pick up a ticket; the gap is only that an analyst gets no benefit from that unless they go to Support first, which most of them do not.- Non-technical: a standing monthly review between Support and the Reporting squad that simply tracks how often this pattern recurs, before either team commits engineering time to it.
## Hypotheses
| ID | Hypothesis (business outcome, user, benefit, one feature) ||---|---|| H-01 | We believe 70 percent of repeated questions will be reused rather than re-asked if the Recurring Analyst gets a fast way to trust an earlier teammate's answer from a searchable answer log tied to the dashboard. || H-02 | We believe 70 percent of repeated questions will be reused rather than re-asked if the Recurring Analyst gets that same trust, surfaced at the moment they start typing, from an in-dashboard prompt that flags a question close to one already on file. || H-03 | We believe 70 percent of repeated questions will be reused rather than re-asked if the Recurring Analyst gets that same trust, found for them by Support, from routing every repeat question through Support's existing triage process. |
The monthly Support and Reporting review in Box 5 has no hypothesis, because it would measure thepattern rather than change it. *Added 2026-09-24:* H-03 alone cannot carry the outcome in Box 2, sincemost repeats never reach Support (see the revision row). Support's triage keeps running as a stopgap.
## What We Need to Learn First
Now H-02. The first pass chose H-03, the cheapest to try because it builds nothing, and its test is in therevision row below. That test showed most repeats happen before an analyst would ever think of Support,so the in-dashboard prompt is the only candidate that reaches an analyst before they decide whom to ask.Its riskiest assumption is not whether a close match can be found; Support already finds earlier answersby hand. It is whether an analyst who is shown an earlier teammate's answer at the moment they starttyping will stop, read it and trust it enough to reuse it, rather than dismiss it and carry on writing.That is a risk to whether analysts value the pointer when it interrupts them, not a risk to whether theproduct can match questions.
## The Least Work to Learn It
Planned for two weeks from 2026-09-28, with no prompt built. At five accounts that agree to take part, aReporting squad member watches the questions analysts type into the product's existing help search. Whenone looks close to a question a teammate at the same account already answered, they send that analyst anin-app message within a few minutes, pointing at the earlier answer. The test counts how many analystsopen the pointer, and how many reuse the earlier answer rather than carry on building their own. Thepointer is sent by a person, so the test learns whether analysts value the interruption before anyonebuilds the matching that would send it automatically.
## Revisions and What Takes Over
| Date | Assumption tested | What was learned | Boxes changed ||---|---|---|---|| 2026-09-24 | H-03's riskiest assumption: whether an analyst would detour to Support's pointer rather than rebuild an answer themselves. For two weeks from 2026-09-09, Support tagged every ticket Jordan Ames's team could identify as a likely repeat and replied with a one-line pointer to the earlier answer, with no new tooling. The same reply asked two questions: would you have checked here yourself first if you had known to, and how many times this month did you ask a teammate or redo work instead of opening a ticket? | Partly held and partly did not. Of the 11 analysts whose tickets were tagged as repeats, 9 said they would have checked a pointer first if they had known to look. But their answers to the second question put the repeats that never reach Support, asked of a teammate or silently redone, at several times the ones that did (illustrative counts). Routing through Support alone will not move most of the repeats this initiative cares about. | The prompt candidate, H-02, moved into Box 7, because it is the only candidate that reaches an analyst before they choose whom to ask. Box 8 now plans a test of it that builds nothing. Box 6 gained a dated note that H-03 alone cannot carry the outcome in Box 2. |
**What takes over when this canvas is finished**, because the team committed to building, changed course,or stopped the initiative: not yet decided. The canvas stays open while the next test, on H-02's riskiestassumption, runs. If that test holds up, a design brief would hand the chosen concept to the people whodesign it. If it does not, Support's triage from the first testis cheap enough to keep running on its own, which would count as the team changing course rather thancommitting to build anything new.Provenance
Section titled “Provenance”The reasoning, the history and every source, in the repository:
- Companion - the long-form argument: why these sections, where the sources disagree, and what the bundle refuses to claim
- History - what changed in this bundle, and when
- Research log - every source consulted, with what each one actually supports
- Catalog metadata - the machine-readable record this page is generated from
Catalog record: 9 sections across 1 format(s), methodology Lean UX, typically owned by Product team (cross-functional).