Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
133 changes: 0 additions & 133 deletions contents/teams/content/objectives.mdx
Original file line number Diff line number Diff line change
@@ -1,133 +1,3 @@
## Editorial

<details>
<summary>2x-ing upper-funnel content</summary>

**Owner:** Natalia Amorim

**Motivation:** We want to build a repeatable system for refreshing existing content and expand our upper-funnel library to capture more organic traffic. The goal is to make our content engine more sustainable, ensuring older articles stay current while consistently adding new ones that meet users earlier in their discovery journey.

**What we'll ship:**

* Test AirOps as a tool to refresh existing articles at scale, optimizing them for both traditional search and LLM visibility. This includes updating metadata, improving page structure for LLM readability, refreshing content, and ensuring all PostHog features and positioning are current.
* Create new upper-funnel content (alternatives, listicles, etc.) that targets high-volume keywords and attracts users in the awareness and consideration stages across all product categories.

**We'll know we're successful when:**

* We’ve established a repeatable refresh workflow that improves LLM visibility and keeps articles accurate and current.
* We have strong upper funnel content coverage capturing high-volume searches across all product categories
* LLM outputs reflect accurate, up-to-date info about PostHog.
* We see steady growth in visibility from both traditional search and LLM outputs.

</details>

<details>
<summary>Sharpening our AEO strategy</summary>

**Owner:** Natalia Amorim

**Motivation:** We want to ensure PostHog is represented accurately and prominently in LLM outputs by tracking prompts, monitoring citations, and running experiments to see how optimized and new content can influence the answers these models generate.

**What we'll ship**

* Roll out an AEO tracking tool to monitor prompts and citations at both a general and per-product level.
* Run a Q4 “blitz” on error tracking as treatment vs control to measure AEO impact before scaling.
* Create and/or optimize content specifically for LLMs
* Pilot YouTube as an AEO lever via prescriptive creator briefs

**We'll know we're successful when**

* We have end-to-end visibility on how PostHog shows up in LLMs across products
* Key competitor and product prompts consistently surface PostHog in accurate, positive ways and echo our developer tool positioning
* We can measure the impact of AEO efforts and expand proven tactics across product lines.

</details>

<details>
<summary>Better reporting on content performance</summary>

**Owner:** Natalia Amorim

**Motivation:** Right now, performance data is scattered and often looked at in isolation. We want to introduce a structured monthly content performance review to give the team clearer visibility across products, spot trends, and use those insights to guide planning, prioritization, and decision-making.

**What we'll ship**

* A recurring monthly content review
* Dashboards and supporting materials

**We'll know we're successful when**

* The team has clear visibility into how content is performing at both an overall and per-product level.
* Everyone can access and understand key metrics without needing to dig.
* Insights from reviews consistently shape our content planning and prioritization.

</details>

<details>
<summary>Newsletter</summary>

**Owner:** Ian Vanagas

**Motivation:** We've scaled back our paid acquisition with the newsletter, because it was bringing in low quality subscribers and clouding our ability to understand how the newsletter is performing. If we want the newsletter to be successful for the long term, we need it to grow organically.

**What we'll ship:**

- A great newsletter every two weeks
- Audit of subscriber list to remove inactive subs
- 3 social (primarily LinkedIn) posts per newsletter to build our social posting muscle

**We'll know we're successful when:**

- We're growing our newsletter audience organically
- We are confident the newsletters we are publishing are performing well

</details>

<details>
<summary>Better high-level messaging</summary>

**Owner:** Ian Vanagas

**Motivation:** We’ve had a lot of changes in terms of positioning of the company lately and that has left a scattering of messaging across our site, content, and how we talk about ourselves.

**What we'll ship:**

- A marketing handbook page with key messaging, such as
- What is PostHog?
- What are the benefits of using PostHog?
- Why use PostHog over other options?
- Update pages that talk about these things to be consistent
- A statement we can use everywhere

**We'll know we're successful when:**

- Our own team and content is using this messaging more
- We hear that messaging back from users
- People on social media use this messaging, instead of "product analytics"

</details>

<details>
<summary>Ship the product engineer handbook this time</summary>

**Owner:** Andy

**Motivation:** We want to completely own the concept of the Product Engineer by creating its central text. We're 80% of the way there. Need to ship final 20%.

**What we'll ship:**

* Intro chapters of the handbook using a similar structure to the company handbook.

**We'll know we're successful when**

* We've shipped the first version of the guide
* Positive initial reaction from our users and readers
* Ranking for product engineer keywords in search
* Incoming users convert to reading other parts of guide
* Converting handbook readers to subscribers of the newsletter

</details>

## Docs

<details>
Expand Down Expand Up @@ -411,9 +281,6 @@
<details>
<summary>Anti-goals</summary>

* Digital PR (both on the community side with Reddit and GitHub, and on the PR outreach side for publications); it's something that could help us move the needle with LLMs, but not a priority in the short or medium term.
* Multimedia product comparisons. Could be a strategic advantage, not something we have capacity to take on right now
* Figuring out long term newsletter strategy
* Writing all product docs for all product teams. It’s not practical or efficient, we do better if we help with planning, reviewing, and organizing new docs instead.
* Overhauling platform docs right now – this a long term goal that our current goals feed into.

Expand Down
15 changes: 15 additions & 0 deletions contents/teams/editorial/index.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
title: Editorial
sidebar: Handbook
showTitle: true
hideAnchor: false
template: team
---

## Slack channel

[#team-editorial](https://app.slack.com/client/TSS5W8YQZ/C09GU689J1X)

## Budget

[Budget is here](https://docs.google.com/spreadsheets/d/1ZHu6rMAAll02hw6OaKPe1A_bzlCDui_kM01TuktTuSs/edit#gid=0) (internally viewable only)
1 change: 1 addition & 0 deletions contents/teams/editorial/mission.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Make PostHog a hub for product engineers to learn and collaborate
116 changes: 116 additions & 0 deletions contents/teams/editorial/objectives.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,116 @@

## 2x-ing upper-funnel content

**Owner:** Natalia Amorim

**Motivation:** We want to build a repeatable system for refreshing existing content and expand our upper-funnel library to capture more organic traffic. The goal is to make our content engine more sustainable, ensuring older articles stay current while consistently adding new ones that meet users earlier in their discovery journey.

**What we'll ship:**

* Test AirOps as a tool to refresh existing articles at scale, optimizing them for both traditional search and LLM visibility. This includes updating metadata, improving page structure for LLM readability, refreshing content, and ensuring all PostHog features and positioning are current.
* Create new upper-funnel content (alternatives, listicles, etc.) that targets high-volume keywords and attracts users in the awareness and consideration stages across all product categories.

**We'll know we're successful when:**

* We’ve established a repeatable refresh workflow that improves LLM visibility and keeps articles accurate and current.
* We have strong upper funnel content coverage capturing high-volume searches across all product categories
* LLM outputs reflect accurate, up-to-date info about PostHog.
* We see steady growth in visibility from both traditional search and LLM outputs.

## Sharpening our AEO strategy

**Owner:** Natalia Amorim

**Motivation:** We want to ensure PostHog is represented accurately and prominently in LLM outputs by tracking prompts, monitoring citations, and running experiments to see how optimized and new content can influence the answers these models generate.

**What we'll ship**

* Roll out an AEO tracking tool to monitor prompts and citations at both a general and per-product level.
* Run a Q4 “blitz” on error tracking as treatment vs control to measure AEO impact before scaling.
* Create and/or optimize content specifically for LLMs
* Pilot YouTube as an AEO lever via prescriptive creator briefs

**We'll know we're successful when**

* We have end-to-end visibility on how PostHog shows up in LLMs across products
* Key competitor and product prompts consistently surface PostHog in accurate, positive ways and echo our developer tool positioning
* We can measure the impact of AEO efforts and expand proven tactics across product lines.

## Better reporting on content performance

**Owner:** Natalia Amorim

**Motivation:** Right now, performance data is scattered and often looked at in isolation. We want to introduce a structured monthly content performance review to give the team clearer visibility across products, spot trends, and use those insights to guide planning, prioritization, and decision-making.

**What we'll ship**

* A recurring monthly content review
* Dashboards and supporting materials

**We'll know we're successful when**

* The team has clear visibility into how content is performing at both an overall and per-product level.
* Everyone can access and understand key metrics without needing to dig.
* Insights from reviews consistently shape our content planning and prioritization.

## Newsletter

**Owner:** Ian Vanagas

**Motivation:** We've scaled back our paid acquisition with the newsletter, because it was bringing in low quality subscribers and clouding our ability to understand how the newsletter is performing. If we want the newsletter to be successful for the long term, we need it to grow organically.

**What we'll ship:**

- A great newsletter every two weeks
- Audit of subscriber list to remove inactive subs
- 3 social (primarily LinkedIn) posts per newsletter to build our social posting muscle

**We'll know we're successful when:**

- We're growing our newsletter audience organically
- We are confident the newsletters we are publishing are performing well

## Better high-level messaging

**Owner:** Ian Vanagas

**Motivation:** We’ve had a lot of changes in terms of positioning of the company lately and that has left a scattering of messaging across our site, content, and how we talk about ourselves.

**What we'll ship:**

- A marketing handbook page with key messaging, such as
- What is PostHog?
- What are the benefits of using PostHog?
- Why use PostHog over other options?
- Update pages that talk about these things to be consistent
- A statement we can use everywhere

**We'll know we're successful when:**

- Our own team and content is using this messaging more
- We hear that messaging back from users
- People on social media use this messaging, instead of "product analytics"

## Ship the product engineer handbook this time

**Owner:** Andy

**Motivation:** We want to completely own the concept of the Product Engineer by creating its central text. We're 80% of the way there. Need to ship final 20%.

**What we'll ship:**

* Intro chapters of the handbook using a similar structure to the company handbook.

**We'll know we're successful when**

* We've shipped the first version of the guide
* Positive initial reaction from our users and readers
* Ranking for product engineer keywords in search
* Incoming users convert to reading other parts of guide
* Converting handbook readers to subscribers of the newsletter

## Anti-goals

* Digital PR (both on the community side with Reddit and GitHub, and on the PR outreach side for publications); it's something that could help us move the needle with LLMs, but not a priority in the short or medium term.
* Multimedia product comparisons. Could be a strategic advantage, not something we have capacity to take on right now
* Figuring out long term newsletter strategy
Loading