Product Management

Product management sits at the intersection of business, technology, and user experience. A product manager is responsible for defining the why, what, and when of a product, while the engineering team determines the how.

Product Strategy

A product strategy is the high-level plan that connects your product to the broader business goals. It answers foundational questions:

• Who are your target customers?
• What problem are you solving for them?
• Why will they choose your product over alternatives?
• How does this product contribute to the success of the business?

A good product strategy provides enough direction to guide decision-making without being so rigid that the team cannot adapt as they learn. Strategy is not a static document. It should evolve as the market, technology, and customer needs change.

Discovery and Validation

Building the right product starts with understanding the problem. Discovery is the process of deeply understanding customer needs before committing to a solution.

• Customer research - Talk to real users and customers. Understand their workflows, frustrations, and goals. Surveys and analytics provide data, but conversations reveal context.
• Problem framing - Clearly define the problem before jumping to solutions. A well-framed problem is half-solved.
• Prototyping - Build lightweight prototypes to test ideas quickly. The goal is to learn, not to ship.
• Assumption testing - Identify the riskiest assumptions behind your product idea and test them early. It is far cheaper to invalidate an assumption with a prototype than with a shipped product.

The goal of discovery is to reduce uncertainty. You will never eliminate it entirely, but you can avoid building something nobody wants.

Roadmapping and Prioritization

A product roadmap communicates the planned direction of the product over time. It is a communication tool, not a commitment.

Prioritization Frameworks

Several frameworks can help structure prioritization decisions:

• RICE scoring - Rate items by Reach, Impact, Confidence, and Effort. Useful for comparing opportunities objectively.
• Cost of delay - Estimate the cost of not doing something. This is particularly useful for time-sensitive opportunities.
• MoSCoW - Categorize items as Must have, Should have, Could have, and Won't have. Useful for scoping releases.
• Opportunity scoring - Identify areas where customer satisfaction is low but importance is high.

No framework replaces judgment. Frameworks help structure the conversation, but the final decision should consider context, strategic alignment, and practical constraints. Prioritization is about saying no to good ideas so you can focus on the best ones.

Go-to-Market

Launching a product is not just a development milestone. A successful launch requires coordination across the organization:

• Positioning and messaging - How do you describe the product to your target audience? What is the value proposition?
• Sales enablement - Does the sales team understand the product, who it is for, and how to sell it?
• Support readiness - Is the support team prepared to handle questions and issues?
• Documentation - Are user guides, API documentation, and help resources available?
• Feedback channels - How will you collect and act on feedback after launch?

The launch is the beginning of a product's life, not the end of a project.

Metrics and Iteration

Defining what success looks like is a critical product management responsibility. Good product metrics are:

• Actionable - They inform decisions. If a metric moves, you know what to investigate or change.
• Accessible - The team can understand and track them without specialized tooling.
• Auditable - You can trust the data and verify how it is calculated.

Common product metrics include adoption rate, retention, engagement, customer satisfaction (NPS, CSAT), and revenue impact. The specific metrics that matter depend on the product, the stage of the product lifecycle, and the business model.

Measurement without action is waste. Use metrics to identify what is working, what is not, and where to invest next.

The Product Manager Role

A product manager does not have direct authority over the people building the product. The role requires influence, not control. This means:

• Building trust with engineering, design, and business stakeholders.
• Communicating clearly and frequently about priorities, trade-offs, and the reasoning behind decisions.
• Being willing to say "I don't know" and then going to find out.
• Taking responsibility for outcomes, not just output.

Product management is not about having all the answers. It is about asking the right questions, making informed trade-offs, and keeping the team focused on delivering value.

References

• Cagan, Marty. Inspired: How to Create Tech Products Customers Love. 2nd Edition. Wiley, 2017.
• Perri, Melissa. Escaping the Build Trap: How Effective Product Management Creates Real Value. O'Reilly Media, 2018.