The four most common problems I've had with PMs:<p>#1 Won't nail down the customer's actual problem, describe it clearly to you and let you come up with a solution. They will just pass on the customer's proposed solution and insist that you build it.<p>#2 Vague, Incomplete and unversioned specifications rife with duplication and redundant information.<p>#3 Inability to prioritize or break down stories coherently.<p>#4 Won't get their hands dirty actually testing the product. That's QA's job.
There's also the corresponding "Good Engineer, Bad Engineer" which I like<p><a href="http://www.chrispliakas.com/2015/01/22/good-engineer-bad-engineer/" rel="nofollow">http://www.chrispliakas.com/2015/01/22/good-engineer-bad-eng...</a>
I have worked with several project managers who cite this article and claim to live by this ideal. However in practice they do everything but what is mentioned of a good product manager in the article. I don't know if I am biased or if the product managers, like most humans it would seem, fail to see themselves in a bad light (and thus correct themselves and set anew on a better path).<p>I also think that this is a subjective article, which, while it tries to list down the differences between good and bad traits of a product manager, fails to strongly separate the bad traits from the good ones by using vague management speak, and in general ends up making product managers feel goody goody about just being product managers.
One of the last times this popped up, I printed it out and annotated it. I wanted to see if it was possible to take something so different to my working world (risk management) and apply it. Annotating it for my situation made it clear that this document should be seen as more far-reaching than just differentiating product managers. It really is pointing out the difference between good workers and bad workers in <i>any</i> organisation.<p>Every single point made has an element that can be applied to any organisation and career; Productive workers understand the context of business ("Good PMs take all important factors..."); successful workers solve the issue, not the symptom ("Good [PMs]...proper deeper into the [problem]"). Sometimes I look back at my annotated pages and score myself about whether I fall to "Bad" or to "Good". I'm still working at it.<p>I urge everybody to read, and apply this to their own careers. Don't pigeonhole this document just because it is defined as important to product managers. I see this as just as influential as Ray Dalio's Principles (<a href="http://www.bwater.com/Uploads/FileManager/Principles/Bridgewater-Associates-Ray-Dalio-Principles.pdf" rel="nofollow">http://www.bwater.com/Uploads/FileManager/Principles/Bridgew...</a>)
Interestingly, author thinks these points may not be relevant today. What has changed?<p><i>Warning: This document was written 15 years ago and is probably not relevant for today’s product managers. I present it here merely as an example of a useful training document.</i><p><a href="http://a16z.com/2012/06/15/good-product-managerbad-product-manager/" rel="nofollow">http://a16z.com/2012/06/15/good-product-managerbad-product-m...</a>
I read this the other day in Ben Horrowitz's book "The Hard Things About Hard Things" and loved the idea by other commenters here to apply it to other fields. Just [my own version](<a href="https://github.com/ajmurmann/good-developer-bad-developer" rel="nofollow">https://github.com/ajmurmann/good-developer-bad-developer</a>) that represents my views on engineering. I tried to stay away from concrete, good practices like TDD or pairing that are en vogue right now. Although I have very strong opinions on some of those, they are controversial and I think they would take value away from the larger points.<p>I would be excited to hear people's thoughts on it!
I am a product manager in the financial sector and generally I agree with this list. What I want to add is "A good PM knows how to balance competing requests from stakeholders and know when to say no". You can't please everybody.
Posted many times yet apparently never discussed: <a href="https://hn.algolia.com/?query=%22Good%20Product%20Manager,%20Bad%20Product%20Manager%22&sort=byDate&dateRange=all&type=story&prefix=false&page=0" rel="nofollow">https://hn.algolia.com/?query=%22Good%20Product%20Manager,%2...</a>.