Lightning Decision Jam Template

An LDJ includes both problem definition and solution generation in a single 60-minute session, whereas a [brainstorming session](/templates/brainstorming-template) focuses only on solution generation for a pre-defined problem. The LDJ also includes effort/impact mapping and experiment definition, taking the team all the way from "what is wrong?" to "what will we try this week?"

Respect the vote. The PM's perspective is already represented in the voting (they get 3 dots like everyone else). If the PM believes the team voted based on incomplete information, they can share the missing context during Step 4 (reframing) and ask if the group wants to reconsider. Do not override the vote unilaterally.

Yes. Use Miro or FigJam with pre-built sticky note areas for each step. The silent writing and voting phases translate well to remote. The facilitator needs to be more active about calling time and managing transitions since physical cues (people putting down markers) are not visible.

For defining experiments, yes. For solving the entire problem, no. The LDJ produces 1-2 small experiments, not a final solution. Run the experiments, learn from the results, and schedule another LDJ if the problem persists. The iterative approach is more reliable than trying to solve everything in one long meeting.

Monthly or bi-weekly works well for most teams. Some teams run a 30-minute LDJ at the end of every sprint retro to convert the top retro item into an experiment. The key is making it a recurring practice, not a one-time event. Problems that resist a single LDJ often yield to two or three iterations. ---