Standard : Problem Framing Completeness
Description
Problem Framing Completeness measures the percentage of opportunities that are fully articulated with problem statements, success criteria, and supporting evidence before delivery begins.
It ensures that teams are solving well-understood problems rather than jumping to solutions.
How to Use
What to Measure
- Opportunities with a complete problem definition (who, what, why).
- Total opportunities considered for delivery in a period.
Problem Framing Completeness (%) = (Opportunities with Complete Problem Definition ÷ Total Opportunities Considered) × 100
Example: 15 of 20 opportunities have full problem framing → 75% completeness.
Instrumentation Tips
- Use a template for problem definition (e.g. lean canvas).
- Review completeness as part of discovery-to-delivery readiness check.
- Store artefacts in a shared repository for traceability.
Why It Matters
- Alignment: Ensures stakeholders agree on the problem.
- Clarity: Improves solution design and prioritisation.
- Efficiency: Reduces waste from building misaligned features.
Best Practices
- Include qualitative and quantitative evidence.
- Define measurable success criteria early.
- Engage cross-functional stakeholders in review.
Common Pitfalls
- Treating ideas as problems without validation.
- Skipping definition due to delivery deadlines.
- Overcomplicating templates, discouraging adoption.
Signals of Success
- Higher proportion of roadmap items tied to clear problem statements.
- Fewer mid-delivery scope changes or rework.
- Improved outcome achievement after release.
- [[Opportunity Validation Rate]]
- [[Outcome vs Output Ratio]]
- [[CoE/Product/Measures/Discovery Effectiveness/Experiment Success Rate]]