Skip to content

Marketing team goals for Q3 2026#18014

Open
joethreepwood wants to merge 6 commits into
masterfrom
mkktg-q3-26
Open

Marketing team goals for Q3 2026#18014
joethreepwood wants to merge 6 commits into
masterfrom
mkktg-q3-26

Conversation

@joethreepwood

Copy link
Copy Markdown
Contributor

Changes

This is a little rough so we can hammer it out if needed.

It's also a little spicy.

My takeaway from the discussion we had was that...

  • Last quarter, nobody completed their sidequests because of capacity, but also because the sidequests weren't really bold or weird enough.
  • It's really hard to choose a PMM goal at this point which isn't just: "Do PMM for [X]" and, while that work is valuable, there probably isn't much value in saying "Do PMM for PostHog Code (Cleo)" because that is already captured in terms of ownership
  • Most of the challenges we isolated for PMMs (sales positioning, cadence of collaboration, focus on self-driving, context warehouse as a thing) are broader than simple product launches and are the most regular limiters

Therefore, I'm proposing that PMMs don't have product-related goals. Instead, they have broader or more specific goals that sit outside of the normal remit of their product (e.g. I could turn away pre-marketing platform as an idea because it isn't about PostHog MCP, but we need it so it should be a goal).

Open to thoughts.

Checklist

  • I've read the docs and/or content style guides.
  • Words are spelled using American English
  • Use relative URLs for internal links
  • I've checked the pages added or changed in the Vercel preview build
  • If I moved a page, I added a redirect in vercel.json

@github-actions

github-actions Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Vale prose linter → found 2 errors, 18 warnings, 0 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/handbook/marketing/ownership.md — 2 errors, 9 warnings, 0 suggestions
Line Severity Message Rule
15:24 warning 'Blitzscale' is a possible misspelling. PostHogBase.Spelling
18:20 warning 'Annika' is a possible misspelling. PostHogBase.Spelling
19:21 warning 'Annika' is a possible misspelling. PostHogBase.Spelling
20:13 warning 'Annika' is a possible misspelling. PostHogBase.Spelling
21:18 warning 'Annika' is a possible misspelling. PostHogBase.Spelling
24:20 warning 'Danilo' is a possible misspelling. PostHogBase.Spelling
55:64 warning 'backlink' is a possible misspelling. PostHogBase.Spelling
69:13 warning 'influencer' is a possible misspelling. PostHogBase.Spelling
101:27 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
101:77 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
125:22 warning Use 'PostHog' instead of 'posthog'. Vale.Terms
contents/teams/marketing/objectives.mdx — 0 errors, 9 warnings, 0 suggestions
Line Severity Message Rule
3:78 warning 'PMMs' is a possible misspelling. PostHogBase.Spelling
8:18 warning 'Waitlists' is a possible misspelling. PostHogBase.Spelling
42:22 warning 'influencers' is a possible misspelling. PostHogBase.Spelling
42:50 warning 'Adlet' is a possible misspelling. PostHogBase.Spelling
45:48 warning 'influencers' is a possible misspelling. PostHogBase.Spelling
50:4 warning 'Sidequests' is a possible misspelling. PostHogBase.Spelling
52:1 warning 'Sidequests' is a possible misspelling. PostHogBase.Spelling
55:31 warning 'Adlet' is a possible misspelling. PostHogBase.Spelling
58:46 warning 'influencers' is a possible misspelling. PostHogBase.Spelling

@github-actions

github-actions Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Jun 30, 2026 04:31PM

Comment thread contents/teams/marketing/objectives.mdx Outdated
- **What we'll ship:** [Planning issue here.](https://github.com/PostHog/requests-for-comments-public/issues/512)
- **Rationale:** Waitlists are helping us drive awareness earlier, but they're fragmented.
- **Things we could do:** Unify the roadmap, WIP, and Coming Soon pages into one source.
- **We'll know we're successful when:** Pre-marketing is an easy, repeatable part of the playbook.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is the intention that we can do this without a PMM being assigned? (ie. it could be treated more as BAU like changelog?)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the goal would be more user and pipeline focused, so I'll tweak this a bit. But yes, I think making it so that this is something eng team leads know to do is also important.

Gives me a good idea regarding layout and design too.

Suggested change
- **We'll know we're successful when:** Pre-marketing is an easy, repeatable part of the playbook.
- **We'll know we're successful when:** Users have one place to register interest, and notifying users is an easy, automated part of how we market.

Comment thread contents/teams/marketing/objectives.mdx Outdated
Comment thread contents/teams/marketing/objectives.mdx Outdated
Comment thread contents/teams/marketing/objectives.mdx Outdated
- **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.
- **Rationale:** We're still betting the farm on it.
- **Things we could do:** Attend sales calls. Find problems. Fix them.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this is glib, but maybe something that included 'make this handbook page indispensable' or something.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Things we could do:** Attend sales calls. Find problems. Fix them.
- **Things we could do:** Attend sales calls. Clarify self-driving for sales. Codify in the handbook.

Comment thread contents/teams/marketing/objectives.mdx Outdated
Comment thread contents/teams/marketing/objectives.mdx Outdated
@github-actions

github-actions Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Bundle report

Total JS (gzip)

6.24 MiB (+0.0 KiB / +0.0%)

Eager graph (static-import closure per entrypoint)

Entrypoint Eager size Budget Modules
app 24.19 MiB (+1.4 KiB / +0.0%) report-only 5516
Largest modules in the app closure
Module Size
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css 713.6 KiB
./src/components/Stickers/Stickers.tsx 696.4 KiB
./.cache/caches/gatsby-plugin-mdx/mdx-scopes-dir/31a094f140f119e73085d847ae81b99b.js + 2 modules 557.7 KiB
./node_modules/.pnpm/@radix-ui+react-icons@1.3.2_react@18.3.1/node_modules/@radix-ui/react-icons/dist/react-icons.esm.js 481.4 KiB
./node_modules/.pnpm/@codemirror+view@6.38.2/node_modules/@codemirror/view/dist/index.js 458.1 KiB
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules 395.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.cjs.js 364.8 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js 354.8 KiB
./src/hooks/useCustomers.tsx + 54 modules 353.9 KiB
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules 351.4 KiB
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js 281.9 KiB
./src/components/ProductComparisonTable/index.tsx + 116 modules 267.6 KiB
./node_modules/.pnpm/@codesandbox+sandpack-react@2.20.0_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@codesandbox/sandpack-react/dist/index.mjs 266.6 KiB
./node_modules/.pnpm/d3@7.9.0/node_modules/d3/src/index.js + 208 modules 247.4 KiB
./src/components/Pricing/PricingSlider/Slider.tsx + 87 modules 239.9 KiB

Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes.

Co-authored-by: Charles Cook <charles@posthog.com>
Comment thread contents/handbook/marketing/ownership.md Outdated
Comment thread contents/teams/marketing/objectives.mdx Outdated
Comment thread contents/teams/marketing/objectives.mdx Outdated
Comment thread contents/teams/marketing/objectives.mdx Outdated
- **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.
- **Rationale:** We're still betting the farm on it.
- **Things we could do:** Attend sales calls. Find problems. Fix them.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Things we could do:** Attend sales calls. Find problems. Fix them.
- **Things we could do:** Attend sales calls. Clarify self-driving for sales. Codify in the handbook.

Comment thread contents/teams/marketing/objectives.mdx Outdated
Comment thread contents/teams/marketing/objectives.mdx Outdated
Comment thread contents/teams/marketing/objectives.mdx Outdated
Some easy suggestionbs

Co-authored-by: Joe Martin <84011561+joethreepwood@users.noreply.github.com>
Comment thread contents/teams/marketing/objectives.mdx Outdated
### Q2 2026 objectives

These are the primary goals the team is prioritizing this quarter.
These are the primary goals the team is prioritizing this quarter. Goals for PMMs are meant to provide an extra level of focus or to define a specific initiative beyond the business-as-usual work that comes from covering a specific product. Supporting [the product they are assigned to](/handbook/marketing/ownership) is always the default quarterly goal.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Practically speaking, when we get together to review at the end of the quarter, will we still separately go 'how did X product go' as well?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can absolutely do that, yeah.

Comment thread contents/teams/marketing/objectives.mdx Outdated
Comment thread contents/teams/marketing/objectives.mdx Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants