Tech Launch Kill-Switch Diagnostic
Evaluate core functionality barriers, irreversible brand erosion, and hardware return thresholds. Determine objectively whether to Ship, Restrict to Closed Beta, or Pull the Plug.
Failure Horizon & Operational Operating Point
Sub-Factor Vulnerability Decomposition
Historical Post-Mortems: Why Technologies Were Cancelled
Based on documented hardware cancellations and product post-mortems.
Apple AirPower (2017–2019)
Promised seamless multi-device charging across any spot by packing 21–24 overlapping induction coils. Physical laws caused extreme magnetic interference and thermal build-up, exceeding consumer safety limits. Cancelled after 18 months of public promises.
Theranos Edison Device
Promised hundreds of lab tests from a fingerstick drop of blood. Microfluidics physics simply could not dilute and preserve required cell counts without catastrophic error variance. Secretly ran tests on diluted commercial Siemens machines before unraveling.
The 20% Return Rule
As veteran hardware executives note: an initial return rate exceeding 20% on hardware or persistent crash rate above 10% on software platforms generates a support debt spiral that eliminates all operating margins and permanently destroys brand equity.
Framework Methodology & Kill Criteria
What separates a regular buggy MVP from a product that must be cancelled?
A true MVP allows edge cases to fail while its central value loop works cleanly. For example, early Twitter had regular fail-whales due to traffic overload, but sending a tweet functioned. By contrast, if the core technology fails basic physical reality (e.g., thermal dissipation, sensor precision, severe unresolvable data mapping corruption), shipping does not shorten feedback loops—it burns runway and exposes leadership to fraud liabilities.
How is the Catastrophic Risk Index calculated?
The model computes a weighted composite index evaluating: (1) Core functionality deficiency weighted at 35%, (2) Critical defect/return rate penalty relative to the 20% hardware or 10% software threshold weighted at 30%, (3) Irreversible brand impairment potential at 20%, and (4) Active red flag penalties (physics impossibility, safety risks, support spikes) contributing up to +50 points.
When should a leadership team pull the plug vs postpone?
Postpone when the remaining hurdles are pure engineering execution with known physical paths and runway > 6 months. Kill immediately when the core mechanism violates thermodynamic or mathematical limits, requires fraudulent benchmark massaging to demonstrate viability, or presents fire/biomedical hazards.