2014 HarperCollins

Overview

Before he became one of the most powerful VCs in Silicon Valley, Ben Horowitz was a tortured CEO trying to keep his startup afloat during the dot-com crash.

You might recognize his name from Andreessen Horowitz (a16z), which — despite sounding like a 200-year-old law firm — is a relatively new venture firm that has skyrocketed in prestige and influence. Its unique founder-focused culture is captured in the motto: “some experience required.”

Marc Andreessen earned that experience by building the first popular web browser and spinning it into a billion-dollar company: Netscape. Horowitz joined a few years later, rose quickly through the ranks, and after Netscape was sold, co-founded a cloud startup called LoudCloud with Andreessen. As CEO, Horowitz piloted LoudCloud through the chaos of the dot-com crash, eventually stabilizing and cruising for a few years before a billion-dollar buyout by HP.

His experience as CEO was harrowing, and the books Horowitz turned to for guidance — notably Built to Last by Jim Collins — offered little help. This book is his response to that brand of secondhand academic wisdom. It’s part trauma journal, part CEO bootcamp: an ode to the man in the arena, tightly focused on Horowitz’s personal struggle. At times, his “how-to” framing leaves you craving the story behind the bullet points — but even so, these pages clearly convey the weight of leadership.

This isn’t the book you read before dropping out of college to found the next Snapchat — it’s the one you should’ve read that might have kept you in school.

Subscribe now

He Can Write

Amidst a sea of business-book blowhards, Horowitz stands out as a surprisingly good writer. Maybe it’s from years of blogging. Maybe it’s his obsession with rap music. Or maybe he just follows his own advice: “CEOs should tell it like it is.”

His voice is wry, clear, and — by tech founder standards — very cool. He opens chapters with lyrics from Nas or DMX, talks about his failures with a sardonic grin, then hammers home a dead-serious lesson.

Of course, we’re talking about a white, nerdy, likely-billionaire VC, so “cool” is relative. But grading on a curve? He pulls it off.

He isn’t afraid to get personal, either. Horowitz writes about crying on his first day of kindergarten, battling depression when his startup seemed doomed, and getting a wake-up call from his dad to fix his marriage. After a short biographical section filled with moments like these, the book jumps into lessons — starting with struggle, honesty, and layoffs, then moving on to demotions, delusions, and “Nobody Cares.”

It’s around here that we start to wonder if our careers would benefit from simply having more panic attacks.

Still, something’s missing. His personal story fades, and the chapters start to feel like disjointed essays.

Almost All Blog

Maybe the downside of being the man in the arena is that you’re too busy to write a book from scratch.

Uncharitably, this is a short but compelling autobiography sandwiched around a thick filling of reused blog posts. It feels a little rich to bill the book as the backstory behind the blog when it’s almost 90% blog. I’m sorry, Mr. Horowitz — I’m telling it like it is.

To be fair, these are great blog posts. We’re talking about the guy who wrote the ultimate PM post: “Good Product Manager / Bad Product Manager.” But by their nature, blog posts don’t add up to a cohesive argument. Some even contradict each other — one claims CEOs are partly born, partly made, while the next insists they’re as synthetic as Jolly Ranchers.

Each post is focused and structured, but taken together they form a kind of hopscotch through loosely related topics. They have firepower, but it’s buckshot, not a sniper bullet.

What’s more, these posts weren’t written for general readers. They’re aimed at a very specific audience: startup CEOs living through what Horowitz experienced.

For CEOs Only?

If you’re not a CEO — and specifically a CEO whose company has grown big enough to suffer from organizational headaches — then much of Horowitz’s advice takes some imagination to apply.

That’s not to say it isn’t valuable. It can make you a better manager, a wise advisor to founders, or simply a very savvy employee. Still, we should add “becoming the CEO” and “scaling to 20+ people” to the list of hard things not in this book.

The posts often read like Horowitz is talking to his past self, processing old wounds by sending instructions back in time. Witnessing that conversation is fascinating — but digesting these generic how-tos, clearly drawn from specific circumstances, can feel like watching a movie with the sound off. “Don’t poach employees from your friend’s company.” “Don’t split a role between two people.” “Concessions to political maneuvering are dangerous.” It’s obvious there are great stories behind each of these; we just don’t get to hear most of them.

Still, there’s a lot of wisdom here. One of the book’s biggest strengths is offering a better definition of the CEO role — something more useful than “the number-one salesperson.” To Horowitz, the CEO must tell the company story, churn out good decisions, give constant feedback, hire and direct great people, and set realistic objectives.

Other pearls follow: blame yourself when you lay people off. Don’t hire big-company execs until you truly need them. Invest more in training than you think you should. Hire people who care about team success, not personal glory. And communication will be your biggest challenge as you grow.

These are great lessons. But Horowitz wasn’t kidding when he said they were “hard.”

This Sounds Awful

Horowitz’s picture of a CEO is unabashedly miserable. Cold sweats, sleepless nights, boiling guts — these are all de rigueur. CEOs are expected to know what to do “in all matters all the time,” and anything that goes wrong is their fault. CEOs are lonely: unable to confide in employees for fear of causing panic, and unable to talk to outsiders who don’t understand. Psychological meltdowns are normal, just not discussed. One CEO friend calls it “the torture.”

If you work for a CEO who isn’t visibly destroying themselves for the company, Horowitz might even make you a little resentful.

Is this really the best model of leadership we have? Horowitz doesn’t describe a bad leader — he depicts an incredible one — but the people powering our economy and reinventing society shouldn’t be so miserable. No wonder they sometimes do crazy things.

Horowitz’s description begs us to search for a better way. Could more vulnerability and a supercharged support system work better? Or should we start training AI agents to be startup CEOs?

Horowitz doesn’t ask these questions, but he makes it hard not to.

Why Even Do It?

So, why would anyone actually want to be a startup CEO?

Given compensation often in the tens of millions, money is the easy answer. But Horowitz tells us to “take care of the people, the product, and the profits — in that order.” He says his primary reason for getting out of bed as CEO was to make his company a good place to work.

Could wanting your employees to be happy really be enough to make the torture worth it? In the same breath he mentions that his employees worked 12- to 16-hour days. Did he forget to include a chapter on how to get teams to happily work 16-hour days?

Spending every waking hour building cloud infrastructure software and “happiness” don’t seem like natural bedfellows. But paired with Horowitz’s emphasis on hiring brilliant people, it starts to conjure an image of elite engineers whose greatest joy is writing cutting-edge code.

Sending such engineers home to see their families might be the real gift. Still, in that rarified world, maybe making employees happy really could be a CEO’s raison d’être. It tracks, too, that many of Horowitz’s former team members later joined him at a16z.

It’s an uplifting thought. But we should probably add “how to hire a team of savants” to the list of hard things this book doesn’t explain.

Courage Is the Job

Though Horowitz’s message is scattered across blog posts, one theme connects the work: courage. Most of his stories and lessons are about pushing past fear to do the hard things.

From meeting his best friend, to meeting his wife, to bouncing back from a 35-cent stock price, courage was the catalyst.

At its core Horowitz’s wisdom is gritty, hands-on experience with the many and endlessly challenging forms courage can take. He says it best: “It’s the moments where you feel most like hiding or dying that you can make the biggest difference as CEO.”

If you can handle the heartburn, the sleeplessness, the torture, the reward is greatness. That’s all it takes — no special gene, no insider connection — just the will to keep going.

It’s ultimately an uplifting message, one that encourages us to rely on our uniqueness.

Conclusion

It would be nice if Horowitz told us the full stories behind his lessons, instead of just the takeaways. That’s what he promised in the introduction — and when he delivers, it’s excellent. His blunt, sardonic personality shines through, and his narrative is a joy to read.

We don’t know if he was too busy, too private, or too kind to dish dirt on former colleagues, but more often than not, he holds out on us. The result is less a cohesive book than a well-curated blog anthology. Thankfully, the posts are still well worth reading, or rereading. Together, they suggest a style of leadership that is both highly admirable and punishingly difficult.

Still, sometimes just admitting that things are hard gives us the clarity to do something, instead of looking for an escape hatch or a secret weapon. Horowitz reminds us there are no silver bullets — only lead bullets: face things head-on, tell it like it is, and, in his words, “embrace the struggle.”

Quinn Mitchell is a product manager in Brooklyn, NY writing about business strategy, product theory, and technology. More at LinkedIn.

1997 Harvard Business Review Press · Revised editions in 2000 and 2016

Overview

Why is success so difficult to sustain?

It’s the question that gave birth to The Innovator’s Dilemma — a book that would go on to be called “a holy book for entrepreneurs in Silicon Valley” (Businessweek) and would dub Clayton Christensen “the most influential business thinker on earth” (The New Yorker). This question drove Christensen to leave his role as CEO of a public company and to enroll at Harvard Business School as a PhD student at the age of 38 so he could study it full time.

If you’re wondering, do real human beings actually do things like that? — Christensen’s status as a real human might already have been in question. He graduated in the top 1% of his class at BYU, attended Oxford as a Rhodes Scholar, earned an MBA from Harvard, consulted at BCG, served as a White House Fellow, and became a CEO of a public company— all before 40.

He clearly had a thing for intellectual powerlifting.

His research led him to a fascinating answer: even the best-managed firms often fail because of what he called disruptive technologies.

Of course, the word “disruptive” has since been thrown around with such abandon that it's almost lost all meaning. But at its origin, Christensen’s theory is disciplined, careful, and compelling.

While it is audacious to assert a single, sweeping answer to this question — and Christensen certainly overreaches at times — the book’s lasting value lies less in an airtight theory of disruption and more in its brilliant, data-backed retelling of recent business history.

Subscribe now

Drier Than Death Valley

Fair warning: before you reach Christensen’s legendary insights, you must make it through an exceedingly dry history of the disk drive industry. At least half of the book is devoted to a painstaking analysis of the rise and fall of various disk drive technologies.

Yes, mentioning disk drive history may cause your date to excuse themselves for the bathroom. And no, disk drives have nothing to do with disc brakes or disc jockeys.

If you don’t know, they are the distant ancestors of the memory chips in our phones. Today, they survive mostly in phrases like “copy the hard drive” or “out of disk space.”

If reading a hundred-odd pages about 8-inch drives overtaking 14-inch drives, only to be overtaken in turn by 5.25-inch and 3.5-inch drives, sounds thrilling, you’re in luck.

If not, this might be the time to take an Adderall.

Just when you think you’ve survived the disk drives, Christensen summons up heaps of data on mechanical excavators, steel mills, discount retailers, and motorcycles.

Still, if you can hang in there, our reward is a stunning view of how industries rise, fall, and transform.

View of History

Somehow, through Christensen’s explanations and charts of megabytes per cubic inch, he starts to win us over. By the end of Chapter One, we feel like we’ve gained the wisdom of living through 50 years of business history.

His thesis is that industrial evolution has recognizable patterns. He shows us recurring scenarios — performance oversupply, northeasterly drift, value networks, sustaining and disruptive technologies — that start to explain failures and successes.

Christensen argues that companies often serve their existing customers too well: chasing higher margins, more features, more performance, until suddenly a cheaper, simpler alternative invades from below.

These concepts, once described, are intuitive and broadly applicable — like cognitive biases for companies. Through Christensen’s eyes, mind-numbing charts turn into real, high-stakes dramas that help explain our world today.

Disruption Can Be Exciting

There’s something thrilling about disruption.

Kids have an instinctive sense of what’s new and cool and what is not — the new phone, the new toy, the new app — these are the subjects on which companies rise and fall. Sometimes the next big thing comes from the expected source, like The Wire following The Sopranos. Other times, it comes out of nowhere — like when Google search appeared one day and knocked Yahoo search out of the ring.

Christensen’s book tries to explain that second case: the upset by the underdog.

We do love an underdog. And in most cases, the disruptive technologies Christensen describes seem to democratize access, creating cheaper and more widely available products.

Is disruptive technology a path to utopia? Probably not. But Christensen makes a strong argument for the power of competition to create societal good.

That said, when we put on our entrepreneurial hats and go looking for the next disruptive rocketship, we may find Christensen’s theory less useful than we had hoped.

Dated, Highly Unique Industry

He largely defines disruptive technology through examples — and at first, all his examples seem to be just smaller and smaller disk drives.

It begs the question: how representative is the disk drive industry?

If a team of engineers left Villeroy & Boch to build a revolutionary 3.5-inch dinner plate, I wouldn’t sell the family farm to invest. Nor would I back the 1.7-inch dinner fork.

The disk drive industry — and the broader computer industry it supplied — have experienced something incredibly unique since the 1950s: They have grown at a mind numbing pace; we’re talking in the ballpark of a million percent growth.

Christensen chose disk drives because their rapid evolution made patterns easier to observe. But we can’t help doubting whether a theory born from such a breakneck industry can be broadly applicable.

To his credit, he does show that disruption happens outside of disk drives — in mechanical excavators, steel mills, discount retail, motorcycles, and computers.

Still, it’s easy to imagine that once armed with a disruptive hammer, every industry starts to look like a nail.

“Disruptive” Becomes Arbitrary

It doesn’t help that being “disruptive” or not is highly debatable.

In trying to fit his theory so neatly to the disk drive industry, Christensen may have weaved too fine a net. Plenty of innovations have toppled leading firms without meeting his criteria for being "disruptive."

By his definition, a disruptive innovation must (1) initially underperform the mainstream alternative, and (2) enter either a low-end or entirely new market.

It’s frustrating — and bad for the credibility of the theory — that you can propose examples like taxi companies losing to Uber, or Nokia and Motorola losing to Apple, only to find out Christensen said neither was disruption because they didn’t precisely fit the mold.

It is possible Christensen played up his strict criteria simply to stop businesspeople from adding "disrupt" to every other sentence.

Still, if too many real-world examples don’t fit the model, the theory starts to feel more like Monday morning quarterbacking than a reliable roadmap.

Backed by Data and History

Yet these critiques don’t diminish the achievement of The Innovator’s Dilemma.

Christensen's cognitive rigor is something to behold. We can tell he is deploying considerable mental horsepower in an earnest pursuit of the truth.

In the preface, he tells us something key to his thinking: “Data only exists in the past. Theory must be derived, therefore, from careful observation of the past.”

Christensen is trying to apply the scientific method to business strategy — and in doing so, he almost defines a new genre.

The Innovator’s Dilemma is that rare thing: a scholarly business book. Between the piles of biographies, autobiographies, how-tos, and advice books, Christensen’s work stands as one of the few examples of evidence-based business theory.

Are his conclusions always supported by ironclad proof? Maybe not. But they are drawn from a virtuosic study of history and a firm grasp of a daunting number of facts.

Unintended Consequences

While The Innovator’s Dilemma often frames disruption as a democratizing force — giving startups a path to challenge giants — it is, at its core, a handbook for incumbents. Christensen’s goal is to help great companies stay great. Yet one wonders: if the most powerful corporations learn to shield themselves from competition, is that really a win for society?

Christensen’s solution to the dilemma is essentially to create conglomerates, and he supplies a framework for making them successful. But without the fresh faces of successful startups, don’t industries drift toward monopolies?

By hacking disruption, has he created a cure that is worse than the disease? If disruption slows — if startups find it harder to topple the entrenched — we risk not just stronger monopolies, but a world that is less diverse, less dynamic, and less alive to possibility.

Final Verdict

The Innovator’s Dilemma is far from a perfect book. It’s almost as dense as a black hole, its central theory is brittle, and it may even be unraveling the forces of creative destruction that kept our economy healthy.

But it is also a serious, courageous attempt to combine science with business strategy — and a vivid journey through fifty years of industrial history.

Though by the end of the book your brain may feel lightly poached, Christensen’s ideas, even when imperfect, sharpen the way we see the world. Once he’s shown you sustaining and disruptive technologies, the pull of value networks, and the slow drift of industries, you can’t unsee them.

If you can endure the desert of disk drives, the view from the other side is worth it.

Quinn Mitchell is a product manager in Brooklyn, NY writing about startup strategy, product theory, and technology. More at LinkedIn.

2008 Wiley · Revised edition in 2017

Overview

If you’ve worked in product management for more than five minutes, someone’s probably told you to read Inspired. The book contains the recipe for organizing product teams that has become the industry gold standard.

It’s written by Marty Cagan, a member of the startup intelligentsia who earned his stripes under Marc Andreessen at Netscape. Cagan went on to lead product at eBay before founding Silicon Valley Product Group (SVPG), a small but elite consultancy that has quietly shaped the playbooks of companies like Google, Netflix, and Airbnb.

Inspired is part product encyclopedia, part call to arms. It tells you how great product teams work, and makes you wonder why yours doesn’t. But the writing often feels overprocessed — as if through too many cycles of feedback its personality was stripped away. It suffers from an abundance of Silicon Valley tech jargon, a reliance on prescriptions without explanations, and a style that might be the solution to your insomnia.

That said, Inspired remains essential reading for product managers everywhere and it answers an impressive number of questions for those trying to understand the job.

Despite the jargon, Cagan comes across as a strong and compassionate leader. He writes with earned authority and a heartfelt desire to help. His critiques of “most” companies are all the sharper because you can almost hear him saying, “I’m not mad; I’m just disappointed.”

Subscribe now

Tech-Speak

Opening the book is a bit like putting on an episode of HBO’s Silicon Valley — you’re entering the tech bubble; the only things missing are the jokes.

Ever wondered what a feasibility prototype, a discovery coach, or a user story map is? Cagan will tell you. Though they may sound like the hallucinations of a product chatbot, these terms actually take on surprising power and clarity from Cagan’s definitions.

Cagan has a gift for making the buzzwords make sense. He becomes our guide, ferrying us past the eye-rolls of our non-techy friends into a world where phrases like “autonomous product missionaries” can be said non-ironically.

Product Encyclopedia

The chapters are short and highly distilled. Most include numbered lists. The book is packed with definitions and designed to serve as an easy reference guide long after an initial read.

And while the writing can occasionally appear like an org chart — or the credits of a Marvel movie — for those unfamiliar with the dizzying array of terminology surrounding product teams, it’s a lifeline.

Cagan gives us the blueprints that are used across the industry. We’ve finally found the source of the bullet points we’ve seen in countless job postings.

He opens a window into the inner workings of the modern tech company and equips you to swim in the product sea, navigating with ease around terms like OKRs, A/B tests, and viability risk.

Received Wisdom

It’s a little hard to believe that all the concepts Cagan describes are actually used in common practice. I wouldn’t blame you for suspecting at least a few of them were invented by Cagan himself — visiontype? Startup canvas? (Don’t confuse this with a canvas startup — though that might be a good entry point into the home oil-painting market.)

Cagan makes it sound like, in the right circles, these terms are all common knowledge. We might even feel a little embarrassed if we don’t know them already.

Instead of “I love A/B tests,” he writes, “We love A/B tests.” Readers have to hope that we refers to the partners of SVPG — not the product manager mafia.

And surprisingly, for someone so steeped in the design-thinking ethos of Silicon Valley — where problems are king and solutions must be tested — Cagan often gives prescriptions without much explanation. He tells you what to do, but not why to do it; how things should be, but not why that’s better. The most he gives us is an assertion that this is how it’s done at top product companies (think FAANG+), and a handful of short profiles of product leaders.

Maybe he considers this book a product that has already been tested and proven. Still, it’s still a little disappointing to find we’re not allowed behind the curtain to see the trial and error behind the formulas.

Coffee Recommended

Cagan’s book can feel a little dry and impersonal. There’s a textbook-like power to that, and the book is certainly packed with information — but some sections are hard to get through. Cagan misses an opportunity to make this book more approachable and engaging by sharing more of himself and his experiences. It also doesn’t help that he takes almost half the book to get to the point.

In a nod to the product gospel, he opens with a problem: a software project early in his career that, despite following best practices at the time, ultimately ended in wasted time and effort.

Then he writes 32 chapters without giving us the solution.

Maybe he’s trying to make us eat our vegetables before dessert, but I imagine more than a few busy PMs have put the book down around the chapter on OKRs and missed the punchline entirely.

Call to Action

Still, if we can find the determination to carry on, our patience is rewarded. The most satisfying section is Part IV; here, Cagan makes his core argument and solves the problem he started with.

Cagan builds up to this moment with several exhortations for PMs to “do their job,” and in Part IV, we finally understand what that means. To Cagan, a product manager’s job is to discover what to build — by running an ongoing series of tests and experiments.

He expects more than just data analysis and internal meetings. He pushes us to bare our untested ideas to the scrutiny of strangers. He instructs us to regularly meet with users and ask them to interact with prototypes we’ve built. He demands courage — but it’s clear how valuable this first-hand feedback can be.

In the most powerful line of the book, Cagan says he would fire PMs who fail to observe “as many users as possible, first hand, interacting with and responding to [their] team’s ideas.”

This is his core idea. This is how he believes we overcome value risk. While it’s a hopelessly jargony term, value risk is Cagan’s name for the fundamental product question: Will people want this?

Cagan’s approach boils down to learning first-hand “if the user really has the problems we think they have, how they solve those problems today, and what it would take for them to switch.”

He offers a couple rules of thumb that feel spot on: find at least six reference customers for each target market, and spend at least two hours a week meeting directly with users. Even though he doesn’t explain why, we likely find ourselves writing these down.

Conclusion

While it can feel impersonal and has a notable jargon problem, for a book with only 368 pages Inspired packs a textbook-level punch. It’s not just a crash course in product terminology; it also gets deep, calling out PMs who aren’t brave or vulnerable enough to get raw feedback on their ideas.

It’s no surprise that teams at Netflix, Apple, Google, and Airbnb have hired Cagan’s consultancy. He’s selling a cutting-edge operating system for modern product teams.

However, Cagan isn’t totally raw and vulnerable with his readers. His big idea is to be brave and share your incomplete ideas with your customers, yet his thoughts here are polished to the point of being sanitized. We finish the book feeling like we barely got to know him and we are a little sadder because of it.

Quinn Mitchell is a product manager in Brooklyn, NY writing about business strategy, product theory, and technology. More at LinkedIn.