Pineapple on pizza

No data available

Members

Goals

Q2 2026 objectives

These are the primary goals the team is prioritizing this quarter.

PMM for MCP & Agents (Joe)
  • Rationale: The future is no interface.
  • Things we could do: Ads. Skills. Onboarding.
  • We'll know we're successful when: MCP becomes the default interface for new users.
  • What we'll ship: Planning issue here.
Connect the observability dots (Sara)
  • Rationale: Error tracking is going proactive. Logs is getting better.
  • Things we could do: Traces/Metrics launch. Error tracking support and repositioning. Cross-sell in onboarding.
  • We'll know we're successful when: We have teams adopting these tools together.
Launch PostHog Code (Cleo)
  • Rationale: We're betting the farm on it.
  • Things we could do: Launch it. Iterate the brand identity. Unite the teams to push it.
  • We'll know we're successful when: 1000+ WAU. Online buzz.
Influencers are multi-format and predictable (Adlet)
  • Rationale: We ramp up the scale and pace, explore new platforms.
  • Things we could do: Reddit influencers. Non-YouTube platforms.
  • We'll know we're successful when: Collabs launching every week.
Get ready to launch Managed Warehouse (Lizzie)
  • Rationale: We want users to know something big is coming.
  • Things we could do: Start building authority and excitement for Managed Warehouse.
  • We'll know we're successful when: People are asking when they can get their hands on the warehouse.

Sidequests

Sidequests are important areas of focus or things the team cares a lot about, but which aren't their primary goal.

Support session replay summarization (Joe)
  • Rationale: This is an important, underrepresented product feature.
  • Things we could do: Support the launch.
Grow Workflows usage (Sara)
  • Rationale: Workflows hasn't blown up yet, but we have plans.
  • Things we could do: Template library.
PMM for Agents (Cleo)
  • Rationale: Headless usage is increasingly common.
  • Things we could do: Put MCP and Skills out there as tier-1 features.
Support data stack growth (Lizzie)
  • Rationale: Our users are building their data infrastructure now.
  • Things we could do: Shout about new data sources and Endpoints.

Handbook

You can find out more about what the marketing team does in the handbook. On Slack we use the #team-marketing channel for most things, while the illustration group uses #design-fish-tank for collecting feedback and sharing work. We also recommend joining #hoglife for irregular doses of hedgehog related joy.

If something needs marketing attention, there are several group handles you can use on Slack.

  • @all-marketers notifies this team, the Docs & Wizard team, the Editorial team, the YouTube team, and James
  • @marketing-team notifies the team members on this page specifically
  • @product-marketers notifies the product marketers on this page specifically

The marketing team isn't responsible for maintaining the website. For that, please refer to the website team.

Product marketing ownership

Product marketers (PMMs) at PostHog are centralized into the marketing team and decide which other teams need dedicated support as part of quarterly planning. This enables the team to allocate resources strategically.

You can see which of our product marketers currently supports which team below.

If a team doesn't have a dedicated PMM then it doesn't mean we won't support it. You can always reach out to the product marketing team in the #team-marketing Slack channel. We explain more about marketing ownership and what product marketers do in the handbook.

Requesting artwork

Need help with artwork, or curious about how illustrators work? Find out how to open an art request.

Questions about this page? or post a community question.