Run Problem Framing in Miro
Frame the obstacle for a specific audience in a specific context before debating solutions. A good frame makes room for alternatives while retaining enough evidence and consequence to guide work.
Before you start: Have authorized customer evidence, business context and an accountable owner. Keep the workshop focused on one decision area.
Worked example: We need an AI assistant is a solution. New owners cannot tell which teammates have permission to view a report is a problem that can be investigated and addressed in several ways.
Step-by-step guide
Gather the evidence
Bring concrete observations and their sources. Mark assumptions rather than allowing every stakeholder claim to become a fact.
Define the audience
State who encounters the obstacle and when. Avoid a universal user label that hides role differences.
Describe the obstacle
Write what prevents progress without naming a feature. Separate an observed symptom from a proposed underlying cause.
Explain consequence
Connect the obstacle to user and business outcomes. Distinguish measured impact from a plausible but unverified cost.
Challenge the boundary
Ask whether the frame is too broad, too narrow or already prescribes a solution. Preserve contradictory contexts.
Choose the discovery question
Save a bounded question, known evidence, uncertainty and owner. Use it to compare research or solution options next.
Common mistakes
Solution in disguise
Remove the preferred technology from the problem.
Everyone as audience
Role and context matter.
Unmeasured cost called fact
Label estimates and uncertainty.
Tips
Ask what the person is trying to accomplish.
Keep one contradictory observation visible.
Write an explicit out-of-scope boundary.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.