The Impatient Leader Trap
The Problem
Pushing your team too fast because you're impatient. You want everything simple. You trick yourself that it IS simple in your brain. You push for speed. "Why is this taking so long? Just do it faster!" But things are ALWAYS more complex than they seem on the surface. The infrastructure is brittle. The data is messy. The requirements keep changing. And if you push an individual, team, or organization too fast, you don't just slow them down—you dissolve the effort altogether. Burnout. Attrition. Quality crashes. The initiative dies.
The Principle
SUSTAINED PROGRESS OVER SPEED: Broad transformation is NOT made with home runs. It's made with progress by the WHOLE team, driving down the SAME side of the road, week over week, month over month. Dean Furness wisdom: "You just need to help people understand their own personal average, and ensure it gets better week over week, month over month, year over year." That's it. That's the secret. The magic formula: Individual + team + organization raising their personal average, over and over and over again, toward a shared mountaintop = unstoppable momentum. Speed is not the answer. Sustained progress is. Temper your enthusiasm: Your pace ≠ their pace. Accept this. Help people find THEIR sustainable pace. Track progress, not speed: Are we better this month than last? That's enough. Celebrate small wins. Tiny improvements compound into massive change. With sustained progress, you will eventually progress faster than you ever imagined. But only if you don't kill the momentum by being too impatient early. The tortoise wins this race. Every. Single. Time.
3 Steps to Take Action
- 1
Help People Find Their Average: What's their typical output? Not best day, not worst - typical. Measure it. Then work to raise it 5-10% per month. That's enough.
- 2
Track Progress Not Speed: Stop asking "why is this taking so long?" Start asking "are we better this month than last?" Celebrate small improvements.
- 3
Set Sustainable Timelines: Add 50% buffer to estimates. If team says 6 months, plan for 9. Better to finish early than burn out halfway through.
In Practice
A VP wanted to modernize their entire analytics stack. The realistic timeline: three years. The VP's timeline: six months. "We need to move faster! The competition is ahead!" Team warned: "This is too aggressive. We'll burn out." VP ignored them. "Work harder. Work smarter. Get it done." Eight weeks in? Three key people quit. Quality tanked. The VP's pet project—the one they pushed hardest—shipped with so many bugs it got pulled back within days. The initiative was shelved for a year while they rebuilt the team. New approach with new leadership: 18-month timeline. Clear monthly wins. Sustainable pace. Team improved 10% each month. Progress was visible on the walls. Morale stayed high. They finished in 16 months—two months ahead of schedule—with better quality, zero burnout, and a team that had grown stronger together. Features that shipped in month 3 were still running smoothly in month 16. The impatient VP learned the hard way: speed kills. The patient leader learned: sustained progress wins. Same team. Different approach. Completely different outcome. The tortoise beat the hare. Again.
