Problem Statement Worksheet
Turns a leader's pain point into a measurable, owned problem statement and feeds the Problem Statement Register that drives the roadmap.
What this is for
Clone Solutions is problem-led. We start with what costs your organization time, money or risk, not with a list of features. A good problem statement names who is affected, what happens today, how often, what it costs and what "fixed" would look like in numbers. Those answers become the baseline, the scoring inputs and, months later, the proof in the results report. A vague problem statement produces a vague result.
When to use it
Right after the executive briefing, in 45-minute deep dives with each executive owner. Use it again at the start of every department rollout (Discover week) to add department-level problems.
Who's involved
- Executive owner: the leader who owns the outcome and signs the statement.
- Process owner and one or two people who do the work: supply the facts.
- Solutions Partner or Implementation Engineer: facilitates and challenges.
- Project Clone: records each statement in the register.
How to fill it in
- Start from the pain point as the leader said it. Write it down verbatim.
- Ask "what actually happens?" until you can describe the current process in five steps or fewer.
- Quantify. If there's no data, take an estimate from the people who do the work and mark it as an estimate. You will replace it with measured baseline data later.
- Write the outcome as a target, not a feature. "Cut matching time per invoice by 60%" not "automate AP."
- List constraints: data the work touches, approvals required, systems involved.
- Get the executive owner to read the final statement back and confirm it.
The template
Worksheet (one per problem)
| Field | Answer |
|---|---|
| ID | PS-___ |
| Title (one line) | |
| Executive owner | |
| Process owner | |
| Department(s) | |
| Pain point as stated | Verbatim from the briefing |
| Who is affected | Roles, team size |
| What happens today | Up to five steps |
| Trigger | What starts the work: an email, a form, a schedule, a ticket |
| Volume | Per day / week / month |
| Effort | Hours per unit or FTE equivalent |
| Cycle time | Start to finish, today |
| Error or rework rate | |
| Cost of failure | Fees, churn, compliance exposure, customer impact |
| Data source for these numbers | Measured / Estimate (by whom) |
| Systems involved | |
| Data sensitivity | Public / Internal / Confidential / Restricted |
| Decisions a person must keep | |
| Desired outcome (measurable) | |
| Target and timeframe | |
| Constraints and dependencies | |
| Related problems | PS-___ |
Problem statement sentence
Write the final statement in this form:
[Who] spends [effort] on [activity] [how often] because [root cause], which results in [cost or risk]. We will know it is fixed when [measurable outcome] by [date].
Example: AP specialists spend about 18 minutes per invoice matching supplier invoices to purchase orders and receipts across the ERP and a shared inbox, for roughly 2,400 invoices a month, because invoices arrive in mixed formats and PO references are often missing. This results in about 3 FTE of manual effort, late-payment fees and a five-day month-end close crunch. We will know it is fixed when average handling time is under 7 minutes and 90% of invoices are matched within 2 business days, by the end of Month 4.
Problem Statement Register
| ID | Title | Department | Executive owner | Volume | Effort today | Target outcome | Data quality | Status |
|---|---|---|---|---|---|---|---|---|
| PS-001 | Measured / Estimate | Draft / Confirmed / Scored / In roadmap / Parked | ||||||
| PS-004 | AP invoice-to-PO matching | Finance | VP Finance | 2,400 / month | ~3 FTE | <7 min per invoice; 90% matched in 2 days | Estimate | Confirmed |
Challenge questions for the facilitator
- Is this one problem or three? Split it if the steps involve different teams or systems.
- Is the root cause a missing tool, missing data, or a missing decision? Clones help most with the first two.
- What would the executive owner accept as proof it worked?
- Which steps must stay with a person, and why?
- Is anyone already working on this? (Avoid colliding with an in-flight project.)
Good looks like
- Numbers, even rough ones. An estimate marked as an estimate beats no number. It also tells you what to measure in the baseline.
- Outcomes, not features. The statement should still make sense if the answer turned out not to be a Clone.
- One executive owner who confirmed the wording.
- Human decisions named. Knowing which decisions stay with people shapes the governance charter and the starting autonomy level.
- Common mistake: writing ten statements for one department and none for the others. Aim for three per leader, then rank.
How Clone helps
The Project Clone keeps the Problem Statement Register current and links each statement to the executive owner, the systems involved and, later, the opportunity score and roadmap slot. The Solutions Architect Clone checks each statement for missing numbers and suggests where baseline data could come from. In the portal, the register is the Problem Statement Register deliverable in Foundation; each confirmed statement flows into the Opportunity Inventory for scoring.
Sign-off
| Role | Name | Date | Decision |
|---|---|---|---|
| Executive owner (per statement) | Confirmed | ||
| Executive sponsor (whole register) | Approved for scoring |