Good Product Manager; Bad Product Manager
An excerpt from “The Hard Thing About Hard Things” by Ben Horowitz
I recently finished reading The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers by Ben Horowitz and came across this interesting passage.
Ben Horowitz is a technology entrepreneur and co-founder of the venture capital firm Andreessen Horowitz. His book focuses on the challenges faced when leading and scaling a startup. I will be adding a more complete review when I’ve finished reading it.
Below is an excerpt from Chapter 5 about what makes a good product manager and what makes a bad product manager.
Good product managers know the market, the product, the product line, and the competition extremely well and operate from a strong basis of knowledge and confidence. A good product manager is the CEO of the product. Good product managers take full responsibility and measure themselves in terms of the success of the product.
They are responsible for right product/ right time and all that entails. A good product manager knows the context going in (the company, our revenue funding, competition, etc.), and they take responsibility for devising and executing a winning plan (no excuses).
Bad product managers have lots of excuses. Not enough funding, the engineering manager is an idiot, Microsoft has ten times as many engineers working on it, I’m overworked, I don’t get enough direction. Our CEO doesn’t make these kinds of excuses and neither should the CEO of a product.
Good product managers don’t get all of their time sucked up by the various organizations that must work together to deliver the right product at the right time. They don’t take all the product team minutes; they don’t project manage the various functions; they are not gofers for engineering. They are not part of the product team; they manage the product team. Engineering teams don’t consider good product managers a “marketing resource.”Good product managers are the marketing counterparts to the engineering manager.
Good product managers crisply define the target, the “what”(as opposed to the “how”), and manage the delivery of the “what.”Bad product managers feel best about themselves when they figure out “how.”Good product managers communicate crisply to engineering in writing as well as verbally. Good product managers don’t give direction informally. Good product managers gather information informally.
Good product managers create collateral, FAQs, presentations, and white papers that can be leveraged by salespeople, marketing people, and executives. Bad product managers complain that they spend all day answering questions for the sales force and are swamped. Good product managers anticipate the serious product flaws and build real solutions. Bad product managers put out fires all day.
Good product managers take written positions on important issues (competitive silver bullets, tough architectural choices, tough product decisions, and markets to attack or yield). Bad product managers voice their opinions verbally and lament that the “powers that be”won’t let it happen. Once bad product managers fail, they point out that they predicted they would fail.
Good product managers focus the team on revenue and customers. Bad product managers focus the team on how many features competitors are building. Good product managers define good products that can be executed with a strong effort. Bad product managers define good products that can’t be executed or let engineering build whatever they want (that is, solve the hardest problem).
Good product managers think in terms of delivering superior value to the marketplace during product planning and achieving market share and revenue goals during the go-to-market phase. Bad product managers get very confused about the differences among delivering value, matching competitive features, pricing, and ubiquity. Good product managers decompose problems. Bad product managers combine all problems into one.
Good product managers think about the story they want written by the press. Bad product managers think about covering every feature and being absolutely technically accurate with the press. Good product managers ask the press questions. Bad product managers answer any press question. Good product managers assume members of the press and the analyst community are really smart. Bad product managers assume that journalists and analysts are dumb because they don’t understand the subtle nuances of their particular technology.
Good product managers err on the side of clarity. Bad product managers never even explain the obvious. Good product managers define their job and their success. Bad product managers constantly want to be told what to do.
Good product managers send their status reports in on time every week, because they are disciplined. Bad product managers forget to send in their status reports on time, because they don’t value discipline.
If you’re a product manager… be a good product manager. Be like Ben.