Map User Jobs to Outcomes in Miro
Describe the progress a person seeks in a real situation, then identify what successful progress looks like. This manual mapping method should preserve customer context rather than convert every request into a job statement.
Before you start: Have interview or observation evidence and a bounded audience. Start with a real situation, not a fictional persona invented to justify a roadmap.
Worked example: A team owner wants to explain weekly progress without assembling screenshots. Export a PDF is a requested solution; sharing an understandable, trusted update is closer to the desired outcome.
Step-by-step guide
Choose a situation
Describe when the need arises and what triggers action. Keep the specific audience and constraints visible.
Extract desired progress
Write what the person is trying to accomplish without naming the preferred feature. Link the claim to its source.
Map current alternatives
Include manual workarounds and doing nothing. These reveal what the user currently trades off.
Define outcome criteria
State how the person judges a successful result, such as reduced preparation or fewer clarification requests. Keep unmeasured aspirations labeled.
Inspect contradictions
Compare different contexts and failed attempts. A single broad job can hide important audience differences.
Connect to discovery
Choose which outcome or constraint needs more evidence. Use the map to guide options rather than declaring a preselected feature inevitable.
Common mistakes
Feature renamed as job
That preserves solution bias.
Context removed
The same action can serve different goals.
Outcome presented as measured
Label what is observed and what remains hypothetical.
Tips
Keep a source reference beside every important job.
Include manual alternatives.
Ask how the customer recognizes success.
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.