At the beginning of a career as a Product Manager. with few exceptions, it is very common to be responsible for a product’s features. Also, if we look at it from a slightly broader perspective, at the beginning of your career in Product you will be tested through 4 responsibilities or, as I like to call it, stages of product development. Are they: Validation of the opportunity of a feature; Features design ; Development of functionalities; Release and iteration of features. Product literature focuses a lot on the first 3 aspects, always citing and renewing the contents of Product Discovery , Double Diamond , prototyping, agile methodologies and so on. Meanwhile, launch and iteration take a backseat as it’s not product work or all that attractive.

However just as important as figuring out the right thing to launch is validating. whether it has achieved its intended purpose and result. Likewise, communicating the solution in a way that highlights your learnings and performance is critical Phone Number List when presenting results. Good PMs don’t just release features and move on to the next big thing. We make decisions about next iterations and come away with new learnings about what worked and why. However, each company has its own way of communicating these results, often poorly optimized and very focused on the functionality offered.

For this reason in this text I will comment on some practical tips on how to communicate. this information to do well in the presentation of results, in addition to sharing the template I use for this. When should I report? ”Hey, I always communicate to the internal teams when we deploy , everyone celebrates the implementation!” Bad example, right? But it’s because you’re in a hurry. The presentation of official results should happen after the execution of all stages of product development, with the initial lessons already collected and organized in a good Product Analytics structure . No data, no results. Wait until the natural frequency of your product responds accordingly.