|
1 | | -### Q4 2025 objectives |
| 1 | +### Q1 2026 objectives |
2 | 2 |
|
3 | | -### Make our best creative more repeatable (Lottie) |
| 3 | +These are the primary goals the team is prioritizing this quarter. |
4 | 4 |
|
5 | | -- **Rationale:** The more we polish, the shinier we get. |
6 | | -- **Things we could do:** Five year plan. Hire and onboard. Illustration guide. |
7 | | -- **We'll know we're successful when:** 80% of art is drafted before deadline. |
| 5 | +### Make data stack central to our positioning (Joe) |
8 | 6 |
|
9 | | -### Make design 50% self-serve (Daniel H) |
| 7 | +- **Rationale:** A more cohesive story here will help everyone. |
| 8 | +- **Things we could do:** Land the repositioning. Support the DS team. Hire a Stack PMM. |
| 9 | +- **We'll know we're successful when:** Everyone understands what PostHog is. |
10 | 10 |
|
11 | | -- **Rationale:** Self-serve enables more polish. |
12 | | -- **Things we could do:** Hog library. Production processes. Templates. |
13 | | -- **We'll know we're successful when:** Demand gen can self-serve ad designs. |
| 11 | +### Clarify the go-to-market for Array (Cleo) |
14 | 12 |
|
15 | | -### Make our parties bigger and better (Daniel Z) |
| 13 | +- **Rationale:** The messaging is too vague right now. |
| 14 | +- **Things we could do:** Define the narrative. Isolate the USP. Identify the persona. |
| 15 | +- **We'll know we're successful when:** Users want to try Array. |
16 | 16 |
|
17 | | -- **Rationale:** Events work, so lets do more. |
18 | | -- **Things we could do:** More incubators. More outreach. Mulled wine. |
19 | | -- **We'll know we're successful when:** Our events start to become over-subscribed. |
| 17 | +### Lead us into the observability space (Sara) |
20 | 18 |
|
21 | | -### Deliver the Workflows marketing foundation (Sara) |
| 19 | +- **Rationale:** Logs is just for starters. |
| 20 | +- **Things we could do:** Launch Logs GA. Support further observability tools. |
| 21 | +- **We'll know we're successful when:** Logs reaches product-market fit. |
22 | 22 |
|
23 | | -- **Rationale:** Workflows needs a solid, reliable foundation to launch confidently, that we can rely on after GA. |
24 | | -- **Things we could do:** Ship the essential content, guides, migration docs, website stuff, and other activities like events that will make the necessary hype. |
25 | | -- **We'll know we're successful when:** Workflows start generating revenue. |
| 23 | +### Target our events to product engineers (Daniel Z) |
26 | 24 |
|
27 | | -### Establish us as an AI-first company (Cleo) |
| 25 | +- **Rationale:** We know what works, now we need to double down. |
| 26 | +- **Things we could do:** Launch new event series. Product for Engineers meetups. Event playbook. |
| 27 | +- **We'll know we're successful when:** Our new event series has a fanbase. |
28 | 28 |
|
29 | | -- **Rationale:** This is the direction of travel. |
30 | | -- **Things we could do:** Launch PostHog AI. Launch Tasks. Land the messaging. |
31 | | -- **We'll know we're successful when:** PostHog AI is seen as equal to product analytics. |
| 29 | +### Create a reliable brand style guide (Daniel H) |
32 | 30 |
|
33 | | -### Boost cross-sell, especially with startups (Joe) |
| 31 | +- **Rationale:** As the team grows, consistency matters more. |
| 32 | +- **Things we could do:** A style guide. Ad templates that adhere to it. |
| 33 | +- **We'll know we're successful when:** The style guide can settle design misalignments. |
34 | 34 |
|
35 | | -- **Rationale:** There's so much to do. So, let's do it. |
36 | | -- **Things we could do:** Push buy-outs. Conquest marketing. CSM for startups. |
37 | | -- **Planning issue:** [Track the cross-sell planning issue](https://github.com/PostHog/meta/issues/377) |
38 | | -- **We'll know we're successful when:** PostHog for Startups ARR triples. |
| 35 | +### Turn our merch into a lifestyle brand (Lottie) |
| 36 | + |
| 37 | +- **Rationale:** We all want to be more fashionable. |
| 38 | +- **Things we could do:** Merch campaign with a central theme. Merch collabs. Faster concept-completion turnaround. |
| 39 | +- **We'll know we're successful when:** Non-users start noticing our stuff. |
| 40 | + |
| 41 | +## Sidequests |
| 42 | + |
| 43 | +Sidequests are important areas of focus or things the team cares a lot about, but which aren't their primary goal. |
| 44 | + |
| 45 | +### Keep capacity in line with ambition (Joe & Daniel Z) |
| 46 | + |
| 47 | +- **Rationale:** We need to make sure we keep pace with the other teams. |
| 48 | +- **Things we could do:** Keep the hiring plan moving. Scale PMM. Create a community team. |
| 49 | + |
| 50 | +### Make design not just about art requests (Lottie & Heidi) |
| 51 | + |
| 52 | +- **Rationale:** Design is getting more resource and can become more proactive. |
| 53 | +- **Things we could do:** A Q1 goal for Heidi. A plan of what _we_ want to do. Progress on that. |
| 54 | + |
| 55 | +### Champion LLM Analytics, internally and externally (Cleo) |
| 56 | + |
| 57 | +- **Rationale:** It has PMF and could be the next big thing for us. |
| 58 | +- **Things we could do:** Make noise about new features. Support their roadmap. Increase startup adoption. |
| 59 | + |
| 60 | +### Keep up the Workflows marketing (Sara) |
| 61 | + |
| 62 | +- **Rationale:** Beta launch went well, and GA is on the horizon. |
| 63 | +- **Things we could do:** A launch plan. Use-case based content. Integration launches. |
0 commit comments