PostHog Handbook Library / Engineering

750 words. Estimated reading time: 4 min.

# Managing small teams

Small team pages are managed in a few places:

1. MDX files in the repo under `/contents/teams/{team-name}`

- _Quarterly goals, team-specific handbook content_

1. Team records in our CMS, with all fields editable directly on the small team page

- _Team photo, mission, crest_

1. Small team FAQs

- _Aggregated from team member profiles, and from our CMS_

#### Team page content

Any MDX files in the repo will display below the team members and _recently shipped_ sections.

#### Quarterly goals

We're moving toward having quarterly goals in their own MDX files, like `2024-Q1.mdx`. This will allow us to show the current team goals, while displaying previous goals in an accordion.

Until then, when adding quarterly goals for a new quarter, add them to the `index.mdx` file and move the previous goals into a section below them (rather than deleting):

    ## Previous goals

    <details>
    <summary>Q3 2024 goals</summary>

    ### Goal 1

    - Details
    - More details

    ### Goal 2

    - Details
    - More details

    </details>

See the 's page as an example of how it will look.

---

### Team management

#### Creating a new small team

##### Website steps

1. Make sure you're logged in to your community account
2. Navigate to `/teams`
3. Click the _New team_ button
4. Fill in all fields
5. Click _Save & publish_

##### Repo steps

1. Create a directory for the team in `/contents/teams/{team-name}` and duplicate `index.mdx` and `objectives.mdx` from another team as a starting point

The new team will be added to the _Teams_ page on the next build.

#### Editing a small team

1. Make sure you're logged in to your community account
2. Navigate to the small team page you wish to edit
3. Click the _Edit_ button (top right corner of the app window)
4. Edit the desired fields
5. Click _Save_

##### Add content to the small team's page

Visit the new small team page to:

1. Add team members (Login, click the Edit button)
2. Assign the team lead (click the crown icon)
3. Update the team photo and caption (click the team photo to upload)
4. Update the team's mission
5. Update the team crest (click _Edit crest_ to customize your team's crest)

- Use the default crest and default mini crest images until you have a custom crest.

##### Other tasks

1. Request a custom team crest from Lottie. Describe your team with a few adjectives, maybe physical tools that can be used in an illustration, and a sentence or two about what you do. She'll create two versions: a large one (for your small team's page) and a mini crest used in other places (like the careers page).
2. Create a new team on GitHub and remove the new members from their previous team. If moving a previous team lead, remove their team lead status from the previous team first.
3. Give that newly-created team Direct Access with Write permission to the `posthog` and `posthog.com` repositories, as well as any other repos they will be contributing to frequently. This allows team members request review from their team instead of having to tag members individually.
4. Create the new `feature/team-{team-name}` labels on GitHub.
5. Add the team's feature ownership to the feature list.

- Features are managed in `/src/hooks/useFeatureOwnership.tsx`.
- `owner`: Use the team's slug (seen in the URL when visiting a small team's page). Supports an array for shared ownership.
- `notes`: (Optional) Displays below owners. (Wrap string in &lt ;em&gt;brackets&lt;/em&gt;)
- `label`: Defaults to the feature name, but slugified. Override with a custom tag if necessary. Supports `false` to hide the label if one doesn't exist.

1. On Slack, create a new channel called #team-{team-name}. Add a new People > User group with the handle @team-{team-name}-folks. Add / Remove people from other groups as necessary.
2. If there are existing forum topics or roadmap items, re-assign them to the new team.

- Make sure there's a group in Zendesk for the new team, and add the `zendeskGroupID` to the team's record in Strapi so community questions are routed to the right team in Zendesk. (Ask the Website & Docs team for help here.)

1. Update small team names in Ashby. These are used to categorize jobs by team on the careers page.

#### Managing a small team

To manage content on the small team page, see the Add content to the small team's page section above.

### Renaming a small team

This requires coordination with the team, as updating team names involves changing slugs which will break builds if not done in the correct order. Ask in #posthogdotcom team for help.

#### Removing a small team

Ask in #posthogdotcom team for help.

Canonical URL: https://posthog.com/handbook/engineering/posthog-com/small-teams

GitHub source: contents/handbook/engineering/posthog-com/small-teams.mdx

Content hash: `91c455d0b05d257e`

Static reader notes

- `MDX_COMPONENT_STATIC_ADAPTER`: Adapted interactive MDX components for static reading: PrivateLink, SmallTeam.