The Hero Worship Trap
The Problem
Celebrating peak performance and hero moments while ignoring the power of consistent improvement. You reward the developer who pulled three all-nighters to save a project that shouldn't have been in crisis. You praise the "rockstar" who ships brilliant work sporadically but burns out teammates. Meanwhile, the person steadily raising their output 5% each month—the one who never creates drama, never misses deadlines, just keeps improving—gets overlooked. Peak performance feels exciting. Consistency feels boring. But consistency wins championships. Heroes cause chaos.
The Principle
PERSONAL AVERAGES OVER PEAK PERFORMANCE: Dean Furness wisdom that changed everything: "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 how teams transform. What is a personal average? Not your best day. Not your worst day. Your TYPICAL day. How much do you typically ship? How many problems do you typically solve? How much value do you typically create? The compounding effect: Week 1 average goes from 5 to 5.5 (+10%). Month 1 average is now 6 (+20% from baseline). Quarter 1 average hits 8 (+60% from baseline). Year 1 you can't recognize how fast you're moving (+150%+ from baseline). When everyone's personal average rises together, organizational fitness rises to levels you never thought possible. Help people see their baseline. Track small improvements—5% better is celebration-worthy. Compare to self, not others. Make progress visible over months. Remove barriers to improvement. Celebrate consistency over flash. Steady improvers beat heroes. Every. Single. Time.
3 Steps to Take Action
- 1
Track Personal Averages: Measure each person's typical output weekly. Not best, not worst - typical. Chart it over time. Make progress visible.
- 2
Stop Rewarding Heroics: No more praise for all-nighters or "saving the day." Celebrate people who steadily improve their average month over month.
- 3
Remove Barriers Systematically: What's slowing people down? Approval delays? Data access? Unclear requirements? Fix one barrier per sprint. Watch averages rise.
In Practice
A BI team had a hero problem. Jake—the "rockstar"—would swoop in, pull all-nighters, ship a dashboard, and save the day. Leadership loved Jake. Gave him raises, promotions, public praise. Nobody noticed Jake created the crises he "saved." Bad planning. Poor communication. Then heroics to fix it. Meanwhile, Maria quietly delivered. Every week. On time. Good quality. Her "typical week" output: 0.5 dashboards per person. Not exciting. Just consistent. New manager tracked the team's actual output: Maria's consistent 0.5 had compounded to 26 dashboards that year—all still in production, all still used. Jake's heroics? 8 dashboards. 5 were retired within months due to quality issues. Manager changed the game: stopped celebrating heroes. Started tracking "personal averages" for everyone. Focused on removing barriers—approval delays, data access issues, unclear requirements. Six months later: Maria's average was 2.1 dashboards per person per week (4x improvement). No heroics. No all-nighters. Just sustained removal of barriers and small improvements compounding. Jake quit because he wasn't getting hero praise anymore. Team productivity went UP after he left. Turns out heroes are expensive and consistency is priceless. The tortoise lapped the hare.
