How to run a Lightning Decision Jam workshop

Some team problems attract plenty of opinions but still lack a route to a decision. The same concerns return in planning meetings, proposed fixes multiply, and the group eventually agrees to continue the discussion elsewhere. This is tactful, but not terribly productive.

A Lightning Decision Jam, often shortened to LDJ, is a timed decision making workshop. It gives that conversation a firm sequence: collect the issues, choose what matters, reframe the chosen problem, then compare possible actions by impact and effort. The 80-minute format below works for 2 to 10 people and produces a decision direction rather than another handsome collection of notes.

If you want the facilitator built into the session, Clarvelo’s Lightning Decision Jam runs the same 80-minute sequence and manages the prompts, timeboxes and private vote.

What this decision making workshop covers

AJ&Smart created the original Lightning Decision Jam and publishes an official LDJ resource page. Shorter versions often stop after choosing and reframing a problem. This 80-minute workshop adds time to develop possible actions and compare them, so the team leaves with a realistic next move rather than a well-labelled problem.

The session combines four activities: Round Robin, Blind Vote, How Might We and an Impact Effort Map. Each output becomes the input to the next activity. That connection matters more than any individual template. Without it, a Decision Jam can feel like four energetic exercises that happen to share a calendar invitation.

Prepare a decision worth making

Give the session a clear boundary. “How do we improve delivery?” is too large. “What should we change to reduce avoidable delays between code review and release?” is specific enough to examine. State what the group can decide, any fixed constraints, and who will own the result. Do not invite people to choose if the answer has already been settled elsewhere.

Invite participants who see different parts of the problem. Ask them to bring examples rather than prepared speeches. Useful evidence might include customer feedback, incident records, delivery data or a recent case. A Decision Jam can structure judgment, but placing a vague hunch on a board does not make it more factual.

Lightning Decision Jam agenda

Protect the full 80 minutes. The Lightning Decision Jam agenda below is the whole workshop, not a buffet of optional extras. If you skip the last two steps, you still have a prioritized problem and no agreed action.

• 20 minutes: collect problems, fixes and constraints with Round Robin
• 10 minutes: select the most useful issues with a Blind Vote
• 25 minutes: reframe selected problems with How Might We questions
• 25 minutes: compare actions on an Impact Effort Map and assign follow-up

Facilitator checklist

• Name one decision area the group can influence
• Invite 2 to 10 people with different views of the problem
• Bring recent examples, evidence and firm constraints
• Decide who can commit to the final direction
• Protect the full 80 minutes from other agenda items

Lightning Decision Jam steps

The Lightning Decision Jam steps are the same four activities, in order. Do not rearrange them. Collecting after you have already voted, or mapping actions before you have a How Might We question, quietly turns the workshop back into an ordinary meeting.

1. Gather the field with Round Robin

Use 20 minutes for Round Robin. Give each person a turn to contribute one concrete problem, candidate fix or action constraint. Continue around the group until the useful material is visible. Ask short clarifying questions: when did this happen, who was affected, and what makes it costly? Keep one idea per contribution so later voting remains intelligible.

Name something the team could recognize in practice. We need events and effects, not a general sense that the process is a bit wonky.

Turn-taking prevents the fastest speaker from setting the entire agenda. It should not become an interrogation or force everybody to invent a novel point. Passing is allowed. The aim is broad collection, including dissent and constraints, before the group starts defending solutions.

2. Narrow the problem with a Blind Vote

Spend 10 minutes choosing which contributions best support clear next steps. Set the criterion before collecting votes: importance, confidence in the evidence, and usefulness after the workshop. Let people vote privately, then reveal the result together. Private voting does not remove authority, but it gives the decision owner a less distorted view of the room.

Select a manageable number of problems for the next stage, usually one or two. Record close alternatives and material objections. A vote is a prioritization signal; it does not prove that the minority is wrong. If a sponsor chooses against the result, note why. Hidden overrides are an efficient way to make the next vote decorative.

3. Reframe with How Might We questions

Use 25 minutes to turn the selected problems into How Might We questions. Good questions remain anchored in the evidence while allowing several responses. “How might we stop release delays?” is broad. “How might we help reviewers identify release-blocking changes before the final approval?” gives the team a useful target without smuggling in a preferred feature.

Write independently first, then compare and combine genuine duplicates. Test each question: does it name the relevant moment or person, permit different answers, and sit within the team’s influence? Choose the strongest frames and generate candidate actions. Keep ambitious ideas visible, but distinguish them from actions the team could actually start.

4. Compare actions on an Impact Effort Map

Give the final 25 minutes to mapping candidate actions by expected impact and implementation effort. Agree what impact means for this decision and make estimates relative, not theatrical. Discuss differences in placement because they often reveal hidden assumptions about dependencies, risk or who must do the work.

High-impact, lower-effort options are sensible starting points, not an automatic answer. A difficult action may address the real cause while an easy one merely tidies the edges. Finish by naming selected actions, an owner, a trigger or start date, and a checkpoint. Park the rest explicitly so nobody leaves believing every sticky note is now a commitment.

Lightning Decision Jam examples

A useful Lightning Decision Jam example is a recurring operational problem the group can actually change. “What do we drop when mid-sprint sales requests arrive, given that some protect renewals?” is a Decision Jam. “Why do our sprint plans keep changing?” is a diagnosis, and “How should we think about strategy?” is too large.

Other examples that fit: a release that slips for the same reason every cycle, a support queue that grows because ownership is unclear, or a planning meeting that always ends with “let’s take this offline.” In each case, collect specific events, vote on which pattern matters most, reframe it as a How Might We question, then compare two or three actions the team could start this week.

Do not use a Decision Jam to decorate a choice that has already been made, to teach decision-making theory, or to fill a Miro template. If you want a board, the workshop still works; the board is not the product.

Why AI changes the Decision Jam

This workshop looks simple on paper, but its value depends on the handoffs. Somebody must collect several participants’ contributions, protect quieter voices, close each timebox, summarize without erasing disagreement, run a private vote and carry the selected problems into reframing. They must then move candidate actions into the map and make the final commitments usable.

Reliable facilitation without a routine consultant budget

A skilled consultant is worthwhile for a fraught or consequential decision. Few teams have the budget to hire one whenever an ordinary operational problem gets stuck. The usual substitute is a template operated by the product manager, engineering manager or whoever made the mistake of being visibly organized.

Clarvelo actively facilitates the workshop. It introduces the exercises, gathers input from everyone, manages transitions and timeboxes, runs voting, synthesizes the material and prompts for actionable outputs. Teams can use reliable process facilitation for routine decisions as well as special occasions with a consultancy line in the budget.

The diligent organizer can join the decision

The person who organizes the workshop often holds important context. When they also explain Round Robin, monitor speaking order, watch four clocks, prepare the vote and rearrange the map, their attention is spent on operating the room. Their contribution arrives late or not at all.

With Clarvelo running the process, that organizer contributes and votes on the same terms as everybody else. Simultaneous collection gives reflective and quieter participants room before discussion takes over. Structured synthesis keeps minority concerns attached to the options, while explicit transitions show how one exercise’s result becomes the next exercise’s input.

AI facilitation does not supply evidence or make political trade-offs disappear. Serious conflict and high-stakes decisions may need independent human judgment. For the recurring decisions that otherwise drift through three meetings, a consistent facilitator and a visible output are a considerable improvement.

Frequently asked questions

How long does a Lightning Decision Jam take?

Plan for 80 minutes. Shorter LDJs often stop after choosing and reframing a problem. This agenda also develops candidate actions and compares them by impact and effort, so the team leaves with a realistic next move.

How many people should join a Decision Jam?

Two to ten people works well. Invite people who see different parts of the problem. Larger groups dilute simultaneous contribution and make private voting harder to interpret.

What do you need before the workshop?

A decision the group can influence, a few recent examples or constraints, and an uninterrupted 80 minutes. You do not need a Miro board, sticky notes pack or a trained facilitator if Clarvelo is running the session.

Can a product or engineering manager facilitate without specialist training?

Yes for routine operational decisions. The hard part is keeping timeboxes, collecting input evenly and carrying outputs between exercises. Clarvelo handles that process so the organizer can contribute on the same terms as everyone else. High-stakes conflict may still need an independent human facilitator.

How is an AI-facilitated LDJ different from a template?

A template is a board someone still has to operate. Clarvelo introduces each activity, gathers input, runs the private vote, synthesizes material and keeps the handoffs visible. Guests join from a link without creating accounts on a whiteboard tool.

Turn the next stuck discussion into a decision

Clarvelo’s Lightning Decision Jam guides 2 to 10 people through Round Robin, Blind Vote, How Might We and an Impact Effort Map. Guests join from a link, while the AI facilitator introduces each activity, keeps context visible and records the selected direction.

Have a stuck discussion worth closing? Start a free Lightning Decision Jam. Bring the people and the examples; Clarvelo will run the workshop process.