Things product managers waste their time on
I&#x27;m going to admit that I&#x27;m ridiculously biased on this topic, which is terrible since I&#x27;ve never been a PM :-)  While I don&#x27;t disagree with anything in this article, it falls a bit flat for me because it doesn&#x27;t say anything that you <i>should</i> do.<p>Here&#x27;s my list of things you should do as a PM:<p>- Understand your product.  Not just conceptually.  Not just how it fits in the market.  Not just what we used to call the &quot;box features&quot; (features you write down on the box in shrinkwrapped software so people will buy it).  You need to understand what the product does in detail.  You need to understand how it does it in detail.  You need to understand exactly how to do every single thing with the software.  You should be an expert -- more than the programmers, more than the QA, more than the users.  You should know what&#x27;s great, what sucks and what&#x27;s in between.<p>- You need to prioritise the incoming work.  By this I don&#x27;t mean &quot;X is priority 1. Y is priority 1. Z is priority 1. ZZ is priority 2&quot;.  Ordinal priority.  If anyone asks about 2 pieces of work, A and B, you should be able to say which one is more important and why.  You should produce reports that are visible and understandable that document these priorities so that everybody can see them.<p>- You need to plan the upcoming work.  This is different than prioritisation.  To plan the upcoming work you need to break larger goals down into smaller vertical pieces, each of which give you some value.  You should then be able to arrange these in an order (again ordinal -- none of this &quot;these 500 things all need to be done at the same time&quot;).  To do this, you will need to work with a variety of different people because you won&#x27;t have all the information to do it by yourself.<p>- You need to ensure that acceptance criteria is available before development for something starts.  You do not have to furnish this acceptance criteria yourself, but you must be able to understand it and to judge critically if it is sufficient.<p>- You need to track development and produce reports.  You should be able to say that something is not yet started, but planned to be started in a specified time frame.  You should be able to say that something has started development.  You should be able to say that something is done (and not just it-compiles-done: done-done-like-we-are-going-to-ship-it-tomorrow-done.)  You need to produce reports that are highly visible by anyone that shows this status.<p>- You need to be active in promoting process that shortens the timescale from feature request to done-done.  Likewise you need to be active in making the movement of work from request to shipping more and more visible to all parties.<p>- You need to handle political problems between the various groups that have a stake in development.  Do not delegate this.<p>As far as I can tell, that&#x27;s it.  Not that it isn&#x27;t a hellishly difficult job with just the above.  As the article suggests, don&#x27;t waste your time doing things other than this -- you don&#x27;t have time!  I&#x27;ve had the good fortune of working with a handful of amazingly good PM&#x27;s in my day.  It&#x27;s not easy, but try to be one of the good ones (they are exceptionally rare)!