There’s no one-size-fits-all approach to running a sprint retro, but a tried-and-true framework includes five steps: Set the stage, gather data, generate insights, decide what to do, and close the retro.
Decision-making is a critical part of the PM’s job. Learn how product feature and product market matrices can help you visualize large quantities of data and inform decisions around product strategy.
Delivering an excellent customer experience is essential to any product. The better the experience, the more repeat purchase, upsell, and advocacy of the product by customers.
A perceptual map is a visual aid that shows how consumers perceive a product compared to its competitors in the market.
The purpose of a customer exit survey is not to discover all of the opportunities for improvement, just the critical issues causing customers to churn.
Divergent thinking is the process of thinking of different ways to overcome a figurative boulder blocking a path instead of obsessing about climbing it.
When teams focus on vanity metrics, they take their product in the wrong direction. Yet, PMs and other teams frequently fall into the pit of vanity metrics.
It might seem like reinventing the wheel, but it takes just 10–20 minutes of prep to devise an exciting retro format — an investment that pays off.
Program management refers to the supervision of separate projects that share a unifying theme or enterprise target.
In today’s customer-centric and data-driven world, capturing the voice of the customer is crucial. Customer satisfaction surveys help you understand how your users feel about your product.
Though PMs and engineering managers are separate roles, they work closely more often than any other two roles on a product team.
In this guide, we’ll describe what quality assurance (QA) is, explain why it is distinct from testing, and the role QA specialists play in the product development lifecycle.
