Launch Readiness Score

Goal of the analysis:

The Launch Readiness Score (LRS) is a composite, evidence-based indicator of whether a product, feature, or offering is ready to go to market across product, operations, commercial, and regulatory dimensions. It enables executives to make a disciplined go/no-go or phased launch decision, reduces execution risk, protects revenue and brand equity, and aligns cross-functional teams around a single, objective view of readiness. The analysis identifies critical gaps early, prioritizes mitigation, and sets an accountable cadence to reach an agreed threshold for launch.

Data required:

• Workstream deliverables and status (core):
  • Product/engineering: feature completion, open defects by severity, performance/security test results, UAT sign-off.
  • Manufacturing/supply chain (if physical): supplier confirmations, yield rates, inventory on hand, logistics readiness.
  • Marketing: messaging, creative assets, content localization, media plans, approvals, launch calendar.
  • Sales/commercial: pricing and discount guidance, contracts/templates, CRM setup, playbooks, channel readiness.
  • Customer support/CSM: staffing, training completion, knowledge base articles, SLA definitions, escalation playbooks.
  • IT/operations: infrastructure capacity, release plan, monitoring/alerting, rollback procedures, change freeze.
• Milestones and gating criteria:
  • Documented go/no-go checklist with must-pass items (e.g., critical defect backlog = 0, regulatory approvals obtained).
  • Milestone dates, dependencies, and exit criteria per deliverable.
• Risk and dependency register:
  • Risks with likelihood/impact, owner, mitigation plans, residual risk rating.
  • Cross-workstream dependencies and critical path tasks.
• Capacity and training:
  • Enablement metrics: sales and support certification rates, content consumption, role-based proficiency scores.
  • Operational capacity: support contact forecast vs staffing, system load tests vs expected peak demand.
• Financial and legal/compliance:
  • Finalized pricing, SKU and tax configuration in ERP, revenue recognition assessment, margin model sign-off.
  • Contract terms, privacy and security reviews, regulatory filings/approvals, labeling and claims clearance.
• External validation and demand signals:
  • Beta/pilot results, NPS/CSAT, defect escape rate, trial-to-paid conversion.
  • Preorders, partner commitments, early pipeline, waitlist volume.
• Historical and benchmark data:
  • Previous launch outcomes (slippage, post-launch incidents, time-to-stability) and their LRS at launch.
  • Internal targets/thresholds by product type and region.

Detailed step-by-step instruction on how to conduct the analysis:

1. Define scope and unit of analysis. Specify the product/SKU or feature, geographies, channels, and the planned launch window. Decide if multiple waves (pilot vs general availability) will be scored separately.
2. Establish the readiness framework. List all relevant workstreams and their deliverables with clear exit criteria. Create a standardized checklist with evidence links for each item.
3. Set weights and must-pass gates. Assign weights to workstreams based on impact on customer experience and risk (e.g., product quality 25%, supply 15%, support 10%). Identify must-pass items that override the composite score (e.g., critical defects unresolved = no-go).
4. Define the scoring rubric. Use a consistent scale per deliverable (e.g., 0, 25, 50, 75, 100) anchored to evidence:
   • 0 = Not started; 50 = >50% complete with partial evidence; 75 = >90% complete with test evidence; 100 = complete with documented sign-off.
   • Translate to RAG thresholds (e.g., Red <70, Amber 70–84, Green ≥85).
5. Build the data pipeline and cadence. Pull status from systems of record (Jira/Asana/Smartsheet, PLM/QMS, ERP/MRP, CRM, LMS, marketing automation, IT monitoring). Define owners and update frequency (e.g., twice weekly), with mandatory evidence attachments.
6. Collect baseline data. Populate the checklist, confirm exit criteria, and resolve definition-of-done ambiguities. Capture risk register entries with current mitigations and due dates.
7. Calculate component scores.
   • Workstream score = weighted average of deliverable scores adjusted for quality: Score_ws = Progress% × Quality factor (e.g., test pass rate).
   • Apply risk penalty: Score_ws_adj = Score_ws − Risk_penalty (e.g., likelihood × impact scaled to 0–15 points).
   • Composite LRS = Σ(Weight_ws × Score_ws_adj) / Σ(Weights). If any must-pass gate = fail, flag overall status as No-Go regardless of LRS.
8. Segment and compare. Produce separate LRS for each region, channel, SKU/variant, and release wave. Highlight weakest segment driving overall risk.
9. Trend and forecast. Track weekly LRS and workstream velocities. Project “date-to-green” when LRS will cross the target threshold, using recent velocity and remaining gap. Run scenarios (e.g., de-scope features, increase support hiring) and recalc impact.
10. Benchmark. Compare to historical launches (e.g., average LRS at launch, post-launch incident rates) and internal targets by product class.
11. Executive review and decision. Present LRS, gate status, top risks, and recommended action (go, go with guardrails/phasing, or delay). Document decision, assumptions, and required mitigations with owners and dates.
12. Post-decision cadence. If go: lock change freeze, run T-30/T-14/T-7/T-1 checkpoints. If delay: re-baseline plan, escalate critical path issues, and maintain weekly reviews until thresholds are met.

Format of the output of analysis:

• Executive scorecard showing overall LRS, must-pass gate status, and projected date-to-green.
• Workstream heatmap (RAG) with evidence links and owner names.
• Checklist compliance table with completion %, quality/test pass rates, and risk penalties.
• Risk waterfall chart quantifying how top risks reduce the score and mitigation impact.
• Critical path Gantt and dependency map highlighting bottlenecks.
• Enablement dashboard (training/certification completion) and support capacity vs forecast.
• Supply/ops readiness dashboard (inventory coverage, supplier confirmations, logistics).
• Go/no-go decision memo summarizing rationale, conditions, guardrails, and next checkpoints.

How to interpret results:

• High LRS (≥85) with all gates green: Launch-ready. Residual risks should be low and mitigations in place. Consider a standard or broad rollout.
• High LRS but any gate failed: Not ready despite the score. Resolve gate(s) or adopt a limited pilot where the gate is not binding.
• Mid LRS (70–84): Borderline. Proceed only with guardrails (e.g., phased rollout, feature flags, traffic throttling) and clear mitigation ownership.
• Low LRS (<70): High risk of launch failure or customer impact. Delay and focus on critical path fixes.
• Segment differences: If certain regions/channels are red while others are green, stagger the launch to de-risk and learn.
• Trends: Improving, steady velocity toward the threshold is positive; volatile or last-minute jumps may indicate reporting optimism—request evidence audits.
• Benchmark context: Compare to prior launches’ LRS and subsequent incident rates. A high LRS historically correlating with smoother launches increases confidence.

Steps a company can take to improve on this measure:

• Governance and process: Establish a cross-functional launch PMO, daily stand-ups on the critical path, enforce a change freeze window, conduct full end-to-end dry runs and go/no-go rehearsals, and maintain a RAID log with executive sponsorship.
• Data and systems: Automate status ingestion from Jira/ERP/CRM/LMS, require evidence links for all green statuses, centralize artifacts in a single source of truth, and instrument telemetry/monitoring for early warning signals.
• Capability and training: Mandate role-based certifications for sales/support, provide concise playbooks and objection handling, run game-day simulations, and staff on-call rotations with clear runbooks.
• Product and scope management: De-scope non-critical features, fix or defer P1/P2 defects, use feature flags and canary releases, and ensure rollback paths are tested and documented.
• Commercial readiness: Finalize pricing/discount policies, complete SKU/tax setup, preload pipeline with offers, secure channel partner commitments, and align incentives to launch priorities.
• Operations and supply chain: Build buffer inventory, secure supplier capacity, pre-book logistics, validate disaster recovery, and run load tests to exceed peak demand assumptions.
• Risk management: Address top risks with specific mitigations, contingency budgets, and decision trees. If LRS is high but risk penalty is concentrated in one area (e.g., support), accelerate targeted mitigations or phase rollout.
• Compliance and legal: Close outstanding filings, complete security/privacy reviews, verify labeling/claims, and finalize contract templates to avoid last-minute blocks.
• Customer validation: Expand beta/pilot cohorts, collect sign-off from lighthouse customers, and ensure UAT is performed by representative users.

Benchmark comparisons:

General benchmarks:

• Typical go/no-go thresholds:
  • SaaS/consumer digital: 80–85 with all must-pass gates green.
  • Enterprise B2B: 85–90 with demonstrated enablement and support capacity.
  • Hardware/CPG: 90+ with inventory/logistics readiness and channel alignment.
  • Regulated (e.g., medical devices, fintech): 95+ with complete documentation and approvals.
• High-performing organizations pair thresholds with strict gate overrides (e.g., zero critical defects, security approvals mandatory).

Segment- or industry-specific benchmarks:

• SMB feature updates (low risk): 75–85 acceptable with feature flags and rapid rollback.
• Financial services releases: ≥90 with evidence of compliance, resilience testing, and incident response readiness.
• Medical devices/pharma: ≥98 and all regulatory checklists closed; pilots and labeling audited.

If robust external benchmarks are unavailable, build internal ones by analyzing the last 10–20 launches: record LRS at launch, post-launch incident rates, time-to-stability, and commercial ramp. Set thresholds to match the top quartile outcomes and refine annually.