Best when vs. Avoid when

Decide fit before you spend session time.

Best when

Cross-functional teams are stuck in recurring complaints without a path to action — the method converts venting into an owned shortlist in one session.
Stakeholder alignment is low, debate is high, and the team needs a structured decision without open-ended discussion taking over.
A decision is needed by end of day and the room has the authority to commit to the top actions without escalation.
A team has tried to prioritise informally and keeps cycling back to the same disagreements — the LDJ pace prevents relitigating.

Avoid when

The problem needs root-cause analysis backed by external data — LDJ works from the room's lived experience, not from evidence gathered outside it.
Only one decision-maker is present — the method produces a shortlist through collective prioritisation; a single voice produces a to-do list, not a commitment.
The team has fundamentally different values or priorities that need alignment before any action can be agreed — LDJ will surface this but cannot resolve it.

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

Collect pain points

What happens

Individuals capture key blockers silently, one per note.

Facilitator does

Set a three-minute individual writing timer and enforce silence. Stop anyone presenting or explaining before the board is full — the pace is the method. One pain per note, written as a specific observed problem, not a general frustration. If someone writes "communication issues," ask them to rewrite it as a concrete incident: when, what happened, what was the effect.

Participants do

Write from personal experience — specific blockers you have observed or felt, not problems you've heard about secondhand. One concrete pain per note.

Output / signal of success

15–25 distinct pain notes on the board, each describing a specific, observable problem with no solutions embedded.

Watch for

Pain points are written as solutions in disguise ("we need a better dashboard," "we should meet less").

Recovery tip

Stop the board. Read the note aloud and ask: "What is happening right now that makes this feel necessary?" Write that answer as the pain point instead. The solution gets parked for Step 3.

Step 2

Convert to challenge statements

What happens

The room votes on the top pains, then rewrites them as How Might We challenge prompts.

Facilitator does

Run a dot vote on pain points first — three dots per person. Then take the top-voted pain and model the reframe together before releasing for independent work: "We have too many status meetings" becomes "How might we keep everyone informed without requiring attendance?" The HMW format prevents solution anchoring. Block any challenge that names a specific feature or tool.

Participants do

Rewrite the top pains as How Might We questions that open the solution space rather than closing it. If your HMW names a technology or tool, rewrite it to describe the underlying need.

Output / signal of success

3–5 challenge statements on the board, each written as a question that could be answered multiple ways — readable by someone outside the team without additional context.

Watch for

Challenge statements are too abstract to generate useful solutions against ("How might we improve our culture?") or too narrow to open options ("How might we build a better Slack channel?").

Recovery tip

For too-abstract challenges, ask: "What specific situation would this fix?" For too-narrow ones, ask: "What underlying need does this address?" Rewrite from those answers before moving to Step 3.

Step 3

Generate solutions

What happens

Individual silent sprint generating solution ideas against the top challenge statement.

Facilitator does

Post the winning challenge statement visibly and keep it on screen throughout. Set a four-minute silent sprint — one solution idea per note, quantity over quality. After time, run a second vote. Keep one challenge visible at a time; if the room has three challenge statements, run three separate sprints. Do not open discussion between sprints.

Participants do

Generate against the visible challenge statement only — not against the other challenges on the board. If an idea addresses a different challenge, write it on a separate note and label it.

Output / signal of success

20–30 solution ideas on the board per challenge, varying in scale and approach, showing clear divergence in direction.

Watch for

Participants solve against multiple challenges simultaneously, producing a mixed board where ideas can't be traced back to specific challenge statements.

Recovery tip

Stop the sprint. Sort the board visually by challenge statement before continuing. If ideas don't map to any challenge, park them in a separate zone and return if time allows.

Step 4

Vote and assign

What happens

Vote on top solutions, assign owners, and commit to a next checkpoint date.

Facilitator does

Give each participant three votes for solutions. After voting, take the top 3–5 voted solutions and force the critical question: "Who owns this and what is the first concrete action?" An unowned action is not an output — it is a note. Hold the room until every shortlisted action has a named owner and a committed next step written next to it.

Participants do

Vote for solutions you would actually support implementing, not the ones that are most creative or familiar. Accept ownership only if you have the authority and capacity to take the first action.

Output / signal of success

3–5 actions on the board, each with a named owner, a first action in specific terms, and a checkpoint date agreed before the session closes.

Watch for

Voting produces a tie and the room re-opens general discussion, stalling the commit step.

Recovery tip

Break ties by asking: "Which action, if we only did one thing this week, would most change the situation?" Force a single answer before continuing. Ties are usually the result of two actions that could be combined — ask if they can merge.

Prep and materials

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

Minimum viable evidence

A room of 4–12 people with direct, firsthand experience of the problems being discussed. LDJ works from lived experience, not from research or data analysis. If the right people aren't in the room, the pain points will reflect whoever is present — and the actions will be owned by people who can't actually implement them.

Pre-work

Problem context
Optional
Operational context note
Optional
Bring examples, pain points, or service evidence the room can point to quickly.

Room setup

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

Tools / materials

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

Templates

LDJ board
Optional
Pain, challenge, solution, and action lanes.
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 LDJ action list has 3–5 items, each traceable to a specific challenge statement that came from a specific pain point. Each action has a named owner, a first concrete next step (not "explore further"), and a checkpoint date agreed in the room. The pain points that didn't make the shortlist are visible and saved — they are not discarded, they are deferred. A weak output is a list of broad intentions with no owners, or a list that jumps from pain directly to action without any challenge reframing step in between.

What this does not produce

LDJ produces a prioritised action shortlist from the room's own experience and judgment. It does not produce a validated diagnosis of root cause, and it does not surface problems the room isn't already aware of. If the real problem is outside the room's direct experience — in customer data, operational data, or external research — LDJ will produce confident actions that address the wrong thing.

Red flags to correct before closing

Skipping challenge reframing.
Leaving actions without owners.

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

Challenge reframing gets skipped under time pressure

Why it happens

Step 2 feels like a process detour when the room already knows what the problems are and wants to jump to solutions. Facilitators under time pressure skip from pain collection to ideation, and the solutions that emerge address symptoms rather than the underlying challenge.

Recover now

If this happens, stop ideation, turn the top pain into one visible challenge statement, and only then restart solution work.

Prevent next time

Next time, make challenge statements a visible gate before solution generation starts.

Failure mode

Actions leave the session without owners or next steps

Why it happens

The session ends on the high of a voted shortlist and the room assumes someone will pick things up afterward. Without explicit ownership assigned in the room, actions default to whoever called the meeting — or to nobody.

Recover now

If this happens, hold the room on the shortlist, assign one owner per action, and confirm the next checkpoint before you close.

Prevent next time

Next time, reserve the final step for owners, dates, and explicit follow-through.

Failure mode

Pain points describe the desired solution, not the current problem

Why it happens

Participants come to the session with solutions already in mind. Writing "we need a better reporting tool" feels specific and concrete, but it's a solution brief disguised as a pain point. It collapses the challenge reframing step and channels all ideation toward one predetermined direction.

Recover now

If this happens, read the note aloud and ask: "What is happening right now because we don't have this?" Write that answer as the pain. Park the solution note in a separate zone — it may become a valid solution idea in Step 3.

Prevent next time

Next time, before Step 1 opens, write one example of a strong pain note and one weak one on the board and keep both visible during the collection phase.

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.

SessionLab - Lightning Decision Jam
AJ&Smart facilitation method reference.
SessionLab - Decision-Making Facilitation Methods
Workshop decision frameworks and facilitation structures.

Reviewed 2026-04-17 by Discovery Waypoint Editorial Team

Related methods

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

Use instead when

Experience Principles Workshop

Choose this if the room still has the same overall job but needs a different move than lightning decision jam (ldj style).

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

Use instead when

Opportunity Solution Tree (Lightweight)

Choose this if the room still has the same overall job but needs a different move than lightning decision jam (ldj style).

A simplified OST session that maps strategic outcome to opportunity areas and candidate solutions, then identifies where evidence is needed next.

Use instead when

Impact vs Effort Prioritisation

Choose this if the room still has the same overall job but needs a different move than lightning decision jam (ldj style).

A rapid prioritization matrix where initiatives are scored by expected impact and implementation effort to identify quick wins and strategic bets.

Use instead when options are still thin

Concept Poster / Concept Cards

Switch to this if the team is trying to choose too early and needs more directions on the table first.

A method where teams package concepts into one-page posters or cards with audience, value, flow, assumptions, and evidence needs.

Lightning Decision Jam (LDJ Style)

Best when vs. Avoid when

Best when

Avoid when

Is this the right room for this method?

Runbook

Collect pain points

Convert to challenge statements

Generate solutions

Vote and assign

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

Challenge reframing gets skipped under time pressure

Actions leave the session without owners or next steps

Pain points describe the desired solution, not the current problem

Adjust for your room

What to do next

References

Known method, unclear next move?

Atlassian Team Health Monitor