Energy Levels Retrospective

Energy Levels Retrospective

The Energy Levels retrospective is built around a question that most sprint retrospectives dance around rather than ask directly: how drained or charged is the team right now — and what's causing it?

Every sprint generates energy signals. A dependency gets resolved without drama and the whole team feels momentum. An unplanned scope change lands on Wednesday and the week closes with people running on fumes. Individually these signals feel like background noise. In aggregate, they're the story of whether your team is moving toward sustainable pace or slowly accumulating debt it can't see. Energy Levels gives that story a structure.

This format works best when brought in with intention. It's not a replacement for your standard reflective formats — it's a targeted check-in for when motivation, engagement, or pace is the real issue under the surface.

When to choose Energy Levels

• After a high-pressure sprint. Crunch weeks leave invisible residue — quiet frustration, reduced initiative, a slightly shorter temper in Slack. Energy Levels creates the right container to name what happened and decide what changes.
• When engagement feels off. If people are completing tasks but not contributing ideas, or if retrospectives themselves are getting quieter, that's an energy signal. This format makes the conversation explicit without putting anyone on the spot.
• When sustainable pace is slipping. Agile's 12th principle says teams should maintain a constant pace indefinitely. If you're noticing sprint-over-sprint capacity strain, Energy Levels surfaces the specific drains before they compound.
• Quarterly team health checks. Standard sprint retros focus on recent events. A quarterly Energy Levels session zooms out — teams identify cumulative drains they've normalised and Recharge ideas that are structural rather than tactical.
• Before a long stretch. Pre-holiday periods, multi-sprint milestones, or upcoming team changes are moments when naming energy expectations in advance prevents capacity surprises mid-run.

Warm up: ⚡ Energy Check

Before the board opens for brainstorming, take the team's temperature.

1. Start icebreaker music and let it play as the team joins. Pick something that matches the energy you want to create — calm and reflective, or upbeat if the team needs a lift.
2. Switch on Brainstorming mode so everyone writes privately. No peeking.
3. Post the prompt in ⚡ Energy Check: "How charged are you feeling right now? Add a number — 1 (empty battery) to 5 (fully charged) — and one word."
4. Reveal — once every card is in, the facilitator switches off Brainstorming mode. Every score appears at once.
5. Read them out without comment. If the average is below 3, name it plainly: "We're starting this retro with a low-energy team. That's exactly why we're here."

The Energy Check column stays on the board throughout the session as a visible anchor. It's useful to glance back at when the conversation drifts — teams sometimes discover their discussion has moved far from the signals people flagged at the start.

🔋 Fully Charged

What energised the team this sprint?

Fully Charged captures the momentum: the collaboration that clicked, the technical decision that simplified rather than complicated, the stakeholder who unblocked rather than added work. These aren't just celebrations — they're replicable patterns. When the team names what charged them up, the implicit question becomes: how do we protect and repeat this next sprint?

Encourage specificity here. "The backend team picking up front-end cards when we were blocked" is far more useful than "good teamwork." Specific examples create specific lessons.

🪫 Drained

What sapped the team's energy or motivation?

Drained is where the real signal lives. Recurring meetings that could be emails. An unclear acceptance criterion that sent a card back three times. Tooling friction that nobody has owned fixing. Scope that arrived mid-sprint without capacity adjustment. These aren't complaints — they're system failures waiting to be addressed.

Frame Drained explicitly as systems, not people. "Unclear requirements at sprint start" invites a process conversation. "Product always sends unclear requirements" derails into blame. The facilitator's job is to keep the column pointed at structures, not individuals.

🔌 Recharge

What changes would restore or sustain the team's energy?

Recharge is the heart of this format. This is where ideas for structural improvement live — adjusting team rituals, redistributing types of work, protecting focus time, investing in tooling that removes chronic friction. Unlike a standard "What needs to change" column, Recharge is explicitly framed around energy restoration, which tends to generate ideas about process health rather than just task management.

Aim for at least two concrete action items from this column. Recharge items that are too vague — "better communication" — should be pushed to specifics during the discussion: what would better communication look like in practice next sprint?

💡 Spark

One idea or experiment to try next sprint

Spark is a forward-facing close. After naming what drained the team and what would recharge it, Spark asks: what's one thing — a small experiment, a new habit, a tool to test — that the team could run next sprint? Framing it as an experiment reduces the commitment pressure and increases the likelihood it actually happens.

---

Facilitating the discussion

After the brainstorm, a time split that works well:

• Energy Check — 5 minutes (read the scores, note the average, move on)
• Fully Charged — 10 minutes (brief celebrations; identify replicable patterns)
• Drained — 20 minutes (group clusters; vote on the highest-impact items)
• Recharge — 20 minutes (convert top Drained items into concrete experiments)
• Spark — 5 minutes (pick one idea, assign an owner, set a check-in date)

Use anonymous voting on Drained and Recharge. It prevents the loudest voice from defining which drains matter most — the person who hasn't spoken in three sprints often has the most useful signal to contribute.

Variations

Energy heatmap. Before the session, ask everyone to share their Energy Check score in a shared doc or mood poll. Plot scores over the past three sprints and use the trend as a discussion opener. A downward trend is a more compelling argument for process change than a single low-score retro.

Two-column sprint check. If the team is under pressure and a full 60 minutes isn't available, run just Drained + Recharge with a 30-minute timebox. Skip the warm-up narrative; go straight to brainstorm. It's less nuanced but still surfaces actionable items.

Quarterly Energy Audit. Run a 90-minute Energy Levels session every quarter using Pulse Survey data from the previous three months to pre-populate Drained with evidence. Survey data grounds the conversation in patterns rather than recency bias — teams are often surprised which drains have been present since the start of the quarter.

Related formats

• Mad Sad Glad — When you want broader emotional reflection rather than a focus specifically on motivation and sustainable pace. Good to alternate with Energy Levels every few sprints.
• Hot Air Balloon retrospective — When the team needs to combine backward reflection with explicit forward risk planning in the same session.
• KALM retrospective — When you want to audit practices directly (Keep, Add, Less, More) rather than through an energy lens.
• Starfish retrospective — When the team wants more granular practice-level feedback across five action-oriented dimensions.

All formats are available on every TeleRetro plan. See pricing for details.

Start an Energy Levels Retro View all retro templates

---

Frequently Asked Questions

What is the Energy Levels retrospective template?

The Energy Levels retrospective is a five-column agile format that treats team motivation and engagement as measurable signals, not background noise. Fully Charged surfaces what keeps the team energised, Drained names what's depleting it, Recharge generates actionable ideas for restoring sustainable pace, and Spark gives the team a forward-looking nudge toward experiments. The warm-up column, Energy Check, doubles as a lightweight team health check-in before the board opens. Unlike emotion-first formats like Mad Sad Glad, Energy Levels focuses specifically on pace and motivation — making it practical for teams managing workload, not just feelings.

When should you use the Energy Levels retrospective?

Use the Energy Levels retrospective after a sprint with unusually high pressure, when team members seem disengaged or unusually quiet, when you're noticing capacity strain sprint after sprint, or when you want to address sustainable pace before burnout becomes visible. It's also well-suited to quarterly check-ins, where the Recharge column generates the kind of structural changes that don't surface in standard sprint retrospectives. Teams in long-running projects benefit from rotating this format in every 4–6 sprints to catch drift in motivation before it becomes a retention risk.

How do you run an Energy Levels retrospective effectively?

To run an effective Energy Levels retrospective, follow these steps:

• Set the stage — Open with a mood check-in and explain the five columns. Emphasise that Drained is about systems and workload, not people
• Warm up — Turn on icebreaker music and switch on Brainstorming mode. Ask everyone to add one card to ⚡ Energy Check: how charged do they feel right now, from 1 (empty) to 5 (full battery)?
• Brainstorm — Give 10 minutes for silent brainstorming across Fully Charged, Drained, Recharge, and Spark. Keep Brainstorming mode on so no one second-guesses what they write
• Group and sort — Group and sort similar cards. Drained usually clusters fastest — pay attention to which themes repeat
• Vote — Use anonymous voting to prioritise. Spend no more than 10 minutes on Fully Charged and at least 20 on Drained and Recharge combined
• Create action items — Assign owners to the top Recharge items. Every recurring Drained theme should produce at least one concrete experiment
• Share summary — Export the retro summary and track actions across sprints

A standard session runs 60 minutes. If the Energy Check scores average below 3, allocate an extra 10 minutes to Recharge.

How is Energy Levels different from Mad Sad Glad?

Mad Sad Glad is an emotion-first format — it asks how the team feels without prescribing a lens. Energy Levels is motivation-first — it specifically asks what charges the team up, what depletes it, and what concrete changes would help. This makes Energy Levels more directly actionable when sustainable pace is the issue. The two formats complement each other well: use Mad Sad Glad to take a broad emotional temperature, use Energy Levels when the symptoms point specifically to workload, pace, or motivation.

What are some alternatives to the Energy Levels retrospective?

If you're looking for different retrospective formats, consider these alternatives:

• Mad Sad Glad — When you want broader emotional reflection rather than a specific focus on motivation and sustainable pace
• Hot Air Balloon — When you need to combine backward reflection with explicit forward risk planning in the same session
• KALM retrospective — When you want to audit practices directly (Keep, Add, Less, More) rather than through an energy lens
• Starfish retrospective — When the team wants more granular practice-level feedback across five action-oriented dimensions

Energy Levels remains the strongest choice when sustainable pace, motivation, or engagement is the primary concern heading into the session.