Leaders Don't Manage People. They Hand Them a Reason to Care.

There's a comfortable lie in most organizations: that leadership is a discipline of management — of slotting experienced people into defined roles and supervising the output. A clip of Steve Jobs describing how the original Macintosh team was built quietly takes that idea apart. What made Apple work, he argued, wasn't management at all. It was three things most companies get backwards.

Vision does the managing for you

Jobs' first claim is the one most leaders resist: the best people don't want to be managed. Hand a self-motivated person a shared vision and a problem worth solving, and supervision becomes redundant. They'll manage themselves — usually harder than you would have managed them.

The job of a leader, then, isn't to direct traffic. It's to make the destination so clear and so worth reaching that people organize their own effort around it. When the purpose is genuinely shared, you stop spending your energy on control and start spending it on clarity. That's a better trade for everyone.

Hire for belief, not résumé

Apple's hiring for the Mac wasn't a credential check. Candidates spent the better part of a day with the team, and at some point they were shown the prototype. The real interview was watching what happened in that moment. Did the person light up? Did they want in on what was being built?

That instinct cuts against how most hiring works. We screen for experience because it's measurable and defensible — nobody gets fired for hiring the veteran. But experience tells you what someone has already done, not what they'll pour themselves into next. Passion for the specific thing you're building is harder to detect and far more predictive. A team of people who believe in the product will outwork a team of professionals who are merely qualified to build it.

Bet on people before the evidence says you should

The boldest part of the story is Debby Coleman, who was put in charge of manufacturing with no manufacturing background. On paper, an indefensible call. In practice, her organizational ability was exactly what the role needed, and she became one of the team's most valuable people.

This is where vision and hiring converge into something rarer: the willingness to give people a stretch bigger than their track record. Most leaders wait for proof before they extend trust. The more powerful move is to read the underlying capability — judgment, drive, the way someone organizes chaos — and bet on it before the résumé catches up. People tend to rise to the size of the trust you place in them. The Mac team didn't just build a computer; many of them signed their names inside the case, because it was theirs.

What this asks of you

Blend the three and a different model of leadership emerges. You're not assigning tasks and checking boxes. You're articulating a vision compelling enough that people self-organize around it, recruiting for conviction rather than credentials, and trusting capability ahead of the evidence.

It's worth being honest about the cost. This approach is riskier than managing by the numbers. Betting on an unproven person sometimes fails. Hiring for passion over experience means occasionally backing the wrong enthusiasm. But the alternative — a building full of qualified people doing competent, uninspired work — is its own kind of failure, just a quieter one.

The practical question for any leader is simple: are you spending your energy controlling people, or giving them something they'd manage themselves to achieve? The teams that change things are almost always the second kind.

---

Inspired by Steve Jobs' reflections on building the original Macintosh team.