In tech leadership, we often obsess over the 10x engineer, that mythical figure who can outperform a dozen peers and carry a complex project to completion. But as any seasoned manager knows, a team of five 10x individuals often performs worse than a team of five cohesive collaborators. (Whether you can attract and retain five 10x engineers is a different question).
To understand why, we can look at the two most iconic archetypes of greatness in basketball: Michael Jordan and Magic Johnson. For a tech leader, deciding which “player” to hire or which one to be is a strategic choice that determines the long-term health of your organization.
Michael Jordan – The “Vertical” Hero
Michael Jordan represents the pinnacle of individual output. In a tech context, this is the staff engineer who restores the outage at 3:00 AM, writes the entire core engine alone, modernizes a legacy system, and all in record time.
The Strengths: High velocity, uncompromising standards, discernment.
The Systemic Cost: Jordan’s leadership was fueled by pressure. He famously pushed teammates to their breaking point. In tech, this often leads to “Hero Culture,” where the system becomes dependent on a single node. If the “Jordan” of your team leaves, the system collapses because they were the only ones holding the knowledge. This is what happened to the Chicago Bulls very quickly after his departure.
The Internal State: Such leaders might suffer from high burnout because they feel they are the only ones doing the work.
Magic Johnson – The “Horizontal” Multiplier
Magic Johnson wasn’t just a scorer; he was a facilitator. His greatness was measured by how many assists he recorded. He looked for the open man before he looked for the basket.
The Strengths: He focused on the interfaces between players. In tech, this is the leader who prioritizes collaboration, documents, mentors others, and builds clean APIs that allow others to move faster.
The Systemic Multiplier: Magic’s value wasn’t just his own points. It was the +20% performance boost he got out of everyone else.
The Internal State: Such leaders find satisfaction in the success of the system. They don’t need to be the hero because they’ve built a great team.
Comparison: Impact
| Feature | Michael Jordan (The Hero) | Magic Johnson (The Multiplier) |
| Primary Metric | Individual Throughput | System Velocity |
| Leadership Style | Pressure & Expectation | Invitation & Facilitation |
| Skill development | Hoarded (to maintain speed) | Distributed (to maintain scale) |
| Team Reaction | Fear of failure, “Watch the master” | Permission to act, “Find the gap” |
The Systemic Refactor: Which are You Building?
If you are a tech leader, you may have started your career as a Michael Jordan. You were the “G.O.A.T.” But as you move into management, staying in Jordan mode becomes a bottleneck.
A consultant might tell you to delegate more. A trainer might teach you how to give better feedback. But as a systemic coach, I ask a different question:
“What is the internal script that tells you it’s safer to be the Hero than the Multiplier?”
Transitioning from Jordan to Magic is an internal refactor. It requires letting go of the ego that needs to win the game personally so you can become the Magic who designs a championship-winning system.
Key Takeaway for Tech Managers:
The manager is responsible for sustainable results and retention. Which archetype aligns better for your case?
- Jordan wins the battle (the sprint)
- Magic wins the war (the roadmap)
Some multiplier moments exhibiting rare game-intelligence:
For dessert, here are the epic last minutes of the 1992 NBA All-Star Game:
Leave a Reply