Back to portfolio
Content & MarketingSimulated project

Product Marketing Manager portfolio brief

A simulated content & marketing exercise for Product Marketing Manager. Treat it as realistic practice, not real client or protocol work.

Objective

Choose one product and map audience, alternatives, and real proof

Expected deliverables

Positioning documentMessage hierarchyLaunch briefAudience and use-case mapFAQCompetitive notePost-launch review

Recommended workflow

  1. Choose one product and map audience, alternatives, and real proof
  2. Write a message hierarchy and launch FAQ
  3. Review a recent launch and identify where messaging diverged from product reality
  4. Review the result against the rubric, then package it as a case study.

Constraints and safety

  • Use only public sources or clearly simulated data.
  • Never include seed phrases, private keys, or wallet secrets.
  • Redact private user, company, security, legal, or compensation information.
  • State every assumption you make.

Tools in practice

Notion
Draft, review, and maintain positioning document and message hierarchy, with owners, source links, and change history.
Figma
Turn positioning and launch requirements into message frameworks, enablement, and channel-ready assets.
product analytics
Define events and funnels, compare cohorts, and test whether acquisition turns into activation and retention.
Dune
Collect and analyse the evidence used in positioning document and message hierarchy, with definitions and reproducible steps.
CRM
Structure the records behind positioning document and message hierarchy and make review status visible.
research and survey tools
Collect structured intake for positioning document and message hierarchy, with consent and ownership fields where needed.

What a strong submission shows

  • A positioning and message system
  • A launch plan
  • A use-case brief
  • A post-launch analysis connecting message to adoption evidence

Weak submission patterns

  • Slogans without product proof
  • Competitive grids based on marketing claims
  • Launch plans that ignore support, docs, or incident states

Review rubric

  • Accuracy of claims and sources
  • Relevance to the target role
  • Decision quality and trade-offs
  • Completeness of the deliverable
  • Clarity of communication
  • Honest limitations and next steps

Present it as a case study

  • Explain the problem, sources, decisions, ownership, constraints, output, review, and what you would change.
  • Show the final artifact before the process notes.
  • State what you owned and what belonged to other people.
  • Label the work as simulated, and keep any real contribution clearly separate.

Interview questions this project helps you answer

  1. How would you position a product whose strongest feature is technically complex and easy to overclaim?

  2. What evidence should exist before calling a launch successful?

  3. How do you change messaging when the shipped product differs from the original plan?

Turn this into an application