Product Launch Enablement

Turn product changes into field-ready messaging, execution guidance, and launch adoption plans.

Confirm Inputs First

Confirm:

• Whether a current revenue-enablement-context exists; if yes, use it as baseline assumptions, if no, capture only the highest-impact missing context.
• What changed and why it matters
• Target audience and impacted teams
• Launch date and rollout model
• Cross-functional owner model (PMM, Enablement, Sales, CS, RevOps, Support)
• Commercial implications and risks
• Required behavior changes for field teams

If details are incomplete, request missing blockers or proceed with assumptions labeled by risk.

Read The Right Reference

Read references/launch-readiness-framework.md before planning. Read references/source-system-guide.md when launch inputs or distribution depend on docs, Slack, enablement platforms, or project trackers.

Default Workflow

1. Classify launch tier by expected field impact.
2. Define readiness requirements by team and role.
3. Build launch narrative, FAQs, and talk-track updates.
4. Create training plan and reinforcement checkpoints.
5. Add manager inspection prompts for first weeks post-launch.
6. Define readiness gates and go/no-go criteria.
7. Build a cross-functional owner matrix with explicit handoffs and escalation paths.
8. Add a 30-day post-launch signal review loop for adoption, friction, and message drift.
9. Produce launch enablement package and execution timeline.

Tool Notes

• Keep deliverables tool-agnostic.
• Use references/source-system-guide.md for source-of-truth, destination mapping, and safe writeback boundaries.
• If requested, map outputs into the user's docs, slides, or project tracker stack.

Output Contract

Default output includes:

• Launch tier and readiness matrix
• Cross-functional owner and handoff matrix
• Internal launch narrative and FAQ
• Talk-track and objection updates
• Training and reinforcement plan
• Go/no-go readiness checklist
• 30-day post-launch signal review plan

Quality Bar

• Launch guidance is role-specific and action-oriented.
• Field teams can explain the change and when to use it.
• Cross-functional ownership and escalation paths are unambiguous.
• Risks and escalation paths are explicit.
• Readiness criteria are concrete before launch day.