Lightning Retrospective

Lightning Retrospective format

Lightning Bolts

What sparked energy and drove progress this sprint?

Lightning Bolts represent the standout moments, wins, and actions that generated real momentum during the sprint. Encourage the team to think about specific events, decisions, or behaviours that felt like a sudden burst of positive energy. This is the team's chance to celebrate what worked and understand why it worked, so those sparks can be repeated.

Thunder Clouds

What created noise, friction, or slowed the team down?

Thunder Clouds represent the rumbles of friction — the blockers, miscommunications, and inefficiencies that created drag during the sprint. Encourage the team to be honest but constructive. The goal isn't to assign blame but to identify patterns of disruption so the team can address them. Ask the team to focus on systemic issues rather than one-off incidents where possible.

Power Surge

How can we amplify our energy and supercharge the next sprint?

Power Surge is the forward-looking, action-oriented topic of the retrospective. Encourage the team to think boldly about what changes, experiments, or improvements would give them the biggest boost in the next sprint. Push for specific, actionable ideas rather than vague aspirations. Help the team commit to one or two high-impact actions they can realistically deliver, and assign clear ownership before the session ends.

When to use this retrospective

• When your team's retrospectives have started to feel repetitive or low-energy and you want to inject fresh momentum into the continuous improvement process.
• When running a short sprint or a time-pressured iteration and you need a retrospective format that delivers real insights without taking up too much time.
• When a team has recently faced a high-intensity period of work and you want a format that matches their energy and helps them process both the highs and the lows.
• When onboarding a new team to agile retrospectives and you want a format that's engaging, easy to understand, and memorable thanks to its vivid metaphors.
• When you want to balance celebrating wins, addressing friction, managing risks, and planning improvements all within a single focused session.

Suggested icebreaker questions

• If your energy this sprint were a weather event, what would it be and why?
• If you could harness the power of lightning for one superpower at work, what would it be?

Ideas and tips for your retrospective meeting

• Keep it fast and focused — the Lightning Retrospective is designed to be energetic and time-boxed. Aim for 45–60 minutes total and use a timer to keep each topic moving. Resist the urge to deep-dive on every point; save detailed discussions for dedicated problem-solving sessions.
• Encourage everyone to contribute before the discussion begins. Having all team members add their ideas independently first helps surface diverse perspectives and prevents the loudest voices from dominating the conversation.
• Don't let the Power Surge topic become a wishlist. Help the team narrow down to one or two concrete, actionable improvements with clear owners and a timeline. Unowned actions rarely get done.
• Watch out for the Thunder Clouds topic becoming a venting session. Acknowledge frustrations, but gently redirect the conversation toward understanding root causes and identifying what the team can actually control or change.
• Use the Ground Wires topic to surface issues that might otherwise stay hidden. Psychological safety is key here — remind the team that raising a risk early is a sign of strength, not weakness.
• Revisit the actions from your last Lightning Retrospective at the start of the session. Celebrating completed actions and acknowledging incomplete ones builds accountability and shows the team that retrospectives lead to real change.