Best when vs. Avoid when

Decide fit before you spend session time.

Best when

A team has a stated strategic objective but no shared understanding of what user progress it requires — everyone is optimising toward different proxies.
Multiple teams are working toward the same goal but making contradictory prioritisation decisions in their own planning cycles.
A new discovery cycle is starting and the team needs a single shared frame before splitting into research streams.
An executive has set a direction but the delivery team cannot yet connect it to what users would need to do or believe differently.

Avoid when

Outcome metrics are already agreed, stable, and tied to active work — running this session creates confusion rather than clarity.
The need is sprint-level planning, not discovery direction — this method produces a framing sheet, not a backlog.
No executive or product leader with authority to commit to a north-star outcome is in the room — without that, the framing sheet will be overwritten by the first planning cycle that follows.
The team has no strategic objective at all — use Problem Framing first if the objective itself is unclear.

Runbook

The core facilitation flow, with enough structure to run the method confidently in the room.

Standard setup for Mixed in remote delivery.

Total planned time: 90 min

Step 1

Define north-star outcome

What happens

Select one measurable strategic outcome.

Facilitator does

Write the candidate north-star on the board and apply this test aloud: 'Is this measuring what the product ships, or what the user can do because of it?' A product milestone ('launch the new onboarding flow') fails. A revenue metric without a user behavior attached ('grow ARR 20%') is incomplete. A user behavior change with a measurable signal ('first-time users complete a meaningful action within 7 days') passes. Rewrite until it describes user progress, not product output.

Participants do

Propose candidate outcomes and test them against the user progress question. Argue for specificity over comfort — a vague north-star produces vague opportunity areas downstream.

Output / signal of success

One outcome statement is written on the board, agreed by the room, and passes the user progress test. The product leader in the room can commit to it as the frame for the discovery cycle.

Watch for

The north-star outcome names a product release or feature delivery rather than a change in what users can do, believe, or experience.

Recovery tip

Ask: "After we ship this, what should a user be able to do that they couldn't before?" Write that answer on the board. That is the north-star candidate — not the feature that enables it.

Step 2

Map user progress

What happens

Describe user progress needed to reach outcome.

Facilitator does

For each progress step, apply the solution filter: 'Is this describing what the user does, or what the product releases?' Block any step that sounds like a sprint deliverable. If participants struggle to write in user-progress language, prompt them: 'What would a user need to be able to do, believe, or feel differently at this stage compared to the one before?'

Participants do

Describe capability or behavior changes in the user — not feature milestones, not team deliverables. Each step should be something a user could recognise as meaningful progress in their own experience.

Output / signal of success

3–6 progress steps are on the board, each describing a change in user capability, behavior, or belief. A person outside the team could read the sequence and understand what the user's journey toward the north-star looks like.

Watch for

Progress steps map to product releases or sprint cycles — the sequence describes what the team builds, not what changes for the user.

Recovery tip

Stop the sequence. Pick one step and ask: "If a user sat down at their computer, what would they actually do differently at this stage?" Rewrite from that answer. Run the same test on each remaining step.

Step 3

Frame opportunity areas

What happens

Generate and cluster opportunity statements linked to the user progress map.

Facilitator does

Before generating, write the solution test on the board: 'Can you build this directly? If yes, it's a solution — rewrite it as the user gap that makes the solution relevant.' Apply this test to every opportunity statement before it gets placed. 'Build a better onboarding checklist' fails — it's a feature. 'New users don't know what value they've unlocked in their first week' passes — it's a gap. Stop the room every time a solution gets placed as an opportunity.

Participants do

Write opportunities as user gaps, unresolved friction points, or unmet needs — not as feature directions. Each statement should complete this sentence: "Users currently can't / don't / won't…"

Output / signal of success

4–8 opportunity areas are on the board, each written as a user gap that passes the solution test. The opportunities connect visibly to the progress steps mapped in Step 2.

Watch for

Opportunity statements are solution briefs with the solution language thinly disguised — 'improve the search experience,' 'redesign onboarding,' 'simplify the dashboard.'

Recovery tip

Say: "Let's strip the solution out. What is the user experiencing right now that makes this a problem?" Write the answer. That rewritten version — describing the gap, not the fix — is the opportunity statement.

Step 4

Commit discovery focus

What happens

Pick top opportunities and owners.

Facilitator does

Before selecting, write this question on the board: 'If we were wrong about this opportunity, what would we stop building?' The areas where the answer is 'a lot' are the right discovery focus — being wrong about them would significantly change the plan. The areas where the answer is 'not much' are low-uncertainty bets. Flag that distinction visibly. Assign one owner and a research start date to each selected area before the session closes.

Participants do

Select based on uncertainty and proximity to the north-star — not familiarity or team preference. Commit to ownership and start dates in the room, not after.

Output / signal of success

The completed north-star framing sheet is on the board with 1–2 selected opportunity areas, each with a named owner and a research start date. The product leader has confirmed the framing sheet reflects the discovery direction they can commit to.

Watch for

The room selects opportunity areas that feel safe or familiar — the ones the team already has a hypothesis about — and avoids the areas where uncertainty is genuinely highest.

Recovery tip

Ask: "Which opportunity, if we ignored it and were wrong, would most change what we build?" If that area isn't in the selected set, ask why. Name the tension explicitly before closing.

Prep and materials

Prepare the room, the evidence, and the working surface so the session can stay focused on synthesis.

Minimum viable evidence

A stated strategic objective from the product or business leader who has authority to commit to a north-star outcome. It can be rough — a direction, not a metric. Without it, the framing sheet will be overwritten by the first planning cycle that follows the session. If no one in the room can commit to an outcome direction, use Problem Framing first to establish one.

Pre-work

Strategic objectives
Optional
Current baseline metrics
Optional
Constraint list
Optional
Operational context note
Optional
Bring examples, pain points, or service evidence the room can point to quickly.

Room setup

Opportunity framing board
Optional
Remote facilitation choreography
Required
Pre-plan handoffs, breakout usage, and how people rejoin the main board.

Tools / materials

Opportunity framing board
Required
Shared digital board with timer and voting
Required
Keep instructions and voting visible at all times.

Templates

North-star framing board
Optional
Outcome, user progress, opportunities, constraints.
Open reference

Run well / recover fast

Keep the output usable, then use the recovery guidance when the room starts drifting.

What strong output looks like

Make the output legible to both sponsors and delivery owners.
A well-formed north-star framing sheet has one outcome statement written as user progress (not a product milestone), 3–6 user progress steps describing capability or behavior changes (not feature releases), and 4–8 opportunity areas written as user gaps or unresolved friction. The top 1–2 selected opportunities have named owners and research start dates. A weak output has a north-star that describes what the product ships, progress steps that map to sprint cycles, and opportunity areas that are feature briefs with the solution language thinly stripped out.

What this does not produce

North Star Framing produces a discovery direction — a shared frame for what to investigate and why. It does not produce a prioritised roadmap, a validated outcome metric, or a solution direction. The opportunity areas named in this session are hypotheses. Each one requires research before it can carry a plan. Teams that treat the framing sheet as a roadmap skip the discovery step the method was designed to protect.

Red flags to correct before closing

Mixing too many strategic goals.
Opportunity statements that are actually solutions.

Re-state decision objective and expected artifact
Timebox discussion and force owner assignment
State what the artifact is confident about versus what still needs tailoring.

Failure mode

North-star outcome is a product milestone, not a user behavior change

Why it happens

Product teams default to what they control — releases, features, deployments — when asked what success looks like. 'Launch the new dashboard' feels measurable and specific; 'users can monitor their key metrics without opening a second tool' feels vague until it's written down. The instinct is to name the output, not the outcome it's supposed to create.

Recover now

If this happens, ask: 'After we ship this, what should a user be able to do that they couldn't before?' Write that answer on the board. That is the north-star candidate — not the feature. Replace the milestone with the behavior change it was supposed to produce.

Prevent next time

Next time, open Step 1 by writing two examples on the board — one milestone (fails) and one user progress statement (passes) — so the room has a concrete reference before they start proposing candidates.

Failure mode

Opportunity statements are disguised solutions

Why it happens

In rooms with engineers or product managers, solution framing arrives faster than opportunity framing because it's more comfortable. 'Users need a better search experience' feels like an opportunity but has already narrowed the solution space. The room reaches for solution language because sitting with an open gap feels unresolved — and unresolved feels unsafe in front of stakeholders.

Recover now

If this happens, apply the solution test aloud: 'Can you build this directly?' If yes, say: 'That's a solution — what user gap makes it relevant?' Write the gap, not the solution. Run the test on every statement that has a verb in it.

Prevent next time

Next time, write the opportunity framing test on the board before Step 3 begins, and model it with one example before anyone generates statements.

Failure mode

Executives leave after Step 1 before opportunity areas are framed

Why it happens

Leaders often feel their job is done once the north-star outcome is agreed. Step 1 feels high-stakes and strategic; Steps 2 and 3 feel like delivery detail. They disengage or drop off, and the opportunity framing in Steps 3–4 loses the authority it needs — particularly around which opportunities are in-scope for the initiative.

Recover now

If this happens, before Step 2, explicitly name the executive's role in the remaining steps: 'We need your judgment in Step 3 on which opportunity areas are inside or outside what this initiative is allowed to pursue. That call can't be made without you.'

Prevent next time

Next time, include the executive's Step 3 role in the pre-session brief: 'You will be asked to mark opportunity areas as in-scope, out-of-scope, or escalation-required before the session closes.'

Adjust for your room

Change the shape of the session only after the fit and runbook are clear.

Open adjustment controlsStandard setup for Mixed in remote delivery.

Session depthChoose how much time and interpretive depth this session can realistically hold.Who this session is forSet the balance between sponsor framing, operational detail, and shared synthesis language.How you will run itOptimize for either physical wall-space or one tightly managed shared board.

Standard variant for Mixed in remote delivery. Waypoint is adapting timing, facilitation emphasis, prep, and recovery guidance here, but the room still needs final tailoring to the exact stakes and participants.

What to do next

Use this after you have checked the fit and know you want to carry the method forward.

The pack is the fastest way to run this now. Use the links below when you need prep, sharing, or a saved reference point.

Jump to prep and materials

References

Sources and references used in this method page.

Product Strategy and Opportunity Framing
Continuous discovery and outcome-driven product strategy references.
IDEO Design Kit - Co-creation and Alignment Methods
Facilitation approaches for alignment and shared framing.

Reviewed 2026-04-16 by Discovery Waypoint Editorial Team

Related methods

A short curated set of adjacent methods so the page feels guided, not database-driven.

Use before commitment

Stakeholder Mapping

Bring this in when the room is converging on a direction but still needs to surface the key risks before locking it in.

A structured map of people and groups who influence the outcome, their level of power, and their current stance.

Use instead when

Current vs Future State Mapping

Choose this if the room still has the same overall job but needs a different move than north star opportunity framing.

A side-by-side map of current-state reality and target future-state outcomes.

Use instead when

Experience Principles Workshop

Choose this if the room still has the same overall job but needs a different move than north star opportunity framing.

A workshop to define a small set of experience principles that guide decisions, trade-offs, and quality expectations across teams.

Use instead when

Design Principles to Metrics

Choose this if the room still has the same overall job but needs a different move than north star opportunity framing.

A translation workshop that maps experience principles to behavioral measures and leading indicators so teams can track whether principles are actually delivered.

North Star Opportunity Framing

Best when vs. Avoid when

Best when

Avoid when

Is this the right room for this method?

Runbook

Define north-star outcome

Map user progress

Frame opportunity areas

Commit discovery focus

Prep and materials

Minimum viable evidence

Pre-work

Room setup

Tools / materials

Templates

Run well / recover fast

What strong output looks like

Red flags to correct before closing

North-star outcome is a product milestone, not a user behavior change

Opportunity statements are disguised solutions

Executives leave after Step 1 before opportunity areas are framed

Adjust for your room

What to do next

Read why this works

References

Known method, unclear next move?

Atlassian Project Kickoff

Amazon PRFAQ / Working Backwards

37signals Shape Up