Problem Statement
beta · Family discovery-docs · Phase define · Sizes lean, full · ~3,300 tokens
The document that frames which problem is worth solving, who has it, and the evidence that it is real, before anyone names a solution. Lean carries the statement, background, who is affected, impact, evidence and the decision it informs; full adds coping today, scope, success signals and open questions.
How to tell whether you need one, how to pick lean or full, and how to grade what comes back before it goes to the decider named in Decision This Informs.
Before you start: is this the right document at all?
Section titled “Before you start: is this the right document at all?”Write a problem statement when you need to name which problem is worth solving, who has it, and what
evidence shows it is real, before anyone names a solution. Nielsen Norman Group’s own definition is
the anchor this bundle builds from: “A concise description of the problem that needs to be solved.”
This document’s whole job, per this library’s discovery-docs family contract, is to frame one
problem and name no solution, option, project, or investment.
Write something else if:
| You actually need | Because |
|---|---|
| a business case | business-case’s own Problem and Opportunity section asks the same questions inside a funded investment comparison. This document comes earlier, asks for no money, and decides whether a problem is worth that comparison at all. One Six Sigma source draws the same line by name: the problem statement “describes what, where, and how much, without the persuasive framing”. The order, statement first, is this library’s own position |
| a project brief | a project brief asks a named approver for authority to start initiation. This document asks for no authority and names no project. The Association for Project Management’s own published glossary has no entry under this document’s name, and defines Brief and Charter as two different things |
| a PRD | this library’s own prd companion already names a problem statement as one of the things that precede a PRD |
| a How Might We question | it already points toward generating solutions, where this document names none |
| a list of constraints | a limit any answer must respect, such as a budget, a deadline or a regulation, bounds a solution, and this document names none. Engineering-design teaching and a capstone proposal label constraints, and one engineering paper puts them inside the problem statement, a dissent this library does not follow; project-brief’s Constraints and Who Should Be Involved section carries them. That routing is this library’s own position |
An opportunity statement is a separate type in this library, and it is not built. Nielsen Norman Group names the two as aliases, “written and used in the same way”, phrased positively instead of as a problem. One business-analysis source dissents for projects specifically, naming the move where “practitioners treat problems and opportunities interchangeably when developing Business Cases and Project Charters” as an error, not a harmless alias. On 2026-10-17 the maintainer ruled the two different documents, and the opportunity statement became catalog entry 207, a candidate type of its own. On 2026-10-22 the maintainer parked it rather than build it (#298), because no template with sections for it was found. Frame an opportunity here when Nielsen Norman Group’s reading fits your case. A design-thinking Point of View statement, by contrast, is listed as an alias of this document.
A net-new initiative, where no product exists yet, can use this document too. Jeff Gothelf publishes a Business Opportunity Statement for that case, and still says: “My advice is to try the Business Problem Statement first.” To fill this document from his formula, put the people the gap leaves unserved in Who Is Affected, named closely enough that someone could go and find one. Put the gap itself in Evidence, with where you saw it. His formula’s line for it reads “What existing products / services fail to address is [this gap].” Leave out his next line, “Our product / service will address this gap by [vision / strategy].” That line names a direction for a solution, which this document never names. Carry it to the document you name in Decision This Informs.
Write nothing at all if no one is positioned to decide, once this document exists, whether the problem is worth pursuing further. GOV.UK frames exactly this decision: “Your discovery is finished when you’ve decided whether or not you want to move on to alpha.” A statement with no real decider named in Decision This Informs has not finished the job this document exists to do.
Picking a variant
Section titled “Picking a variant”Lean carries Problem Statement, Background, Who Is Affected, Impact and Why Now, Evidence, and Decision This Informs: enough to frame the problem, show it is real, and name the decision it feeds. Full inserts How People Cope Today, What Is Not Part of the Problem, How We Will Know It Is Solved, and Open Questions and Assumptions, in that order, between Evidence and Decision This Informs. The signal to move from lean to full: will a reader reasonably ask how people work around the problem today, what this statement deliberately excludes, what solved would look like, or what is still unknown, not only who has the problem and what shows it is real.
Both sizes stay short. NHS Wales puts a typical instance at “about 18 words long”, and Nielsen Norman Group’s own brevity rule holds at both sizes: “If you can condense your problem statement down to a few sentences, others will quickly understand what you focus on and why, and what’s out of scope.” The full variant adds four named fields around the statement; it does not add length to the statement itself, and no source read for this bundle abandons that brevity convention for a longer form.
The rubric
Section titled “The rubric”Score each row 0, 1 or 2. Below 14 out of 20 on a full statement, a reader cannot tell whether this problem is worth taking to a project brief or a business case without going back to ask the author questions this document should have answered on its own. Below 9 out of 12 on a lean statement, the same gap opens with four fewer sections standing between a weak answer and the decider.
| # | Criterion | 0 | 1 | 2 |
|---|---|---|---|---|
| 1 | No solution or cause | The statement names a feature, a tool, or a fix to build, or states a cause as settled fact | No solution or cause is named, but you cannot tell from the sentence who has the problem or what is happening to them | You can point to the sentence, name the affected person and what is happening to them, and no solution or cause appears anywhere in it |
| 2 | Affected group is findable | “Users” or “customers,” with nothing more | A group is named, but too broadly for anyone to go find a member of it | Someone could take the sentence and go find a person who matches it, without guessing |
| 3 | Origin is traceable | No indication of how the problem came to attention, or which team or product owns it | An origin is named, but you cannot tell what specifically surfaced it now rather than earlier | You can name who or what flagged the problem, and point to the specific event that surfaced it |
| 4 | Evidence outranks opinion | Every row in the table is an assertion with no named source | At least one row names a source, but the strongest row is still an unsourced assertion | The strongest row names where it came from, specifically enough that someone could go check it themselves |
| 5 | Cost tied to timing | No cost or consequence is named, or a cost is named with no reason to act now rather than later | A cost and a timing reason both appear, but you cannot tell whether the cost actually grows if nothing changes | You can point to a trend or a date in the document, and tell from it why waiting costs more than acting now |
| 6 | Decision has an owner | No name, role, or date appears, and the next document is left generic | A decider, a date, and a next document are all named, but nothing shows the decider agreed to decide | You can point to when and how the named decider agreed to decide, and the specific next document the decision leads to |
| 7 | Workaround stays evidence (full only) | No workaround or prior attempt is named | A workaround is named in enough implementation detail that it reads as a proposed fix | The workaround is named at the level needed to judge how painful it is, and a prior attempt plus why it fell short is also named |
| 8 | Exclusion draws a boundary (full only) | The field is blank, or says everything else is out of scope | A neighbouring problem is named, but you cannot say who would have assumed it was included | A specific neighbouring problem is named, and you can say who would reasonably have assumed it was in scope before this line drew the boundary |
| 9 | Measure carries no target (full only) | No measure is named, or the row names a solution’s output instead of a measure of the affected person’s experience | A measure and a current level both appear, but a target number or a solution’s output also appears in the row | The row names a measure, its current level, and a direction, with no target number anywhere in it |
| 10 | Root cause stays hypothesis (full only) | A cause is stated as settled fact anywhere in the document | A cause is labeled a hypothesis in this section, but an open question or assumption elsewhere still reads as settled | Every suspected cause in the document sits only here, labeled a hypothesis, and at least one open question is named that would change the statement if answered differently |
Which rows apply to what. Full ships all ten rows because a reader of the full variant can ask about coping, exclusion, success, and open questions as well as who, what, and why. Lean ships six, every row the lean variant has a section to support.
| Document | Rows | Maximum | Score against |
|---|---|---|---|
| lean | 1-6 | 12 | 9 |
| full | all 10 | 20 | 14 |
Anti-patterns
Section titled “Anti-patterns”A solution in disguise. Digital NSW and GOV.UK both publish the identical corrective move, rewriting a handed-down solution as a problem, and Build for Good states the rule directly: “Do not include solutions in your problem statement.”
Scope set too broad or too narrow. A UX design guide states the tension directly: the scope should be “broad enough to allow for creative thinking and innovative solutions, but narrow enough that it can provide a direction for that solution.”
Opinion standing in for evidence. NHS Wales’s own warning is blunt: “without evidence of your problem, you are left with opinion.” Digital NSW’s review checklist asks the same question as a gate: “Is this based on evidence rather than assumptions?”
A predetermined cause dressed up as a problem statement. A good statement “does not offer commentary on a proposed solution. It does not attempt to diagnose the problem, nor assign blame. It is objective and factual.” NHS Wales draws the same line from the other side: “problem statements do not describe the solution or root causes.”
A laundry list of unrelated problems. Nielsen Norman Group’s own rule holds that a discovery effort “should have one problem statement, and the problem statement should be focused on one problem.”
One neutral statement flattening genuinely different stakeholder views. A Canada School of Public Service job aid writes a point-of-view statement once per stakeholder rather than merging them into a single voice, illustrated from one inspector’s own line about a device that “is not secure, which makes me feel vulnerable and inefficient.” Where stakeholders genuinely disagree on what the problem is, write more than one statement rather than flattening the disagreement into a false consensus.
A costed estimate where a directional figure belongs. A Six Sigma source draws the line this
document stops short of: “the problem statement describes what, where, and how much, without the
persuasive framing”, while a specific dollar estimate “gives a sponsor something concrete to weigh”
in a business case, not here. Writing a full costed estimate with its own methodology has stepped
into business-case’s job, not this document’s.
A target number smuggled into the success-measure row. (full only) Queensland’s own “Defining success” play draws a line this section is built to respect: “The outcome is not an output or a metric of your project.” Name the measure and its current level; leave the number that says how far to move it for the document that proposes how to move it.
When it is good enough
Section titled “When it is good enough”When the statement names no solution anywhere in it, when the strongest row in the Evidence table names a source a reader could go check, and when a named person has actually agreed to decide whether the problem is worth pursuing further, by a real date.
Then delete every HTML comment. A statement nobody has agreed to decide on has not finished the job it exists to do, whatever else it contains, so the last thing worth checking is not a section of the statement at all: has the person named in Decision This Informs actually agreed to decide, not merely been copied on the draft.
The artifacts
Section titled “The artifacts”problem-statement_template-lean.md · ~3,300 tokens
---title: "{{problem_name}} Problem Statement"problem_name: "{{problem_name}}"author: "{{author}}"decider: "{{decider}}"status: "{{status}}"last_updated: "{{date}}"doc_type: problem-statementsize: leansource_template: problem-statementsource_template_version: 0.1.2---
<!--LEAN PROBLEM STATEMENT. The shortest form that still names which problem is worth solving, who hasit, and what evidence shows it is real, before anyone names a solution. Use it to decide whether aproblem is worth taking to a project brief or a business case at all, not to make that case itself.To grow it into a form that also carries success measures, a boundary on what the problem excludes,and open questions, see problem-statement_template-full.md. ADD sections between Evidence andDecision This Informs; never rename or reorder the ones below, because the full variant is a strictordered superset of this one.
SHORT AT BOTH SIZES, NOT ONLY THIS ONE. Nielsen Norman Group's own brevity rule reads, "If you cancondense your problem statement down to a few sentences, others will quickly understand what youfocus on and why, and what's out of scope," and NHS Wales puts a typical instance at "about 18 wordslong." The full variant adds four named fields around the statement; it does not add length to thestatement itself. See problem-statement_companion.md section 4.
WHAT A PROBLEM STATEMENT IS, AND IS NOTIt names which problem is worth solving, who has it, and what evidence shows it is real, beforeanyone names a solution, an option, a project, or an investment. It is NOT a business case (thislibrary's own `business-case` bundle asks the same questions inside a funded investment comparison;this document comes earlier, asks for no money, and decides whether a problem is worth thatcomparison at all; one Six Sigma source draws the same line by name, and the order, statement first,is this library's own POSITION). It is NOT a project brief (which asks a named approverfor authority to start initiation; this document asks for no authority and names no project; anAssociation for Project Management consultation draft read for this library's `project-brief`research names the three documents as interchangeable for one early rationale, but APM's ownpublished glossary carries no "problem statement" entry and defines "Brief" and "Charter" as twodifferent things). It is NOT a PRD (this library's own `prd` companion already names a problemstatement as one of the things that precede a PRD). It is NOT a hypothesis statement, a How Might Wequestion, or a job story (each of those already points at a solution or tests one). It is NOT, inthis library, an opportunity statement: that is a separate catalog type, not yet built, thoughNielsen Norman Group names the two "written and used in the same way." A design-thinking Point ofView statement is listed as an alias of this document.See problem-statement_companion.md section 6 and section 8.
HOW TO FILL THIS IN1. Read the comment under each heading: WHAT it wants, WHY it matters (with a pointer into problem-statement_companion.md), guiding questions to ASK, a GOOD and a WEAK example, and the TRAP to avoid. For the table, PRIORITY explains the ordering rule and ROW HINT says what a good row contains.2. Replace each {{placeholder}} with your content. Name no solution, option, project, or investment anywhere in this document; that is a later document's job.3. If a section does not apply, write "N/A" and one line of why, rather than deleting it.4. Before you send this for a decision: self-grade against problem-statement_guide.md, then DELETE every HTML comment. They are guidance, not content.-->
# {{problem_name}} Problem Statement
## Problem Statement
<!-- WHAT The statement itself: a few sentences, from the affected person's perspective, naming no solution. WHY Nielsen Norman Group's own definition anchors this section, "A concise description of the problem that needs to be solved," and NHS Wales adds the brevity bar, "about 18 words long." Atlassian's own Problem Framing play names the same four elements this section asks for, "who is affected, what is affecting them, why it needs to be solved, and where the problem is happening." Deep dive: problem-statement_companion.md section 3 (Anatomy > Problem Statement). ASK Who has this problem? What is happening to them? Why does it need to be solved? Where and when does it occur? GOOD "Patrons who borrow ebooks through the library's mobile app cannot renew a loan from within the app, and must call the branch during open hours to ask staff to renew it for them." WEAK "We need to add a renew button to the ebook app." (a solution stated as if it were the problem; nothing is left to investigate) TRAP Naming a solution instead of a problem. Nielsen Norman Group's own quality rule reads, "Leave solutions out of your problem statement. At the beginning of discovery, there are too many unknowns, so the best solution is not obvious." -->
{{problem_statement}}
## Background
<!-- WHAT Where the problem shows up, how it came to attention, and what is affecting the people who have it. WHY Nielsen Norman Group names the question directly, "Which organization or department has the problem and what is the problem? Why has the problem arisen?" and Atlassian's own prompts ask, "What is the nature of the problem? What signs point to there being a problem?" Deep dive: problem-statement_companion.md section 3 (Anatomy > Background). ASK Which team, product, or service has this problem? How did it come to attention? Why has it arisen now rather than earlier? GOOD "Flagged by three branch managers in the October staffing review, after phone-renewal requests started crowding out other reference calls during the two weekday hours the branches are fully staffed." WEAK "The app has some issues." (no organization named, no origin, no reason it surfaced now) TRAP Restating the Evidence section's data as narrative instead of explaining where the problem shows up and how it was noticed. -->
{{background}}
## Who Is Affected
<!-- WHAT The people who have the problem, named specifically enough to find them. WHY Nielsen Norman Group's own wording leaves room for more than one group, "There could be multiple user groups affected by a specific problem in different ways," and Atlassian asks the verification question directly, "Who is experiencing this problem? How do we know that they are experiencing it?" NHS Scotland's Problem Framer tool carries a closely related field, "Who The Problem Most Affects." Deep dive: problem-statement_companion.md section 3 (Anatomy > Who Is Affected). ASK Who specifically has this problem? Is there more than one affected group, and does each experience it differently? How do you know they are experiencing it, rather than assuming it? Does an existing persona already describe this group? GOOD "Patrons who borrow ebooks through the app, especially those who use it in the evening or on weekends when no branch phone line is staffed." WEAK "Our users." (no group named specifically enough to find them) TRAP Folding more than one differently affected group into one generic line. Nielsen Norman Group treats more than one group as the normal case, not the exception. -->
- Who is affected: {{who_is_affected}}- Existing persona, if one already describes this group: {{persona_reference}}
## Impact and Why Now
<!-- WHAT What the problem costs the people who have it and the organization, and why it matters now rather than later. WHY Nielsen Norman Group's own prompt runs, "If the problem is not fixed, what will be the effect on the organization?" and Atlassian asks it from the affected person's side, "What happens if we don't solve it?" GOV.UK adds the instruction to size the impact where possible, "You should also consider quantifying the value of solving the problem." Keep any figure directional: a Six Sigma source draws the line this section stops short of, "the problem statement describes what, where, and how much, without the persuasive framing," while a specific dollar estimate belongs to a business case. Deep dive: problem-statement_companion.md section 3 (Anatomy > Impact and Why Now). ASK What does this problem cost the affected people, and the organization? Why does it matter now rather than later? What changes if nothing is done? What is a rough, directional figure for the cost of not solving it, not a costed estimate? GOOD "Branch phone lines run near capacity during the two staffed hours, and the October survey named the call-in renewal step the top app complaint. Ebook loans are a growing share of total borrowing, so the volume of calls this causes is rising each quarter." WEAK "This is frustrating for everyone." (no organizational effect, no timing reason, no figure at all, directional or otherwise) TRAP Writing a full costed estimate with its own methodology. That is a business case's job, not this one's; a rough, directional figure is enough here. -->
- Impact: {{impact}}- Why now: {{why_now}}
## Evidence
<!-- WHAT What shows the problem is real, where each piece came from, and how strong it is. WHY Digital NSW states the obligation plainly, "Use the evidence you gather to document your clearly defined problem," and NHS Wales states the cost of skipping it, "without evidence of your problem, you are left with opinion." Name the extent of the problem, not only its existence: a Six Sigma source adds the magnitude question, "it is essential to explain the extent or magnitude of the issue." Deep dive: problem-statement_companion.md section 3 (Anatomy > Evidence). ASK What evidence shows this problem is real? Where did each piece come from? How strong is it, a direct measurement, a survey, or an anecdote? How large or widespread is the problem, not only that it exists? PRIORITY List the strongest, most direct evidence first. A statement resting only on the weakest row is a statement resting on opinion. ROW HINT A good row names where the evidence came from and what it shows, specifically enough that a reader could go check it. A weak row asserts a fact with no named source. GOOD | Branch call logs, Sept-Oct | Renewal-assistance calls are the largest single call category during staffed hours | Direct measurement | WEAK | Staff say it's a problem | | Anecdote | TRAP Opinion standing in for evidence. NHS Wales's own warning is blunt: without evidence, a problem statement is left with opinion, not a documented fact. -->
| Evidence | What it shows | Strength ||---|---|---|| {{evidence_source}} | {{evidence_summary}} | {{evidence_strength}} |
## Decision This Informs
<!-- WHAT Who decides whether this problem is worth pursuing further, by when, and which document takes over if the answer is yes. WHY GOV.UK frames the decision itself, "Your discovery is finished when you've decided whether or not you want to move on to alpha," adding, "It's not a failure to stop at the end of the discovery phase," and Digital NSW's own checklist ends on the same question, "Is the problem clear enough to investigate further?" Which document takes over is this library's own POSITION, from the `discovery-docs` family contract's successor obligation: name the specific document, a project brief, a business case, or both in sequence, rather than leaving the pointer generic. Deep dive: problem-statement_companion.md section 3 (Anatomy > Decision This Informs). ASK Who decides whether this problem is worth pursuing further? By when do they need to decide? Which specific document takes over if the answer is yes, a project brief, a business case, or both in sequence? GOOD "Decider: the digital services manager, by the end of the month. If the problem is confirmed worth pursuing, a project brief is written next to ask for authority to investigate options." WEAK "We'll figure out next steps later." (no decider, no date, no named next document) TRAP Leaving the next document generic, or naming an option or a project instead of a decision. This section names who decides and what happens to the answer, nothing more. -->
- Decider: {{decider}}- Decide by: {{decision_deadline}}- Next document if pursued: {{next_document}}problem-statement_template-full.md · ~5,400 tokens
---title: "{{problem_name}} Problem Statement"problem_name: "{{problem_name}}"author: "{{author}}"decider: "{{decider}}"status: "{{status}}"last_updated: "{{date}}"doc_type: problem-statementsize: fullsource_template: problem-statementsource_template_version: 0.1.2---
<!--FULL PROBLEM STATEMENT. Everything the lean variant carries, plus How People Cope Today, What IsNot Part of the Problem, How We Will Know It Is Solved, and Open Questions and Assumptions, insertedbetween Evidence and Decision This Informs, in that order. Use it once a reader will reasonably askhow people work around the problem today, what it deliberately excludes, what solved would looklike, or what is still unknown, not only who has the problem and what shows it is real.
THIS VARIANT IS A STRICT ORDERED SUPERSET OF THE LEAN ONE. The six lean sections appear here underthe same headings, in the same order, with the same placeholders; four sections are inserted betweenEvidence and Decision This Informs. If you started lean, grow into this without rewriting anythingyou already filled in.
SHORT EVEN AT THIS SIZE. Nielsen Norman Group's own brevity rule reads, "If you can condense yourproblem statement down to a few sentences, others will quickly understand what you focus on andwhy, and what's out of scope," and NHS Wales puts a typical instance at "about 18 words long." Thefour added sections are named fields around the statement, each resting on a source this bundle'sresearch actually read; they do not turn this into a business case. Options, a recommendedsolution, a cost estimate, a project scope, and a funding request stay out at every size. So doconstraints: the sources that label them use them to bound a solution, and `project-brief` carriesthem. See problem-statement_companion.md section 4.
WHAT A PROBLEM STATEMENT IS, AND IS NOTIt names which problem is worth solving, who has it, and what evidence shows it is real, beforeanyone names a solution, an option, a project, or an investment. It is NOT a business case (thislibrary's own `business-case` bundle asks the same questions inside a funded investment comparison;this document comes earlier, asks for no money, and decides whether a problem is worth thatcomparison at all; one Six Sigma source draws the same line by name, and the order, statement first,is this library's own POSITION). It is NOT a project brief (which asks a named approverfor authority to start initiation; this document asks for no authority and names no project; anAssociation for Project Management consultation draft read for this library's `project-brief`research names the three documents as interchangeable for one early rationale, but APM's ownpublished glossary carries no "problem statement" entry and defines "Brief" and "Charter" as twodifferent things). It is NOT a PRD (this library's own `prd` companion already names a problemstatement as one of the things that precede a PRD). It is NOT a hypothesis statement, a How Might Wequestion, or a job story (each of those already points at a solution or tests one). It is NOT, inthis library, an opportunity statement: that is a separate catalog type, not yet built, thoughNielsen Norman Group names the two "written and used in the same way." A design-thinking Point ofView statement is listed as an alias of this document.See problem-statement_companion.md section 6 and section 8.
A ROOT CAUSE STAYS OUT OF THE PROBLEM STATEMENT SECTION. NHS Wales states plainly that "problemstatements do not describe the solution or root causes," while Digital NSW's own checklist asks "Dowe understand the root cause?" This bundle follows the University of South Carolina's A3 template,which keeps the two apart structurally: a suspected cause goes under Open Questions and Assumptions,labeled a hypothesis, and the Problem Statement section itself names none. That placement is thislibrary's own POSITION, not a point every source agrees on. See problem-statement_companion.mdsection 3 (Anatomy > Open Questions and Assumptions) and section 6.
HOW TO FILL THIS IN1. Read the comment under each heading: WHAT it wants, WHY it matters (with a pointer into problem-statement_companion.md), guiding questions to ASK, a GOOD and a WEAK example, and the TRAP to avoid. For the tables, PRIORITY explains the ordering rule and ROW HINT says what a good row contains.2. Replace each {{placeholder}} with your content. Name no solution, option, project, or investment anywhere in this document; that is a later document's job.3. If a section does not apply, write "N/A" and one line of why, rather than deleting it.4. Before you send this for a decision: self-grade against problem-statement_guide.md, then DELETE every HTML comment. They are guidance, not content.-->
# {{problem_name}} Problem Statement
## Problem Statement
<!-- WHAT The statement itself: a few sentences, from the affected person's perspective, naming no solution. WHY Nielsen Norman Group's own definition anchors this section, "A concise description of the problem that needs to be solved," and NHS Wales adds the brevity bar, "about 18 words long." Atlassian's own Problem Framing play names the same four elements this section asks for, "who is affected, what is affecting them, why it needs to be solved, and where the problem is happening." Deep dive: problem-statement_companion.md section 3 (Anatomy > Problem Statement). ASK Who has this problem? What is happening to them? Why does it need to be solved? Where and when does it occur? GOOD "Patrons who borrow ebooks through the library's mobile app cannot renew a loan from within the app, and must call the branch during open hours to ask staff to renew it for them." WEAK "We need to add a renew button to the ebook app." (a solution stated as if it were the problem; nothing is left to investigate) TRAP Naming a solution instead of a problem. Nielsen Norman Group's own quality rule reads, "Leave solutions out of your problem statement. At the beginning of discovery, there are too many unknowns, so the best solution is not obvious." -->
{{problem_statement}}
## Background
<!-- WHAT Where the problem shows up, how it came to attention, and what is affecting the people who have it. WHY Nielsen Norman Group names the question directly, "Which organization or department has the problem and what is the problem? Why has the problem arisen?" and Atlassian's own prompts ask, "What is the nature of the problem? What signs point to there being a problem?" Deep dive: problem-statement_companion.md section 3 (Anatomy > Background). ASK Which team, product, or service has this problem? How did it come to attention? Why has it arisen now rather than earlier? GOOD "Flagged by three branch managers in the October staffing review, after phone-renewal requests started crowding out other reference calls during the two weekday hours the branches are fully staffed." WEAK "The app has some issues." (no organization named, no origin, no reason it surfaced now) TRAP Restating the Evidence section's data as narrative instead of explaining where the problem shows up and how it was noticed. -->
{{background}}
## Who Is Affected
<!-- WHAT The people who have the problem, named specifically enough to find them. WHY Nielsen Norman Group's own wording leaves room for more than one group, "There could be multiple user groups affected by a specific problem in different ways," and Atlassian asks the verification question directly, "Who is experiencing this problem? How do we know that they are experiencing it?" NHS Scotland's Problem Framer tool carries a closely related field, "Who The Problem Most Affects." Deep dive: problem-statement_companion.md section 3 (Anatomy > Who Is Affected). ASK Who specifically has this problem? Is there more than one affected group, and does each experience it differently? How do you know they are experiencing it, rather than assuming it? Does an existing persona already describe this group? GOOD "Patrons who borrow ebooks through the app, especially those who use it in the evening or on weekends when no branch phone line is staffed." WEAK "Our users." (no group named specifically enough to find them) TRAP Folding more than one differently affected group into one generic line. Nielsen Norman Group treats more than one group as the normal case, not the exception. -->
- Who is affected: {{who_is_affected}}- Existing persona, if one already describes this group: {{persona_reference}}
## Impact and Why Now
<!-- WHAT What the problem costs the people who have it and the organization, and why it matters now rather than later. WHY Nielsen Norman Group's own prompt runs, "If the problem is not fixed, what will be the effect on the organization?" and Atlassian asks it from the affected person's side, "What happens if we don't solve it?" GOV.UK adds the instruction to size the impact where possible, "You should also consider quantifying the value of solving the problem." Keep any figure directional: a Six Sigma source draws the line this section stops short of, "the problem statement describes what, where, and how much, without the persuasive framing," while a specific dollar estimate belongs to a business case. Deep dive: problem-statement_companion.md section 3 (Anatomy > Impact and Why Now). ASK What does this problem cost the affected people, and the organization? Why does it matter now rather than later? What changes if nothing is done? What is a rough, directional figure for the cost of not solving it, not a costed estimate? GOOD "Branch phone lines run near capacity during the two staffed hours, and the October survey named the call-in renewal step the top app complaint. Ebook loans are a growing share of total borrowing, so the volume of calls this causes is rising each quarter." WEAK "This is frustrating for everyone." (no organizational effect, no timing reason, no figure at all, directional or otherwise) TRAP Writing a full costed estimate with its own methodology. That is a business case's job, not this one's; a rough, directional figure is enough here. -->
- Impact: {{impact}}- Why now: {{why_now}}
## Evidence
<!-- WHAT What shows the problem is real, where each piece came from, and how strong it is. WHY Digital NSW states the obligation plainly, "Use the evidence you gather to document your clearly defined problem," and NHS Wales states the cost of skipping it, "without evidence of your problem, you are left with opinion." Name the extent of the problem, not only its existence: a Six Sigma source adds the magnitude question, "it is essential to explain the extent or magnitude of the issue." Deep dive: problem-statement_companion.md section 3 (Anatomy > Evidence). ASK What evidence shows this problem is real? Where did each piece come from? How strong is it, a direct measurement, a survey, or an anecdote? How large or widespread is the problem, not only that it exists? PRIORITY List the strongest, most direct evidence first. A statement resting only on the weakest row is a statement resting on opinion. ROW HINT A good row names where the evidence came from and what it shows, specifically enough that a reader could go check it. A weak row asserts a fact with no named source. GOOD | Branch call logs, Sept-Oct | Renewal-assistance calls are the largest single call category during staffed hours | Direct measurement | WEAK | Staff say it's a problem | | Anecdote | TRAP Opinion standing in for evidence. NHS Wales's own warning is blunt: without evidence, a problem statement is left with opinion, not a documented fact. -->
| Evidence | What it shows | Strength ||---|---|---|| {{evidence_source}} | {{evidence_summary}} | {{evidence_strength}} |
## How People Cope Today
<!-- WHAT How the people who have the problem work around it now, and what has already been tried and why it did not work, held as evidence and never as an option. WHY Heap's own worksheet asks, "How do people currently solve this problem?" and its named author restates the same question as part of a wider framing exercise, "how customers work around the problem." A University of Waterloo submission form asks for the same history under its own field, "Failure analysis," prompting "Describe previous attempts to solve the problem and why they failed." Deep dive: problem-statement_companion.md section 3 (Anatomy > How People Cope Today). ASK How do the affected people work around this today? What, if anything, has already been tried? Why did it fall short? GOOD "Patrons call during the two staffed hours, or let the loan lapse and rejoin the title's hold queue. A help-center article on renewing from the app was published in August; call volume did not change in the two months after it published." WEAK "People find ways to cope." (no workaround named, no prior attempt, no evidence of weight) TRAP Describing a workaround in enough implementation detail that it reads as a proposed fix. This section is evidence of how painful the workaround is, not an options list. -->
- How people cope today: {{coping_today}}- Prior attempts, and why they fell short: {{prior_attempts}}
## What Is Not Part of the Problem
<!-- WHAT Neighbouring problems this statement deliberately leaves out, agreed before anyone scopes work against it. WHY GOV.UK names the move directly, "Reframing the problem also includes agreeing what is not part of the problem," and a Rose-Hulman course template asks for "what is to be included and, perhaps more importantly, what isn't." Atlassian's own prompt asks the boundary from the other side, "In what circumstances does it not occur?" Deep dive: problem-statement_companion.md section 3 (Anatomy > What Is Not Part of the Problem). ASK What neighbouring problem is this statement deliberately not about? Where does the boundary sit, and would a reader otherwise assume it is included? GOOD "Not part of this problem: in-branch renewal at the circulation desk, which already works. Overall checkout wait times are a separate, already-tracked issue." WEAK "Everything else is out of scope." (names no specific neighbouring problem, so the boundary cannot actually be checked) TRAP Writing a project scope instead of a problem boundary. This section draws the edge of the problem itself, not of the work that might follow if it is pursued. -->
{{not_part_of_problem}}
## How We Will Know It Is Solved
<!-- WHAT Observable signals that the problem has shrunk, stated without naming a solution: the measure, its current level, and the direction it needs to move. WHY Jeff Gothelf's Business Problem Statement formula closes on exactly this question, "as determined by [these measurable changes in their behavior]," and his own walkthrough asks it again, "what customer behavior or metric shift will we see?" Heap's worksheet gives it a labeled field, "Metric(s) and Baseline: Define how you'll evaluate success," and a Rose-Hulman template asks for "A summary of the primary success criteria." This is genuinely disputed, not settled: Queensland's own "Defining success" play treats it as separate, later work that assumes, "You should already have a well-defined problem," and draws its own line, "The outcome is not an output or a metric of your project." This section carries the split rather than resolving it. Deep dive: problem-statement_companion.md section 3 (Anatomy > How We Will Know It Is Solved), section 6. ASK What measure would show this problem has shrunk? What is its current level? Which direction does it need to move? Leave the target number out; that belongs to the document that proposes how to move it. PRIORITY List the measure closest to the affected person's own experience first, ahead of an operational measure that only indirectly reflects it. ROW HINT A good row names a measure and its current level, with no target number attached. A weak row names a target, or names an output of a specific solution instead of a measure. GOOD | Share of ebook renewals completed without a phone call | About 5 percent today | Up | WEAK | Renewal button usage | 0 | 100 percent after launch | TRAP Naming a target, or naming a solution's own output as the measure. Name the measure and its current level; leave the target for the document that proposes how to move it. -->
| Measure | Current level | Direction needed ||---|---|---|| {{success_measure}} | {{current_level}} | {{direction_needed}} |
## Open Questions and Assumptions
<!-- WHAT What is not yet known, what is being assumed true until research says otherwise, and a root cause the team suspects, labeled as a hypothesis. WHY Heap's worksheet carries a literal "Open Questions" field, and a Canada School of Public Service job aid states the underlying caution directly: a statement written before research "should be considered as being based on assumptions." A root cause stays out of the Problem Statement section itself: the University of South Carolina's A3 template keeps the two apart, with the problem statement as its own step and "What is your most likely root cause?" as a separate, later step. Nielsen Norman Group names refining the statement "if you've learned root causes or how much a problem costs your organization" as a normal, later move, not a sign the first draft was wrong. Deep dive: problem-statement_companion.md section 3 (Anatomy > Open Questions and Assumptions), section 6. ASK What is not yet known that would change this statement? What is being assumed true until research says otherwise? Does the team suspect a root cause? If so, name it here as a hypothesis, not as settled fact. GOOD "Open question: whether patrons cannot find the renew control in the app, or the app blocks a renewal outright when the title has a hold queue. Hypothesis, not yet confirmed: the renewal control is present but easy to miss on a small screen." WEAK "The cause is that the app is poorly designed." (a cause stated as settled fact, not labeled a hypothesis, and specific enough to read as a diagnosis rather than a guess) TRAP Stating a suspected cause as fact anywhere in this document, including here. A suspected cause is a hypothesis to test, not a conclusion to act on yet. -->
- Open questions: {{open_questions}}- Assumptions: {{assumptions}}- Suspected root cause, labeled as a hypothesis: {{root_cause_hypothesis}}
## Decision This Informs
<!-- WHAT Who decides whether this problem is worth pursuing further, by when, and which document takes over if the answer is yes. WHY GOV.UK frames the decision itself, "Your discovery is finished when you've decided whether or not you want to move on to alpha," adding, "It's not a failure to stop at the end of the discovery phase," and Digital NSW's own checklist ends on the same question, "Is the problem clear enough to investigate further?" Which document takes over is this library's own POSITION, from the `discovery-docs` family contract's successor obligation: name the specific document, a project brief, a business case, or both in sequence, rather than leaving the pointer generic. Deep dive: problem-statement_companion.md section 3 (Anatomy > Decision This Informs). ASK Who decides whether this problem is worth pursuing further? By when do they need to decide? Which specific document takes over if the answer is yes, a project brief, a business case, or both in sequence? GOOD "Decider: the digital services manager, by the end of the month. If the problem is confirmed worth pursuing, a project brief is written next to ask for authority to investigate options." WEAK "We'll figure out next steps later." (no decider, no date, no named next document) TRAP Leaving the next document generic, or naming an option or a project instead of a decision. This section names who decides and what happens to the answer, nothing more. -->
- Decider: {{decider}}- Decide by: {{decision_deadline}}- Next document if pursued: {{next_document}}---title: "New-Account Second-View Stall Problem Statement"problem_name: "New-Account Second-View Stall"author: "Priya Nair, PM, Reporting"decider: "Dana Okoro, VP Product"status: "pending decision"last_updated: "2026-01-09"doc_type: problem-statementsize: fullsource_template: problem-statementsource_template_version: 0.1.2---
> **Worked example.** A filled `problem-statement`, full variant, for the same Acme Analytics product used> throughout this library's examples. Per the discovery-docs family contract, this document extends the> shared timeline **backward**, to before any of the documents it leads to: it is dated 2026-01-09, four> days after the [user persona](../user-persona/user-persona_example.md) that names the Recurring Analyst> (2026-01-05), five days before the product vision (2026-01-14), seven days before the project brief> (2026-01-16), and eleven days before the business case (2026-01-20) that the project brief and this> statement together lead to. Nothing in the body below names a solution, an option, a project, or an> investment, and nothing cites a document dated after this one as already existing, because none of them> did yet when this was written.>> All figures are illustrative. They are internally consistent with the other examples in this library and> are not drawn from a real company.
# New-Account Second-View Stall Problem Statement
## Problem Statement
New accounts to Acme Analytics' Reporting product that have no dedicated data analyst and no querybackground stall at the step where they first choose a table, a join, and a measure, and most of themnever build a second dashboard view within the first two weeks after signup.
## Background
Dana Okoro, VP Product, raised Acme's flat revenue-per-account trend at the December 2025 leadershipreview, after finance confirmed the trend had held for five straight quarters and asked for a fundingdecision on it rather than letting it wait for the FY26 planning cycle to reach it on its own schedule. TheReporting team reviewed its own product telemetry in the first week of January and located where thetrend actually starts: not at signup, and not at sharing, but at the single step where a new account firsthas to pick which table, which join, and which measure answers the question it opened the product toanswer, before it has had any chance to see value from Reporting at all.
## Who Is Affected
- Who is affected: New Acme accounts that reach that step within their first two weeks after signup and have no dedicated data analyst and no query background of their own to draw on. Their profile matches a group Acme already has a name for, and they are also the fastest-growing part of the signup base, which is why finance is asking about it now rather than treating it as something to monitor at leisure.- Existing persona, if one already describes this group: the [Recurring Analyst](../user-persona/user-persona_example.md#who-they-are), named in the 2026-01-05 user persona built from interviews with operations, fulfilment, and finance managers across 9 mid-market accounts (n=12): a person who looks at the same numbers on the same schedule because there is nobody else to do it, with no dedicated analyst and no query background. The accounts that stall at the dataset-picker step share that profile, but they are met earlier, before the weekly cadence that defines the persona has had a chance to form.
## Impact and Why Now
- Impact: Revenue per new account has stayed flat for five straight quarters even as sign-ups grew 40 percent over the same period, so the share of new accounts the product is failing to convert into continued use is growing, not holding steady. Two years of incremental investment in documentation, in tutorials, and in services capacity has not moved that number.- Why now: The segment that stalls at the dataset-picker step is the fastest-growing part of the signup base, so the flat trend worsens on its current trajectory rather than correcting on its own. Finance wants a funding decision ahead of the FY26 planning cycle's own schedule, which is why this statement is being written now rather than waiting for that cycle to raise the same question again.
## Evidence
| Evidence | What it shows | Strength ||---|---|---|| Reporting-team review of product telemetry, first week of January 2026 | Only 31 percent of new accounts build a second dashboard view within 14 days of signup, and the drop concentrates at the dataset-picker step rather than at signup or at sharing | Direct measurement || Session recordings reviewed alongside the telemetry | Two-thirds of the accounts that stall at the dataset-picker step never return to authoring at all | Direct measurement || Finance's revenue reporting, reviewed at the December 2025 leadership review | Revenue per new account has been flat for five straight quarters while sign-ups grew 40 percent over the same period | Direct measurement || Reporting-team record of documentation, tutorial, and services-capacity investment over the last two years | Incremental investment of this kind has not moved the 31 percent figure above over that period | Direct measurement, but weaker: it shows an absence of movement, not the mechanism behind it |
## How People Cope Today
- How people cope today: An account that stalls at the dataset-picker step either pays for time from Acme's services team to get a working view built for it, or settles for whatever single view it landed on during onboarding and does not come back to build a second one.- Prior attempts, and why they fell short: Acme's documentation library and in-product tutorial content for the dataset-picker step both grew substantially over the last two years, and services capacity was added alongside them. None of that moved the 31 percent figure in the Evidence section above. The Reporting team's working read, not yet confirmed, is that the accounts who stall are not failing to find the documentation; they are failing before they would know what to search for.
## What Is Not Part of the Problem
Not part of this problem: accounts that already have a dedicated analyst or a query background of theirown, who pass the dataset-picker step today without the telemetry showing any comparable drop. Also notpart of this problem: the rest of the onboarding flow before that step, which the telemetry does not showlosing accounts, and the quality or design of the dashboard view itself once an account succeeds inbuilding one, which is a separate, already-tracked product area with its own support-ticket history.
## How We Will Know It Is Solved
| Measure | Current level | Direction needed ||---|---|---|| Share of new accounts that build a second dashboard view within 14 days of signup | About 31 percent, per the Evidence section above | Up || Share of new accounts whose first substantive interaction with Reporting is a request to a data analyst or to the services team for help choosing what to look at | Not yet tracked as its own number; today's support-ticket tagging does not separate this reason from other requests | Down, once tracked || Revenue per new account | Flat for five straight quarters | Up |
## Open Questions and Assumptions
- Open questions: Whether accounts stall because the dataset-picker step is hard to find or operate, or because it requires knowledge, which table, which join, which measure, that this segment does not have at all. Whether the fastest-growing segment's current growth rate continues or levels off. Whether the two years of documentation and services investment actually reached the accounts that stall, or whether those accounts never engaged it in the first place.- Assumptions: That an account which stalls at the dataset-picker step would, in fact, go on to build a second view if that step itself were easier to get past, an assumption not yet tested against real account behavior. That the segment's recent growth rate is representative of its near-term trajectory rather than a temporary spike.- Suspected root cause, labeled as a hypothesis: Hypothesis, not yet confirmed: the dataset-picker step requires knowledge this segment does not have, rather than being present but merely hard to find or awkward to operate. The Reporting team has not yet tested this against the accounts that actually stall.
## Decision This Informs
- Decider: Dana Okoro, VP Product.- Decide by: 2026-01-15, a date Dana Okoro agreed to when this statement was circulated, so that the answer lands before the FY26 planning cycle would reach the question on its own schedule.- Next document if pursued: If Dana Okoro's answer is yes, a project brief follows, requesting the Reporting team's authority to look into the problem further. This statement does not describe what that brief would contain, who would write it, or when it would arrive; that is its own job, not this one's.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: 10 sections across 1 format(s), methodology UX discovery / service design, typically owned by PM / UXR.