Steve Jobs: Managers and Bozos

I came across "bozo management" on the Blind App, and found it a surprisingly durable framing for a failure mode that shows up at nearly every scaling startup I've seen. Steve Jobs coined the phrase; the mechanics are worth unpacking.

If you cannot watch the video, here are the words from him.

We went through that stage at Apple where we thought, 'Oh, we're going to be a big company, let's go out and hire professional management.' We went out and hired a bunch of professional management; it didn't work at all. Most of them were Bozos. They knew how to manage, but they didn't know how to DO anything.

If you are a great person, why do you want to work for somebody you cannot learn anything from? And you know what's interesting - you know what the best managers are? They are the great individual contributors who never ever wanted to be a manager, but decide they have to be a manager because no one else is able to do as good a job as them.

Why the bozo explosion happens

The mechanism is a proxy failure. A growing company needs more managers than it can internally promote. HR, under pressure, hires on "years of management experience" because that proxy is easy to check against a résumé. The proxy assumes management is a generalist skill that transfers across industries — you managed a 30-person team at a Fortune 500, so you can manage a 30-person team here.

That assumption breaks for any technical or product-led company. Managing a team of engineers requires evaluating technical trade-offs that experienced-but-distant managers can't evaluate. They default to process (more meetings, more status updates, more escalation paths) because process is what they know. The team, which can evaluate trade-offs, stops bringing the hard problems to them — and once that happens, the manager becomes a reporting relay rather than a decision-maker. Multiply this by three layers of hierarchy and the organization's decision velocity collapses.

Jobs' point is that the better proxy is demonstrated excellence at the underlying work. A great engineer turned manager can still referee an architecture debate; a career manager who last wrote code in 2004 can only ask who the team consensus favors.

How to spot a bozo manager

The pattern is consistent once you know what to look for:

• Can't explain the actual work in technical detail. Asked about a specific trade-off their team is making, they redirect to "the team is looking into it" rather than taking a position.
• Escalates trade-off decisions rather than making them. Every hard call becomes a broader discussion or gets punted upward.
• Measures activity instead of outcomes. Weekly reporting emphasizes tickets closed, meetings held, docs written — not customer outcomes, revenue moved, or tech-debt paid down.
• Can't prototype, spec, or critique a design. In a whiteboard session, they listen and summarize rather than contribute.
• Defers all hard calls to "let's get the team's input." Consensus-seeking is a feature of good culture; consensus-dependence is a tell.
• Avoids the details where the real risk lives. They sit at a layer of abstraction above where the bugs and the bad decisions actually are.
• Hires people they can manage comfortably rather than people who challenge them. Over time, this is the most corrosive symptom — it compounds generationally.

Any one of these in isolation is noise. The pattern, repeated, is the signal.

When professional managers actually work

The nuance: "bozo" isn't a synonym for "career manager." Past a certain scale — somewhere in the 200-500 person range, depending on the business — pure managers become necessary. Cross-org coordination, career development, performance calibration, and process design are real skills that don't automatically come with IC excellence. Some of the best operators in tech history (Sheryl Sandberg, Tim Cook, Bill Campbell) were career managers who never shipped the flagship product themselves.

Andy Grove's framing in High Output Management helps here: a manager's output is the output of their team plus the output of teams they influence. At small scale, the leverage is technical and the best leverage comes from a manager who can make the hard technical call. At larger scale, the leverage is organizational — hiring, structure, incentives, unblocking — and a strong career manager can out-leverage a senior IC who got reluctantly promoted.

The failure mode isn't hiring career managers. It's hiring them too early, or installing them over ICs whose craft they can't respect.

Practical framework for founders

During the 10-100 person phase, three heuristics have held up well:

1. Promote from within before hiring external managers. Your senior ICs have context, trust, and — critically — the respect of the team. The downside is that some don't want to manage. Let them say no without penalty.
2. For external manager hires, require recent hands-on work in the same craft. "Engineering manager who wrote code in the last two years" is a different candidate pool than "engineering manager." The former pool is smaller; the hires are dramatically better.
3. Use trial projects, not interviews, to evaluate management hires. Have a candidate scope a real decision, write the doc, run the meeting. Interviews select for polish; trial projects select for judgment.

See also

• Simon Sinek: How Great Leaders Inspire Action? Golden Circle — on the "why" underneath leadership.
• Parkinson's Law of Triviality / Bikeshedding — another failure mode where process displaces substance.
• Good to Great — Jim Collins on Level 5 leadership and "first who, then what."