PostHog Handbook Library / Growth

402 words. Estimated reading time: 2 min.

# Growth reviews

Now that PostHog has found product market fit, we hold regular growth reviews where we plan work to accelerate our growth and drive revenue. These sessions are only worth running _after_ you've found product market fit because until then you need to focus on building a solution users feel they really need. Once you've found product market fit, growth sessions can help you optimize.

We've established a successful pattern for running these meetings every four weeks and actions we've taken from them have led to some significant increases in monthly revenue growth.

### Attendees

We find it's important to bring a mixture of technical people, and those with wide context of what the business is working on. Regular attendees include...

- Raquel (Manages lots of engineering teams)
- Tim (Co-CEO)
- James (Co-CEO)
- Charles (Sales/Marketing/Ops Exec)

### Running a growth review

#### Before the meeting

- Before the meeting, everyone creates a list of hypotheses. These can be problems which limit growth, or opportunities to accelerate. They should all be related to growth engineering (e.g. not simple bug fixes), and they should be focused on improving our long term monthly growth rate.

Examples:

- "New, more expensive pricing has hurt signups"

- "We're not solving bugs quickly and this is hurting word of mouth growth"

- "We are losing B2C customers to open source"

- "We should charge for products separately so we can upsell on features rather than volume. This would let us charge sooner than our current 1m events/month limit, and would let us keep prices low for people that don't use the full breadth of the platform"

#### During the meeting

- When the meeting starts, allocate 10 minutes for people to read through everything and to add any additional hypotheses.

- After reading, watch session recordings of users going through key flows of the product. Allocate 20 minutes for this. This may generate some further hypotheses. For example, users converting to paying customers, users activating, users inviting their colleagues.

- During the meeting, you should work through each hypothesis to determine if it is correct and decide how to respond. Answer each hypothesis using available data and write up any actions, such as experiments you want to run, with clearly allocated owners.

#### After the meeting

- Four weeks later, re-run the entire meeting. You may end up carrying some hypotheses from session to session if they're blocked or lower priority.

### Growth session template

    ## Agenda

    * 10 mins to read through / add or edit hypotheses
    * 20 mins to review session recordings
    * 4 hours to work through hypotheses and to create actions

    ## Hypothesis

    Why aren't we growing faster?

    *

    ## Actions

    *

### Relevant docs

- Growth review recurring doc (Internal only)

Canonical URL: https://posthog.com/handbook/growth/growth-engineering/growth-sessions

GitHub source: contents/handbook/growth/growth-engineering/growth-sessions.md

Content hash: `b618e3e249b7f26c`