The Hard Thing About Hard Things by Ben Horowitz — Cliff Notes Summary

About the book and the author

• AuthorBen Horowitz
• PublisherHarperBusiness
• PublishedMarch 4, 2014
• Length289 pages (hardcover, per Open Library)
• ISBN978-0-06-227320-8

Page counts vary by edition and listing. Open Library lists the HarperBusiness hardcover at 289 pages and the ebook at 304 pages (Open Library), while the Publishers Weekly prepublication review listed 336 pages at a $29.99 list price. The book has nine chapters plus an appendix, per the Open Library table of contents.

Horowitz was born in 1966 and studied computer science at Columbia and UCLA, per Wikipedia. He started as an engineer at Silicon Graphics in 1990 and joined Marc Andreessen at Netscape as a product manager in 1995. In 1999 he co-founded Loudcloud with Andreessen, Tim Howes and In Sik Rhee, and he took it public in 2001.

In 2002 Loudcloud sold its managed services business to EDS for $63.5 million and became Opsware, an enterprise software company that Horowitz grew to 550 employees and over $100 million in annual revenue, per Wikipedia. Wikipedia's Opsware page puts the price at $1.65 billion in cash, or $14.25 a share. Horowitz and Andreessen launched Andreessen Horowitz in 2009 with $300 million; the firm now manages at least $90 billion, per Wikipedia.

In a 2014 TechCrunch Q&A, Horowitz said a HarperCollins editor who had read his blog asked him to write the book, and that he wanted to fill a gap: a book about what happens when everything goes wrong. HarperCollins notes that he opens lessons with lyrics from his favorite rap songs.

How the book is organized

Per the Open Library table of contents, the first three chapters are Horowitz's own story (chapter 1 is titled From Communist to Venture Capitalist). The rest reads as a field manual:

• Chapter 4: When Things Fall Apart. The Struggle, telling it like it is, layoffs, firing an executive, demoting a loyal friend, and Lead Bullets.
• Chapter 5: Take Care of the People, the Products, and the Profits, in That Order. A good place to work, training, hiring executives, management debt and management quality assurance.
• Chapter 6: Concerning the Going Concern. Minimizing politics, titles and promotions, when smart people are bad employees, one-on-ones and scaling.
• Chapter 7: How to Lead Even When You Don't Know Where You Are Going. The most difficult CEO skill, fear and courage, Peacetime CEO/Wartime CEO, and how to evaluate CEOs.
• Chapter 8: First Rule of Entrepreneurship: There Are No Rules. Accountability versus creativity, the Freaky Friday technique, staying great, and whether to sell.
• Appendix. A list of questions for hiring a head of enterprise sales, which is the part sales leaders often flip to first.

The key ideas, paraphrased

• The Struggle. In his 2012 post, Horowitz describes the Struggle as the stretch when nothing goes to plan, staff and cash run low, and you wonder why you started. His advice is to share every burden you can, look for a move (he took Loudcloud public in 2001 with $2M in trailing revenue, 340 employees and six weeks of cash), and not take it personally.
• Peacetime CEO, wartime CEO. In his 2011 post, peacetime means a company has a big lead in a growing market; wartime means it faces an existential threat. Peacetime leaders encourage broad creativity, while wartime leaders demand tight alignment to one mission. Horowitz wrote that he was a peacetime CEO for about 9 months and a wartime CEO for the next 7 years. One line sums it up: "Wartime CEO lets the war define the culture."
• Preparing to fire an executive. His 2011 post lays out a four-step process: find the root cause, inform the board, prepare the conversation, and prepare the company communication. The key point is that a failed executive usually signals a failure in your own hiring and integration process, such as hiring for lack of weakness instead of strength or hiring for scale too soon.
• Lay people off the right way. In his 2010 post, Horowitz credits Bill Campbell with the reminder that the layoff message is for the people who are staying, and he tells CEOs to stay visible and present afterward.
• Lead bullets. In his 2011 post, Horowitz says there is no silver bullet when a rival's product is better: Opsware spent nine months building a better product and regained the lead. He pushes founders who blame their channel to fight for the direct sale instead.
• Train your people. Horowitz writes in his 2010 post that reading Andy Grove's High Output Management changed his view of training. As Director of Product Management at Netscape, he wrote the Good Product Manager/Bad Product Manager memo to set his expectations.
• Good product manager, bad product manager. The memo says a good product manager is the CEO of the product, owns the result with no excuses, defines the what rather than the how, and focuses the team on revenue and customers. Horowitz now warns that it is old and is best read as an example of a training document.
• Management debt. His 2012 post borrows from technical debt: an expedient short-term management decision with an expensive long-term cost. His examples are putting two people in one job, overpaying a key employee who brings a rival offer, and skipping performance reviews and feedback. He credits Joanne Bradford with the term.
• People, products, profits, in that order. The title of chapter 5, per the Open Library contents, sets the order of priority. Its sections are mostly about people: a good place to work, training, hiring executives, and checking the quality of your managers.

Criticisms and context

The Publishers Weekly review was mixed. It said Horowitz repeatedly leans on war and military metaphors, called him sharper when he is blunt and candid, and said most of the useful insights come from other leaders such as Andy Grove and Bill Campbell. It summed the book up as war stories from the 1990s boom-and-bust era mixed with older platitudes.

The audience is narrow. The book is about venture-backed tech companies, and many lessons assume a board, venture funding and a fight for survival. Engineering leader Cate Huston, writing on her blog in 2015, also noted that Horowitz uses the pronoun she throughout but, apart from his wife, tells stories almost only about men.

The wartime label has drawn pushback too. A 2023 Safe for Work newsletter conversation with an executive coach argued that it can become an excuse for leaders to drop empathy and treat their own employees as the enemy. Horowitz himself frames wartime as a temporary mode for an existential threat, per his original post.

What sales leaders can take from it (our interpretation)

The book is written for CEOs, not for sales teams. These are our suggestions, not Horowitz's.

• Know whether your team is at war. A territory losing to a new competitor needs tight focus and daily inspection; a growing, well-defended book of business can give reps more room to experiment.
• Treat a failed sales hire as your miss. Before you fire a VP of sales, run Horowitz's root-cause step on your own hiring: was the role defined, and did you hire for real strength where you needed it?
• Write your own good rep, bad rep memo. His product manager memo is a model for a one-page expectations document that new reps get on day one.
• Watch your management debt. Matching a rival offer for one rep, or skipping pipeline and performance reviews to keep the peace, tends to come due later across the whole team.
• Fire lead bullets at a better competitor. If you are losing deals on product or value, a new partner channel or discount is rarely the fix. Go win the head-to-head.
• Use the appendix. The questions for a head of enterprise sales are a ready-made interview guide for senior sales hires.

Questions people ask

Sources

• Open Library: The Hard Thing About Hard Things (HarperBusiness, 2014) · Publisher, year, 289 pages, ISBN, table of contents
• Open Library: The Hard Thing About Hard Things (ebook) · Ebook, 304 pages
• HarperCollins: The Hard Thing About Hard Things · On sale March 4, 2014; publisher description
• Publishers Weekly review · Review; 336 pages and $29.99 list price in the prepublication listing
• Wikipedia: Ben Horowitz · Background, Netscape, Loudcloud, Opsware, sale to HP, Andreessen Horowitz
• Wikipedia: Opsware · HP purchase price and per-share price
• Wikipedia: Andreessen Horowitz · Founding and assets under management
• a16z: Peacetime CEO/Wartime CEO (Ben Horowitz, 2011) · Wartime vs. peacetime definitions and the culture line
• a16z: The Struggle (Ben Horowitz, 2012) · The Struggle and the 2001 IPO
• a16z: Preparing to Fire an Executive (Ben Horowitz, 2011) · Four-step process
• a16z: The Right Way to Lay People Off (Ben Horowitz, 2010) · Layoff advice
• a16z: Lead Bullets (Ben Horowitz, 2011) · No silver bullets
• a16z: Why Startups Should Train Their People (Ben Horowitz, 2010) · Origin of the product manager memo
• a16z: Good Product Manager/Bad Product Manager · The memo
• a16z: Management Debt (Ben Horowitz, 2012) · Management debt and its examples
• TechCrunch: A Q&A with Ben Horowitz on his new book (2014) · Why he wrote the book
• Cate Huston, Accidentally in Code: Book: High Output Management (2015) · Critique of the book's examples
• Safe for Work: Why wartime CEOs may win the battle but lose the war (2023) · Critique of the wartime label
• Wikimedia Commons: Ben Horowitz at TechCrunch Disrupt (TechCrunch, CC BY 2.0) · Hero photo

This summary is an independent explainer written in our own words and does not reproduce the book. Facts were read from the linked pages on November 3, 2026; read the book for the primary detail. The hero photo shows Ben Horowitz at TechCrunch Disrupt in 2010 (TechCrunch, CC BY 2.0, via Wikimedia Commons).

Top photo: TechCrunch / CC BY 2.0 via Wikimedia Commons