"Choose your battles wisely. After all, life isn’t measured by how many times you stood up to fight. It’s not winning battles that makes you happy, but it’s how many times you turned away and chose to look into a better direction. Life is too short to spend it on warring. Fight only the most, most, most important ones, let the rest go."― C. JoyBell C.
A Product manager (PM)is always bogged down by feature requests and bugs from Client facing teams. These requests or bugs may get piled up in a huge list causing difficulties for a PM to determine which one to tackle first. Every Customer Support Representative or Customer Sucesss Manager (CSM) will claim their tickets to be prioritized or resolved first. This becomes tricky for the PM to focus on the priority. It can also affect the pre-planned product roadmap and timelines for the planned feature roll-out. A bad prioritization can lead to issues at all level including client retention, revenue impact, NPS score, etc. To help a PM get out of this mess, the Customer Success Team (CS) have a huge role to play in this process. Let us look at how this is going to become possible:
A few years ago when I shifted my career from a Business analyst to a PO/PM, I did not know if the new title would bring in any additional responsibilites or work. I just liked the fancy new designation and went about doing the same work I did before. Little did I know that the PO/PM role was much more than I had imagined (and it still is…) What I aim to do in this post is to keep it simple and explain what you should be doing (not limited to) if you just landed yourself in a PM/PO role. Img Source: Freepik.com/macrovector
A Product Manager and a Software Engineer walk into a bar. They look into the menu and order their food and drinks. The Product Manager has few drinks and rants to the Engineer asking about the new fad called ‘API’. The tipsy Engineer smiles when the waiter serves the order and tells the PM that he just made an API call.