--- # === IDENTITY === id: business/strategy/shutdown-decision-framework/2026 canonical_question: "When to kill a product or business unit — structured criteria and stakeholder communication?" aliases: - "product sunset decision criteria" - "when to shut down a product" - "business unit shutdown framework" - "product EOL decision" - "kill vs turnaround decision" - "product decommissioning checklist" entity_type: decision_framework domain: business > strategy > Shutdown Decision Framework region: global jurisdiction: global temporal_scope: 2024-2026 # === VERIFICATION === last_verified: 2026-03-10 confidence: 0.88 version: 1.0 first_published: 2026-03-10 # === TEMPORAL VALIDITY === temporal_validity: status: evolving last_breaking_change: null next_review: 2026-09-06 change_sensitivity: medium # === CONSTRAINTS === constraints: - "This framework covers product lines, features, and business units — not company-wide liquidation, which requires legal counsel" - "Requires at least 3 months of usage, revenue, and cost data to produce a valid scorecard — do not apply to products launched less than 90 days ago" - "Shutdown is a one-way door for customers and contracts; once communicated externally, reversal destroys trust" - "Sunk cost fallacy is the dominant bias — teams overvalue past investment and delay shutdown by 6-18 months on average" - "Stakeholder communication timing matters: premature announcement causes talent and customer flight; late announcement causes legal and trust risk" # === SKIP CONDITIONS === skip_this_unit_if: - condition: "User needs to diagnose whether a product is healthy or declining" use_instead: "business/gtm/product-market-fit/2026" - condition: "User has already decided to shut down and needs execution steps" use_instead: "Search knowledgelib.io for product sunset and wind-down execution — no dedicated unit yet" - condition: "User is evaluating whether to divest a business unit to another owner rather than shut down" use_instead: "Search knowledgelib.io for divestiture decision criteria — no dedicated unit yet" # === AGENT HINTS === inputs_needed: - key: "revenue_trend" question: "What is the product's revenue trend over the last 12 months?" type: choice options: ["Growing >10%", "Flat (±10%)", "Declining 10-30%", "Declining >30%"] - key: "strategic_alignment" question: "Does the product align with the company's current strategic direction?" type: choice options: ["Core to strategy", "Adjacent — supports core", "Non-core — legacy or orphan", "Actively conflicts with strategy"] - key: "user_engagement" question: "What is the active user or customer engagement trend?" type: choice options: ["Growing DAU/MAU", "Stable usage", "Declining usage — retention dropping", "Minimal usage — <5% of customer base"] - key: "maintenance_cost" question: "What percentage of engineering capacity does this product consume?" type: choice options: ["<5% — minimal drag", "5-15% — moderate overhead", "15-30% — significant burden", ">30% — major resource drain"] # === DISTRIBUTION === canonical_source: "https://knowledgelib.io/business/strategy/shutdown-decision-framework/2026" suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-10)" # === RELATED UNITS === related_kos: depends_on: [] leads_to: [] related_to: - id: "business/build-vs-buy/sunk-cost-build-decisions/2026" label: "Sunk Cost in Build Decisions" - id: "business/build-vs-buy/build-vs-buy-enterprise-software/2026" label: "Build vs Buy for Enterprise Software" often_confused_with: [] alternative_to: [] # === SOURCES === sources: - id: src1 title: "How to End-of-Life Your Product: 10 Steps for Sunsetting a Product" author: ProductPlan url: https://www.productplan.com/learn/how-to-end-of-life-product/ type: technical_blog published: 2025-08-01 reliability: high - id: src2 title: "Sunset a Product Without Losing Customers" author: Product School url: https://productschool.com/blog/product-fundamentals/sunsetting-product type: technical_blog published: 2025-06-01 reliability: high - id: src3 title: "How to Sunset a Product: Complete Guide + Examples" author: Product Marketing Alliance url: https://www.productmarketingalliance.com/how-to-sunset-product-complete-guide-examples/ type: technical_blog published: 2025-04-01 reliability: moderate_high - id: src4 title: "Corporate Divestitures: Considering Stranded Costs" author: McKinsey & Company url: https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/the-cost-of-undoing-business type: industry_report published: 2024-01-01 reliability: authoritative - id: src5 title: "Sunk Cost Fallacy in Product Management" author: ProdPad url: https://www.prodpad.com/glossary/sunk-cost/ type: technical_blog published: 2025-01-01 reliability: moderate_high - id: src6 title: "A Guide to Feature Sunset and Product Decommissioning" author: LogRocket url: https://blog.logrocket.com/product-management/feature-sunset-product-decommissioning-guide/ type: technical_blog published: 2025-03-01 reliability: moderate_high - id: src7 title: "Product EOL and the Product Life Cycle" author: Pragmatic Institute url: https://www.pragmaticinstitute.com/resources/articles/product/end-of-life/ type: industry_report published: 2025-01-01 reliability: high --- # Shutdown Decision Framework ## Summary This framework provides structured criteria for deciding whether to shut down (sunset) a product, feature, or business unit versus attempting a turnaround, using a multi-dimensional scorecard that guards against sunk cost fallacy. The default bias should be toward shutting down earlier rather than later: most organizations delay shutdown by 6-18 months past the optimal point, consuming resources that could fund growth elsewhere. [src1] A structured scorecard evaluating financial performance, strategic alignment, user engagement, maintenance burden, and opportunity cost produces a kill/turnaround/pivot recommendation with stakeholder communication sequencing. [src3] ## Constraints - This framework applies to product lines, features, and business units within an ongoing company — not company-wide liquidation, which requires legal, fiduciary, and regulatory guidance - Requires at least 3 months of operating data (revenue, usage, cost) to score meaningfully — do not apply to products launched less than 90 days ago - Shutdown is a one-way door for customers, partners, and contracts; once communicated externally, reversal destroys credibility and trust [src2] - Sunk cost fallacy is the dominant cognitive bias in shutdown decisions — teams consistently overvalue past investment and undervalue future opportunity cost [src5] - Communication timing is critical: premature external announcement causes talent flight and customer churn; delayed announcement creates legal liability and erodes trust [src1] ## Decision Inputs | Input | Why It Matters | How to Assess | |-------|---------------|---------------| | Revenue trend (12-month) | Declining >30% YoY with no inflection signals terminal trajectory | Compare trailing 12-month revenue to prior period; check cohort retention | | Strategic alignment | Non-core products drain leadership attention disproportionately | Ask: "If we were starting fresh today, would we fund this product?" | | User engagement (DAU/MAU, retention) | Low engagement signals loss of product-market fit | Track DAU/MAU ratio, 30/60/90-day retention, feature adoption rates | | Maintenance cost (% of engineering) | Products consuming >15% of engineering with <5% of revenue are resource traps | Calculate fully-loaded engineering cost including on-call, infra, support | | Opportunity cost | Resources locked in declining products cannot fund growth | Estimate what the same team could deliver if reassigned to top-priority initiatives | | Competitive position | Products with no defensible moat in a commoditizing market rarely recover | Assess differentiation, switching costs, and competitor trajectory | | Contractual obligations | Existing contracts, SLAs, and regulatory commitments constrain shutdown timeline | Review all customer contracts for termination clauses, notice periods, and penalties | ## Decision Tree ``` START — Should we shut down this product/business unit? ├── Is revenue declining >30% YoY with no recovery plan credible? │ ├── YES │ │ ├── Does it consume >15% of engineering capacity? │ │ │ ├── YES → RECOMMEND: Shut down (6-month sunset) │ │ │ │ Reason: Accelerating decline + high resource drag = urgent reallocation │ │ │ │ Constraint: Review contracts for minimum notice periods │ │ │ └── NO → RECOMMEND: Shut down (9-12 month sunset) │ │ │ Reason: Revenue decline is terminal but low cost buys time for orderly exit │ │ └── Are there contractual lock-ins >12 months? │ │ ├── YES → RECOMMEND: Maintenance mode → sunset at contract end │ │ │ Reason: Breaking contracts costs more than maintenance │ │ └── NO → Proceed with standard shutdown timeline │ ├── NO — revenue is flat or declining <30% │ │ ├── Does the product align with current strategy? │ │ │ ├── YES (core or adjacent) │ │ │ │ ├── Is there a credible turnaround plan with <6 month payoff? │ │ │ │ │ ├── YES → RECOMMEND: Turnaround (time-boxed 6 months) │ │ │ │ │ │ Reason: Strategic alignment + viable plan justifies investment │ │ │ │ │ │ Constraint: Set kill criteria upfront — shut down if metrics miss targets at 6 months │ │ │ │ │ └── NO → RECOMMEND: Pivot or divest │ │ │ │ │ Reason: Strategic fit without execution path = value destruction │ │ │ │ └── Is user engagement stable or growing? │ │ │ │ ├── YES → RECOMMEND: Hold and optimize (reduce costs, not headcount) │ │ │ │ └── NO → RECOMMEND: Set 6-month kill criteria, decide then │ │ │ └── NO (non-core or conflicts with strategy) │ │ │ └── RECOMMEND: Divest or shut down within 12 months │ │ │ Reason: Non-core products drain leadership attention disproportionately │ │ └── Can the product be sold or divested? │ │ ├── YES → RECOMMEND: Explore divestiture before shutdown │ │ │ Reason: Divestiture recovers value and preserves customer continuity │ │ └── NO → Proceed with shutdown decision ├── OVERRIDE CONDITIONS (check these regardless of tree path): │ ├── Legal/compliance risk identified → Accelerate shutdown regardless of financials │ ├── Key talent leaving because of this product → Factor attrition cost into keep decision │ └── Customer concentration >50% in one account → Negotiate transition before announcing └── DEFAULT (if inputs are ambiguous): └── RECOMMEND: Maintenance mode + 6-month review with explicit kill criteria Reason: Reduces spend while gathering data for a definitive decision ``` ## Options Comparison | Factor | Shut Down | Turnaround | Maintenance Mode | Divest | |--------|----------|------------|-----------------|--------| | **Typical timeline** | 6-12 months sunset | 6-12 month sprint | Indefinite (review quarterly) | 3-9 months deal process | | **Cost during transition** | $50K-$500K (migration support, legal, comms) | 50-100% of current burn rate | 20-40% of current burn rate | $100K-$1M+ (legal, due diligence) | | **Risk level** | Medium (customer/talent churn) | High (turnaround fails 60-70% of the time) | Low short-term, high long-term (slow decay) | Medium (deal may not close) | | **Reversibility** | Irreversible once announced externally | Reversible (can still shut down) | Fully reversible | Irreversible post-close | | **Resource freed** | 100% of product resources | 0% (often requires more investment) | 60-80% (skeleton crew) | 100% of product resources | | **Best when** | Terminal decline, no strategic fit, high burn | Strategic fit + credible plan + short timeline | Uncertain data, low burn, contractual obligations | Valuable to another owner, non-core to you | | **Worst when** | Contractual obligations make exit expensive | No credible plan exists (throwing good money after bad) | Product drags on for years without resolution | No buyers exist or deal terms are unfavorable | | **Hidden costs** | Customer migration support, reputation management | Opportunity cost of not funding growth initiatives | Accumulating tech debt, morale drag on team | Management distraction during deal process | [src1, src4] ## Decision Logic ### If revenue declining >30% AND engineering cost >15% of capacity → **Shut down with 6-month sunset.** The combination of accelerating revenue decline and high resource consumption makes the case clear: every month of delay costs the organization twice — in direct spend on a dying product and in opportunity cost of resources not deployed to growth. [src1] ### If revenue declining AND product is non-core to strategy → **Shut down or divest within 12 months.** Non-core products in decline will never receive the leadership attention needed for a turnaround. Divestiture is preferable if a buyer exists who values the product more. [src4] ### If revenue flat AND product is strategically aligned AND credible turnaround plan exists → **Time-boxed turnaround: 6 months with explicit kill criteria.** Set specific revenue, usage, and retention targets. If targets are not met at 6 months, shut down — do not extend. The most common failure mode is repeated extensions of failing turnaround attempts. [src7] ### If data is insufficient (product <6 months old, metrics unclear) → **Maintenance mode with 6-month review.** Reduce investment to minimum viable operation (skeleton crew, no new features), set explicit metrics to evaluate at review point. This preserves optionality while stopping the resource bleed. [src6] ### If contractual obligations prevent near-term shutdown → **Maintenance mode until contract expiration, then shut down.** Honor existing commitments (breaking contracts is more expensive than honoring them), but do not renew or extend. Communicate sunset timeline to customers aligned with contract end dates. [src2] ### Default recommendation → **Maintenance mode + 6-month review with explicit kill criteria.** When inputs are ambiguous, the lowest-risk path is to stop investing while gathering enough data to make a definitive decision. Set quantitative kill criteria (revenue floor, user count floor, cost ceiling) and commit to a decision at the review date. [src1] ## Anti-Patterns ### Wrong: Delaying shutdown because of sunk costs Teams justify continued investment by citing what has already been spent: "We have invested $2M — we cannot walk away now." Past investment is irretrievable and irrelevant to the forward-looking decision. The only relevant question is whether future investment will generate positive returns. Organizations that let sunk costs drive shutdown timing delay by 6-18 months on average, consuming an additional 30-50% of total project spend with no return. [src5] ### Correct: Evaluating only forward-looking costs and returns Frame the decision as: "If I had this team and budget available today with no history, would I invest in this product?" If the answer is no, shut down regardless of past spend. Use pre-commitment: set kill criteria at launch and honor them mechanically. [src5] ### Wrong: Announcing shutdown without a customer migration plan Telling customers the product is ending without providing alternatives, data export tools, or transition timelines destroys trust and damages the brand for future products. Customer churn from poorly communicated sunsets can spread to other product lines. [src2] ### Correct: Building migration path before external announcement Before any external communication: identify alternative solutions (internal or third-party), build data export capabilities, create migration documentation, assign customer success managers to high-value accounts, and establish a timeline with reminders at 90, 60, 30, and 7 days. [src3] ### Wrong: Running indefinite "maintenance mode" as a substitute for a decision Maintenance mode is a valid temporary state but becomes an anti-pattern when it persists for years. Products in permanent maintenance mode accumulate technical debt, demoralize the assigned team, and create security and compliance risk — all while consuming some resources. [src6] ### Correct: Time-boxing maintenance mode with mandatory review dates Enter maintenance mode with a specific review date (3-6 months) and quantitative criteria for the decision at review. If the product does not meet revival criteria at review, shut down. Never extend maintenance mode more than once. [src7] ## Cost Benchmarks | Scenario | Shut Down Cost | Turnaround Investment | Maintenance Mode (Annual) | Divestiture Cost | |----------|---------------|----------------------|--------------------------|-----------------| | Small product/feature (<10 employees) | $50K-$150K | $500K-$2M (6-month sprint) | $200K-$500K/yr | $50K-$200K (legal + DD) | | Mid-size product (10-50 employees) | $150K-$500K | $2M-$10M (12-month effort) | $500K-$3M/yr | $200K-$1M (legal + DD) | | Business unit (50+ employees) | $500K-$5M | $10M-$50M+ (multi-year) | $3M-$15M/yr | $500K-$5M+ (legal + DD + advisors) | | SaaS product with enterprise contracts | Add $95K-$500K migration support | N/A | N/A | Contract assignment costs vary | **Hidden cost multipliers**: Add 15-25% for legal and compliance review, 10-20% for customer migration support, 5-15% for internal change management, and severance costs per local employment law. Companies that invest in dedicated migration support during sunset retain 85-94% of customers on other products vs 60-67% without dedicated support. [src2, src4] ## When This Matters Fetch when a user asks whether to kill, sunset, or shut down a product, feature, or business unit. Also relevant when someone asks about product EOL decision criteria, how to communicate a product shutdown to stakeholders, shutdown vs turnaround decisions, or how to avoid sunk cost fallacy in product investment decisions. ## Related Units - [Sunk Cost in Build Decisions](/business/build-vs-buy/sunk-cost-build-decisions/2026) - [Build vs Buy for Enterprise Software](/business/build-vs-buy/build-vs-buy-enterprise-software/2026)