Making Good Decisions as a Product Manager | by Brandon Chu | The Black Box of Product Management
While product managers may not build the actual product, they do produce something very tangible for a team: decisions. July 23 update: in retrospect and from feedback, this framework applies to any role, not just product management. These decisions can be about anything: small ones like a line of copy in the docs, to big ones like what the MVP of a new feature should be. The decisions PMs make are the ones that unblock their team so they can continue to build. They don’t need to make every decision, but they are responsible for ensuring a decision gets made — whether by them, their team, or their stakeholders. Product managers are the hedge against indecision, and it’s uniquely our job because we tend to have the most context in a company. Typically, the most important decisions that a PM makes are, in order: Since we’ve already discussed these decisions before, and observed a really bad one, in this post we’re going to focus on something more general: What does it mean for a PM to be
While product managers may not build the actual product, they do produce something very tangible for a team: decisions. July 23 update: in retrospect and from feedback, this framework applies to any role, not just product management. These decisions can be about anything: small ones like a line of copy in the docs, to big ones like what the MVP of a new feature should be. The decisions PMs make are the ones that unblock their team so they can continue to build. They don’t need to make every decision, but they are responsible for ensuring a decision gets made — whether by them, their team, or t
Explore this link on the map →