Product Launch Readiness - AiPro Institute\u2122<\/title>\n <style>\n * {\n margin: 0;\n padding: 0;\n box-sizing: border-box;\n }\n\n body {\n font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen, Ubuntu, Cantarell, sans-serif;\n line-height: 1.6;\n color: #333;\n background: #ffffff;\n padding: 2rem;\n min-height: 100vh;\n }\n\n .page-title {\n text-align: center;\n font-size: 2.5rem;\n font-weight: 700;\n margin-bottom: 2rem;\n background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);\n -webkit-background-clip: text;\n -webkit-text-fill-color: transparent;\n background-clip: text;\n }\n\n .card {\n max-width: 1200px;\n margin: 0 auto;\n background: white;\n border-radius: 12px;\n box-shadow: 0 10px 40px rgba(0, 0, 0, 0.1);\n overflow: hidden;\n }\n\n .card-header {\n background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);\n color: white;\n padding: 2.5rem;\n }\n\n .card-header h1 {\n font-size: 2.5rem;\n margin-bottom: 1.5rem;\n font-weight: 700;\n }\n\n .meta-container {\n display: flex;\n gap: 1rem;\n margin-bottom: 1.5rem;\n flex-wrap: wrap;\n }\n\n .meta-badge {\n background: rgba(255, 255, 255, 0.2);\n padding: 0.4rem 1rem;\n border-radius: 20px;\n font-size: 0.9rem;\n display: flex;\n align-items: center;\n gap: 0.5rem;\n }\n\n .compatibility-container {\n display: flex;\n gap: 0.75rem;\n flex-wrap: wrap;\n }\n\n .compatibility-badge {\n background: transparent;\n border: 1px solid rgba(255, 255, 255, 0.4);\n padding: 0.4rem 1rem;\n border-radius: 20px;\n font-size: 0.85rem;\n }\n\n .card-body {\n padding: 2.5rem;\n }\n\n .section {\n margin-bottom: 3rem;\n }\n\n .section-title-container {\n display: flex;\n justify-content: space-between;\n align-items: center;\n margin-bottom: 1.5rem;\n }\n\n .section-title {\n font-size: 1.8rem;\n color: #667eea;\n border-left: 4px solid #667eea;\n padding-left: 1rem;\n font-weight: 600;\n }\n\n .copy-button {\n background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);\n color: white;\n border: none;\n padding: 0.6rem 1.5rem;\n border-radius: 8px;\n cursor: pointer;\n font-size: 1rem;\n font-weight: 600;\n transition: transform 0.2s, box-shadow 0.2s;\n }\n\n .copy-button:hover {\n transform: translateY(-2px);\n box-shadow: 0 5px 15px rgba(102, 126, 234, 0.4);\n }\n\n .prompt-box {\n background: #f8f9fa;\n border: 2px solid #e9ecef;\n border-radius: 8px;\n padding: 1.5rem;\n font-family: 'Courier New', monospace;\n white-space: pre-wrap;\n line-height: 1.8;\n font-size: 0.95rem;\n }\n\n .placeholder {\n color: #fd7e14;\n font-weight: bold;\n }\n\n .tip-box {\n background: #fff9e6;\n border-left: 4px solid #ffc107;\n padding: 1rem 1.5rem;\n margin-top: 1rem;\n border-radius: 4px;\n }\n\n .tip-box strong {\n color: #f59e0b;\n }\n\n .logic-principle {\n margin-bottom: 2rem;\n }\n\n .logic-principle h3 {\n color: #667eea;\n font-size: 1.3rem;\n margin-bottom: 0.75rem;\n font-weight: 600;\n }\n\n .logic-principle p {\n color: #555;\n line-height: 1.8;\n }\n\n .example-box {\n background: #f0f4ff;\n border: 2px solid #667eea;\n border-radius: 8px;\n padding: 1.5rem;\n margin-top: 1rem;\n }\n\n .example-box h4 {\n color: #667eea;\n margin-bottom: 1rem;\n font-size: 1.1rem;\n }\n\n .chain-step {\n background: #f8f9fa;\n border-left: 4px solid #667eea;\n padding: 1.5rem;\n margin-bottom: 1.5rem;\n border-radius: 4px;\n }\n\n .chain-step h3 {\n color: #667eea;\n margin-bottom: 1rem;\n font-size: 1.2rem;\n }\n\n .chain-step .prompt-text {\n background: white;\n padding: 1rem;\n border-radius: 4px;\n font-family: 'Courier New', monospace;\n margin: 1rem 0;\n border: 1px solid #e9ecef;\n }\n\n .hitl-tip {\n margin-bottom: 2rem;\n }\n\n .hitl-tip h3 {\n color: #667eea;\n font-size: 1.2rem;\n margin-bottom: 0.75rem;\n font-weight: 600;\n }\n\n .hitl-tip p {\n color: #555;\n line-height: 1.8;\n }\n\n .card-footer {\n background: #f8f9fa;\n padding: 1.5rem 2.5rem;\n border-top: 1px solid #e9ecef;\n display: flex;\n justify-content: space-between;\n align-items: center;\n }\n\n .footer-stat {\n display: flex;\n align-items: center;\n gap: 0.5rem;\n color: #666;\n font-size: 0.95rem;\n }\n\n .checkmark {\n color: #10b981;\n margin-right: 0.5rem;\n }\n\n @media (max-width: 768px) {\n body {\n padding: 1rem;\n }\n\n .page-title {\n font-size: 1.8rem;\n }\n\n .card-header h1 {\n font-size: 1.8rem;\n }\n\n .card-body {\n padding: 1.5rem;\n }\n\n .section-title-container {\n flex-direction: column;\n align-items: flex-start;\n gap: 1rem;\n }\n\n .copy-button {\n width: 100%;\n }\n\n .card-footer {\n flex-direction: column;\n gap: 1rem;\n align-items: flex-start;\n }\n }\n <\/style>\n<\/head>\n<body>\n <div class=\"page-title\">AiPro Institute\u2122 Prompt Library<\/div>\n\n <div class=\"card\">\n <div class=\"card-header\">\n <h1>\ud83d\ude80 Product Launch Readiness<\/h1>\n <div class=\"meta-container\">\n <div class=\"meta-badge\">\ud83d\udcc1 Product & Operations<\/div>\n <div class=\"meta-badge\">\u23f1\ufe0f 30-40 minutes<\/div>\n <div class=\"meta-badge\">\ud83c\udfaf Advanced<\/div>\n <\/div>\n <div class=\"compatibility-container\">\n <div class=\"compatibility-badge\">ChatGPT<\/div>\n <div class=\"compatibility-badge\">Claude<\/div>\n <div class=\"compatibility-badge\">Gemini<\/div>\n <div class=\"compatibility-badge\">Perplexity<\/div>\n <div class=\"compatibility-badge\">Grok<\/div>\n <\/div>\n <\/div>\n\n <div class=\"card-body\">\n <div class=\"section\">\n <div class=\"section-title-container\">\n <h2 class=\"section-title\">The Prompt<\/h2>\n <button class=\"copy-button\" onclick=\"copyPrompt()\">\ud83d\udccb Copy Prompt<\/button>\n <\/div>\n <div class=\"prompt-box\" id=\"promptContent\">You are an elite Product Launch Strategist specializing in go-to-market planning, cross-functional coordination, and launch risk management. Your expertise lies in assessing launch readiness across product, engineering, marketing, sales, support, and operations to ensure successful market entry with minimal post-launch firefighting.\n\n**CONTEXT SETTING:**\nI need you to conduct a comprehensive launch readiness assessment for <span class=\"placeholder\">[PRODUCT_NAME: e.g., \"Mobile App 3.0 redesign\" or \"Enterprise API Platform\" or \"Premium subscription tier\" or \"Hardware device + companion app\"]<\/span> scheduled to launch on <span class=\"placeholder\">[LAUNCH_DATE: e.g., \"March 15, 2026\" or \"Q2 2026\" or \"6 weeks from today\"]<\/span> to identify gaps, risks, and critical path items requiring attention before go-live.\n\n**REQUIRED INPUTS:**\n\n\ud83c\udfaf **Launch Scope & Strategy:**\n- Launch Type: <span class=\"placeholder\">[LAUNCH_TYPE: e.g., \"New product launch\" or \"Major version upgrade\" or \"Feature expansion\" or \"Market expansion (new geography\/segment)\" or \"Rebrand\/reposition\"]<\/span>\n- Target Audience: <span class=\"placeholder\">[AUDIENCE: e.g., \"Existing customers (upgrade path)\" or \"New market segment: enterprise users\" or \"Geographic: EU market entry\" or \"Both new + existing users\"]<\/span>\n- Launch Approach: <span class=\"placeholder\">[APPROACH: e.g., \"Big bang launch to all users\" or \"Phased rollout (beta \u2192 limited \u2192 general availability)\" or \"Invite-only early access \u2192 public launch\" or \"Soft launch \u2192 marketing push\"]<\/span>\n- Success Metrics: <span class=\"placeholder\">[SUCCESS_CRITERIA: e.g., \"10K signups in week 1, 2K paid conversions in month 1, <2% critical bug rate, NPS >40\" or \"Zero downtime, 95% customer satisfaction, 25% adoption in 30 days\"]<\/span>\n\n\ud83d\udee0\ufe0f **Product & Technical Readiness:**\n- Product Status: <span class=\"placeholder\">[PRODUCT_STATE: e.g., \"Feature complete, in QA testing\" or \"95% complete, 2 features in progress\" or \"MVP ready, enhancement backlog identified\" or \"In closed beta with 50 users\"]<\/span>\n- Outstanding Work: <span class=\"placeholder\">[REMAINING_WORK: e.g., \"3 critical bugs, 8 minor bugs, 12 UX polish items, performance optimization needed\" or \"Documentation incomplete, onboarding flow needs refinement\"]<\/span>\n- Technical Risks: <span class=\"placeholder\">[TECH_RISKS: e.g., \"Scalability unproven (load tested to 1K users, expect 10K), database migration complex, third-party API dependency, legacy system integration fragile\"]<\/span>\n- Quality Status: <span class=\"placeholder\">[QUALITY: e.g., \"80% test coverage, 12 automated test suites, manual QA completed for core flows\" or \"Limited testing, known edge cases unaddressed\"]<\/span>\n\n\ud83d\udce2 **Go-to-Market Readiness:**\n- Marketing Materials: <span class=\"placeholder\">[MARKETING_STATUS: e.g., \"Landing page live, blog posts drafted, demo video 80% complete, case studies in progress\" or \"Not started\u2014need 3 weeks to prepare\" or \"Social media scheduled, PR outreach planned, launch event confirmed\"]<\/span>\n- Sales Enablement: <span class=\"placeholder\">[SALES_STATUS: e.g., \"Pitch deck ready, pricing finalized, sales training scheduled for week before launch\" or \"Account executives not yet trained, demo environment unstable, objection handling scripts missing\"]<\/span>\n- Channel Strategy: <span class=\"placeholder\">[CHANNELS: e.g., \"Email to 50K user base, Product Hunt launch, paid ads ($30K budget), partnership co-marketing\" or \"In-app announcement, organic social, no paid promotion\"]<\/span>\n\n\ud83c\udf93 **Enablement & Support:**\n- Documentation: <span class=\"placeholder\">[DOCS_STATUS: e.g., \"User guides complete, API docs 70% done, video tutorials scripted but not recorded, changelog ready\" or \"Knowledge base articles drafted, migration guide incomplete\"]<\/span>\n- Support Readiness: <span class=\"placeholder\">[SUPPORT_STATUS: e.g., \"Support team trained, FAQ prepared, ticket categories created, 2x coverage planned for launch week\" or \"Team unaware of launch, training not scheduled\"]<\/span>\n- Customer Success: <span class=\"placeholder\">[CS_STATUS: e.g., \"Onboarding playbook created, welcome email sequence ready, proactive outreach plan for key accounts\" or \"No specialized onboarding planned\"]<\/span>\n\n\u2699\ufe0f **Operations & Infrastructure:**\n- Infrastructure: <span class=\"placeholder\">[INFRA_STATUS: e.g., \"Auto-scaling configured, monitoring alerts set up, capacity tested to 5x expected load\" or \"Running on single server, scaling plan theoretical, monitoring basic\"]<\/span>\n- Data & Analytics: <span class=\"placeholder\">[ANALYTICS_STATUS: e.g., \"Event tracking implemented, dashboards built, A\/B test framework ready\" or \"Analytics instrumentation incomplete, no launch dashboard\"]<\/span>\n- Compliance & Legal: <span class=\"placeholder\">[COMPLIANCE: e.g., \"Terms of service updated, privacy policy reviewed, GDPR compliant, security audit passed\" or \"Legal review pending, data retention policies undefined\"]<\/span>\n\n\ud83d\udc65 **Team & Resource Status:**\n- Team Availability: <span class=\"placeholder\">[TEAM_STATUS: e.g., \"Core team dedicated, on-call rotation staffed for launch week, engineering capacity reserved for hotfixes\" or \"Team split across multiple projects, key engineer on vacation during launch\"]<\/span>\n- Decision Authority: <span class=\"placeholder\">[DECISION_MAKING: e.g., \"Launch\/no-launch decision owned by VP Product, go\/no-go meeting scheduled 3 days before\" or \"Unclear launch authority, no rollback criteria defined\"]<\/span>\n- Stakeholder Alignment: <span class=\"placeholder\">[ALIGNMENT: e.g., \"Executive team briefed and supportive, board aware, cross-functional teams aligned on timeline\" or \"Some resistance from sales team, concerns about readiness from engineering\"]<\/span>\n\n\ud83d\udcc5 **Timeline & Dependencies:**\n- Current Date: <span class=\"placeholder\">[TODAY: e.g., \"February 1, 2026\" or \"6 weeks before launch\"]<\/span>\n- Critical Path Items: <span class=\"placeholder\">[CRITICAL_PATH: e.g., \"Must complete: database migration (2 weeks), Apple App Store review (1-2 weeks uncertain), sales training (1 week), load testing (3 days)\" or \"No clear critical path identified\"]<\/span>\n- Known Blockers: <span class=\"placeholder\">[BLOCKERS: e.g., \"Waiting on legal approval for terms, third-party vendor integration delayed 2 weeks, design resource bottleneck\" or \"None identified\"]<\/span>\n\n**LAUNCH READINESS FRAMEWORK PRINCIPLES:**\n\n1. **Cross-Functional Completeness** - Product launch requires readiness across product, engineering, marketing, sales, support, operations, and legal\u2014weakness in any area jeopardizes success\n2. **Risk-Based Prioritization** - Not all gaps are equal; distinguish launch blockers (must fix) from day-2 improvements (can defer) based on impact and likelihood\n3. **Customer Impact Scenarios** - Evaluate readiness from customer perspective: Can they discover, evaluate, purchase, onboard, and use the product successfully?\n4. **Rollback & Contingency Planning** - Every launch needs abort criteria, rollback procedures, and contingency plans for identified risks\n5. **Post-Launch Readiness** - Launch day is just the beginning; readiness includes monitoring, rapid response, and continuous improvement capabilities\n6. **Stakeholder Alignment** - Launch success requires coordinated execution across teams with clear ownership, communication protocols, and decision authority\n7. **Realistic Timeline Assessment** - Wishful thinking kills launches; assess actual capacity, dependency risk, and build in buffer for inevitable surprises\n\n**YOUR COMPREHENSIVE LAUNCH READINESS ASSESSMENT MUST INCLUDE:**\n\n**SECTION 1: EXECUTIVE SUMMARY**\n<span class=\"checkmark\">\u2705<\/span> Overall launch readiness verdict (Ready\/At Risk\/Not Ready)\n<span class=\"checkmark\">\u2705<\/span> Confidence level in hitting launch date\n<span class=\"checkmark\">\u2705<\/span> Top 3-5 critical risks requiring immediate attention\n<span class=\"checkmark\">\u2705<\/span> Launch decision recommendation (go\/no-go\/conditional go)\n<span class=\"checkmark\">\u2705<\/span> Alternative scenario if current date is unrealistic\n\n**SECTION 2: PRODUCT & TECHNICAL READINESS**\n<span class=\"checkmark\">\u2705<\/span> Feature completeness assessment\n<span class=\"checkmark\">\u2705<\/span> Outstanding bug severity and resolution plan\n<span class=\"checkmark\">\u2705<\/span> Quality assurance coverage and gaps\n<span class=\"checkmark\">\u2705<\/span> Performance and scalability validation\n<span class=\"checkmark\">\u2705<\/span> User experience polish and edge case handling\n<span class=\"checkmark\">\u2705<\/span> Technical debt and known limitations\n<span class=\"checkmark\">\u2705<\/span> Platform\/device compatibility verification\n<span class=\"checkmark\">\u2705<\/span> Data migration and integration testing (if applicable)\n\n**SECTION 3: GO-TO-MARKET READINESS**\n<span class=\"checkmark\">\u2705<\/span> Marketing asset completeness (website, content, creative)\n<span class=\"checkmark\">\u2705<\/span> Sales enablement materials and training status\n<span class=\"checkmark\">\u2705<\/span> Channel activation plan and budget allocation\n<span class=\"checkmark\">\u2705<\/span> Pricing and packaging finalization\n<span class=\"checkmark\">\u2705<\/span> Messaging and positioning clarity\n<span class=\"checkmark\">\u2705<\/span> Partner and ecosystem coordination\n<span class=\"checkmark\">\u2705<\/span> Launch communications timeline (internal and external)\n\n**SECTION 4: CUSTOMER EXPERIENCE READINESS**\n<span class=\"checkmark\">\u2705<\/span> Onboarding flow validation (user testing completed?)\n<span class=\"checkmark\">\u2705<\/span> Documentation comprehensiveness and quality\n<span class=\"checkmark\">\u2705<\/span> In-product guidance and help resources\n<span class=\"checkmark\">\u2705<\/span> Support team training and resource allocation\n<span class=\"checkmark\">\u2705<\/span> FAQ and troubleshooting content preparation\n<span class=\"checkmark\">\u2705<\/span> Customer success playbooks for different segments\n<span class=\"checkmark\">\u2705<\/span> Migration path for existing users (if applicable)\n\n**SECTION 5: OPERATIONS & INFRASTRUCTURE**\n<span class=\"checkmark\">\u2705<\/span> Infrastructure scalability and capacity planning\n<span class=\"checkmark\">\u2705<\/span> Monitoring, alerting, and observability setup\n<span class=\"checkmark\">\u2705<\/span> Incident response and on-call procedures\n<span class=\"checkmark\">\u2705<\/span> Analytics instrumentation and dashboard readiness\n<span class=\"checkmark\">\u2705<\/span> Security and compliance validation\n<span class=\"checkmark\">\u2705<\/span> Third-party service dependencies and SLAs\n<span class=\"checkmark\">\u2705<\/span> Backup and disaster recovery procedures\n\n**SECTION 6: RISK ASSESSMENT & MITIGATION**\n<span class=\"checkmark\">\u2705<\/span> Comprehensive risk register (likelihood \u00d7 impact matrix)\n<span class=\"checkmark\">\u2705<\/span> Launch blocker identification (must-fix before launch)\n<span class=\"checkmark\">\u2705<\/span> High-priority risks with mitigation strategies\n<span class=\"checkmark\">\u2705<\/span> Accepted risks with monitoring plans\n<span class=\"checkmark\">\u2705<\/span> Rollback triggers and procedures\n<span class=\"checkmark\">\u2705<\/span> Contingency plans for likely failure scenarios\n<span class=\"checkmark\">\u2705<\/span> \"Break glass\" escalation procedures\n\n**SECTION 7: TIMELINE & CRITICAL PATH**\n<span class=\"checkmark\">\u2705<\/span> Remaining work breakdown by team\/function\n<span class=\"checkmark\">\u2705<\/span> Critical path analysis with dependencies\n<span class=\"checkmark\">\u2705<\/span> Resource capacity vs. required work assessment\n<span class=\"checkmark\">\u2705<\/span> Timeline risk factors (optimistic vs. realistic vs. pessimistic)\n<span class=\"checkmark\">\u2705<\/span> Go\/no-go decision timeline and criteria\n<span class=\"checkmark\">\u2705<\/span> Buffer analysis (slack in schedule for surprises)\n\n**SECTION 8: LAUNCH EXECUTION PLAN**\n<span class=\"checkmark\">\u2705<\/span> Launch day runbook (hour-by-hour activities)\n<span class=\"checkmark\">\u2705<\/span> Team roles and responsibilities (RACI matrix)\n<span class=\"checkmark\">\u2705<\/span> Communication protocols (internal escalation, external updates)\n<span class=\"checkmark\">\u2705<\/span> Success criteria and monitoring dashboard\n<span class=\"checkmark\">\u2705<\/span> Week 1 priorities and rapid response plan\n<span class=\"checkmark\">\u2705<\/span> Post-launch retrospective planning\n\n**SECTION 9: GAP ANALYSIS & ACTION ITEMS**\n<span class=\"checkmark\">\u2705<\/span> Comprehensive gap identification across all readiness dimensions\n<span class=\"checkmark\">\u2705<\/span> Prioritized action items (critical\/high\/medium\/low)\n<span class=\"checkmark\">\u2705<\/span> Owner assignment for each action item\n<span class=\"checkmark\">\u2705<\/span> Timeline and completion criteria\n<span class=\"checkmark\">\u2705<\/span> Dependencies and blockers for each action\n<span class=\"checkmark\">\u2705<\/span> Daily standup plan to track gap closure\n\n**SECTION 10: LAUNCH DECISION RECOMMENDATION**\n<span class=\"checkmark\">\u2705<\/span> Go\/No-Go recommendation with supporting rationale\n<span class=\"checkmark\">\u2705<\/span> Confidence assessment (% likelihood of successful launch)\n<span class=\"checkmark\">\u2705<\/span> Conditional scenarios (what needs to happen to launch safely)\n<span class=\"checkmark\">\u2705<\/span> Alternative date recommendation if current timing is risky\n<span class=\"checkmark\">\u2705<\/span> Trade-off analysis (launch with limitations vs. delay for polish)\n<span class=\"checkmark\">\u2705<\/span> Success criteria for declaring launch a win vs. need for course correction\n\n**OUTPUT FORMATTING REQUIREMENTS:**\n- Use readiness indicators: \ud83d\udfe2 Ready, \ud83d\udfe1 At Risk, \ud83d\udd34 Not Ready, \u26a0\ufe0f Blocker\n- Assign severity to risks: \ud83d\udd34 Critical, \ud83d\udfe1 High, \ud83d\udd35 Medium, \u26aa Low\n- Show completion status: \u2705 Complete, \ud83d\udd04 In Progress, \u274c Not Started, \u23f8\ufe0f Blocked\n- Provide specific, actionable recommendations (not generic advice)\n- Include owner, timeline, and success criteria for each action item\n- Present trade-offs clearly when perfect readiness is impossible\n- End each major section with \"Readiness Assessment\" summary\n- Final recommendation must be clear: Go \/ No-Go \/ Conditional Go with specific conditions\n\n**ANALYSIS DEPTH:**\nThis is a launch risk assessment, not a cheerleading exercise. Be honest about gaps, realistic about timelines, and specific about risks. A delayed launch is better than a botched one that damages brand trust, overwhelms support, or creates technical debt. Identify the minimum viable launch criteria vs. ideal state, and help leadership make an informed decision with eyes wide open about trade-offs.<\/div>\n <div class=\"tip-box\">\n <strong>\ud83d\udca1 Pro Tip:<\/strong> Launch readiness assessments are most effective when conducted 4-6 weeks before planned launch\u2014early enough to fix gaps, late enough that you have real work to assess. Schedule a formal go\/no-go review 3-5 days before launch with clear decision authority and rollback criteria.\n <\/div>\n <\/div>\n\n <div class=\"section\">\n <h2 class=\"section-title\">The Logic<\/h2>\n \n <div class=\"logic-principle\">\n <h3>1. Cross-Functional Completeness Prevents Siloed Failure<\/h3>\n <p>A launch is only as strong as its weakest link. A perfect product with untrained support staff creates frustrated customers and overwhelmed teams. Brilliant marketing without sales enablement generates leads that don't convert. Excellent positioning but unstable infrastructure causes outages that destroy trust. Cross-functional readiness assessment forces every team to examine their preparedness and dependencies. Product can't launch if legal hasn't approved terms; marketing can't execute if the product isn't feature-complete; sales can't sell without pricing and packaging finalization. This framework identifies where teams are out of sync\u2014where product thinks marketing is handling onboarding communication while marketing assumes product built it into the UI. Forcing explicit assessment of each function's readiness exposes dangerous assumptions before they become launch-day disasters.<\/p>\n <\/div>\n\n <div class=\"logic-principle\">\n <h3>2. Risk-Based Prioritization Separates Critical from Nice-to-Have<\/h3>\n <p>Not all gaps are created equal. A typo in documentation is annoying but not a launch blocker; a critical authentication bug that exposes user data absolutely is. Risk assessment\u2014evaluating each gap by impact (how bad if it happens) \u00d7 likelihood (probability it happens)\u2014distinguishes must-fix issues from can-defer improvements. High-impact, high-likelihood risks (server crashes under expected load, core feature doesn't work on iOS) are launch blockers requiring resolution or significant mitigation. Low-impact, low-likelihood risks (edge case bug affecting <1% of users in rare scenario) can be monitored post-launch. This framework prevents both dangerous launches (ignoring critical risks) and perfectionism paralysis (delaying for trivial polish). It creates honest conversations about trade-offs: Can we launch with this limitation? What's our backup plan if this risk materializes? What's the cost of delay versus accepting managed risk?<\/p>\n <\/div>\n\n <div class=\"logic-principle\">\n <h3>3. Customer Impact Scenarios Ground Readiness in Reality<\/h3>\n <p>Teams often assess readiness from their own perspective\u2014engineering considers product \"ready\" when features are built; marketing when assets are created; support when training is complete. But readiness must be measured from the customer perspective: Can a customer discover the product, understand its value, decide to purchase, complete payment, onboard successfully, and achieve their desired outcome? Walking through this end-to-end customer journey exposes gaps that silo-focused assessments miss. What happens when a customer tries to sign up during peak load? Where do they go if onboarding confuses them? What if they need help but documentation is incomplete? If a feature breaks, how long until they get support? Customer impact scenarios\u2014literally role-playing the customer journey\u2014reveal hidden dependencies and coordination failures that abstract checklists miss, ensuring launch readiness translates to actual customer success.<\/p>\n <\/div>\n\n <div class=\"logic-principle\">\n <h3>4. Rollback Planning Enables Confident Risk-Taking<\/h3>\n <p>The ability to rapidly reverse a launch decision transforms risk calculus. Without rollback capability, every risk becomes existential\u2014you're trapped with whatever breaks. With clear rollback procedures, abort criteria, and tested mechanisms to revert to previous state, you can take calculated risks knowing you're not betting the company. Rollback planning forces clarity on critical questions: At what point do we pull the plug? How quickly can we revert? What's the blast radius if we roll back (affected users, data loss, communication needed)? Who has authority to make the rollback call? Teams that plan rollbacks paradoxically launch more confidently because they know they're not trapped\u2014if things go sideways, there's an escape hatch. This transforms launch decisions from irrevocable leaps of faith into reversible experiments where you can fail safely, learn quickly, and try again with improvements.<\/p>\n <\/div>\n\n <div class=\"logic-principle\">\n <h3>5. Post-Launch Readiness Determines Long-Term Success<\/h3>\n <p>Launch day is just the beginning\u2014post-launch execution determines whether early momentum compounds or collapses. Post-launch readiness means having monitoring to detect problems before customers complain, rapid response capability to fix issues quickly, communication protocols to keep stakeholders informed, and continuous improvement processes to iterate on feedback. Teams often focus all energy on launch day, then exhaust themselves and disband, leaving the product to drift. But Week 1 post-launch is when you discover what actually breaks under real usage, learn which assumptions were wrong, and identify the improvements with highest impact. Post-launch readiness includes on-call rotations, incident response playbooks, daily standups to review metrics and issues, customer feedback collection and analysis, and reserved capacity for rapid iterations. Products that launch well but lack post-launch machinery falter; products with strong post-launch operations can recover from rough launches and continuously improve toward product-market fit.<\/p>\n <\/div>\n\n <div class=\"logic-principle\">\n <h3>6. Realistic Timeline Assessment Prevents Compressed Failure<\/h3>\n <p>Wishful thinking is the most common launch risk. Teams estimate based on optimistic scenarios (everything goes smoothly, no surprises, perfect execution) and ignore historical evidence that projects rarely finish on time. Realistic timeline assessment means acknowledging actual team capacity (accounting for meetings, context switching, competing priorities), dependency risk (waiting on others, external approvals, third-party services), and Murphy's Law buffer (inevitable surprises, scope creep, illness, technical complications). If your critical path requires perfect execution with zero slack, you're not planning\u2014you're hoping. Realistic assessment exposes when dates are fantasy, forcing honest conversations: Do we cut scope? Add resources? Accept a delayed launch? Launch with limitations? Teams resist these conversations because they're uncomfortable, but the alternative\u2014pretending an unrealistic date is achievable\u2014leads to crunch time death marches, burnout, quality shortcuts, and ultimately, launch failure or delay anyway. Realistic timelines with buffer enable sustainable execution and informed decisions.<\/p>\n <\/div>\n <\/div>\n\n <div class=\"section\">\n <h2 class=\"section-title\">Example Output Preview<\/h2>\n <div class=\"example-box\">\n <h4>\ud83d\ude80 Launch Readiness Assessment - TaskFlow Mobile App 3.0 (Launch: March 15, 2026)<\/h4>\n \n <p><strong>EXECUTIVE SUMMARY<\/strong><\/p>\n <p><strong>Overall Launch Readiness: \ud83d\udfe1 AT RISK<\/strong><\/p>\n <p><strong>Confidence in Launch Date: 60% (Conditional Go)<\/strong><\/p>\n \n <p><strong>Verdict:<\/strong> Launch is possible on March 15, but significant risks exist across technical stability, support readiness, and GTM execution. Recommend <strong>CONDITIONAL GO<\/strong> with specific must-complete criteria outlined below, OR consider 2-week delay to April 1 for safer launch with higher confidence.<\/p>\n\n <p><strong>Top 5 Critical Risks Requiring Immediate Attention:<\/strong><\/p>\n <ol style=\"line-height: 1.8;\">\n <li>\ud83d\udd34 <strong>BLOCKER: iOS App Store Review Timing<\/strong> - Submitted 2 days ago, average review time is 2-5 days but can be 7-10 days if rejected and resubmitted. High risk of missing March 15 launch if any issues found. <strong>Mitigation:<\/strong> Prepare Android-only launch plan as backup; have developer on standby for immediate fixes if rejected.<\/li>\n <li>\ud83d\udd34 <strong>Infrastructure Scalability Unproven<\/strong> - Load tested to 2,000 concurrent users; expect 5,000+ at launch based on user base + marketing push. Database queries showing performance degradation at scale. <strong>Risk:<\/strong> Launch day slowdowns or outages. <strong>Mitigation:<\/strong> Implement database query optimization (5 days), add caching layer (3 days), set up auto-scaling with aggressive thresholds.<\/li>\n <li>\ud83d\udfe1 <strong>Support Team Under-Prepared<\/strong> - Training scheduled for March 12 (3 days before launch), no practice runs with actual product. 18 support agents, but only 2 have used beta version. <strong>Risk:<\/strong> Overwhelmed support, poor customer experience in critical first week. <strong>Mitigation:<\/strong> Move training to March 8, require all agents to complete 2-hour product walkthrough by March 10, create cheat sheets for common issues.<\/li>\n <li>\ud83d\udfe1 <strong>Migration Path for Existing Users Untested<\/strong> - 47,000 existing users must migrate to new app. Migration tested with 50 beta users successfully, but edge cases (users with >100 projects, special characters in data, expired subscriptions) not fully validated. <strong>Risk:<\/strong> Data loss, failed migrations, support ticket surge. <strong>Mitigation:<\/strong> Phased migration: power users first (March 15-17), then general rollout (March 18-22) with rollback capability.<\/li>\n <li>\ud83d\udfe1 <strong>Marketing Landing Page Not Live<\/strong> - Design approved, content finalized, but site not deployed or tested. Dev handoff happening March 8, needs QA and final approval. <strong>Risk:<\/strong> Traffic from launch campaigns lands on incomplete\/broken page. <strong>Mitigation:<\/strong> Prioritize landing page deployment by March 10 with 5 days for testing and iteration.<\/li>\n <\/ol>\n\n <p><strong>Launch Decision Recommendation: CONDITIONAL GO<\/strong><\/p>\n <p><strong>Conditions for Safe Launch:<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>\u2705 iOS App Store approval received by March 12 (3 days before launch) - If not, delay to March 22<\/li>\n <li>\u2705 Infrastructure optimization complete and load tested to 6,000 concurrent by March 11<\/li>\n <li>\u2705 Support team training completed and agents demonstrate competency by March 12<\/li>\n <li>\u2705 Landing page live and tested by March 10<\/li>\n <li>\u2705 Go\/No-Go review meeting March 13 with clear abort criteria<\/li>\n <\/ul>\n\n <p><strong>Alternative Scenario:<\/strong> If 3+ conditions above are not met by March 13, recommend <strong>2-week delay to April 1<\/strong>. Cost of delay: ~$40K in lost revenue, 2 weeks of team opportunity cost. Benefit: Significantly reduced launch risk, better customer experience, higher confidence in technical stability.<\/p>\n\n <p><strong>PRODUCT & TECHNICAL READINESS: \ud83d\udfe1 AT RISK<\/strong><\/p>\n \n <p><strong>Feature Completeness: \ud83d\udfe2 READY<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>All planned features implemented and functional<\/li>\n <li>Beta testing with 150 users completed; feedback incorporated<\/li>\n <li>No missing features that would block launch<\/li>\n <\/ul>\n\n <p><strong>Bug Status: \ud83d\udfe1 AT RISK<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li><strong>Critical Bugs:<\/strong> 0 (all resolved) \u2705<\/li>\n <li><strong>High Priority:<\/strong> 3 open (2 under investigation, 1 fix in QA)<\/li>\n <li><strong>Medium Priority:<\/strong> 12 open (acceptable to launch, monitor post-launch)<\/li>\n <li><strong>Low Priority:<\/strong> 27 open (defer to future releases)<\/li>\n <li><strong>Concern:<\/strong> High-priority bug #247 (offline sync occasionally fails to resolve conflicts) still being investigated\u2014could be launch blocker if root cause isn't understood. Target resolution: March 10.<\/li>\n <\/ul>\n\n <p><strong>Quality Assurance: \ud83d\udfe2 ADEQUATE<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>85% automated test coverage on core flows<\/li>\n <li>Manual QA completed on iOS (iPhone 13-15) and Android (Samsung S22-S24, Pixel 7-8)<\/li>\n <li>Regression testing passed for all critical user journeys<\/li>\n <li>Accessibility testing completed (WCAG 2.1 AA compliance verified)<\/li>\n <li><strong>Gap:<\/strong> Limited testing on older devices (iPhone 11, Android 10) - 15% of user base; may encounter edge case issues<\/li>\n <\/ul>\n\n <p><strong>Performance & Scalability: \ud83d\udd34 NOT READY<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li><strong>Load Testing:<\/strong> Validated to 2,000 concurrent users; performance acceptable<\/li>\n <li><strong>Expected Load:<\/strong> 5,000-7,000 concurrent at launch peak (based on 47K user base + marketing surge)<\/li>\n <li><strong>Bottleneck Identified:<\/strong> Database queries for project loading degrade beyond 3,000 users (avg response time: 850ms \u2192 3.2s)<\/li>\n <li><strong>Infrastructure:<\/strong> Auto-scaling configured but never tested at target load; monitoring alerts set but thresholds untested<\/li>\n <li><strong>REQUIRED ACTIONS:<\/strong><\/li>\n <li style=\"margin-left: 2rem;\">1. Database query optimization (identify N+1 queries, add indexes) - ENG team, 5 days, Due: March 10<\/li>\n <li style=\"margin-left: 2rem;\">2. Implement Redis caching for frequently accessed project data - ENG team, 3 days, Due: March 11<\/li>\n <li style=\"margin-left: 2rem;\">3. Load test to 8,000 concurrent users and validate response times <2s p95 - QA team, 2 days, Due: March 13<\/li>\n <\/ul>\n\n <p><strong>Technical Debt & Limitations: \ud83d\udfe1 ACCEPTABLE<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>Known limitation: Real-time collaboration limited to 8 simultaneous editors (acceptable for MVP; 95% of projects have <5 collaborators)<\/li>\n <li>Workaround documented: Users with >8 collaborators can use \"turn-based\" editing mode<\/li>\n <li>Technical debt: Legacy API endpoints still supported but should be deprecated within 6 months post-launch<\/li>\n <\/ul>\n\n <p><strong>Readiness Assessment:<\/strong> Product is feature-complete and quality is acceptable for launch. Primary concern is performance at scale\u2014infrastructure optimization is on critical path and must complete by March 11 for safe launch. If load testing on March 13 reveals issues, we lack time to fix before March 15 launch.<\/p>\n\n <p><strong>GO-TO-MARKET READINESS: \ud83d\udfe1 AT RISK<\/strong><\/p>\n \n <p><strong>Marketing Assets: \ud83d\udfe1 AT RISK<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>\u2705 Blog post announcing launch (drafted, scheduled for March 15, 9am)<\/li>\n <li>\ud83d\udd04 Landing page (design approved, in development, not yet live) - <strong>CRITICAL: Deploy by March 10<\/strong><\/li>\n <li>\u2705 Demo video (90 seconds, professional production, completed)<\/li>\n <li>\u2705 Social media assets (graphics, copy for LinkedIn, Twitter, Facebook scheduled)<\/li>\n <li>\ud83d\udd04 Case study with beta customer (interview complete, writeup 70% done, targeting March 12)<\/li>\n <li>\u274c Press release (not started, optional\u2014decided not to pursue press outreach for this launch)<\/li>\n <\/ul>\n\n <p><strong>Sales Enablement: \ud83d\udfe2 READY<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>\u2705 Pitch deck updated with v3.0 features and benefits<\/li>\n <li>\u2705 Pricing finalized: Free tier (unchanged), Basic $12\/mo (new tier), Pro $24\/mo (upgraded from $18)<\/li>\n <li>\u2705 Sales training scheduled March 12, 2-hour session with product demo and objection handling<\/li>\n <li>\u2705 Demo environment stable and accessible to all account executives<\/li>\n <li>\u2705 Internal FAQ for common customer questions prepared<\/li>\n <\/ul>\n\n <p><strong>Channel Activation: \ud83d\udfe2 READY<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li><strong>Email:<\/strong> Launch announcement email to 47,000 existing users scheduled for March 15, 10am<\/li>\n <li><strong>In-App:<\/strong> Notification banner prepared for web app users directing to mobile app download<\/li>\n <li><strong>Paid Ads:<\/strong> $30K budget allocated; campaigns created in Google Ads and Facebook Ads, targeting \"project management app\" keywords; scheduled to go live March 15<\/li>\n <li><strong>Product Hunt:<\/strong> Submission prepared, scheduled for March 16 (day after launch to build momentum)<\/li>\n <li><strong>Partnerships:<\/strong> Co-marketing email with integration partner (Zapier) scheduled for March 18<\/li>\n <\/ul>\n\n <p><strong>Readiness Assessment:<\/strong> GTM execution is mostly ready. Landing page deployment is on critical path and creates launch day risk if not completed by March 10. All other assets are on track. Sales team is aligned and prepared.<\/p>\n\n <p><em>[Assessment continues with Customer Experience Readiness, Operations & Infrastructure, Risk Assessment, Timeline Analysis, Launch Execution Plan, Gap Analysis, and Final Launch Decision sections...]<\/em><\/p>\n\n <p><strong>FINAL LAUNCH DECISION RECOMMENDATION<\/strong><\/p>\n \n <p><strong>Recommendation: CONDITIONAL GO for March 15, 2026<\/strong><\/p>\n <p><strong>Confidence Level: 60%<\/strong><\/p>\n\n <p><strong>GO Decision Conditions (All Must Be Met by March 13):<\/strong><\/p>\n <ol style=\"line-height: 1.8;\">\n <li>\u2705 iOS App Store approval received (currently in review, submitted March 1)<\/li>\n <li>\u2705 Infrastructure performance validated to 6,000+ concurrent users with <2s p95 response time<\/li>\n <li>\u2705 High-priority bug #247 (offline sync) resolved or decision made to launch with workaround documented<\/li>\n <li>\u2705 Support team training completed with demonstrated product competency<\/li>\n <li>\u2705 Landing page live, tested, and validated across devices<\/li>\n <\/ol>\n\n <p><strong>Go\/No-Go Review: Thursday, March 13, 4pm<\/strong><\/p>\n <p><strong>Decision Makers:<\/strong> VP Product (launch owner), VP Engineering (technical go), VP Marketing (GTM readiness), CTO (infrastructure approval)<\/p>\n <p><strong>Abort Criteria (Automatic No-Go Triggers):<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>iOS App Store rejection received after March 12 (insufficient time to fix and resubmit)<\/li>\n <li>Load testing on March 13 reveals critical performance issues requiring >2 days to fix<\/li>\n <li>Database migration failure rate >5% in power user testing (March 12-13)<\/li>\n <li>Discovery of critical security vulnerability<\/li>\n <\/ul>\n\n <p><strong>Rollback Plan:<\/strong> If launched and critical issues emerge in first 24 hours:<\/p>\n <ul style=\"line-height: 1.8;\">\n <li><strong>Trigger:<\/strong> >5% of users reporting data loss, sustained outage >2 hours, security breach<\/li>\n <li><strong>Authority:<\/strong> CTO or VP Product can call rollback<\/li>\n <li><strong>Procedure:<\/strong> (1) Disable new user signups, (2) Halt marketing campaigns, (3) Display maintenance message, (4) Revert to v2.0 app in stores, (5) Migrate users back to previous version<\/li>\n <li><strong>Communication:<\/strong> Email to all users within 4 hours explaining situation and timeline<\/li>\n <\/ul>\n\n <p><strong>Alternative Recommendation: If Conditions Not Met by March 13<\/strong><\/p>\n <p><strong>Delay to April 1, 2026 (2-week delay)<\/strong><\/p>\n <p><strong>Rationale:<\/strong> Two additional weeks provides buffer to resolve technical risks, complete marketing assets without rush, allow fuller support preparation, and reduce launch day stress. Cost of delay is manageable; cost of botched launch is significantly higher (brand damage, overwhelmed support, technical debt from rushed fixes).<\/p>\n\n <p><strong>Success Metrics (Declaring Launch Successful):<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li><strong>Week 1 Targets:<\/strong> 8,000+ downloads, <3% crash rate, <5% critical support tickets, 70%+ positive app store reviews<\/li>\n <li><strong>Month 1 Targets:<\/strong> 15,000 downloads, 25% existing user migration, 1,200+ paid conversions, NPS >40<\/li>\n <li><strong>Must Not Occur:<\/strong> Sustained outage >4 hours, data loss affecting >100 users, security incident, negative press coverage<\/li>\n <\/ul>\n\n <p><strong>Post-Launch Plan:<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li><strong>Daily standups:<\/strong> March 15-22, 9am, product + eng + support leads<\/li>\n <li><strong>On-call rotation:<\/strong> 24\/7 coverage March 15-18, business hours March 19-25<\/li>\n <li><strong>Metrics monitoring:<\/strong> Real-time dashboard tracking downloads, crashes, support tickets, performance<\/li>\n <li><strong>Retrospective:<\/strong> March 29, full team debrief on what went well and what to improve<\/li>\n <\/ul>\n <\/div>\n <\/div>\n\n <div class=\"section\">\n <h2 class=\"section-title\">Prompt Chain Strategy<\/h2>\n \n <div class=\"chain-step\">\n <h3>Step 1: Cross-Functional Readiness Assessment<\/h3>\n <div class=\"prompt-text\">Using the main prompt, first generate the Executive Summary, Product & Technical Readiness, and Go-to-Market Readiness sections. Assess each functional area's preparation and identify major gaps.<\/div>\n <p><strong>Expected Output:<\/strong> High-level readiness verdict with clear assessment of product quality, technical stability, and GTM preparedness. Identifies whether you have a product problem, technical risk, or GTM execution gap.<\/p>\n <\/div>\n\n <div class=\"chain-step\">\n <h3>Step 2: Operations, Risk, and Timeline Analysis<\/h3>\n <div class=\"prompt-text\">\"Now expand with Customer Experience Readiness, Operations & Infrastructure, Risk Assessment & Mitigation, and Timeline & Critical Path sections. Evaluate end-to-end customer experience, infrastructure readiness, comprehensive risk register, and realistic timeline assessment. Identify launch blockers vs. day-2 issues.\"<\/div>\n <p><strong>Expected Output:<\/strong> Detailed risk analysis with severity ratings, critical path identification showing what must complete before launch, and operations validation ensuring post-launch support readiness. Reveals hidden dependencies and timeline risks.<\/p>\n <\/div>\n\n <div class=\"chain-step\">\n <h3>Step 3: Launch Decision and Execution Plan<\/h3>\n <div class=\"prompt-text\">\"Complete the assessment with Launch Execution Plan, Gap Analysis & Action Items, and Launch Decision Recommendation sections. Provide specific action items with owners and timelines, create launch day runbook, define go\/no-go criteria, and give clear launch recommendation with conditions. Include rollback plan and success metrics.\"<\/div>\n <p><strong>Expected Output:<\/strong> Actionable launch plan with clear decision recommendation (go\/no-go\/conditional), specific conditions that must be met, prioritized action items to close gaps, and post-launch monitoring plan. Enables leadership to make informed launch decision with clear risk understanding.<\/p>\n <\/div>\n <\/div>\n\n <div class=\"section\">\n <h2 class=\"section-title\">Human-in-the-Loop Refinements<\/h2>\n \n <div class=\"hitl-tip\">\n <h3>1. Conduct Pre-Mortem Exercise<\/h3>\n <p>Imagine the launch failed catastrophically. Request: \"Conduct a pre-mortem analysis\u2014assume the launch on March 15 was a disaster. What are the 10 most likely failure scenarios that could have caused this? For each scenario: (1) What specifically went wrong? (2) What early warning signs would we have seen? (3) What could we have done to prevent it? (4) What's our mitigation strategy if it happens?\" Pre-mortems surface risks teams are unconsciously avoiding and create proactive mitigation strategies before problems occur.<\/p>\n <\/div>\n\n <div class=\"hitl-tip\">\n <h3>2. Validate with Cross-Functional Reality Check<\/h3>\n <p>AI assessments need ground truth validation. Prompt: \"I've shared this readiness assessment with engineering, marketing, sales, and support leads. Here's their feedback [provide feedback]. Where do their concerns differ from this assessment? Are there risks I'm underestimating or gaps they're seeing that weren't captured? Update the risk register and action items based on this team input.\" Frontline teams often see practical execution challenges that high-level assessments miss.<\/p>\n <\/div>\n\n <div class=\"hitl-tip\">\n <h3>3. Stress Test the Timeline with Pessimistic Scenarios<\/h3>\n <p>Optimistic timelines always slip. Ask: \"Re-analyze the critical path assuming pessimistic but realistic scenarios: (1) iOS App Store takes 8 days to approve, (2) Infrastructure optimization takes 2x longer than estimated, (3) One key engineer is sick for 3 days, (4) Marketing asset approval delayed 2 days. Does the March 15 launch survive? What breaks? What's the realistic date with these contingencies factored in?\" Pessimistic planning reveals when your timeline has no margin for normal friction.<\/p>\n <\/div>\n\n <div class=\"hitl-tip\">\n <h3>4. Define Minimum Viable Launch Criteria<\/h3>\n <p>Perfect readiness is often impossible. Request: \"Define three launch tiers: (1) Ideal launch\u2014everything perfect, zero compromises; (2) Good launch\u2014acceptable trade-offs, manageable risks; (3) Minimum viable launch\u2014bare minimum to launch without disaster. For the current state, which tier are we in? What specific improvements move us from minimum viable to good? What's truly non-negotiable vs. nice-to-have?\" This framework helps teams make honest trade-off decisions rather than pretending everything is critical.<\/p>\n <\/div>\n\n <div class=\"hitl-tip\">\n <h3>5. Build Launch Day Incident Response Playbook<\/h3>\n <p>Murphy's Law guarantees something will break. Prompt: \"Create a launch day incident response playbook covering: (1) How do we detect problems (monitoring, support tickets, social media)? (2) Escalation paths\u2014who gets alerted for what severity? (3) Communication templates for common issues (outage, bugs, feature not working). (4) Rollback decision tree\u2014when do we abort vs. patch? (5) Hotfix deployment process without standard approval gates. Make this actionable enough that anyone on-call can execute it.\" Incidents are less catastrophic when response is pre-planned rather than improvised in panic.<\/p>\n <\/div>\n\n <div class=\"hitl-tip\">\n <h3>6. Schedule Post-Launch Learning Retrospective<\/h3>\n <p>Launches are learning opportunities regardless of outcome. Request: \"Design a post-launch retrospective framework to be conducted 2 weeks after launch: (1) What went well that we should replicate? (2) What went poorly that we should fix? (3) What surprised us that we didn't anticipate? (4) What would we do differently next launch? (5) What processes or tools should we build to make future launches smoother? Create this framework now so we're prepared to capture learning while it's fresh.\" Teams that systematize launch learning compound their capabilities; those that don't repeat the same mistakes every launch.<\/p>\n <\/div>\n <\/div>\n <\/div>\n\n <div class=\"card-footer\">\n <div class=\"footer-stat\">\u2b50 <strong>4.8\/5.0<\/strong> rating<\/div>\n <div class=\"footer-stat\">\ud83d\udccb Copied <strong>2,187<\/strong> times<\/div>\n <div class=\"footer-stat\">\ud83d\udcac <strong>173<\/strong> reviews<\/div>\n <\/div>\n <\/div>\n\n <script>\n function copyPrompt() {\n const promptContent = document.getElementById('promptContent').innerText;\n navigator.clipboard.writeText(promptContent).then(() => {\n const button = document.querySelector('.copy-button');\n const originalText = button.innerHTML;\n button.innerHTML = '\u2705 Copied!';\n setTimeout(() => {\n button.innerHTML = originalText;\n }, 2000);\n }).catch(err => {\n console.error('Failed to copy text: ', err);\n alert('Failed to copy to clipboard');\n });\n }\n <\/script>\n<\/body>\n<\/html>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"<p>Product Launch Readiness – AiPro Institute\u2122 AiPro Institute\u2122 Prompt Library \ud83d\ude80 Product Launch Readiness \ud83d\udcc1 Product & Operations \u23f1\ufe0f 30-40 minutes \ud83c\udfaf Advanced ChatGPT Claude Gemini Perplexity Grok The Prompt \ud83d\udccb Copy Prompt You are an elite Product Launch Strategist specializing in go-to-market planning, cross-functional coordination, and launch risk management. Your expertise lies in assessing…<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[187],"tags":[],"class_list":["post-4954","post","type-post","status-publish","format-standard","hentry","category-product-operations"],"acf":[],"_links":{"self":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts\/4954","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/comments?post=4954"}],"version-history":[{"count":4,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts\/4954\/revisions"}],"predecessor-version":[{"id":4963,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts\/4954\/revisions\/4963"}],"wp:attachment":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/media?parent=4954"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/categories?post=4954"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/tags?post=4954"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

\n\t\t\t\t\t\t

\n\t\t\t\t\t

\n\t\t\t

\n\t\t\t\t\t\t

\n\t\t\t\t\t\n\n\n \n \n Product Launch Readiness - AiPro Institute\u2122<\/title>\n <style>\n * {\n margin: 0;\n padding: 0;\n box-sizing: border-box;\n }\n\n body {\n font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen, Ubuntu, Cantarell, sans-serif;\n line-height: 1.6;\n color: #333;\n background: #ffffff;\n padding: 2rem;\n min-height: 100vh;\n }\n\n .page-title {\n text-align: center;\n font-size: 2.5rem;\n font-weight: 700;\n margin-bottom: 2rem;\n background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);\n -webkit-background-clip: text;\n -webkit-text-fill-color: transparent;\n background-clip: text;\n }\n\n .card {\n max-width: 1200px;\n margin: 0 auto;\n background: white;\n border-radius: 12px;\n box-shadow: 0 10px 40px rgba(0, 0, 0, 0.1);\n overflow: hidden;\n }\n\n .card-header {\n background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);\n color: white;\n padding: 2.5rem;\n }\n\n .card-header h1 {\n font-size: 2.5rem;\n margin-bottom: 1.5rem;\n font-weight: 700;\n }\n\n .meta-container {\n display: flex;\n gap: 1rem;\n margin-bottom: 1.5rem;\n flex-wrap: wrap;\n }\n\n .meta-badge {\n background: rgba(255, 255, 255, 0.2);\n padding: 0.4rem 1rem;\n border-radius: 20px;\n font-size: 0.9rem;\n display: flex;\n align-items: center;\n gap: 0.5rem;\n }\n\n .compatibility-container {\n display: flex;\n gap: 0.75rem;\n flex-wrap: wrap;\n }\n\n .compatibility-badge {\n background: transparent;\n border: 1px solid rgba(255, 255, 255, 0.4);\n padding: 0.4rem 1rem;\n border-radius: 20px;\n font-size: 0.85rem;\n }\n\n .card-body {\n padding: 2.5rem;\n }\n\n .section {\n margin-bottom: 3rem;\n }\n\n .section-title-container {\n display: flex;\n justify-content: space-between;\n align-items: center;\n margin-bottom: 1.5rem;\n }\n\n .section-title {\n font-size: 1.8rem;\n color: #667eea;\n border-left: 4px solid #667eea;\n padding-left: 1rem;\n font-weight: 600;\n }\n\n .copy-button {\n background: linear-gradient(135deg, #667eea 0%, #764ba2 100%);\n color: white;\n border: none;\n padding: 0.6rem 1.5rem;\n border-radius: 8px;\n cursor: pointer;\n font-size: 1rem;\n font-weight: 600;\n transition: transform 0.2s, box-shadow 0.2s;\n }\n\n .copy-button:hover {\n transform: translateY(-2px);\n box-shadow: 0 5px 15px rgba(102, 126, 234, 0.4);\n }\n\n .prompt-box {\n background: #f8f9fa;\n border: 2px solid #e9ecef;\n border-radius: 8px;\n padding: 1.5rem;\n font-family: 'Courier New', monospace;\n white-space: pre-wrap;\n line-height: 1.8;\n font-size: 0.95rem;\n }\n\n .placeholder {\n color: #fd7e14;\n font-weight: bold;\n }\n\n .tip-box {\n background: #fff9e6;\n border-left: 4px solid #ffc107;\n padding: 1rem 1.5rem;\n margin-top: 1rem;\n border-radius: 4px;\n }\n\n .tip-box strong {\n color: #f59e0b;\n }\n\n .logic-principle {\n margin-bottom: 2rem;\n }\n\n .logic-principle h3 {\n color: #667eea;\n font-size: 1.3rem;\n margin-bottom: 0.75rem;\n font-weight: 600;\n }\n\n .logic-principle p {\n color: #555;\n line-height: 1.8;\n }\n\n .example-box {\n background: #f0f4ff;\n border: 2px solid #667eea;\n border-radius: 8px;\n padding: 1.5rem;\n margin-top: 1rem;\n }\n\n .example-box h4 {\n color: #667eea;\n margin-bottom: 1rem;\n font-size: 1.1rem;\n }\n\n .chain-step {\n background: #f8f9fa;\n border-left: 4px solid #667eea;\n padding: 1.5rem;\n margin-bottom: 1.5rem;\n border-radius: 4px;\n }\n\n .chain-step h3 {\n color: #667eea;\n margin-bottom: 1rem;\n font-size: 1.2rem;\n }\n\n .chain-step .prompt-text {\n background: white;\n padding: 1rem;\n border-radius: 4px;\n font-family: 'Courier New', monospace;\n margin: 1rem 0;\n border: 1px solid #e9ecef;\n }\n\n .hitl-tip {\n margin-bottom: 2rem;\n }\n\n .hitl-tip h3 {\n color: #667eea;\n font-size: 1.2rem;\n margin-bottom: 0.75rem;\n font-weight: 600;\n }\n\n .hitl-tip p {\n color: #555;\n line-height: 1.8;\n }\n\n .card-footer {\n background: #f8f9fa;\n padding: 1.5rem 2.5rem;\n border-top: 1px solid #e9ecef;\n display: flex;\n justify-content: space-between;\n align-items: center;\n }\n\n .footer-stat {\n display: flex;\n align-items: center;\n gap: 0.5rem;\n color: #666;\n font-size: 0.95rem;\n }\n\n .checkmark {\n color: #10b981;\n margin-right: 0.5rem;\n }\n\n @media (max-width: 768px) {\n body {\n padding: 1rem;\n }\n\n .page-title {\n font-size: 1.8rem;\n }\n\n .card-header h1 {\n font-size: 1.8rem;\n }\n\n .card-body {\n padding: 1.5rem;\n }\n\n .section-title-container {\n flex-direction: column;\n align-items: flex-start;\n gap: 1rem;\n }\n\n .copy-button {\n width: 100%;\n }\n\n .card-footer {\n flex-direction: column;\n gap: 1rem;\n align-items: flex-start;\n }\n }\n <\/style>\n<\/head>\n<body>\n <div class=\"page-title\">AiPro Institute\u2122 Prompt Library<\/div>\n\n <div class=\"card\">\n <div class=\"card-header\">\n <h1>\ud83d\ude80 Product Launch Readiness<\/h1>\n <div class=\"meta-container\">\n <div class=\"meta-badge\">\ud83d\udcc1 Product & Operations<\/div>\n <div class=\"meta-badge\">\u23f1\ufe0f 30-40 minutes<\/div>\n <div class=\"meta-badge\">\ud83c\udfaf Advanced<\/div>\n <\/div>\n <div class=\"compatibility-container\">\n <div class=\"compatibility-badge\">ChatGPT<\/div>\n <div class=\"compatibility-badge\">Claude<\/div>\n <div class=\"compatibility-badge\">Gemini<\/div>\n <div class=\"compatibility-badge\">Perplexity<\/div>\n <div class=\"compatibility-badge\">Grok<\/div>\n <\/div>\n <\/div>\n\n <div class=\"card-body\">\n <div class=\"section\">\n <div class=\"section-title-container\">\n <h2 class=\"section-title\">The Prompt<\/h2>\n <button class=\"copy-button\" onclick=\"copyPrompt()\">\ud83d\udccb Copy Prompt<\/button>\n <\/div>\n <div class=\"prompt-box\" id=\"promptContent\">You are an elite Product Launch Strategist specializing in go-to-market planning, cross-functional coordination, and launch risk management. Your expertise lies in assessing launch readiness across product, engineering, marketing, sales, support, and operations to ensure successful market entry with minimal post-launch firefighting.\n\n**CONTEXT SETTING:**\nI need you to conduct a comprehensive launch readiness assessment for <span class=\"placeholder\">[PRODUCT_NAME: e.g., \"Mobile App 3.0 redesign\" or \"Enterprise API Platform\" or \"Premium subscription tier\" or \"Hardware device + companion app\"]<\/span> scheduled to launch on <span class=\"placeholder\">[LAUNCH_DATE: e.g., \"March 15, 2026\" or \"Q2 2026\" or \"6 weeks from today\"]<\/span> to identify gaps, risks, and critical path items requiring attention before go-live.\n\n**REQUIRED INPUTS:**\n\n\ud83c\udfaf **Launch Scope & Strategy:**\n- Launch Type: <span class=\"placeholder\">[LAUNCH_TYPE: e.g., \"New product launch\" or \"Major version upgrade\" or \"Feature expansion\" or \"Market expansion (new geography\/segment)\" or \"Rebrand\/reposition\"]<\/span>\n- Target Audience: <span class=\"placeholder\">[AUDIENCE: e.g., \"Existing customers (upgrade path)\" or \"New market segment: enterprise users\" or \"Geographic: EU market entry\" or \"Both new + existing users\"]<\/span>\n- Launch Approach: <span class=\"placeholder\">[APPROACH: e.g., \"Big bang launch to all users\" or \"Phased rollout (beta \u2192 limited \u2192 general availability)\" or \"Invite-only early access \u2192 public launch\" or \"Soft launch \u2192 marketing push\"]<\/span>\n- Success Metrics: <span class=\"placeholder\">[SUCCESS_CRITERIA: e.g., \"10K signups in week 1, 2K paid conversions in month 1, <2% critical bug rate, NPS >40\" or \"Zero downtime, 95% customer satisfaction, 25% adoption in 30 days\"]<\/span>\n\n\ud83d\udee0\ufe0f **Product & Technical Readiness:**\n- Product Status: <span class=\"placeholder\">[PRODUCT_STATE: e.g., \"Feature complete, in QA testing\" or \"95% complete, 2 features in progress\" or \"MVP ready, enhancement backlog identified\" or \"In closed beta with 50 users\"]<\/span>\n- Outstanding Work: <span class=\"placeholder\">[REMAINING_WORK: e.g., \"3 critical bugs, 8 minor bugs, 12 UX polish items, performance optimization needed\" or \"Documentation incomplete, onboarding flow needs refinement\"]<\/span>\n- Technical Risks: <span class=\"placeholder\">[TECH_RISKS: e.g., \"Scalability unproven (load tested to 1K users, expect 10K), database migration complex, third-party API dependency, legacy system integration fragile\"]<\/span>\n- Quality Status: <span class=\"placeholder\">[QUALITY: e.g., \"80% test coverage, 12 automated test suites, manual QA completed for core flows\" or \"Limited testing, known edge cases unaddressed\"]<\/span>\n\n\ud83d\udce2 **Go-to-Market Readiness:**\n- Marketing Materials: <span class=\"placeholder\">[MARKETING_STATUS: e.g., \"Landing page live, blog posts drafted, demo video 80% complete, case studies in progress\" or \"Not started\u2014need 3 weeks to prepare\" or \"Social media scheduled, PR outreach planned, launch event confirmed\"]<\/span>\n- Sales Enablement: <span class=\"placeholder\">[SALES_STATUS: e.g., \"Pitch deck ready, pricing finalized, sales training scheduled for week before launch\" or \"Account executives not yet trained, demo environment unstable, objection handling scripts missing\"]<\/span>\n- Channel Strategy: <span class=\"placeholder\">[CHANNELS: e.g., \"Email to 50K user base, Product Hunt launch, paid ads ($30K budget), partnership co-marketing\" or \"In-app announcement, organic social, no paid promotion\"]<\/span>\n\n\ud83c\udf93 **Enablement & Support:**\n- Documentation: <span class=\"placeholder\">[DOCS_STATUS: e.g., \"User guides complete, API docs 70% done, video tutorials scripted but not recorded, changelog ready\" or \"Knowledge base articles drafted, migration guide incomplete\"]<\/span>\n- Support Readiness: <span class=\"placeholder\">[SUPPORT_STATUS: e.g., \"Support team trained, FAQ prepared, ticket categories created, 2x coverage planned for launch week\" or \"Team unaware of launch, training not scheduled\"]<\/span>\n- Customer Success: <span class=\"placeholder\">[CS_STATUS: e.g., \"Onboarding playbook created, welcome email sequence ready, proactive outreach plan for key accounts\" or \"No specialized onboarding planned\"]<\/span>\n\n\u2699\ufe0f **Operations & Infrastructure:**\n- Infrastructure: <span class=\"placeholder\">[INFRA_STATUS: e.g., \"Auto-scaling configured, monitoring alerts set up, capacity tested to 5x expected load\" or \"Running on single server, scaling plan theoretical, monitoring basic\"]<\/span>\n- Data & Analytics: <span class=\"placeholder\">[ANALYTICS_STATUS: e.g., \"Event tracking implemented, dashboards built, A\/B test framework ready\" or \"Analytics instrumentation incomplete, no launch dashboard\"]<\/span>\n- Compliance & Legal: <span class=\"placeholder\">[COMPLIANCE: e.g., \"Terms of service updated, privacy policy reviewed, GDPR compliant, security audit passed\" or \"Legal review pending, data retention policies undefined\"]<\/span>\n\n\ud83d\udc65 **Team & Resource Status:**\n- Team Availability: <span class=\"placeholder\">[TEAM_STATUS: e.g., \"Core team dedicated, on-call rotation staffed for launch week, engineering capacity reserved for hotfixes\" or \"Team split across multiple projects, key engineer on vacation during launch\"]<\/span>\n- Decision Authority: <span class=\"placeholder\">[DECISION_MAKING: e.g., \"Launch\/no-launch decision owned by VP Product, go\/no-go meeting scheduled 3 days before\" or \"Unclear launch authority, no rollback criteria defined\"]<\/span>\n- Stakeholder Alignment: <span class=\"placeholder\">[ALIGNMENT: e.g., \"Executive team briefed and supportive, board aware, cross-functional teams aligned on timeline\" or \"Some resistance from sales team, concerns about readiness from engineering\"]<\/span>\n\n\ud83d\udcc5 **Timeline & Dependencies:**\n- Current Date: <span class=\"placeholder\">[TODAY: e.g., \"February 1, 2026\" or \"6 weeks before launch\"]<\/span>\n- Critical Path Items: <span class=\"placeholder\">[CRITICAL_PATH: e.g., \"Must complete: database migration (2 weeks), Apple App Store review (1-2 weeks uncertain), sales training (1 week), load testing (3 days)\" or \"No clear critical path identified\"]<\/span>\n- Known Blockers: <span class=\"placeholder\">[BLOCKERS: e.g., \"Waiting on legal approval for terms, third-party vendor integration delayed 2 weeks, design resource bottleneck\" or \"None identified\"]<\/span>\n\n**LAUNCH READINESS FRAMEWORK PRINCIPLES:**\n\n1. **Cross-Functional Completeness** - Product launch requires readiness across product, engineering, marketing, sales, support, operations, and legal\u2014weakness in any area jeopardizes success\n2. **Risk-Based Prioritization** - Not all gaps are equal; distinguish launch blockers (must fix) from day-2 improvements (can defer) based on impact and likelihood\n3. **Customer Impact Scenarios** - Evaluate readiness from customer perspective: Can they discover, evaluate, purchase, onboard, and use the product successfully?\n4. **Rollback & Contingency Planning** - Every launch needs abort criteria, rollback procedures, and contingency plans for identified risks\n5. **Post-Launch Readiness** - Launch day is just the beginning; readiness includes monitoring, rapid response, and continuous improvement capabilities\n6. **Stakeholder Alignment** - Launch success requires coordinated execution across teams with clear ownership, communication protocols, and decision authority\n7. **Realistic Timeline Assessment** - Wishful thinking kills launches; assess actual capacity, dependency risk, and build in buffer for inevitable surprises\n\n**YOUR COMPREHENSIVE LAUNCH READINESS ASSESSMENT MUST INCLUDE:**\n\n**SECTION 1: EXECUTIVE SUMMARY**\n<span class=\"checkmark\">\u2705<\/span> Overall launch readiness verdict (Ready\/At Risk\/Not Ready)\n<span class=\"checkmark\">\u2705<\/span> Confidence level in hitting launch date\n<span class=\"checkmark\">\u2705<\/span> Top 3-5 critical risks requiring immediate attention\n<span class=\"checkmark\">\u2705<\/span> Launch decision recommendation (go\/no-go\/conditional go)\n<span class=\"checkmark\">\u2705<\/span> Alternative scenario if current date is unrealistic\n\n**SECTION 2: PRODUCT & TECHNICAL READINESS**\n<span class=\"checkmark\">\u2705<\/span> Feature completeness assessment\n<span class=\"checkmark\">\u2705<\/span> Outstanding bug severity and resolution plan\n<span class=\"checkmark\">\u2705<\/span> Quality assurance coverage and gaps\n<span class=\"checkmark\">\u2705<\/span> Performance and scalability validation\n<span class=\"checkmark\">\u2705<\/span> User experience polish and edge case handling\n<span class=\"checkmark\">\u2705<\/span> Technical debt and known limitations\n<span class=\"checkmark\">\u2705<\/span> Platform\/device compatibility verification\n<span class=\"checkmark\">\u2705<\/span> Data migration and integration testing (if applicable)\n\n**SECTION 3: GO-TO-MARKET READINESS**\n<span class=\"checkmark\">\u2705<\/span> Marketing asset completeness (website, content, creative)\n<span class=\"checkmark\">\u2705<\/span> Sales enablement materials and training status\n<span class=\"checkmark\">\u2705<\/span> Channel activation plan and budget allocation\n<span class=\"checkmark\">\u2705<\/span> Pricing and packaging finalization\n<span class=\"checkmark\">\u2705<\/span> Messaging and positioning clarity\n<span class=\"checkmark\">\u2705<\/span> Partner and ecosystem coordination\n<span class=\"checkmark\">\u2705<\/span> Launch communications timeline (internal and external)\n\n**SECTION 4: CUSTOMER EXPERIENCE READINESS**\n<span class=\"checkmark\">\u2705<\/span> Onboarding flow validation (user testing completed?)\n<span class=\"checkmark\">\u2705<\/span> Documentation comprehensiveness and quality\n<span class=\"checkmark\">\u2705<\/span> In-product guidance and help resources\n<span class=\"checkmark\">\u2705<\/span> Support team training and resource allocation\n<span class=\"checkmark\">\u2705<\/span> FAQ and troubleshooting content preparation\n<span class=\"checkmark\">\u2705<\/span> Customer success playbooks for different segments\n<span class=\"checkmark\">\u2705<\/span> Migration path for existing users (if applicable)\n\n**SECTION 5: OPERATIONS & INFRASTRUCTURE**\n<span class=\"checkmark\">\u2705<\/span> Infrastructure scalability and capacity planning\n<span class=\"checkmark\">\u2705<\/span> Monitoring, alerting, and observability setup\n<span class=\"checkmark\">\u2705<\/span> Incident response and on-call procedures\n<span class=\"checkmark\">\u2705<\/span> Analytics instrumentation and dashboard readiness\n<span class=\"checkmark\">\u2705<\/span> Security and compliance validation\n<span class=\"checkmark\">\u2705<\/span> Third-party service dependencies and SLAs\n<span class=\"checkmark\">\u2705<\/span> Backup and disaster recovery procedures\n\n**SECTION 6: RISK ASSESSMENT & MITIGATION**\n<span class=\"checkmark\">\u2705<\/span> Comprehensive risk register (likelihood \u00d7 impact matrix)\n<span class=\"checkmark\">\u2705<\/span> Launch blocker identification (must-fix before launch)\n<span class=\"checkmark\">\u2705<\/span> High-priority risks with mitigation strategies\n<span class=\"checkmark\">\u2705<\/span> Accepted risks with monitoring plans\n<span class=\"checkmark\">\u2705<\/span> Rollback triggers and procedures\n<span class=\"checkmark\">\u2705<\/span> Contingency plans for likely failure scenarios\n<span class=\"checkmark\">\u2705<\/span> \"Break glass\" escalation procedures\n\n**SECTION 7: TIMELINE & CRITICAL PATH**\n<span class=\"checkmark\">\u2705<\/span> Remaining work breakdown by team\/function\n<span class=\"checkmark\">\u2705<\/span> Critical path analysis with dependencies\n<span class=\"checkmark\">\u2705<\/span> Resource capacity vs. required work assessment\n<span class=\"checkmark\">\u2705<\/span> Timeline risk factors (optimistic vs. realistic vs. pessimistic)\n<span class=\"checkmark\">\u2705<\/span> Go\/no-go decision timeline and criteria\n<span class=\"checkmark\">\u2705<\/span> Buffer analysis (slack in schedule for surprises)\n\n**SECTION 8: LAUNCH EXECUTION PLAN**\n<span class=\"checkmark\">\u2705<\/span> Launch day runbook (hour-by-hour activities)\n<span class=\"checkmark\">\u2705<\/span> Team roles and responsibilities (RACI matrix)\n<span class=\"checkmark\">\u2705<\/span> Communication protocols (internal escalation, external updates)\n<span class=\"checkmark\">\u2705<\/span> Success criteria and monitoring dashboard\n<span class=\"checkmark\">\u2705<\/span> Week 1 priorities and rapid response plan\n<span class=\"checkmark\">\u2705<\/span> Post-launch retrospective planning\n\n**SECTION 9: GAP ANALYSIS & ACTION ITEMS**\n<span class=\"checkmark\">\u2705<\/span> Comprehensive gap identification across all readiness dimensions\n<span class=\"checkmark\">\u2705<\/span> Prioritized action items (critical\/high\/medium\/low)\n<span class=\"checkmark\">\u2705<\/span> Owner assignment for each action item\n<span class=\"checkmark\">\u2705<\/span> Timeline and completion criteria\n<span class=\"checkmark\">\u2705<\/span> Dependencies and blockers for each action\n<span class=\"checkmark\">\u2705<\/span> Daily standup plan to track gap closure\n\n**SECTION 10: LAUNCH DECISION RECOMMENDATION**\n<span class=\"checkmark\">\u2705<\/span> Go\/No-Go recommendation with supporting rationale\n<span class=\"checkmark\">\u2705<\/span> Confidence assessment (% likelihood of successful launch)\n<span class=\"checkmark\">\u2705<\/span> Conditional scenarios (what needs to happen to launch safely)\n<span class=\"checkmark\">\u2705<\/span> Alternative date recommendation if current timing is risky\n<span class=\"checkmark\">\u2705<\/span> Trade-off analysis (launch with limitations vs. delay for polish)\n<span class=\"checkmark\">\u2705<\/span> Success criteria for declaring launch a win vs. need for course correction\n\n**OUTPUT FORMATTING REQUIREMENTS:**\n- Use readiness indicators: \ud83d\udfe2 Ready, \ud83d\udfe1 At Risk, \ud83d\udd34 Not Ready, \u26a0\ufe0f Blocker\n- Assign severity to risks: \ud83d\udd34 Critical, \ud83d\udfe1 High, \ud83d\udd35 Medium, \u26aa Low\n- Show completion status: \u2705 Complete, \ud83d\udd04 In Progress, \u274c Not Started, \u23f8\ufe0f Blocked\n- Provide specific, actionable recommendations (not generic advice)\n- Include owner, timeline, and success criteria for each action item\n- Present trade-offs clearly when perfect readiness is impossible\n- End each major section with \"Readiness Assessment\" summary\n- Final recommendation must be clear: Go \/ No-Go \/ Conditional Go with specific conditions\n\n**ANALYSIS DEPTH:**\nThis is a launch risk assessment, not a cheerleading exercise. Be honest about gaps, realistic about timelines, and specific about risks. A delayed launch is better than a botched one that damages brand trust, overwhelms support, or creates technical debt. Identify the minimum viable launch criteria vs. ideal state, and help leadership make an informed decision with eyes wide open about trade-offs.<\/div>\n <div class=\"tip-box\">\n <strong>\ud83d\udca1 Pro Tip:<\/strong> Launch readiness assessments are most effective when conducted 4-6 weeks before planned launch\u2014early enough to fix gaps, late enough that you have real work to assess. Schedule a formal go\/no-go review 3-5 days before launch with clear decision authority and rollback criteria.\n <\/div>\n <\/div>\n\n <div class=\"section\">\n <h2 class=\"section-title\">The Logic<\/h2>\n \n <div class=\"logic-principle\">\n <h3>1. Cross-Functional Completeness Prevents Siloed Failure<\/h3>\n <p>A launch is only as strong as its weakest link. A perfect product with untrained support staff creates frustrated customers and overwhelmed teams. Brilliant marketing without sales enablement generates leads that don't convert. Excellent positioning but unstable infrastructure causes outages that destroy trust. Cross-functional readiness assessment forces every team to examine their preparedness and dependencies. Product can't launch if legal hasn't approved terms; marketing can't execute if the product isn't feature-complete; sales can't sell without pricing and packaging finalization. This framework identifies where teams are out of sync\u2014where product thinks marketing is handling onboarding communication while marketing assumes product built it into the UI. Forcing explicit assessment of each function's readiness exposes dangerous assumptions before they become launch-day disasters.<\/p>\n <\/div>\n\n <div class=\"logic-principle\">\n <h3>2. Risk-Based Prioritization Separates Critical from Nice-to-Have<\/h3>\n <p>Not all gaps are created equal. A typo in documentation is annoying but not a launch blocker; a critical authentication bug that exposes user data absolutely is. Risk assessment\u2014evaluating each gap by impact (how bad if it happens) \u00d7 likelihood (probability it happens)\u2014distinguishes must-fix issues from can-defer improvements. High-impact, high-likelihood risks (server crashes under expected load, core feature doesn't work on iOS) are launch blockers requiring resolution or significant mitigation. Low-impact, low-likelihood risks (edge case bug affecting <1% of users in rare scenario) can be monitored post-launch. This framework prevents both dangerous launches (ignoring critical risks) and perfectionism paralysis (delaying for trivial polish). It creates honest conversations about trade-offs: Can we launch with this limitation? What's our backup plan if this risk materializes? What's the cost of delay versus accepting managed risk?<\/p>\n <\/div>\n\n <div class=\"logic-principle\">\n <h3>3. Customer Impact Scenarios Ground Readiness in Reality<\/h3>\n <p>Teams often assess readiness from their own perspective\u2014engineering considers product \"ready\" when features are built; marketing when assets are created; support when training is complete. But readiness must be measured from the customer perspective: Can a customer discover the product, understand its value, decide to purchase, complete payment, onboard successfully, and achieve their desired outcome? Walking through this end-to-end customer journey exposes gaps that silo-focused assessments miss. What happens when a customer tries to sign up during peak load? Where do they go if onboarding confuses them? What if they need help but documentation is incomplete? If a feature breaks, how long until they get support? Customer impact scenarios\u2014literally role-playing the customer journey\u2014reveal hidden dependencies and coordination failures that abstract checklists miss, ensuring launch readiness translates to actual customer success.<\/p>\n <\/div>\n\n <div class=\"logic-principle\">\n <h3>4. Rollback Planning Enables Confident Risk-Taking<\/h3>\n <p>The ability to rapidly reverse a launch decision transforms risk calculus. Without rollback capability, every risk becomes existential\u2014you're trapped with whatever breaks. With clear rollback procedures, abort criteria, and tested mechanisms to revert to previous state, you can take calculated risks knowing you're not betting the company. Rollback planning forces clarity on critical questions: At what point do we pull the plug? How quickly can we revert? What's the blast radius if we roll back (affected users, data loss, communication needed)? Who has authority to make the rollback call? Teams that plan rollbacks paradoxically launch more confidently because they know they're not trapped\u2014if things go sideways, there's an escape hatch. This transforms launch decisions from irrevocable leaps of faith into reversible experiments where you can fail safely, learn quickly, and try again with improvements.<\/p>\n <\/div>\n\n <div class=\"logic-principle\">\n <h3>5. Post-Launch Readiness Determines Long-Term Success<\/h3>\n <p>Launch day is just the beginning\u2014post-launch execution determines whether early momentum compounds or collapses. Post-launch readiness means having monitoring to detect problems before customers complain, rapid response capability to fix issues quickly, communication protocols to keep stakeholders informed, and continuous improvement processes to iterate on feedback. Teams often focus all energy on launch day, then exhaust themselves and disband, leaving the product to drift. But Week 1 post-launch is when you discover what actually breaks under real usage, learn which assumptions were wrong, and identify the improvements with highest impact. Post-launch readiness includes on-call rotations, incident response playbooks, daily standups to review metrics and issues, customer feedback collection and analysis, and reserved capacity for rapid iterations. Products that launch well but lack post-launch machinery falter; products with strong post-launch operations can recover from rough launches and continuously improve toward product-market fit.<\/p>\n <\/div>\n\n <div class=\"logic-principle\">\n <h3>6. Realistic Timeline Assessment Prevents Compressed Failure<\/h3>\n <p>Wishful thinking is the most common launch risk. Teams estimate based on optimistic scenarios (everything goes smoothly, no surprises, perfect execution) and ignore historical evidence that projects rarely finish on time. Realistic timeline assessment means acknowledging actual team capacity (accounting for meetings, context switching, competing priorities), dependency risk (waiting on others, external approvals, third-party services), and Murphy's Law buffer (inevitable surprises, scope creep, illness, technical complications). If your critical path requires perfect execution with zero slack, you're not planning\u2014you're hoping. Realistic assessment exposes when dates are fantasy, forcing honest conversations: Do we cut scope? Add resources? Accept a delayed launch? Launch with limitations? Teams resist these conversations because they're uncomfortable, but the alternative\u2014pretending an unrealistic date is achievable\u2014leads to crunch time death marches, burnout, quality shortcuts, and ultimately, launch failure or delay anyway. Realistic timelines with buffer enable sustainable execution and informed decisions.<\/p>\n <\/div>\n <\/div>\n\n <div class=\"section\">\n <h2 class=\"section-title\">Example Output Preview<\/h2>\n <div class=\"example-box\">\n <h4>\ud83d\ude80 Launch Readiness Assessment - TaskFlow Mobile App 3.0 (Launch: March 15, 2026)<\/h4>\n \n <p><strong>EXECUTIVE SUMMARY<\/strong><\/p>\n <p><strong>Overall Launch Readiness: \ud83d\udfe1 AT RISK<\/strong><\/p>\n <p><strong>Confidence in Launch Date: 60% (Conditional Go)<\/strong><\/p>\n \n <p><strong>Verdict:<\/strong> Launch is possible on March 15, but significant risks exist across technical stability, support readiness, and GTM execution. Recommend <strong>CONDITIONAL GO<\/strong> with specific must-complete criteria outlined below, OR consider 2-week delay to April 1 for safer launch with higher confidence.<\/p>\n\n <p><strong>Top 5 Critical Risks Requiring Immediate Attention:<\/strong><\/p>\n <ol style=\"line-height: 1.8;\">\n <li>\ud83d\udd34 <strong>BLOCKER: iOS App Store Review Timing<\/strong> - Submitted 2 days ago, average review time is 2-5 days but can be 7-10 days if rejected and resubmitted. High risk of missing March 15 launch if any issues found. <strong>Mitigation:<\/strong> Prepare Android-only launch plan as backup; have developer on standby for immediate fixes if rejected.<\/li>\n <li>\ud83d\udd34 <strong>Infrastructure Scalability Unproven<\/strong> - Load tested to 2,000 concurrent users; expect 5,000+ at launch based on user base + marketing push. Database queries showing performance degradation at scale. <strong>Risk:<\/strong> Launch day slowdowns or outages. <strong>Mitigation:<\/strong> Implement database query optimization (5 days), add caching layer (3 days), set up auto-scaling with aggressive thresholds.<\/li>\n <li>\ud83d\udfe1 <strong>Support Team Under-Prepared<\/strong> - Training scheduled for March 12 (3 days before launch), no practice runs with actual product. 18 support agents, but only 2 have used beta version. <strong>Risk:<\/strong> Overwhelmed support, poor customer experience in critical first week. <strong>Mitigation:<\/strong> Move training to March 8, require all agents to complete 2-hour product walkthrough by March 10, create cheat sheets for common issues.<\/li>\n <li>\ud83d\udfe1 <strong>Migration Path for Existing Users Untested<\/strong> - 47,000 existing users must migrate to new app. Migration tested with 50 beta users successfully, but edge cases (users with >100 projects, special characters in data, expired subscriptions) not fully validated. <strong>Risk:<\/strong> Data loss, failed migrations, support ticket surge. <strong>Mitigation:<\/strong> Phased migration: power users first (March 15-17), then general rollout (March 18-22) with rollback capability.<\/li>\n <li>\ud83d\udfe1 <strong>Marketing Landing Page Not Live<\/strong> - Design approved, content finalized, but site not deployed or tested. Dev handoff happening March 8, needs QA and final approval. <strong>Risk:<\/strong> Traffic from launch campaigns lands on incomplete\/broken page. <strong>Mitigation:<\/strong> Prioritize landing page deployment by March 10 with 5 days for testing and iteration.<\/li>\n <\/ol>\n\n <p><strong>Launch Decision Recommendation: CONDITIONAL GO<\/strong><\/p>\n <p><strong>Conditions for Safe Launch:<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>\u2705 iOS App Store approval received by March 12 (3 days before launch) - If not, delay to March 22<\/li>\n <li>\u2705 Infrastructure optimization complete and load tested to 6,000 concurrent by March 11<\/li>\n <li>\u2705 Support team training completed and agents demonstrate competency by March 12<\/li>\n <li>\u2705 Landing page live and tested by March 10<\/li>\n <li>\u2705 Go\/No-Go review meeting March 13 with clear abort criteria<\/li>\n <\/ul>\n\n <p><strong>Alternative Scenario:<\/strong> If 3+ conditions above are not met by March 13, recommend <strong>2-week delay to April 1<\/strong>. Cost of delay: ~$40K in lost revenue, 2 weeks of team opportunity cost. Benefit: Significantly reduced launch risk, better customer experience, higher confidence in technical stability.<\/p>\n\n <p><strong>PRODUCT & TECHNICAL READINESS: \ud83d\udfe1 AT RISK<\/strong><\/p>\n \n <p><strong>Feature Completeness: \ud83d\udfe2 READY<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>All planned features implemented and functional<\/li>\n <li>Beta testing with 150 users completed; feedback incorporated<\/li>\n <li>No missing features that would block launch<\/li>\n <\/ul>\n\n <p><strong>Bug Status: \ud83d\udfe1 AT RISK<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li><strong>Critical Bugs:<\/strong> 0 (all resolved) \u2705<\/li>\n <li><strong>High Priority:<\/strong> 3 open (2 under investigation, 1 fix in QA)<\/li>\n <li><strong>Medium Priority:<\/strong> 12 open (acceptable to launch, monitor post-launch)<\/li>\n <li><strong>Low Priority:<\/strong> 27 open (defer to future releases)<\/li>\n <li><strong>Concern:<\/strong> High-priority bug #247 (offline sync occasionally fails to resolve conflicts) still being investigated\u2014could be launch blocker if root cause isn't understood. Target resolution: March 10.<\/li>\n <\/ul>\n\n <p><strong>Quality Assurance: \ud83d\udfe2 ADEQUATE<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>85% automated test coverage on core flows<\/li>\n <li>Manual QA completed on iOS (iPhone 13-15) and Android (Samsung S22-S24, Pixel 7-8)<\/li>\n <li>Regression testing passed for all critical user journeys<\/li>\n <li>Accessibility testing completed (WCAG 2.1 AA compliance verified)<\/li>\n <li><strong>Gap:<\/strong> Limited testing on older devices (iPhone 11, Android 10) - 15% of user base; may encounter edge case issues<\/li>\n <\/ul>\n\n <p><strong>Performance & Scalability: \ud83d\udd34 NOT READY<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li><strong>Load Testing:<\/strong> Validated to 2,000 concurrent users; performance acceptable<\/li>\n <li><strong>Expected Load:<\/strong> 5,000-7,000 concurrent at launch peak (based on 47K user base + marketing surge)<\/li>\n <li><strong>Bottleneck Identified:<\/strong> Database queries for project loading degrade beyond 3,000 users (avg response time: 850ms \u2192 3.2s)<\/li>\n <li><strong>Infrastructure:<\/strong> Auto-scaling configured but never tested at target load; monitoring alerts set but thresholds untested<\/li>\n <li><strong>REQUIRED ACTIONS:<\/strong><\/li>\n <li style=\"margin-left: 2rem;\">1. Database query optimization (identify N+1 queries, add indexes) - ENG team, 5 days, Due: March 10<\/li>\n <li style=\"margin-left: 2rem;\">2. Implement Redis caching for frequently accessed project data - ENG team, 3 days, Due: March 11<\/li>\n <li style=\"margin-left: 2rem;\">3. Load test to 8,000 concurrent users and validate response times <2s p95 - QA team, 2 days, Due: March 13<\/li>\n <\/ul>\n\n <p><strong>Technical Debt & Limitations: \ud83d\udfe1 ACCEPTABLE<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>Known limitation: Real-time collaboration limited to 8 simultaneous editors (acceptable for MVP; 95% of projects have <5 collaborators)<\/li>\n <li>Workaround documented: Users with >8 collaborators can use \"turn-based\" editing mode<\/li>\n <li>Technical debt: Legacy API endpoints still supported but should be deprecated within 6 months post-launch<\/li>\n <\/ul>\n\n <p><strong>Readiness Assessment:<\/strong> Product is feature-complete and quality is acceptable for launch. Primary concern is performance at scale\u2014infrastructure optimization is on critical path and must complete by March 11 for safe launch. If load testing on March 13 reveals issues, we lack time to fix before March 15 launch.<\/p>\n\n <p><strong>GO-TO-MARKET READINESS: \ud83d\udfe1 AT RISK<\/strong><\/p>\n \n <p><strong>Marketing Assets: \ud83d\udfe1 AT RISK<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>\u2705 Blog post announcing launch (drafted, scheduled for March 15, 9am)<\/li>\n <li>\ud83d\udd04 Landing page (design approved, in development, not yet live) - <strong>CRITICAL: Deploy by March 10<\/strong><\/li>\n <li>\u2705 Demo video (90 seconds, professional production, completed)<\/li>\n <li>\u2705 Social media assets (graphics, copy for LinkedIn, Twitter, Facebook scheduled)<\/li>\n <li>\ud83d\udd04 Case study with beta customer (interview complete, writeup 70% done, targeting March 12)<\/li>\n <li>\u274c Press release (not started, optional\u2014decided not to pursue press outreach for this launch)<\/li>\n <\/ul>\n\n <p><strong>Sales Enablement: \ud83d\udfe2 READY<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>\u2705 Pitch deck updated with v3.0 features and benefits<\/li>\n <li>\u2705 Pricing finalized: Free tier (unchanged), Basic $12\/mo (new tier), Pro $24\/mo (upgraded from $18)<\/li>\n <li>\u2705 Sales training scheduled March 12, 2-hour session with product demo and objection handling<\/li>\n <li>\u2705 Demo environment stable and accessible to all account executives<\/li>\n <li>\u2705 Internal FAQ for common customer questions prepared<\/li>\n <\/ul>\n\n <p><strong>Channel Activation: \ud83d\udfe2 READY<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li><strong>Email:<\/strong> Launch announcement email to 47,000 existing users scheduled for March 15, 10am<\/li>\n <li><strong>In-App:<\/strong> Notification banner prepared for web app users directing to mobile app download<\/li>\n <li><strong>Paid Ads:<\/strong> $30K budget allocated; campaigns created in Google Ads and Facebook Ads, targeting \"project management app\" keywords; scheduled to go live March 15<\/li>\n <li><strong>Product Hunt:<\/strong> Submission prepared, scheduled for March 16 (day after launch to build momentum)<\/li>\n <li><strong>Partnerships:<\/strong> Co-marketing email with integration partner (Zapier) scheduled for March 18<\/li>\n <\/ul>\n\n <p><strong>Readiness Assessment:<\/strong> GTM execution is mostly ready. Landing page deployment is on critical path and creates launch day risk if not completed by March 10. All other assets are on track. Sales team is aligned and prepared.<\/p>\n\n <p><em>[Assessment continues with Customer Experience Readiness, Operations & Infrastructure, Risk Assessment, Timeline Analysis, Launch Execution Plan, Gap Analysis, and Final Launch Decision sections...]<\/em><\/p>\n\n <p><strong>FINAL LAUNCH DECISION RECOMMENDATION<\/strong><\/p>\n \n <p><strong>Recommendation: CONDITIONAL GO for March 15, 2026<\/strong><\/p>\n <p><strong>Confidence Level: 60%<\/strong><\/p>\n\n <p><strong>GO Decision Conditions (All Must Be Met by March 13):<\/strong><\/p>\n <ol style=\"line-height: 1.8;\">\n <li>\u2705 iOS App Store approval received (currently in review, submitted March 1)<\/li>\n <li>\u2705 Infrastructure performance validated to 6,000+ concurrent users with <2s p95 response time<\/li>\n <li>\u2705 High-priority bug #247 (offline sync) resolved or decision made to launch with workaround documented<\/li>\n <li>\u2705 Support team training completed with demonstrated product competency<\/li>\n <li>\u2705 Landing page live, tested, and validated across devices<\/li>\n <\/ol>\n\n <p><strong>Go\/No-Go Review: Thursday, March 13, 4pm<\/strong><\/p>\n <p><strong>Decision Makers:<\/strong> VP Product (launch owner), VP Engineering (technical go), VP Marketing (GTM readiness), CTO (infrastructure approval)<\/p>\n <p><strong>Abort Criteria (Automatic No-Go Triggers):<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li>iOS App Store rejection received after March 12 (insufficient time to fix and resubmit)<\/li>\n <li>Load testing on March 13 reveals critical performance issues requiring >2 days to fix<\/li>\n <li>Database migration failure rate >5% in power user testing (March 12-13)<\/li>\n <li>Discovery of critical security vulnerability<\/li>\n <\/ul>\n\n <p><strong>Rollback Plan:<\/strong> If launched and critical issues emerge in first 24 hours:<\/p>\n <ul style=\"line-height: 1.8;\">\n <li><strong>Trigger:<\/strong> >5% of users reporting data loss, sustained outage >2 hours, security breach<\/li>\n <li><strong>Authority:<\/strong> CTO or VP Product can call rollback<\/li>\n <li><strong>Procedure:<\/strong> (1) Disable new user signups, (2) Halt marketing campaigns, (3) Display maintenance message, (4) Revert to v2.0 app in stores, (5) Migrate users back to previous version<\/li>\n <li><strong>Communication:<\/strong> Email to all users within 4 hours explaining situation and timeline<\/li>\n <\/ul>\n\n <p><strong>Alternative Recommendation: If Conditions Not Met by March 13<\/strong><\/p>\n <p><strong>Delay to April 1, 2026 (2-week delay)<\/strong><\/p>\n <p><strong>Rationale:<\/strong> Two additional weeks provides buffer to resolve technical risks, complete marketing assets without rush, allow fuller support preparation, and reduce launch day stress. Cost of delay is manageable; cost of botched launch is significantly higher (brand damage, overwhelmed support, technical debt from rushed fixes).<\/p>\n\n <p><strong>Success Metrics (Declaring Launch Successful):<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li><strong>Week 1 Targets:<\/strong> 8,000+ downloads, <3% crash rate, <5% critical support tickets, 70%+ positive app store reviews<\/li>\n <li><strong>Month 1 Targets:<\/strong> 15,000 downloads, 25% existing user migration, 1,200+ paid conversions, NPS >40<\/li>\n <li><strong>Must Not Occur:<\/strong> Sustained outage >4 hours, data loss affecting >100 users, security incident, negative press coverage<\/li>\n <\/ul>\n\n <p><strong>Post-Launch Plan:<\/strong><\/p>\n <ul style=\"line-height: 1.8;\">\n <li><strong>Daily standups:<\/strong> March 15-22, 9am, product + eng + support leads<\/li>\n <li><strong>On-call rotation:<\/strong> 24\/7 coverage March 15-18, business hours March 19-25<\/li>\n <li><strong>Metrics monitoring:<\/strong> Real-time dashboard tracking downloads, crashes, support tickets, performance<\/li>\n <li><strong>Retrospective:<\/strong> March 29, full team debrief on what went well and what to improve<\/li>\n <\/ul>\n <\/div>\n <\/div>\n\n <div class=\"section\">\n <h2 class=\"section-title\">Prompt Chain Strategy<\/h2>\n \n <div class=\"chain-step\">\n <h3>Step 1: Cross-Functional Readiness Assessment<\/h3>\n <div class=\"prompt-text\">Using the main prompt, first generate the Executive Summary, Product & Technical Readiness, and Go-to-Market Readiness sections. Assess each functional area's preparation and identify major gaps.<\/div>\n <p><strong>Expected Output:<\/strong> High-level readiness verdict with clear assessment of product quality, technical stability, and GTM preparedness. Identifies whether you have a product problem, technical risk, or GTM execution gap.<\/p>\n <\/div>\n\n <div class=\"chain-step\">\n <h3>Step 2: Operations, Risk, and Timeline Analysis<\/h3>\n <div class=\"prompt-text\">\"Now expand with Customer Experience Readiness, Operations & Infrastructure, Risk Assessment & Mitigation, and Timeline & Critical Path sections. Evaluate end-to-end customer experience, infrastructure readiness, comprehensive risk register, and realistic timeline assessment. Identify launch blockers vs. day-2 issues.\"<\/div>\n <p><strong>Expected Output:<\/strong> Detailed risk analysis with severity ratings, critical path identification showing what must complete before launch, and operations validation ensuring post-launch support readiness. Reveals hidden dependencies and timeline risks.<\/p>\n <\/div>\n\n <div class=\"chain-step\">\n <h3>Step 3: Launch Decision and Execution Plan<\/h3>\n <div class=\"prompt-text\">\"Complete the assessment with Launch Execution Plan, Gap Analysis & Action Items, and Launch Decision Recommendation sections. Provide specific action items with owners and timelines, create launch day runbook, define go\/no-go criteria, and give clear launch recommendation with conditions. Include rollback plan and success metrics.\"<\/div>\n <p><strong>Expected Output:<\/strong> Actionable launch plan with clear decision recommendation (go\/no-go\/conditional), specific conditions that must be met, prioritized action items to close gaps, and post-launch monitoring plan. Enables leadership to make informed launch decision with clear risk understanding.<\/p>\n <\/div>\n <\/div>\n\n <div class=\"section\">\n <h2 class=\"section-title\">Human-in-the-Loop Refinements<\/h2>\n \n <div class=\"hitl-tip\">\n <h3>1. Conduct Pre-Mortem Exercise<\/h3>\n <p>Imagine the launch failed catastrophically. Request: \"Conduct a pre-mortem analysis\u2014assume the launch on March 15 was a disaster. What are the 10 most likely failure scenarios that could have caused this? For each scenario: (1) What specifically went wrong? (2) What early warning signs would we have seen? (3) What could we have done to prevent it? (4) What's our mitigation strategy if it happens?\" Pre-mortems surface risks teams are unconsciously avoiding and create proactive mitigation strategies before problems occur.<\/p>\n <\/div>\n\n <div class=\"hitl-tip\">\n <h3>2. Validate with Cross-Functional Reality Check<\/h3>\n <p>AI assessments need ground truth validation. Prompt: \"I've shared this readiness assessment with engineering, marketing, sales, and support leads. Here's their feedback [provide feedback]. Where do their concerns differ from this assessment? Are there risks I'm underestimating or gaps they're seeing that weren't captured? Update the risk register and action items based on this team input.\" Frontline teams often see practical execution challenges that high-level assessments miss.<\/p>\n <\/div>\n\n <div class=\"hitl-tip\">\n <h3>3. Stress Test the Timeline with Pessimistic Scenarios<\/h3>\n <p>Optimistic timelines always slip. Ask: \"Re-analyze the critical path assuming pessimistic but realistic scenarios: (1) iOS App Store takes 8 days to approve, (2) Infrastructure optimization takes 2x longer than estimated, (3) One key engineer is sick for 3 days, (4) Marketing asset approval delayed 2 days. Does the March 15 launch survive? What breaks? What's the realistic date with these contingencies factored in?\" Pessimistic planning reveals when your timeline has no margin for normal friction.<\/p>\n <\/div>\n\n <div class=\"hitl-tip\">\n <h3>4. Define Minimum Viable Launch Criteria<\/h3>\n <p>Perfect readiness is often impossible. Request: \"Define three launch tiers: (1) Ideal launch\u2014everything perfect, zero compromises; (2) Good launch\u2014acceptable trade-offs, manageable risks; (3) Minimum viable launch\u2014bare minimum to launch without disaster. For the current state, which tier are we in? What specific improvements move us from minimum viable to good? What's truly non-negotiable vs. nice-to-have?\" This framework helps teams make honest trade-off decisions rather than pretending everything is critical.<\/p>\n <\/div>\n\n <div class=\"hitl-tip\">\n <h3>5. Build Launch Day Incident Response Playbook<\/h3>\n <p>Murphy's Law guarantees something will break. Prompt: \"Create a launch day incident response playbook covering: (1) How do we detect problems (monitoring, support tickets, social media)? (2) Escalation paths\u2014who gets alerted for what severity? (3) Communication templates for common issues (outage, bugs, feature not working). (4) Rollback decision tree\u2014when do we abort vs. patch? (5) Hotfix deployment process without standard approval gates. Make this actionable enough that anyone on-call can execute it.\" Incidents are less catastrophic when response is pre-planned rather than improvised in panic.<\/p>\n <\/div>\n\n <div class=\"hitl-tip\">\n <h3>6. Schedule Post-Launch Learning Retrospective<\/h3>\n <p>Launches are learning opportunities regardless of outcome. Request: \"Design a post-launch retrospective framework to be conducted 2 weeks after launch: (1) What went well that we should replicate? (2) What went poorly that we should fix? (3) What surprised us that we didn't anticipate? (4) What would we do differently next launch? (5) What processes or tools should we build to make future launches smoother? Create this framework now so we're prepared to capture learning while it's fresh.\" Teams that systematize launch learning compound their capabilities; those that don't repeat the same mistakes every launch.<\/p>\n <\/div>\n <\/div>\n <\/div>\n\n <div class=\"card-footer\">\n <div class=\"footer-stat\">\u2b50 <strong>4.8\/5.0<\/strong> rating<\/div>\n <div class=\"footer-stat\">\ud83d\udccb Copied <strong>2,187<\/strong> times<\/div>\n <div class=\"footer-stat\">\ud83d\udcac <strong>173<\/strong> reviews<\/div>\n <\/div>\n <\/div>\n\n <script>\n function copyPrompt() {\n const promptContent = document.getElementById('promptContent').innerText;\n navigator.clipboard.writeText(promptContent).then(() => {\n const button = document.querySelector('.copy-button');\n const originalText = button.innerHTML;\n button.innerHTML = '\u2705 Copied!';\n setTimeout(() => {\n button.innerHTML = originalText;\n }, 2000);\n }).catch(err => {\n console.error('Failed to copy text: ', err);\n alert('Failed to copy to clipboard');\n });\n }\n <\/script>\n<\/body>\n<\/html>\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>","protected":false},"excerpt":{"rendered":"<p>Product Launch Readiness – AiPro Institute\u2122 AiPro Institute\u2122 Prompt Library \ud83d\ude80 Product Launch Readiness \ud83d\udcc1 Product & Operations \u23f1\ufe0f 30-40 minutes \ud83c\udfaf Advanced ChatGPT Claude Gemini Perplexity Grok The Prompt \ud83d\udccb Copy Prompt You are an elite Product Launch Strategist specializing in go-to-market planning, cross-functional coordination, and launch risk management. Your expertise lies in assessing…<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[187],"tags":[],"class_list":["post-4954","post","type-post","status-publish","format-standard","hentry","category-product-operations"],"acf":[],"_links":{"self":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts\/4954","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/comments?post=4954"}],"version-history":[{"count":4,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts\/4954\/revisions"}],"predecessor-version":[{"id":4963,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/posts\/4954\/revisions\/4963"}],"wp:attachment":[{"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/media?parent=4954"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/categories?post=4954"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/teen.aiproinstitute.com\/zh\/wp-json\/wp\/v2\/tags?post=4954"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}