Sharebird

What does Product Management have to provide in their Project Briefs in order for Product Marketing to be successful?

Example: Project Briefs should include: problem, solution, etc.

Answer
11 Answers
  1. Jon Rooney
    Jon Rooney

    Box Vice President Product Marketing | Formerly Splunk, New Relic, Microsoft, Unity, Oracle • 2mo

    Whether PM provides this or, as we've done in my teams, PMM works with PM to codify/confirm - the following iss the primary handoff from PM to PMM: Problem statement What is the pain point that customers have today that we are solving?   Describe it?   How does this impact their business? Customer awareness of the problem Do customers know that they have this pain point?   How do they know?   Who in the business knows about it (persona - level, title, function)?   Who experiences this pain point ...Read More

    558 Views
  2. Becky Trevino
    Becky Trevino

    Flexera Chief Product Officer | Formerly Rackspace, Dell • 5y

    When the transfer of information between PM and PMM occurs via a Project Brief, it is essential that the PM include a good description of the market problem this feature/product is intended to solve, why is this problem worth pursuing, who cares about it, why is our solution different than anything else the target customer could have purchased in market, and key use cases. The use case information should be broken down into feature and benefits.

    1,709 Views
  3. Don Fuss
    Don Fuss

    ServiceNow Director of Product Marketing • 1mo

    The product brief should include:

    • what customer or market problem are we solving? Why does it matter now?

    • who is this for specifically? ICP, buyer personas, user personas, industries, company sizes, etc.

    • customer insights and evidence

    • business objective such as revenue growth, retention, expansion, competitive differentiation, market entry, adoption, etc.

    • product vision and strategy alignment

    582 Views
  4. Victoria Chernova
    Victoria Chernova

    OpenAI Product Marketing • 4y

    There are different levels of information PMM needs from their PM partners throughout the development process. Depending on how your product documentation works, this information could entirely live in a product/feature brief or be split up between the brief and the product spec.  At a high level, here's a deck we've used internally to build collaboration between PM and PMM. To be honest, we don't always get the answers to these questions in document format (or early enough), so sometimes this i ...Read More

    989 Views
  5. Lauren Craigie
    Lauren Craigie

    Inngest Head of Marketing • 4y

    oh mylanta I love this question. I think a lot of this can be an interative process with the PMM, but I think the things I see most often left out of these documents that could completely change the way a new feature is positioned includes: - Not just what problem this solves, but how was the problem solved before this feature existed? (Was there a workaround in our product, or did users lean on external solutions?) - Not just who will use the solution, but who, downstream, benefits from its use ...Read More

    743 Views
  6. Stephanie Kelman
    Stephanie Kelman

    Shopify Senior Product Marketing Lead • 6mo

    Ugh, nothing worse than getting a project brief that's basically "we built this thing, make people want it, launch is next week, thanks!" I swear, half the time PMMs are playing detective just trying to figure out what the product actually does and why anyone should care. A good brief can be the difference between a killer launch and a frantic scramble. Here's what PMs need to include for PMMs to actually succeed: 1. The Problem Context What customer pain are we solving? Why does this problem ma ...Read More

    772 Views
  7. Katie Levinson
    Katie Levinson

    MyFitnessPal VP Product Marketing | Formerly LinkedIn, Credit Karma, Handshake • 1y

    In order for Product Marketing to be successful, it’s helpful to project briefs to include: Feature description: A clear and concise explanation of the feature, including what it does and how it works. This serves as the foundation for PMM to develop messaging and positioning. Insights/research: Any relevant data, research, or insights that influenced the decision to build the feature. This helps PMM understand the “why” behind the feature, enabling them to craft compelling narratives that align ...Read More

    544 Views
  8. Mary Sheehan
    Mary Sheehan

    Adobe Head of Lightroom Product Marketing | Formerly Google, AdRoll • 8y

    The more context the better. PMMs should help to fill in the gaps, but a product brief should include:

    - What problem this product / feature solves

    - Who it solves for and insights about this audience

    - Why we solve it differently (different > better)

    - Timeline with milestones to get there

    - Risks to timeline 

    - Broader context/ how this fits in with other things you're doing (or if it's brand new, why / how) 

    Others?

    792 Views
  9. Max A.
    Max A.

    Google Product • 8y

    I’ll probably need to write a blog post about it one day. :) For now, here is a brief summary of what we aligned on with the product team in terms of the categories of inputs we need to prepare a successful launch:Earlier in the process:1. Feature Description2. Target Audience3. Use Case and Customer Benefits4. TimelineLater in the process:5. Business Objective6. Availability (plans the feature will be available under – might not be relevant in your case)7. Support Needed from Marketing8. Linked ...Read More

    684 Views
  10. Tracy Montour
    Tracy Montour

    HiredScore Head of Product Marketing • 3y

    Product Managers have to give us PMMs the information we need to be successful, but it's often on us to inform them of what we need and hold them accountable for providing the proper documentation. Ensure you have a good relationship with the PMs you engage with, as well as the VP of Product who can give you the clearance to hold PMs responsible for providing the right context in the form of a feature brief.  While the work starts WAY before the feature brief is created, here is what I hold the ...Read More

    315 Views
  11. This is a tricky question! I’d argue that there is more to the collaboration between Product Management and Product Marketing than the effectiveness of the Project Brief. As for what to include in the project (or Product) brief, it should outline (at least) the following: Product name and release date Who the product is targeted to Product description Summary of the customer needs the product will meet Customer value proposition The impact the product will have on the customer Launch plan descri ...Read More

    490 Views

Related Ask Me Anything Sessions

Top Product Marketing Mentors