The Power of One — a five-minute team-leader briefing
Why a briefing, not just the article
The agent-facing article works on its own. The briefing works better. A team that has the conversation together, sees the maths on a whiteboard, and hears their team leader land the point in their own words remembers it. A team that’s asked to “read this article” usually doesn’t. The briefing is what closes the loop.
The five-minute script (deliver as-is, or in your own words)
Open (30 seconds). “I want to spend five minutes today on something I’ve been thinking about. It’s about how each of you, individually, moves the service level we get measured on. The maths surprised me when I first saw it. I think it’ll surprise you too.”
The setup (1 minute). “We’re a team of [N] on the phones. We forecast somewhere around [X] calls an hour. Our service-level target is 80% answered in 20 seconds. When we’re staffed right, the maths just about works. When we’re short by even one person, the queue feels it within minutes.”
The maths (90 seconds). Walk through it on a whiteboard or flipchart. “Imagine we’re a team of twenty. Twenty agents on the phones, eighty per cent SL.” Draw a row of twenty dots, mark SL at 84%. “Now imagine one person steps off line for twenty minutes — an extended break, a long aux code, anything. The team becomes nineteen for those twenty minutes.” Cross out one dot. “The SL for that hour falls to about 70%. Dozens of customers wait longer than 20 seconds. That’s the whole hour’s SL, gone, from one person off line for twenty minutes.”
The flip side (45 seconds). “The same maths runs the other way. One agent coming back from break a minute early, taking one extra call, helping a colleague clear a complex wrap quickly — all of that moves the SL the right way. It’s why the agents I notice on the floor aren’t the ones who take the most calls. They’re the ones who show up at the right time, consistently, and make the easy choice when the queue is busy. That’s the power of one. One person. One choice. One hour. Visibly different customer experience.”
The why-this-isn’t-pressure line (45 seconds). “I want to be clear — this isn’t about watching every minute. Nobody’s expecting 100% productivity. The plan already assumes breaks, queries, system slow-downs, the lot. What it doesn’t assume is the avoidable stuff. The thirty-minute aux code that should have been three minutes. The casual no-show on a Saturday morning. The wrap-up that turned into a chat. The dial that’s moved by this conversation isn’t the maximum — it’s the consistency. And the consistency is what makes the operation hit its SL.”
The close (30 seconds). “You don’t need to work harder than you already do. You need to keep doing what you do consistently — on time, on code, on calls. The operation runs on that. Thanks. Good shift.”
The handout (one paragraph, on the desk)
Print this and leave on every desk for a week. “On this team, every one of you moves the SL. The maths proves it: one agent off line for 20 minutes on a team of 20 = a missed SL for that hour. The reverse is also true. Small choices add up. Coming back from break a minute early. Coding aux time honestly. Helping a colleague clear a tough wrap. Flagging a long call early to your TL. We don’t need miracles. We need the team being the team, consistently. That’s what makes the SL real. Thank you for the work.”
Common mistakes when running this briefing
Pitching it as pressure. “You need to do better” doesn’t belong in this briefing. The briefing is recognition that the work matters and explanation of how it stacks up. Pressure framing turns it into a stick and undoes the benefit.
Using it to single out poor performers. Never deliver this briefing the same day you’ve had a performance conversation with someone in the team. The connection will be obvious; the cultural cost will outlast the message.
Skipping the maths. The maths is what makes the point believable. Without it, this is a generic “everyone matters” speech that nobody remembers. Sketch the dots. Show the SL bars. Make it visible.
Doing it once and never again. One delivery is a moment; fortnightly delivery is a habit. Refresh the example each time — different numbers, different stories, different agents named for the right reasons. The frequency is what makes it part of the culture.
Tips for delivery
Pick a moment when SL was hit, not missed, to deliver it. The briefing lands as recognition then, not as criticism. Name a specific agent who exemplified the behaviour the week before, with their permission, and use it as the live example. Keep the language plain — the briefing should sound like you, not like a corporate cascade. End with the “good shift” line; don’t over-extend.
What good looks like a quarter later
If this briefing is delivered fortnightly and supported by the day-to-day recognition that goes with it (see incentives that actually work), three things become visible within a quarter. Adherence improves quietly — not enforced by the WFM team, but by the agents themselves. Aux-code usage becomes more honest. The team starts policing itself on long unscheduled breaks. None of those become punitive conversations; they just become the way the team works. That’s the briefing landing.
Conclusion
The Power of One isn’t a slogan. It’s a piece of arithmetic that makes the daily work visible. Delivered well, it’s the most under-used five minutes a team leader has. The script is here; the maths is on the whiteboard; the conversation is yours. Use it.
Pair this with the agent-facing Power of One, hosting a good morning standup, incentives that actually work, and coaching from QA results.