Product management is a toolkit to make you a better team
During a recent tech event, an audience member ask the panelists about the type of process they use to manage product development.
“I’ve heard a lot about sprints and agile, so we are trying that? What do you use, what is the best process in your opinion?”
So many teams approach product management as if there is a single ‘right way’ of doing it. They are using a tool for the sake of using a tool, as opposed to using the tool because it solves the problems their team is experiencing.
A hammer is a great tool. But, unless you have a picture that needs to be hung up, or new shingles that need to be put on your roof, a hammer isn’t going to give you a ton of value on it’s own.
The best solution comes from understanding the problem you need to solve. Product management is a toolkit that can help you solve a variety of problems; in order to understand what tool is required, you need to first understand what is the main problem hindering your team when building out your product.
The most common problems that product teams face are:
- Lack of a unified product vision
- Difficulty measuring output and velocity of development team
- Poor communication and unclear expectations
- Regularly rebuilding and redefining product features
A strong product management process is a great solution to these problems…but which one? What is the best product management process between agile, scrum, sprints, customer-centred development, story pointing, Trello to-do lists, or any of the other dozen options?
Each technique has merit, but you need to understand your problem before you can know which will provide the most tangible value for your product development. Product Management is about finding the right solution for the current problem — both externally (with product and market) and internally (with PM processes and team challenges).
Before jumping into choosing a which you want to use for your team, I suggest all product leaders invest time up front in identifying key problems preventing your team from becoming a better version of itself.
Want to discuss/argue this? Let me know @therobhayes