Lightning Retrospective

A fast three-column retro for short or busy sprints.

Try this retrospective live

Lightning Bolts

What sparked energy and drove progress this sprint?

The mid-sprint demo with the client was a real lightning bolt. Their excitement gave the whole team a boost and clarified our direction instantly.
Pairing up on the tricky API integration made a big difference. We unblocked ourselves in hours instead of days.
Our daily standups have been super focused lately. Short, sharp and actually useful.
Thunder Clouds

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

Too many interruptions from outside the team mid-sprint. It's hard to stay in flow when we're constantly context-switching.
Requirements kept shifting after we'd already started building. We need a clearer definition of ready before we pull work in.
The deployment pipeline was flaky again. We lost a lot of time waiting on builds that should have taken minutes.
Power Surge

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

Let's try a quick 10-minute team sync at the start of each day focused purely on blockers. No status updates, just unblocking.
I'd love to introduce a 'no meeting Wednesday' so we can get deep work done without interruption.
We should set up automated alerts for build failures so we're not discovering problems hours later.

What is the Lightning Retrospective?

The Lightning Retrospective is a short, energetic format for teams that want to reflect without a long meeting. It borrows the imagery of a thunderstorm: lightning for the moments that drove progress, thunder clouds for the friction that slowed you down, and a power surge for the changes that would give the next sprint a lift. The board has three columns. Lightning Bolts captures the wins, decisions and habits that created momentum, so you can repeat them. Thunder Clouds collects the blockers, miscommunication and drag, with the focus on patterns over one-off bad days. Power Surge is the forward-looking column, where the team picks one or two concrete changes and gives each an owner. Each column is meant to be quick: short notes, a fast vote and a focused discussion on the top items. It suits teams on short sprints and teams whose retros have started to drag. You can explain it in a minute, and most teams finish in under an hour.

Lightning Retrospective format

Lightning Bolts

What sparked energy and drove progress this sprint?

Lightning Bolts are the standout moments, wins and decisions that created real momentum this sprint. Ask the team for specific events or behaviors that felt like a burst of energy, then ask why they worked so you can repeat them.

Thunder Clouds

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

Thunder Clouds are the friction: blockers, miscommunication and anything else that created drag. Keep it honest and blameless. The goal is to find patterns the team can fix, so steer toward systemic issues over one-off incidents.

Power Surge

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

Power Surge is the forward-looking column. Ask which changes or experiments would give the next sprint the biggest lift, and push for specific ideas over vague hopes. Help the team commit to one or two it can realistically deliver, and give each an owner before the session ends.

When to use this retrospective

  • When your retrospectives feel repetitive or low on energy and you want a quicker format.
  • When you're running a short sprint and need a retro that gets to actions without taking much time.
  • After an intense stretch of work, when the team wants to process the highs and lows without a long meeting.
  • When introducing a new team to retrospectives and you want a format that's easy to explain.
  • When you want to cover wins, friction and next steps in one 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?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Keep it moving. Aim for 30–45 minutes and use a timer for each column. Save deep dives for a separate problem-solving session.
  • Have everyone add ideas on their own before discussion starts, so the loudest voices don't set the agenda.
  • Don't let Power Surge become a wish list. Narrow it to one or two concrete changes with owners and a timeline, because unowned actions rarely get done.
  • Watch for Thunder Clouds turning into a venting session. Acknowledge the frustration, then steer toward root causes and what the team can actually change.
  • Ask people to add risks to Thunder Clouds as well as problems that already happened. A risk raised early is much cheaper to deal with.
  • Start by reviewing the actions from your last Lightning Retrospective. Acknowledging what got done, and what didn't, shows the team that the retro leads to change.

Frequently asked questions

What is a Lightning Retrospective?
It's a fast retrospective with three columns: Lightning Bolts for what sparked progress, Thunder Clouds for what slowed the team down and Power Surge for changes to try next sprint.
How long does a Lightning Retrospective take?
Most teams finish in 30 to 45 minutes. Three columns, a short timebox for each and a quick vote keep it tight.
When should a team use a Lightning Retrospective?
Use it for short or busy sprints, or when your usual retro has started to drag. It still ends with one or two concrete actions, just in less time.
How is it different from Start Stop Continue?
Both are short and simple. Start Stop Continue sorts ideas by what to change, while the Lightning Retrospective sorts them by what helped, what slowed you down and what would give the next sprint a lift.
Can remote teams run it?
Yes. In TeamRetro everyone adds ideas privately, then the team groups, votes and agrees on actions together. The short format suits distributed teams that struggle to find a long meeting slot.

Related templates

WWE Smackdown Showdown Retrospective

Tag-team your sprint review with a wrestling theme.

Working, Not Working Retrospective

Sort what's working from what isn't, then fix it.

Quarterly Retrospective

Step back from the sprints and review the whole quarter.

Baby Steps Retrospective

Pick one small change your team will actually finish.

Ready to run this retrospective?Try this retrospective live