CPM Product Launch and Go-to-Market 2 — Questions and Answers
Question 1: What is 'feature flag' usage in product launches?
- Marking features as important in the backlog
- A technique for enabling or disabling features for specific users or segments without re-deploying code (Correct answer)
- A UI component for displaying new features
- A flag raised during a product launch event
Correct answer: A technique for enabling or disabling features for specific users or segments without re-deploying code
Feature flags allow teams to control the rollout of features to specific user groups, enabling gradual releases, A/B tests, and quick rollbacks without new deployments.
Question 2: What does 'sales enablement' mean in the context of a product launch?
- Hiring more salespeople for the launch
- Providing the sales team with the knowledge, content, and tools needed to effectively sell the new product (Correct answer)
- Automating the entire sales process with software
- Eliminating the sales team through self-serve channels
Correct answer: Providing the sales team with the knowledge, content, and tools needed to effectively sell the new product
Sales enablement ensures the sales team has the training, materials, and competitive information they need to effectively communicate the product's value and close deals.
Question 3: What is a 'launch checklist' and why is it important?
- A list of features to build before launch
- A comprehensive list of tasks across all functions that must be completed to ensure a successful product release (Correct answer)
- A legal compliance document required for all launches
- A personal to-do list for the product manager
Correct answer: A comprehensive list of tasks across all functions that must be completed to ensure a successful product release
A launch checklist ensures nothing critical is missed by capturing all cross-functional tasks — from support readiness to legal review — required for a successful launch.
Question 4: What is 'beta testing' and how does it reduce launch risk?
- Testing by the QA team before any users see the product
- Releasing a pre-launch version to real users to identify issues and gather feedback before the full release (Correct answer)
- A second round of internal code review
- Testing on a second server before production
Correct answer: Releasing a pre-launch version to real users to identify issues and gather feedback before the full release
Beta testing exposes a product to real users before the public launch, uncovering bugs, usability issues, and unmet expectations in time to fix them.
Question 5: What is 'product-led growth' (PLG) as a go-to-market model?
- A model where the product team controls all marketing spend
- A GTM strategy where the product itself drives user acquisition, expansion, and retention without heavy sales involvement (Correct answer)
- A strategy that only applies to consumer products
- A model where product features are sold à la carte
Correct answer: A GTM strategy where the product itself drives user acquisition, expansion, and retention without heavy sales involvement
In PLG, the product creates its own adoption through viral loops, freemium models, or inherent shareability, reducing dependence on sales and marketing for growth.
Question 6: What is a 'launch retrospective' and when should it be conducted?
- A meeting held before launch to plan logistics
- A post-launch review analyzing what went well, what didn't, and what to improve in future launches (Correct answer)
- A retrospective conducted only when a launch fails
- A financial audit of launch spending
Correct answer: A post-launch review analyzing what went well, what didn't, and what to improve in future launches
A launch retrospective captures lessons learned shortly after a product launch, improving future launch processes by reviewing both successes and failures.
CPM Product Launch and Go-to-Market 2
What is 'feature flag' usage in product launches?