-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
Team lead: @lucasheriques
Team Members: @lucasheriques @adboio @fivestarspicy
Exec: @raquelmsmith
The team can decide who's responsible for completing these. Most of it makes sense to fall under the team lead figure but none of it requires any administrator privilege
Setting up a product
- As soon as you start seriously planning a new product, add it as an early access feature as a
concept. You can read more about it here - Inform the Marketing team a new roadmap item is available via the #team-marketing channel
- Create a new folder in the
products/folder in the PostHog repo. You should include at least amanifest.tsxfile defining the base structure of your product.- Category should be
"Unreleased"to avoid showing up in customer's sidebars too early.
- Category should be
- Create an alpha feature flag in
constants.tsx(and in PostHog) to hide your product behind it. This should NOT be the same feature flag as the one in the preview roadmap. You'll wanna change it to the preview roadmap one only once you get close to releasing it to customers.
Moving the product to Alpha
- Slowly add customers you've talked into using your product to the feature flag
- Active alpha users: Giraffe (Holly/Adam), BuildKite (Patrick), SimpleClub (Dennis), Ben's B2B2C platform, Plain (Dimitra), Younes (Frigade comparison user)
- Update
manifest.tsxto include your product under an accurate category other than"Unreleased"
Moving the product to Beta
Beta is when you open up the product to all users who want to opt-in. See releasing as beta for detailed guidance.
- Update your code to use this feature flag rather than the old one
- Make sure you've moved over alpha users to the new feature flag before switching the flag
- Ensure your roadmap item has a feedback link and docs link
- Make sure you're capturing product intent for your product already. You should keep iterating on what's intent and what's not.
- Ensure your roadmap item has a payload with the
ProductKeyyou defined in yourmanifest.tsxfile:{ "product_intent": "your_product_key" }or else people won't see your product in their sidebar - Move your roadmap item from
concepttobeta - Inform the marketing teams a new beta is available via the
#team-marketingchannel - Let
#team-growthknow about the move to get your product added to user's sidebars - product should be added to everyone who already has a product from the same category as the new product in their own sidebar
Launching a new product (GA)
If you're planning to launch your product on a specific quarter, you MUST let the Marketing team know about it at the start of the Quarter.
- Create a Pricing RFC to coordinate with the Billing team
- Pricing signal: strong preference for subscription/flat monthly ($25-50 range). Per-step/impression models deincentivize tour creation. Tim advocated subscription for new products. Billing team building subscription infra for Twig. See RFC pricing section for full signal.
- Inform the
#team-marketingchannel that a new Pricing RFC has been created, they'll create a Launch Plan for you - Continue to communicate timelines in the
#team-marketingchannel - Add your product to the Onboarding flow,
#team-growthcan help with that but you can simply copy it from other products - Update
posthog.comto capture page views on your docs to redirect people to your product during onboarding - Include your product to the "Quick Start" section with some basic
- Figure out what your activation metric is, you can get a PM to help you in case your team doesn't have a PM yet, ask in the
#pmchannel for help
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels