Product Manager as Leader Without Authority
The PM job isn't specs or interviews; it's leading via influence so the product wins in the market
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 3
- Confidence
- 90%
Product management is different at every company and has no standard training, so PMs fixate on tasks (specs, press, requirements docs) and mistake them for the job. The actual job is fundamentally a leadership job made tricky because nobody reports to you. Your real objective is to get a product into market that customers love and that beats anything anyone else ships. Everything else is optional tooling toward that end.
Origin
The thesis behind Horowitz's famous 'Good Product Manager, Bad Product Manager,' written out of frustration for his Netscape team in ~1996 when talented PMs kept missing the concept.
Core principles
- 01The job is a leadership job that's hard precisely because no one reports to you
- 02Your job is a product customers love that's better than anything else in the market, not any specific task
- 03Real leadership is influence without the levers of promotion, firing, or pay
- 04A PM is effectively the CEO of the product: keeper of the vision who consolidates and prioritizes ideas, not the source of every idea
How to run it
- 1
Redefine the job as the outcome, not the tasks
State your job as: get a product into market that customers love and that beats anything anyone else in the world ships. Specs, interviews, and PR documents are tasks that may or may not serve that.
Pro tip When you catch yourself measuring success by whether you wrote a good spec, re-anchor on whether the product wins.
Watch out Different companies emphasize different tasks; don't let whichever task your org fixates on become your definition of the job.
- 2
Lead through influence, not authority
Since you can't pay, fire, or promote anyone, get people to do what's needed by giving engineering clarity about the market, competitors, and technology, and by understanding engineering with equal clarity.
Pro tip Leaning on formal authority is a crutch; building influence now is what makes you capable of ever being a CEO.
Watch out If you find yourself yelling at people, you probably haven't clearly explained what you want; explanation, not authority, is the tool.
- 3
Own the vision and consolidate ideas
Act as keeper of the vision: gather the good ideas, prioritize them, decide which to build, and get everyone to a high-fidelity shared understanding of it.
Pro tip You don't need to originate every idea; a CEO who sources every idea is misunderstanding the role, and so is a PM.
In the wild
At Netscape around 1996 Horowitz had a very talented product team (including future VMware CEO Raghu Raghuram) who kept missing that the job was leadership, not task-completion. Rather than keep yelling, he wrote the concept down to explain what he wanted.
→ The internal memo, published later, became one of the most-linked pieces of product-management literature and is still shared despite Horowitz's own note that its task-specific details are dated.
Common mistakes
Mistaking tasks for the job
Getting wrapped around specs, press, or requirements docs treats the tooling as the goal; none of those are the job, which is a winning product.
Yelling instead of explaining
When people aren't doing what you want, frustration usually means you failed to clearly explain the goal, not that they need more pressure.
Is it for you?
Best for
Product managers, and any cross-functional lead who must drive outcomes without direct reports
Not ideal for
Roles where authority genuinely is the right lever, or PMs at a stage where a specific deliverable (e.g., a regulatory spec) truly is the priority
From the transcript
“the job is fundamentally a leadership job and it's a tricky leadership job because nobody is actually reporting to you”
“your actual job is to get a product into market that customers love that's better than anything that anybody else in the world puts in…”
“How do I get people to do what I want?”
From the episode
$46B of hard truths from Ben Horowitz: Why founders fail and why you need to run toward fear (a16z co-founder)