PostHog Handbook Library / Customer Success

866 words. Estimated reading time: 4 min.

Shipping product changes

Being a CSM at PostHog is about being as impactful for our customers as possible. Part of that is improving the product for them if we can. Aligned with that goal, every new CSM should aim to merge at least one product PR in their first 90 days. This is a goal, not a requirement.

For former engineers, this is an exercise in learning how we ship. For non-engineers, what you're really after is three things the docs won't teach you:

Pick something

Start small! It should be impactful, ideally tied to a customer request or an outcome you want to drive. A couple of examples of good first PRs:

Skip anything already on a team's roadmap, or anything that spans products. Warehouse sources are a good place to start. Each source is its own module, so the blast radius is small and easy to see, and the repo has agent skills for them in .agents/skills/.

Best practices

Building it

Getting it merged

What done looks like

You can say what your change touched, which checks ran and what they test, how long it took to reach prod, and who owns that code.

If the PR gets closed instead, that's fine. Sometimes the owning team takes your fix and ships a better version, which still counts. Leave a comment saying why it closed and link whatever replaced it.

Your book is still the job. If you get stuck after a few days on the PR, it's best to hand it to the owning team with what you learned and they'll take it from there. Then, when the next opportunity presents itself, start at the top and do it all again.

Canonical URL: https://posthog.com/handbook/customer-success/shipping-product-changes

GitHub source: contents/handbook/customer-success/shipping-product-changes.md

Content hash: 7022b9524c91a00b

Static reader notes
  • MDX_COMPONENT_STATIC_ADAPTER: Adapted interactive MDX components for static reading: PrivateLink.