As leaders, we’ve all encountered a team that’s struggling—an underperforming group that seems stuck in a cycle of missed deadlines, low morale, or inconsistent delivery. It’s tempting to double down on oversight or push harder for results, but I’ve learned that the real breakthrough comes from giving that team a voice. Not just a platform to vent, but a structured way to articulate their challenges, take ownership of their work, and show upper management what they’re capable of achieving with the right support.
The key? Pairing accountability with visibility through meaningful metrics—drawn from DevOps, CI/CD, and Agile practices—and using those numbers to tell a story of progress, not just problems.
Step 1: Empower Through Accountability
An underperforming team often feels voiceless because they’re caught in a reactive loop—firefighting issues without a clear path to improvement. To break that cycle, start by giving them ownership of their process. This isn’t about blame; it’s about trust. Introduce common DevOps and Agile metrics that resonate with their day-to-day work and align with broader goals. Think:
- Cycle Time: How long does it take to move a task from “in progress” to “done”? This shines a light on bottlenecks without pointing fingers.
- Deployment Frequency: Are we shipping small, frequent updates or stuck in long, risky release cycles? This ties directly to CI/CD maturity.
- Mean Time to Recovery (MTTR): When things break, how quickly can we recover? This reflects resilience, not just failure.
- Sprint Velocity: Are we consistently delivering value, or are scope creep and interruptions derailing us?
These aren’t just numbers—they’re a language the team can use to define their reality. Sit down with them, set baselines, and agree on what “better” looks like. The act of measuring empowers them to hold themselves accountable, shifting the narrative from “we’re failing” to “we’re improving.”
Step 2: Turn Metrics Into a Megaphone
Here’s where leadership steps up. An underperforming team rarely has the clout to get the resources or attention they need from upper management. That’s your job. Take those same metrics—cycle time, deployment frequency, MTTR, velocity—and weave them into a story for the C-suite. Don’t just dump data on their desks; show trends.
For example: “Three months ago, our cycle time was 14 days due to manual testing bottlenecks. We’ve brought it down to 7 days by automating key checks, but we’re still capped by limited QA bandwidth. With one more engineer, we could hit 4 days—unlocking faster feedback and happier customers.” Suddenly, the team’s struggle isn’t a complaint; it’s a business case with a clear ROI.
This approach does two things: It gives the team visibility—proof they’re not just spinning their wheels—and it positions you as a leader who bridges the gap between boots-on-the-ground reality and executive priorities.
Step 3: Celebrate Progress, Not Perfection
Metrics aren’t a stick to beat the team with; they’re a compass. Celebrate upward trends, even if they’re incremental. Did deployment frequency jump from once a month to twice? That’s a win. Did MTTR drop by 20% after a post-mortem led to better alerting? Shout it out. These milestones build momentum and morale, showing the team their voice is being heard—and acted on.
Upper management notices this too. When they see consistent progress tied to tangible outcomes (faster delivery, fewer outages, happier stakeholders), they’re more likely to invest in the team—whether it’s headcount, tools, or training. That support fuels the flywheel: accountability drives improvement, improvement earns trust, and trust unlocks success.
The Payoff: A Team That Speaks for Itself
I’ve seen this play out with a team that was drowning in technical debt and missed deadlines. We started small—tracking cycle time and velocity to pinpoint where they were stuck. They owned the numbers, I amplified their story, and within two quarters, we secured budget for a new CI/CD pipeline. Deployment frequency tripled, morale soared, and the team went from “underperforming” to a case study in resilience. They didn’t just find their voice—they became a chorus.
Leadership isn’t about fixing every problem yourself. It’s about giving your team the tools to define their challenges, the metrics to measure their progress, and the visibility to earn the support they need. When you do that, you’re not just lifting a struggling team—you’re setting them up to lead.
Leave a Reply