launch-readiness
/launch-readiness
Planuje i ocenia gotowość produktu lub funkcji do premiery: dobiera poziom, rozpisuje fazy od T-60 do T+30 i wskazuje braki przed decyzją.
- Autor
- Hyde-and-Larkin ↗
- Repozytorium
- product-marketing-toolkit ↗
- Licencja
- CC-BY-4.0
- Ostatnia zmiana repozytorium
- 08.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 08.11.2026, bez odwołań do wycofanych modeli i API.
CC-BY-4.0, otwarta.
Co robi i kiedy
Planuje i ocenia gotowość produktu lub funkcji do premiery: dobiera poziom, rozpisuje fazy od T-60 do T+30 i wskazuje braki przed decyzją.
Oryginalny opis (EN)
Plan and score a product or feature launch: pick a launch tier, build a phased plan (T-60 to T+30), check readiness across messaging, enablement, support and measurement, and flag what's missing before go/no-go. Use for launch plans, GTM readiness reviews, release tiering, or launch checklists.
Jak działa
- Overview
- Release Tier System
- Launch Phase Framework
- Launch Readiness Checklist
- Enablement Asset Library
- Success Metrics by Tier
- Cross-Functional Coordination
- Best Practices
- Using This Framework
- Customizing This Framework
Podgląd SKILL.md
--- name: launch-readiness description: "Plan and score a product or feature launch: pick a launch tier, build a phased plan (T-60 to T+30), check readiness across messaging, enablement, support and measurement, and flag what's missing before go/no-go. Use for launch plans, GTM readiness reviews, release tiering, or launch checklists." --- # Launch Readiness Planner > **Part of the [Product Marketing Toolkit](../../README.md).** Before you start, read whatever exists in `context/` (company, positioning, and competitors, plus any launch brief or existing assets the user shares). If those files are empty or missing, ask for the essentials instead of guessing. Label anything you infer as an assumption, and never invent statistics, customer names, or quotes: use a bracketed placeholder like `[sourced metric, n, date]` instead. A comprehensive framework for planning, coordinating, and executing product launches with structured tiers, timelines, and checklists. ## Overview This skill provides a systematic approach to product launches, helping teams: - Categorize releases by impact and effort - Plan launches in structured phases - Coordinate cross-functional work - Track readiness across teams - Ensure nothing falls through the cracks ## Release Tier System Launches are categorized into three tiers based on their impact and required effort. Teams use different criteria depending on their function. ### For Sales & Product Development Teams **Tier 1: New Revenue Opportunities** - Products or features that directly drive new revenue - Significantly increase deal size or average order value - Create new selling motions or go-to-market approaches - Require comprehensive enablement and training - **Example Indicators:** New product line, major pricing change, platform expansion **Tier 2: Fundamental Updates** - Important platform updates that improve competitive positioning - Features that enhance existing value propositions - Functionality that addresses common customer requests - Updates sales teams should know to effectively position - **Example Indicators:** Major feature enhancements, workflow improvements, integration additions **Tier 3: Minor Enhancements** - Small improvements that don't significantly change selling approach - Quality of life updates or incremental feature additions - Changes that require minimal explanation to customers - Updates that don't need extensive enablement - **Example Indicators:** UI improvements, bug fixes, minor feature tweaks ### For Customer Success & Onboarding Teams **Tier 1: Major Change Management** - Releases requiring significant user adjustment or retraining - Introducing entirely new concepts or workflows - Changes that substantially alter how customers use the product - Require dedicated training programs and migration support - **Example Indicators:** New product modules, workflow redesigns, deprecated features **Tier 2: Moderate Change Management** - Updates introducing new functionalities requiring some adjustment - Modifications to existing features that change user workflows - Enhancements that require updated documentation and training - Features that may trigger support questions - **Example Indicators:** New automation options, additional settings, expanded capabilities **Tier 3: Minor Enhancements** - Cosmetic or minor functional changes - Updates requiring minimal training or adjustment - Improvements that are self-explanatory in the UI - Changes that reduce support burden rather than increase it - **Example Indicators:** UI polish, performance improvements, minor bug fixes ## Launch Phase Framework ### Pre-Launch Phase (T-60 to T-14 days) **Early Planning (T-60 to T-30)** *GTM Scoping* - Define target customer segments and personas - Identify target channels for launch communication - Size opportunity and estimate acquisition costs - Develop messaging strategy and positioning - Conduct competitive intelligence gathering *Product & Technical* - Complete beta testing and gather feedback - Finalize product functionality and edge cases - Prepare demo environments and accounts - Document known issues and workarounds - Plan technical support escalation paths *Content Development* - Draft core messaging and positioning - Create initial sales pitch and talking points - Develop use case examples and scenarios - Begin FAQ document development - Plan visual assets and screenshots **Mid-Planning (T-30 to T-14)** *Enablement Asset Creation* - Sales pitch deck (see Asset Library below) - One-pagers (customer-facing and sales-facing) - Demo scripts and video recordings - Battlecards vs. key competitors - Objection handling guide - Discovery question framework - Product screenshots and UI walkthroughs *Cross-Functional Alignment* - Lock pricing and packaging details - Finalize go-to-market strategy and tactics - Complete internal FAQ document - Prepare support team training materials - Schedule enablement sessions - Set success metrics and monitoring approach *Marketing Preparation* - Develop campaign creative and messaging - Build landing pages or web updates - Create email templates and sequences - Prepare social media assets - Draft press release (if applicable) - Set up analytics and tracking ### Launch Phase (T-14 to Launch Day) **Final Preparation (T-14 to T-7)** - Publish all assets to wherever the field already looks (enablement platform, wiki, CRM) - Conduct live training sessions for sales and support teams - Distribute launch communications to internal teams - Run final QA checks and smoke tests - Confirm go/no-go with key stakeholders **Launch Week (T-7 to Launch)** - Daily stand-ups with launch team - Monitor all systems and readiness indicators - Address any last-minute blockers - Prepare day-of launch communications - Set up real-time monitoring dashboards **Launch Day** - Execute launch communications (internal → external) - Activate marketing campaigns - Monitor product performance and usage - Track support ticket volume and themes - Hold launch team check-ins - Capture early wins and customer feedback ### Post-Launch Phase (Launch to T+30 days) **Week 1 Post-Launch** - Daily performance monitoring and reporting - Rapid response to issues or feedback - Collect field team feedback on enablement quality - Document early wins and customer success stories - Address gaps in documentation or training - Update FAQs based on actual questions **Week 2-4 Post-Launch** - Weekly performance reviews against KPIs - Iterate on messaging based on what's landing - Update enablement materials with learnings - Conduct post-launch retrospective - Document lessons learned - Plan ongoing enablement and support ## Launch Readiness Checklist This comprehensive checklist ensures all workstreams stay coordinated. ### GTM Scoping (T-60) - [ ] Target customer segments defined - [ ] Target channels identified - [ ] Opportunity sizing and cost estimates completed - [ ] Messaging strategy drafted - [ ] Positioning vs. competitors clarified - [ ] Success metrics and KPIs defined ### Product & Technical (T-30 to T-14) - [ ] Beta testing completed - [ ] Product functionality finalized - [ ] Demo environment prepared - [ ] Known issues documented - [ ] Technical support escalation paths defined - [ ] Product screenshots captured ### Messaging & Positioning (T-30) - [ ] Core messaging framework finalized - [ ] Value propositions documented - [ ] Use cases developed - [ ] Competitive differentiation clarified - [ ] Claims validated and legal-approved - [ ] Messaging tested with sales team ### Enablement Assets (T-30 to T-14) **Tier 1 Required Assets:** - [ ] Sales pitch deck (10-15 slides) - [ ] Sales-facing one-pager - [ ] Customer-facing one-pager - [ ] Demo video or script (2-3 minutes) - [ ] FAQ document (internal) - [ ] Battlecard vs. top 2-3 competitors - [ ] Discovery question guide - [ ] Objection handling guide - [ ] Launch cheat sheet **Tier 2 Required Assets:** - [ ] Feature-specific one-pager - [ ] FAQ additions - [ ] Update to existing playbook - [ ] Demo talking points - [ ] Competitive updates (if relevant) **Tier 3 Required Assets:** - [ ] FAQ updates - [ ] Brief talking points - [ ] Include in roundup communications ### Training & Enablement (T-14 to Launch) - [ ] Live training sessions scheduled - [ ] Training materials published - [ ] Demo accounts distributed - [ ] Enablement hub updated (platform, wiki, or CRM) - [ ] Internal comms distributed - [ ] Support team briefed ### Marketing & Communications (T-14) - [ ] Campaign creative finalized - [ ] Landing pages or web updates ready - [ ] Email sequences built - [ ] Social media assets prepared - [ ] Analytics and tracking configured - [ ] Press release drafted (if applicable) ### Launch Day Execution - [ ] Internal announcement sent - [ ] Customer communications distributed - [ ] Marketing campaigns activated - [ ] Product released to target audience - [ ] Monitoring dashboards active - [ ] Launch team standing by for issues ### Post-Launch (T+7 to T+30) - [ ] Performance metrics reviewed daily/weekly - [ ] Field feedback collected and synthesized - [ ] Enablement materials updated based on feedback - [ ] Win stories documented - [ ] Lessons learned captured - [ ] Post-launch retrospective completed ## Enablement Asset Library ### Tier 1 Asset Specifications **Sales Pitch Deck (10-15 slides)** *Structure:* 1. Market context / why now 2. Customer pain points 3. Solution overview 4. Key differentiators (vs. competitors) 5. Proof points and customer stories 6. Use cases by vertical 7. Pricing and packaging 8. Competitive positioning 9. Objection handling 10. Next steps / call to action **Sales-Facing One-Pager** *Contents:* - Quick reference for discovery calls - Key messages and value props - Common objections with responses - Competitive talking points - Discovery questions - Success stories or proof points - Where to find more resources **Customer-Facing One-Pager** *Contents:* - Problem statement and solution - Key benefits and outcomes - Use case examples - Proof points or customer testimonials - Pricing summary (if applicable) - Call to action **Demo Video or Script (2-3 minutes)** *Structure:* - Problem setup (30 seconds) - Solution walkthrough (90 seconds) - Results / proof (30 seconds) - Call to action (15 seconds) **FAQ Document (Internal)** *Categories:* - Product functionality - Pricing and packaging - Technical requirements - Competitive positioning - Roadmap questions - Implementation process **Battlecard** *Structure:* - At-a-glance comparison (us vs. them) - When you'll encounter them - Why we win - How to position against them - Objection handling - Trap-setting questions - Win stories **Discovery Question Guide** *Question Types:* - Situation questions (understand current state) - Problem questions (surface pain) - Implication questions (amplify cost of inaction) - Need-payoff questions (build desire) - Trap-setting questions (expose competitor weaknesses) **Objection Handling Guide** *Common Objection Categories:* - Price objections - Feature/capability objections - Competitive objections - Timing objections - Risk/uncertainty objections - Technical/integration objections **Launch Cheat Sheet** *Quick-win content for first 30 days:* - Top 3 messages - Top 3 differentiators - Top 3 proof points - Top 3 objections with responses - Where to find more resources ## Success Metrics by Tier ### Tier 1 Launch Metrics **Readiness Indicators** - Live training attendance rate (target: >80%) - Training satisfaction score (target: >4.0/5.0) - Asset utilization rate in first 2 weeks (target: >70%) - Demo account adoption (target: >90%) - Support ticket volume on launch day (target: <10% of BAU) **Engagement Indicators** - Sales pitch deck usage in first month - Battlecard views and downloads - Customer-facing one-pager shares - Discovery calls mentioning new product/feature - Win/loss reporting with feature tag **Business Outcomes** - Product adoption rate (% of target segment) - Revenue attribution (deals influenced or closed) - Deal size impact (change in ACV/AOV) - Win rate vs. key competitors - Customer satisfaction scores ### Tier 2 Launch Metrics **Readiness Indicators** - Asset views in enablement platform - FAQ utilization rate - Support team confidence score **Engagement Indicators** - Feature adoption rate - Customer inquiries or interest signals - Sales team mentions in calls **Business Outcomes** - Feature usage metrics - Support ticket reduction (for workflow improvements) - Customer satisfaction or NPS impact ### Tier 3 Launch Metrics **Readiness Indicators** - Internal awareness (% of teams aware) - FAQ updates completed - Support documentation updated **Business Outcomes** - Feature adoption rate - Customer feedback sentiment - Support ticket volume related to change ## Cross-Functional Coordination ### Key Roles and Responsibilities **Product Marketing Manager (PMM) - DRI** - Overall GTM strategy and execution - Messaging and positioning development - Enablement asset creation - Cross-functional coordination - Launch communication - Post-launch measurement **Product Manager (PM)** - Product readiness and functionality - Beta program execution - Technical documentation - Roadmap communication - Feature prioritization **Sales Enablement** - Training program delivery - Asset distribution and platform management - Field feedback collection - Ongoing enablement support **Marketing** - Campaign development and execution - Web and content updates - Demand generation - Lifecycle communications **Customer Success / Support** - Customer communication - Training material development (customer-facing) - Support escalation planning - Customer feedback collection **Engineering / Product Delivery** - Product release execution - Technical monitoring - Bug fixes and issue resolution - Performance optimization ### Communication Cadence **Weekly (During Active Launch Planning)** - Launch team sync (status, blockers, decisions) - Cross-functional standup (quick updates) - Stakeholder communication (async where possible) **Bi-Weekly** - Steering committee or leadership updates - Go/no-go checkpoint reviews - Risk and mitigation planning **Ad-Hoc** - Blocker resolution - Emergency decision-making - Rapid response to issues ## Best Practices **Start Early** - Tier 1 launches need 8+ weeks of planning - Tier 2 launches need 4-6 weeks - Tier 3 launches need 2-4 weeks - Buffer for unexpected delays **Over-Communicate** - Regular status updates to all stakeholders - Make blockers visible early - Document all decisions with rationale - Use centralized source of truth (e.g., shared doc, project tracker) **Prioritize Enablement** - Train before launch, never surprise teams - Multiple formats: live, recorded, written, quick reference - Make materials easy to find and search - Show, don't just tell (demos beat descriptions) **Measure and Iterate** - Define success metrics before launch - Monitor closely in first 2 weeks - Collect feedback systematically - Update materials based on what's working **Plan the Post-Launch** - Don't treat launch day as finish line - Schedule regular check-ins for first month - Document wins and lessons learned - Plan ongoing enablement and optimization ## Using This Framework ### For a Tier 1 Launch: 1. Start planning at T-60 (8+ weeks before launch) 2. Complete all GTM scoping activities 3. Develop full asset library (pitch deck, one-pagers, demo, FAQ, battlecard, etc.) 4. Conduct live training for all customer-facing teams 5. Execute comprehensive marketing campaign 6. Monitor closely post-launch with daily check-ins 7. Iterate based on feedback ### For a Tier 2 Launch: 1. Start planning at T-30 (4-6 weeks before launch) 2. Develop targeted assets (one-pager, FAQ additions, demo points) 3. Update existing playbooks and materials 4. Brief teams through existing channels (roundup meetings, Slack) 5. Light marketing support (web updates, email inclusion) 6. Monitor and collect feedback ### For a Tier 3 Launch: 1. Start planning at T-14 (2-4 weeks before launch) 2. Create minimal assets (FAQ update, talking points) 3. Communicate through existing channels 4. Include in regular product update communications 5. Light monitoring and feedback collection ## Customizing This Framework This framework can be adapted for different: - **Company sizes**: Adjust timeline and asset requirements - **Product types**: Platform releases vs. feature updates vs. new products - **Market segments**: SMB vs. Enterprise requires different approaches - **Launch urgency**: Emergency releases may compress timeline The core principles remain: - Tiered approach based on impact - Phase-based planning - Cross-functional coordination - Comprehensive checklists - Clear ownership and accountability ## Common Pitfalls to Avoid **Underestimating Timeline** - Starting too late leads to rushed execution and gaps - Build in buffer for dependencies and unexpected issues **Skipping Post-Launch** - First 2 weeks after launch are critical for iteration - Feedback collected early shapes long-term success **Over-Tiering** - Not every release is Tier 1 - Save comprehensive approach for high-impact launches **Lack of Ownership** - Ambiguous DRIs lead to dropped balls - Make one person accountable for each workstream **Training After Launch** - Teams need enablement BEFORE customers start asking questions - Never surprise the field with new products or features **Ignoring Field Feedback** - Sales and support teams know what's landing - Create feedback loops and act on input ## Integration with Other Frameworks This Launch Readiness Planner works alongside: - Messaging frameworks (for positioning and value props) - Competitive intelligence (for battlecards and differentiation) - Sales enablement programs (for training delivery) - Product development processes (for beta and release management) - Marketing campaign planning (for demand generation) --- This skill provides structure and process for product launches, ensuring teams coordinate effectively and nothing falls through the cracks. Adapt the framework to your organization's needs while maintaining the core principles of tiered planning, phase-based execution, and comprehensive readiness tracking.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · Hyde-and-Larkin/product-marketing-toolkit | 95 | CC-BY-4.0 |
| RizwanZafaris/product-manager-OS | 100 | MIT |
| event4u-app/agent-config | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 72ae3fbb6acf (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100gtm-launch
Planuje start produktu lub funkcji i sprawdza gotowość: cel, narrację, materiały, kanały, enablement i bramkę gotowości; domyślnie dla segmentu SMB. - 100go-to-market
Pomaga planować premierę produktu lub funkcji: strategia wejścia na rynek, komunikaty, kanały, enablement i kryteria sukcesu premiery. - 100pm-launch-plan
Buduje plan wprowadzenia na rynek (GTM) i listę gotowości według Pragmatic: programy, enablement i okno rynkowe, jako Markdown lub Word. - 100launch-command
Koordynuje start produktu i ocenia gotowość, śledząc zadania w zespołach funkcjonalnych oraz bramki go lub no-go. - 90product-launch-gtm
Prowadzi start produktu lub funkcji od początku do końca: wielkość startu, wybór kanałów GTM, uzgodnienia i przegląd po premierze. - 100launch-checklist
Tworzy listę kontrolną premiery oprogramowania obejmującą gotowość techniczną, komunikację z klientami, wsparcie i kroki uruchomienia.