JUSTANOTHERPM

The only email you need to read to become a better product manager

Every week, I spend 50+ hours researching an important product management topic.

I summarize the learning into a practical guide.

I share it in this newsletter.

    No spam. Unsubscribe any time.

    Three essential questions for every product release, who should answer them, why are they important
    1 min read

    Three essential questions for every product release, who should answer them, why are they important

    For every feature that your team builds, answer these critical questions: "Why", "What", and "How".

    Why

    Who answers it:

    Product Manager.

    Definition:

    1. In this section, state the business reason for focusing on a specific problem.
    2. Include data (and analysis) that helped you prioritize the problem. Also, include the projected impact on revenue (or other relevant metrics.)
    3. For example: "We observed a drop of 15% in signups over the last three weeks. We project that improving the singnup flow will increase the signups by at least 7%. Please see the attached analysis for more details."

    It is important because:

    1. It communicates the reason for focusing on the probem, the goal, and the projected impact.
    2. It enables the engineers to understand and agree (or disagree) to the business reason for focusing on the problem.
    3. It allows you to derive the success criteria for the feature.

    What

    Who answers it:

    The product manager primarily answers this question. However, great PMs start involving engineers at this stage to improve the quality of the answer.

    Definition:

    1. Define the problem you are solving, or define what you are building.
    2. For simple features, ensure you focus only on the problem. For example, "Allow users to login using social login."
    3. For more complicated features, also briefly mention the proposed solution. For example, "Create a bot for the customer support chat by integrating with a third party ready-to-use solution."

    It is important because:

    Defining the "what" helps the product manager align with the engineers on the problem they intend to solve.

    How

    Who asks it:

    Engineering manager and engineers

    Definition:

    This section includes technical details on how the engineers will build the solution.

    It is important because:

    Defining the solution before engineers build it is important to create a detailed version of the solution. The details often help in uncovering potential limitations, and missed use cases.


    Like what you read? Subscribe to our newsletter and get one practical guide every week.