Test-n-Tell.com - making product decisions

  The product ops process is a high-level framework that could help you identify how your product teams work, introduce changes in a controlled way, improve things and optimise your organisation for higher productivity and job satisfaction.  In the last post , I suggested what the first stage of the process might be - surveying . It's when you aim to understand how your product teams work, how your entire organisation works, discover problems, turn them into products and make those products successful on the market. In this post, I'll cover the central phase of the product ops process - experimentation. 

  Product operations, or product ops , is an emerging field of product management focused on empowering and increasing the effectiveness of product organisations. As with any establishing functions, the product ops process is not yet decisively defined. Every org does product ops differently at the moment. 

  Even though the product operations process is complex and nuanced, it could be logically split into three major stages. Those are not sequential stages and you could be doing all three at the same time. 

  The product ops topic is gaining traction in the product management community. More and more product leaders are now considering creating product ops in their organisations. In this post, I'd like to offer some food for thought to anyone who looks to hire and build their product ops. 

  Lately, I've noticed the increasing number of product management job ads in gaming companies. On one side, it's great to see product management continues to develop as a discipline and a growing number of companies embracing the role. On the other side, it's a bit worrying that certain industries that previously were considered artistic now hire product managers.

  Healthy competition is a good thing. It drives innovation and brings benefits to customers. However, at times a product team might get obsessed with their competitors which leads them astray.