Don’t use project management tools for Product Management
I’m seeing a troubling trend in product management. Too often, project management tools end up being the core tools used by product managers.
However, project management and product management are distinct practices and by using a project management tool you are very possibly distorting the product management process to fit within the confines of the project management tools.
Project Management vs Product Management
Projects, by their very definition, have a distinct beginning, middle and an end. Projects get assigned a set of resources with which to complete the project. Each project has a well defined goal to be achieved at the end of the project. This makes it very easy to work out whether a project was successful. Did the project achieve the goal within the given constraints? If yes, it was successful and if no, it wasn’t.
Product Management isn’t the same. It’s a discovery process as much as anything, and is unique from Project Management in a number of ways:
- Product management doesn’t have any definite beginning, middle or end. Instead, Product Management is a cycle of continuous iteration, feedback and deployment. In fact, it isn’t really one cycle, but a series of cycles that orbit a vision and narrative of what the product is. These cycles cover aspects such as experimentation, usability testing, customer discovery, development and deployment of updates.
- Product management is not a linear process, and the iterative processes involved actually encourage you to change tack on a pretty regular basis. Haven’t we all prioritised something up one development cycle only to drop it down the next cycle because new information suddenly made it less important? Or found that after digging into a certain problem to be solved we found that “must have” item was no longer so “must have”.
- Product management doesn’t work within defined dates. As much as our stakeholders would love us to agree to specific dates for those long-term roadmap items, it just doesn’t work that way – there’s too much to learn along the way, and therefore too much which can (and invariably will) change before we get there.
Our approach at ProdPad was to build a roadmap tool that wasn’t constrained by dates.
This trend is worrying because shoehorning product management into a project management tool will only lead to poor practice. Product management is not just a set of tasks to be completed by various resources by certain dates. Things do not neatly move left to right in our world.
Any tool you use for product management should allow for non-linear processes and help with discovery.
This isn’t to say that a project management tool or a task manager cannot be used in some aspects of product management. Once a product spec is ‘Go’, these tools can certainly help with development management, where you’ll have defined resources, a goal and realistic timeline – this is why ProdPad integrates with these type of tools. Where they fall short is in deciding which feature should be ‘Go’ in the first place! Project management tools simply aren’t fit for purpose for managing the overall process of product management.
So to those of you Product Managers who are debating which tools to use for your day-to-day job, I say:
Be a Product Manager, not a glorified Gantt chart jockey!
- Solving Real World Problems with Product - May 15, 2015
- The ProdPad Community’s Getting Busy – Suspension’s Zap for Slack - October 10, 2014
- Regenerating ProdPad: Risking a Re-write - October 2, 2014
- Why did we hire a UX specialist to regenerate ProdPad? - September 17, 2014
- Team Foundation Server Integration is Here. - July 18, 2014
- ProdPad and Pivotal Tracker: Integrating Product Management for Even More Product Teams - June 23, 2014
- Keeping Customers in the Loop: ProdPad and UserVoice - June 16, 2014
- ProdPad and Trello take it to the next level - June 9, 2014