Moneyball Teams
If you search "We only hire the best," you'll discover that literally everyone only hires the best. How can 100% of businesses hire from the top 5% of the talent pool? What happens to the other 95% of developers?
The answer is simple: it's nonsense. Nobody hires exclusively the best, nor should they. We don't even have industry-wide objective metrics to measure developers consistently.
This post explores how to build strong teams focused on total throughput instead of hiring based on abstract criteria where you can only hope for the best.
Learning from Baseball Economics
In 2002, a pathologically losing baseball team in California faced a death blow: losing their star player. The 2011 film "Moneyball" documents how this revenue-poor team completely changed their hiring strategy and started winning games, permanently changing how team managers think about talent acquisition.
Oakland's team budget was 100 million. They achieved the same results with a fraction of the resources by applying basic math and statistical analysis to player evaluation.
The movie is really about math and business management rather than sports. It demonstrates how focusing on the right metrics can overcome resource constraints through smarter decision-making.
Rethinking the Goal of Hiring
Your company's ambitions eventually exceeded what your development teams could deliver, forcing you to hire. The ultimate goal should be helping your team match your business ambitions.
Hiring "the best" seems obvious, but reveals two hidden traps:
The widening capability-vs-ambition gap: If business ambitions grow constantly, they'll be out of sync with team capabilities. More work enters the system than can be completed. Reducing business ambitions to match team throughput makes you less likely to grow your product or innovate.
The Individual Excellence Trap: Team throughput fluctuates due to upstream product changes, unclear direction, technical challenges, debt, process issues, and focus dilution. Hiring a brilliant individual may not address these systemic problems. Your "10x developer" could have their productivity divided by 10 when placed on a dysfunctional team.
The traditional view treats developers as interchangeable units with different capability levels ("Senior" or "Junior"). This ignores the open secret that one Senior Developer may be capable of wildly different things than another. This mindset implies individual contributors act as teams of one, rather than members who set each other up for success.
A Better Hiring Framework
Business success requires positive return on investment over time. If hiring aims to increase throughput, the correct investment should maximize total business throughput, not simply add individual capability.
The goal isn't increasing "lines of code per day" or tickets completed per week. It's improving overall business delivery capacity, which may require changing business processes themselves.
Skills Matrix Done Right
Most teams have Frontend/Backend developers, and hiring often focuses on increasing role specialization. However, teams need non-discipline-specific skills to function effectively. These sometimes surface in culture interviews, but we can do better with stronger focus.
A skills matrix becomes powerful when used correctly, but degenerates into trivia contests about algorithms, data structures, and syntax when used poorly. Focus your matrix on things teams do regularly:
- Technical discussions
- Code review
- Architecture decisions
- Scaling solutions
- Testing practices
- Code quality maintenance
- Mentoring others
- Pragmatic problem-solving
- Collaboration and motivation
Not all of these are technical skills, reflecting the reality that software development involves human factors as much as code. Choose skills meaningful to your specific organization.
Map these skills against mastery levels:
- Developing: Uninformed but learning
- Proficient: Consistently applies skill well
- Expert: Mentors others and leads thinking
This framework clarifies your next investment decisions. Should you hire to cover specific team weaknesses? Which team members need training? Can you run peer mentorship programs? Do you have unchallenged experts with no growth opportunities?
The Power of Focused Thinking
Consider typical brainstorming sessions. Someone (usually the boss) stands at a whiteboard asking for random ideas, makes on-the-spot judgments, and after four hours the consensus covers only obvious or undesirable options.
Edward de Bono's "Six Thinking Hats" system addresses this problem by focusing intellectual effort into specific modes that ensure multiple perspectives. Teams using this system generate more innovative solutions faster and understand exactly what skill balance various tasks require. A team of average people can achieve amazing results without requiring 150+ IQs.
Apply this focused, specialized thinking to team building. Look for lateral solutions rather than always hiring more developers. Demand for "top x%" talent is highly competitive, time-consuming, and expensive.
Scale Horizontally, Not Vertically
Instead of always seeking individual excellence, consider:
- Process improvements that multiply team effectiveness
- Tool investments that reduce friction
- Training programs that elevate team capabilities
- Collaboration structures that leverage diverse strengths
- Clear communication that reduces rework and confusion
The goal is building teams where the whole exceeds the sum of parts, rather than collecting individual superstars who may not work well together.
Focus on total team throughput. Measure what matters for business outcomes. Invest in the combinations of skills and people that will actually move your organization forward.
Sometimes the best hire isn't the most impressive individual contributor. Sometimes it's the person who makes everyone else more effective, or fills the gaps.