Better small teams pages (#7786)

* team index view, move small team nav * polish * added crest, started to move PA team page blocks around * moving components around * encapsulate milestones and team updates inside box * team icon * source from graphql * team page start * fixed small team person card hover ux * flex da people * placeholder header image * more responsive * add other sections * add team images * add nav * fix subscribe flow * added sum stickers * moved icons * add pineapple sticker * added all country icons, fixed pineapple icons * added all flags * implemented mayor badge * hide small team sidebar (for now) * tighten text * fix in progress modal * update objectives files * cleanup * added GB flag, updated flag pack * tightening text * add objectives to own section * added pineapple sticker * added borked thumbs up sticker * subheader polish * small adj * dark mode * link to small teams --------- Co-authored-by: Eli Kinsey <[email protected]>
PostHog · Mar 5, 2024 · 19f66ad · 19f66ad
1 parent d498062
commit 19f66ad
Show file tree

Hide file tree

Showing 50 changed files with 1,994 additions and 601 deletions.
diff --git a/contents/handbook/small-teams/customer-success/index.mdx b/contents/handbook/small-teams/customer-success/index.mdx
@@ -1,20 +1,11 @@
 ---
-title: Customer Success Team
+title: Customer Success
 sidebar: Handbook
 showTitle: true
 hideAnchor: false
+template: team
 ---
 
-<TeamUpdate />
-
-## People
-
-<TeamMembers />
-
-## Mission
-
-<Mission />
-
 ## Responsibilities
 
 * Own initial inbound contact requests from the website
@@ -23,10 +14,6 @@ hideAnchor: false
 * Make it easy to become a paying customer
 * Ensure long term success with PostHog
 
-## Q1 2024 Goals
-
-<Objectives />
-
 ## Customer
 
 Primarily brand new and existing users of our self-serve product
@@ -60,8 +47,4 @@ Compelling product demonstrations aren't about features; they tell the story of
 
 ## Slack channel
 
-[#team-customer-success](https://posthog.slack.com/messages/team-customer-success)
-
-## What we're building
-
-<TeamRoadmap />
+[#team-customer-success](https://posthog.slack.com/messages/team-customer-success)
diff --git a/contents/handbook/small-teams/data-warehouse/index.mdx b/contents/handbook/small-teams/data-warehouse/index.mdx
@@ -1,24 +1,7 @@
 ---
-title: Data Warehouse Team
+title: Data Warehouse
 sidebar: Handbook
 showTitle: true
 hideAnchor: false
+template: team
 ---
-
-<TeamUpdate />
-
-## People
-
-<TeamMembers />
-
-## Mission
-
-<Mission />
-
-## Q1 2024 Goals
-
-<Objectives />
-
-## What we're building
-
-<TeamRoadmap />
diff --git a/contents/handbook/small-teams/data-warehouse/objectives.mdx b/contents/handbook/small-teams/data-warehouse/objectives.mdx
@@ -1,5 +1,3 @@
-### Goals (Q1)
-
 5 reference customers of data warehouse and imports
 
 * **Key Results:**

diff --git a/contents/handbook/small-teams/exec/index.mdx b/contents/handbook/small-teams/exec/index.mdx
@@ -1,22 +1,7 @@
 ---
-title: Exec Team
+title: Exec
 sidebar: Handbook
 showTitle: true
 hideAnchor: false
+template: team
 ---
-
-## People
-
-<TeamMembers />
-
-## Mission
-
-<Mission />
-
-## Q1 2024 Goals
-
-<Objectives />
-
-## What we're building
-
-<TeamRoadmap />
diff --git a/contents/handbook/small-teams/exec/objectives.mdx b/contents/handbook/small-teams/exec/objectives.mdx
@@ -1,5 +1,3 @@
-### Goals
-
 * Stay in control of our destiny by hitting the [ARR goal](https://docs.google.com/document/d/1Ofpxd5N4e_PKlSbRDEJ86T9Rs2ihfpKQf5MFuohWP1g/edit) and staying within budget
 * Figure out what the (technical) building blocks are of the Product OS
 * Ensure engineering team structure runs smoothly
diff --git a/contents/handbook/small-teams/feature-success/index.mdx b/contents/handbook/small-teams/feature-success/index.mdx
@@ -1,46 +1,11 @@
 ---
-title: Feature Success Team
+title: Feature Success
 sidebar: Handbook
 showTitle: true
 hideAnchor: false
+template: team
 ---
 
-<TeamUpdate />
-
-## People
-
-<TeamMembers />
-
-## Mission
-
-Makers everywhere get better at building products because of PostHog
-
-## Q1 2024 Goals
-
-As always, reliability is the #1 unwritten goal: Making sure feature flags are reliable trumps every other objective.
-
-
-### Objective: Doubling down on surveys
-
-Last quarter, we officially launched surveys and gathered lots of feedback! This quarter, we're building out more of the things that'll make surveys the obvious choice for customers to collect user feedback. 
-
-We will, in order of priority build:
-
-- Event based targeting for surveys
-- Branching logic with multiple questions
-- Better result visualisation for customer experience metric surveys (NPS, CSAT, etc)
-
-### Objective: Doubling down on experiments
-
-Last quarter, we built out the core missing features for feature flags. Now to leverage these building blocks we want to focus on improving our A/B testing platform.
-
-Broadly, we will focus on two themes:
-
-1. Make it easy for people to set up experiments and understand the results, with clear action items on when to end and what to do after ending experiments.
-2. Expand what is possible to track in experiments: From statistical significance for secondary metrics, to having a linked dashboard for extra result exploration.
-
-
-
 ## Values
 - Fast, iterative and high output rather not slow and thoughtful - achieving this
 - Feedback-driven not spec-driven - we do a decent job at this
@@ -130,7 +95,3 @@ Since it's not a positioning issue, Bob & Alice decide that it makes sense to in
 PostHog keeps analysing metrics for this flag over time, and notifies Bob and Alice when their customers behaviour change. For example, if the conversion for users in UK has taken a turn for the better, or if enterprise customers have taken a turn for the worse.
 
 Our long term vision is to make all of this possible.
-
-## What we're building
-
-<TeamRoadmap />
diff --git a/contents/handbook/small-teams/feature-success/objectives.mdx b/contents/handbook/small-teams/feature-success/objectives.mdx
@@ -0,0 +1,21 @@
+As always, reliability is the #1 unwritten goal: Making sure feature flags are reliable trumps every other objective.
+
+
+### Objective: Doubling down on surveys
+
+Last quarter, we officially launched surveys and gathered lots of feedback! This quarter, we're building out more of the things that'll make surveys the obvious choice for customers to collect user feedback. 
+
+We will, in order of priority build:
+
+- Event based targeting for surveys
+- Branching logic with multiple questions
+- Better result visualisation for customer experience metric surveys (NPS, CSAT, etc)
+
+### Objective: Doubling down on experiments
+
+Last quarter, we built out the core missing features for feature flags. Now to leverage these building blocks we want to focus on improving our A/B testing platform.
+
+Broadly, we will focus on two themes:
+
+1. Make it easy for people to set up experiments and understand the results, with clear action items on when to end and what to do after ending experiments.
+2. Expand what is possible to track in experiments: From statistical significance for secondary metrics, to having a linked dashboard for extra result exploration.
diff --git a/contents/handbook/small-teams/growth/index.mdx b/contents/handbook/small-teams/growth/index.mdx
@@ -1,20 +1,11 @@
 ---
-title: Growth Team
+title: Growth
 sidebar: Handbook
 showTitle: true
 hideAnchor: false
+template: team
 ---
 
-<TeamUpdate />
-
-## People
-
-<TeamMembers />
-
-## Mission
-
-Maximize the number of people who get value out of PostHog, and help them realize and leverage all the value we offer.
-
 ## What the Growth team does
 
 - Sign up and authentication
@@ -31,25 +22,10 @@ Maximize the number of people who get value out of PostHog, and help them realiz
   - Revenue reporting
 - Internal metrics reporting (company scorecard)
 
-
-## Q1 2024 objectives
-
-- **Objective 1**: Double activation rates for product analytics and session replay
-  - Reasoning: Activation is lower than we'd like it to be, and activation is a leading indicator for retention and revenue
-  - **KR**: 2 customer interviews per week
-  - **KR**: Start 1 new experiment every week
-- **Objective 2**: Launch pricing for Data warehouse, queries, CDP
-  - Reasoning: Customers get lots of value out of these and should be charged accordingly
-  - **KR**: Cost of collaboration doesn't feel too high
-
 ## How to work with the Growth team
 
 In addition to covering specific areas of the product, members of the Growth team can temporarily join other small teams to execute jointly on growth-related tasks.
 This can be done by requesting help during Sprint planning, or at the beginning of the Quarter during the OKR definition phase.
 
 ## Feature ownership
 You can find out more about the features we own [here](/handbook/engineering/feature-ownership)
-
-## What we're building
-
-<TeamRoadmap />
diff --git a/contents/handbook/small-teams/growth/objectives.mdx b/contents/handbook/small-teams/growth/objectives.mdx
@@ -0,0 +1,7 @@
+- **Objective 1**: Double activation rates for product analytics and session replay
+  - Reasoning: Activation is lower than we'd like it to be, and activation is a leading indicator for retention and revenue
+  - **KR**: 2 customer interviews per week
+  - **KR**: Start 1 new experiment every week
+- **Objective 2**: Launch pricing for Data warehouse, queries, CDP
+  - Reasoning: Customers get lots of value out of these and should be charged accordingly
+  - **KR**: Cost of collaboration doesn't feel too high
diff --git a/contents/handbook/small-teams/infrastructure/index.mdx b/contents/handbook/small-teams/infrastructure/index.mdx
@@ -1,25 +1,11 @@
 ---
-title: Infrastructure Team
+title: Infrastructure
 sidebar: Handbook
 showTitle: true
 hideAnchor: false
+template: team
 ---
 
-import Mission from "./mission.mdx"
-import Objectives from "./objectives.mdx"
-
-<TeamUpdate />
-
-## People
-
-<TeamMembers />
-
-## Mission
-
-<Mission />
-
-<Objectives />
-
 ## Slack channel
 
 [#team-infrastructure](https://posthog.slack.com/archives/C01MM7VT7MG)
@@ -73,8 +59,4 @@ The board also acts as a source of truth for other teams to have a quick check i
 
 ## Slack channel
 
-[#team-infrastructure](https://posthog.slack.com/messages/team-platform)
-
-## What we're building
-
-<TeamRoadmap />
+[#team-infrastructure](https://posthog.slack.com/messages/team-platform)
diff --git a/contents/handbook/small-teams/infrastructure/objectives.mdx b/contents/handbook/small-teams/infrastructure/objectives.mdx
@@ -1,5 +1,3 @@
-## Q1 2024 Goals
-
 ### 💪 Deploy with confidence
 Our deploy speed keeps us moving fast but bigger changes would benefit from better tooling to gradually roll out, validate and roll back if necessary.
 

diff --git a/contents/handbook/small-teams/marketing/index.mdx b/contents/handbook/small-teams/marketing/index.mdx
@@ -1,24 +1,11 @@
 ---
-title: Marketing Team
+title: Marketing
 sidebar: Handbook
 showTitle: true
 hideAnchor: false
+template: team
 ---
 
-<TeamUpdate />
-
-## People
-
-<TeamMembers />
-
-## Mission
-
-<Mission />
-
-## Q1 2024 Goals
-
-<Objectives />
-
 ## Slack channel
 
 [#team-marketing](https://posthog.slack.com/messages/team-marketing)

diff --git a/contents/handbook/small-teams/marketing/objectives.mdx b/contents/handbook/small-teams/marketing/objectives.mdx
@@ -1,4 +1,3 @@
-**Goal**
 Increase the number of people signing up for PostHog's products beyond Product Analytics.
 
 **Rationale**

diff --git a/contents/handbook/small-teams/people/index.mdx b/contents/handbook/small-teams/people/index.mdx
@@ -1,26 +1,11 @@
 ---
-title: People & ops team
+title: People & Ops
 sidebar: Handbook
 showTitle: true
 hideAnchor: false
+template: team
 ---
 
-<TeamUpdate />
-
-## People
-
-<TeamMembers />
-
-## Mission
-
-<Mission />
-
-## Objectives & key results
-
-## Q1 2024
-
-<Objectives />
-
 ## Responsibilities
 
 Our people team works across talent, people, operations, and culture. This is what we care about:

diff --git a/contents/handbook/small-teams/pipeline/index.mdx b/contents/handbook/small-teams/pipeline/index.mdx
@@ -1,22 +1,11 @@
 ---
-title: Pipeline Team
+title: Pipeline
 sidebar: Handbook
 showTitle: true
 hideAnchor: false
+template: team
 ---
 
-<TeamUpdate />
-
-## People
-
-<TeamMembers />
-
-## Mission
-
-<Mission />
-
-<Objectives />
-
 ## Responsibilities
 
 Our team owns our ingestion pipeline end-to-end. That means we own:
@@ -83,7 +72,3 @@ It's acceptable for the secondary responsibilities to take up all of your time.
 ## Slack channel
 
 [#team-ingestion](https://posthog.slack.com/messages/team-ingestion)
-
-## What we're building
-
-<TeamRoadmap />