Best Practice Communications Cheat Sheet
Last updated: February 13, 2024
Designing and maintaining best practices is a collaborative effort between Product teams and Commercial teams. However, in order to execute, we’ve identified specific ownership during specific product stages – you can find those and a couple FAQs listed below.
Quick Resources
Best practice ownership and expectation during each product stage
| Stage | Who (Main owner is bold) | What |
|---|---|---|
| PRD creation | PM creates Product Marketing and Quality Control are tagged in document |
Begin reading, understanding in preparation for beta OR If there will not be a beta align with PM on next steps/timing |
| Beta, other testing or before release (if no beta or testing) | PM Product Marketing Quality Control |
Align on INITIAL best practices to be shared in HP, trainings, etc QC is responsible for asking and aligning with PM/others participating in beta on: 1. What are best practices? 2. How are we maintaining quality after general release? (examples below) – Do we need to monitor initial usage? – Do we want to audit usage at a certain adoption rate or time frame? |
| At release | Product Marketing | Product Marketing is responsible for relaying best practice information to org (through slack, trainings, help pages, etc) |
| After release | Product Marketing Product Champions – QC is included in Product Champions for visibility (and can assist if needed) but not driving this part |
Through additional training, best practice feedback form submissions and/or strategic Product Champions usage, Product Marketing is responsible for maintaining best practices. “Strategic PC usage” = Product Champions are asked specific questions on initial usage and best practices and if any adjustments are needed or learnings have been had – Timing and needs TBD per feature – Product Marketing executes any updates as needed (HP, Trainings, slack posts, etc) |
FAQs
How can we ensure best practices are created for all features / updates even if all features do not have betas?
- PRDs – to be edited to include explicit Best Practice section
What are our expectations for best practices throughout a features lifecycle?
- At general release:
- Good fits and Bad fits
- When enabling – are there other features or settings we need to disable or enable?
- Intended use – should teams use it immediately? should this be replacing existing hacks? should this be used for new clients, existing or both moving forward?
- Other functional best practices, if applicable, to protect conversions or usability – for example, naming conventions, making sure it’s easy to support
- After general release – Any adjustments to previously stated best practices using information from those that have spent time with the feature “in the wild”
- More specific use cases (good or bad) with results (conversions, support time, etc)