The Lightning Decision Jam: A Step-by-Step Guide for Leadership Teams

The Problem with Leadership Meetings

Picture your last leadership sync. The VP of Product and the Head of Sales spent 45 minutes debating "cross-functional alignment" while the rest of the room quietly checked Slack.

When the clock ran out, you ended the meeting with a muddled compromise and a vague promise to "circle back" next week. Sound familiar?

Open discussion is the default setting for most leadership teams, but it is a terrible way to solve problems. It favors the most extroverted people in the room, encourages circular debates, and rarely leads to concrete action.

If you want to move fast and actually fix operational bottlenecks, you need to replace open discussion with a structured process. This is where the Lightning Decision Jam (LDJ) comes in.

What is a Lightning Decision Jam?

Created by the design agency AJ&Smart, the Lightning Decision Jam is a highly structured workshop exercise designed to solve any problem quickly. It takes the best elements of design thinking and agile methodologies and strips them down to their absolute essence.

Instead of talking in circles, the team works through a series of rapid, timed exercises to identify problems, pitch solutions, and decide on next steps.

The secret sauce to a productive team isn't better tools or a bigger talent pool. It is replacing unstructured brainstorming with a process that provides clear guardrails.

For non-facilitators—like a Director of Engineering trying to fix a deployment pipeline, or an L&D manager trying to improve onboarding—the LDJ offers a foolproof structure. You do not need to be an expert facilitator to run it. You just need a timer, some sticky notes, and the willingness to enforce a few simple rules.

The Core Principle: Together, Alone

Before diving into the steps, you must understand the golden rule of the LDJ: Together, Alone.

During the ideation phases, nobody talks. Everyone works simultaneously in silence, writing their thoughts on sticky notes. This eliminates groupthink, prevents senior leaders from anchoring the discussion, and ensures that the quietest person in the room has the exact same volume as the loudest.

When you are planning your next agenda in METODIC (metodic.io), try dropping an LDJ into the slot where you would normally put "Open Discussion." Here is exactly how to run it.

Step 1: Start on a Positive Note (10 mins)

If you start immediately with problems, the room's energy will tank. You need to warm up the group and acknowledge what is actually working.

Draw a sailboat on a whiteboard. Draw a water line, with a sail catching the wind above it, and an anchor dragging below it. The wind represents things moving you forward. The anchor represents what is holding you back.

Set a timer for four minutes. Ask the team to silently write down everything that is currently working well regarding your topic. Use one sticky note per idea.

When the timer rings, have each person briefly read their notes and place them on the top half of the sailboat. No discussion or debate is allowed.

Step 2: Capture the Problems (5 mins)

Now, shift the focus to the anchors. What is frustrating the team? What is broken?

Set the timer for four minutes. Again, everyone works in silence, writing down problems, concerns, and bottlenecks. One problem per sticky note.

This time, participants do not read their notes aloud. This prevents people from feeling attacked or put on the spot. When the time is up, everyone simply walks to the board and places their notes on the bottom half of the sailboat.

Step 3: Prioritize the Problems (3 mins)

You cannot solve every problem in one session. You need to find the most critical issue.

Give each participant three dot stickers. Set a timer for three minutes and ask them to vote on the problems they believe are most important to solve right now. They vote in silence.

They can put all three dots on one massive issue, or spread them out. Once the voting is done, take the sticky notes with the most votes and arrange them in order of priority. You now have a clear, democratic mandate on what to tackle first.

Step 4: The "How Might We" Reframe (3 mins)

Take the top-voted problem. Let's say it says: "Marketing and Product are completely siloed and never share data."

If you ask the team to solve that statement, they will get defensive. Instead, you must reframe it as a standardized challenge using the "How Might We" (HMW) format.

• How assumes the problem is solvable.
• Might suggests there are multiple possible answers.
• We reinforces that this is a team effort.

Rewrite the problem as: "How Might We make Product and Marketing data visible to both teams by default?" This simple linguistic shift turns a complaint into a solvable puzzle.

Step 5: Ideate Solutions (6 mins)

Place your HMW question at the top of the board. Set the timer for five minutes.

The team now works in silence to write down as many potential solutions as possible. Emphasize that you want quantity over quality. A mass of half-baked ideas is better than three "perfect" ones, because you can curate and combine them later.

Remind the team to avoid filtering themselves. Even wild, unrealistic ideas can spark a practical solution from someone else.

Step 6: Prioritize the Solutions (5 mins)

Just like you voted on problems, you will now vote on solutions. Give everyone six dot stickers.

Set the timer for five minutes. The team silently reads the proposed solutions and votes for the ones they believe will best solve the HMW challenge.

Take the highest-voted solutions and prepare to map them out.

Step 7: Decide What to Execute (10 mins)

Draw a simple matrix on the board. The vertical axis is Impact (Low to High). The horizontal axis is Effort (Low to High).

Take the top-voted solution. Hover it over the center of the matrix and ask the team: "Is the impact higher or lower?" Move it up or down based on their consensus. Then ask: "Is the effort higher or lower?" Move it left or right.

Repeat this for your top solutions. You are looking for the "Sweet Spot"—solutions that are high impact and low effort. These are your actionable experiments.

Step 8: Make it Actionable (5 mins)

A solution is useless if nobody owns it. Take the ideas from your Sweet Spot and turn them into actionable experiments.

For each solution, define what the very next physical step is. Not a massive project plan, just the immediate next action. Assign an owner and a deadline.

For example, if the solution is "Create a shared dashboard," the actionable step might be: "Sarah will schedule a 30-minute call with the data engineer by Thursday to scope the dashboard requirements."

Stop Discussing, Start Deciding

The Lightning Decision Jam proves that you do not need long, painful meetings to achieve leadership alignment. By enforcing strict time limits and replacing open debate with silent ideation, you strip the politics out of problem-solving.

Next time your team is stuck in a rut, do not schedule another two-hour sync. Put a timer on the screen, hand out the sticky notes, and let the process do the heavy lifting.