Opportunity Framing Workshop Kit

Welcome — Why this workshop matters

This half-day workshop helps teams move from vague complaints and scattered ideas to clear discovery questions, prioritized assumptions, and minimal, testable hypotheses. Good framing reduces wasted effort, lowers experiment risk, and produces clearer, faster learning. Use this kit when you want to discover what to learn next — not when you're ready to design a final solution.

Who this helps

Product leads, program managers, service designers, operations leads, researchers, and cross-functional teams who need to:

• Turn anecdote or frustration into measurable discovery questions
• Expose and prioritize critical assumptions before building
• Create a pipeline of small experiments that produce clear signals

Outcomes (what you should leave with)

• 2–4 framed opportunity statements (How Might We) aligned to user or business outcomes
• A prioritized assumption map highlighting high-impact, low-evidence risks
• Hypothesis briefs for top opportunities (minimal test, success criteria, owner)
• A clear next-step plan with owners, timelines, and measures to launch experiments

Before you run (read at least 48 hours before)

Participants

• Facilitator (neutral process lead)
• Decision owner (product lead, sponsor) — empowered to commit next steps
• Scribe (captures artifacts and exports digital files)
• 2–4 subject-matter experts or data owners
• 6–10 cross-functional participants with direct knowledge of customers, ops, or the process

Pre-work (short, clear)

1. Bring 1–3 one-sentence observations: an observed problem, customer quote, or idea.
2. Collect quick evidence if available: support tickets, metrics, photos, or short interviews.

Materials & setup

• Room with wall space or a digital whiteboard (Miro, Mural, Jamboard)
• Printed templates or digital canvases: How-Might-We, Assumption Map, Hypothesis Canvas
• Sticky notes, markers, timer, projector, and a clear recording device (photo or export)

Suggested half-day agenda (approx. 3.5–4 hours)

1. Welcome & outcomes — 15 min: Explain purpose, outputs, and how results will be used. Name the decision this workshop should inform.
2. Collect & cluster inputs — 30 min: Rapid round of participant notes and affinity clustering to surface themes.
3. Choose focus areas — 20 min: Dot-vote to select top 3–5 clusters for framing.
4. Reframe as opportunity statements (How Might We) — 30 min: Craft HMWs that translate clusters into changeable problems.
5. Assumption mapping — 40 min: For each HMW, map assumptions, evidence, and consequences; flag highest-risk items.
6. Hypothesis canvases — 45 min: Build minimal, testable hypotheses for top assumptions (split into pairs if needed).
7. Prioritize tests & decide next steps — 30 min: Prioritize experiments by impact & ease; assign owners.
8. Wrap & commitments — 10–15 min: Confirm owners, timelines, and immediate next actions.

Facilitation notes & prompts

Collect & cluster inputs

Ask participants to write single-sentence observations focused on behaviors, not opinions. Use prompts such as:

• "When X happens, what frustrates you?"
• "Describe a recent customer interaction that surprised you."
• "What's a repeated support request that slows us down?"

Cluster quickly; don’t over-engineer early synthesis. Preserve nuance by tagging notes with roles or data sources.

How Might We guidance

Use the pattern: "How might we [enable/avoid/reduce/increase] for [user/stakeholder] so they can [outcome]?" Keep HMWs generative and in-scope. Avoid prescribing solutions in the statement.

Assumption mapping (practical)

For each HMW, list assumptions that must be true for the opportunity to matter: user need, willingness to change, feasibility, and viability. For each assumption capture:

• Assumption (brief)
• Existing evidence (what we know right now)
• Impact if false (what fails)
• Ease to test (quick/cheap or slow/expensive)

Hypothesis canvas (fields)

• Opportunity / Problem statement (1–2 sentences)
• Target user / context
• Explicit assumption to test
• Minimal test (what you will do and with whom)
• Observable success criteria (metrics or behaviors)
• Data to collect and who will collect it
• Owner and timeline (aim for 1–2 weeks)

Worked example (short)

Example inputs: "Customers abandon checkout on mobile" and "Support logs show many 'payment failed' errors."

Cluster → HMW

How might we reduce checkout abandonment on mobile so that shoppers complete purchases more often?

Assumption map (example items)

• Assumption: Mobile users are abandoning due to payment errors — Evidence: support logs show errors, but unclear how many are genuine payment failures — Impact if false: redesigning checkout won't help — Ease to test: quick (collect error rates & user session recordings)
• Assumption: Users can’t find the coupon field — Evidence: anecdotal; Impact: small conversion uplift if true; Ease: very quick to test via user observation
• Assumption: Mobile UI performance causes abandonment — Evidence: slow page load metrics on some devices; Impact: high; Ease: moderate

Hypothesis canvas (example)

• Opportunity: Reduce mobile checkout abandonment
• Target: Mobile shoppers on Android with 3G networks
• Assumption to test: Payment errors in logs correspond to actual failed payments for customers (not reporting artifacts)
• Minimal test: Correlate server-side payment gateway responses with session IDs for 100 recent checkout attempts; interview 5 affected users
• Success criteria: Confirm whether >60% of logged 'payment failed' events are real; if real, identify common gateway errors; if not, identify logging bug
• Data/collector: Payments analyst will run correlation; UX researcher will interview users; timeline: 5 working days
• Owner: Payments lead; Next action: run data pull and schedule interviews

Typical outputs (artifact examples)

• HMW statements (2–4 prioritized)
• Assumption map with 'high impact, low evidence' items flagged
• Hypothesis briefs ready for experiments
• Experiment backlog with owners, timelines, and measures

Prioritization method (quick)

Use an impact vs ease matrix. Rate each hypothesis on estimated impact (1–5) and ease to test (1–5). Prioritize high-impact, high-ease tests first, then high-impact/low-ease if the decision owner commits resources.

Roles during the workshop

• Facilitator: manages time, enforces guardrails, prevents solution jumping
• Scribe: captures artifact content clearly and exports photos/exports
• Decision owner: makes quick scope decisions and commits resources where needed

Common pitfalls & guardrails

• Solution fixation: ask "What do we actually need to learn?" before proposing designs
• Ill-defined problems: insist on observable behaviors and measurable outcomes
• Skipping evidence: require at least one piece of evidence or an explicit 'no evidence' note
• Overloading experiments: prefer small, fast tests that give clear signals

Adaptations

For a 60–90 minute sprint: collect inputs beforehand, focus on 1–2 HMWs, and run a single assumption map + hypothesis canvas. For a full day: add user-story mapping, rapid persona sketching, and extended experiment design with prototypes or data queries.

Follow-up (within 48–72 hours)

1. Circulate photographed artifacts and filled canvases
2. Add hypothesis briefs to an experiment backlog or tracker
3. Schedule first experiment kickoff with owners and data collectors
4. Plan a short review (1–2 weeks after experiment) to inspect learnings and plan next steps

Suggested templates & filenames

• OpportunityFraming_Agenda.pdf
• HowMightWe_Template.pdf
• AssumptionMap_Canvas.pdf
• HypothesisCanvas_Template.pdf
• ParticipantWorksheet.pdf
• FacilitatorNotes_Checklist.pdf

Measurement ideas (examples)

Design success criteria that are observable and time-bounded. Examples:

• Increase conversion by X percentage points within 4 weeks of the experiment
• Reduce time to complete a task by Y minutes among tested users
• At least Z users perform the target behavior during the test window

Quick facilitator script (short)

Start by naming the decision this workshop will inform. Keep asking: "What assumption would make this idea worthless?" Push teams to the smallest, quickest test that will give a clear signal. If someone proposes a solution, ask: "What would we need to prove first before spending time building that?"

Accessibility, remote, and inclusion tips

• Allow remote participants to add notes directly to the board; appoint a remote co-facilitator to monitor chat and breakout rooms.
• Use short rounds for voice contributions and allow written input for people who prefer it.
• Provide materials in advance and use high-contrast colors and readable fonts on shared boards.

Where this kit can grow (capability suggestions)

This Workshop Kit is an excellent candidate to become an adaptive, ownable toolkit for teams. Consider adding:

• An interactive Hypothesis Canvas form that teams can fill and submit (so hypothesis briefs are saved automatically)
• Automated capture of assumption maps and hypothesis submissions into an experiment backlog or tracker
• Pre-built dashboards showing experiment status and recent learnings

Suggested image search phrase

workshop facilitation materials