The Strategic Pivot: How to Ask the Question That Saved Intel

By

Overview

In 1985, Intel faced an existential crisis. Japanese competitors had seized the memory chip market Intel helped create, leaving the company scrambling for direction. During a pivotal conversation, President Andy Grove asked CEO Gordon Moore a deceptively simple question: “If we were replaced tomorrow, what would a new CEO do?” Moore’s answer was immediate: exit the memory business. They both knew the right move but had hesitated to act. This moment of strategic clarity reshaped Intel—and the entire tech industry—by focusing on microprocessors.

The Strategic Pivot: How to Ask the Question That Saved Intel
Source: www.fastcompany.com

The lesson extends far beyond Intel. Organizations everywhere accumulate “zombie projects”—initiatives that never fully succeed but never die. These projects drain leadership attention, budget, and talent. The antidote is a structured approach to choosing what to stop and what to double down on. This tutorial provides a step-by-step framework to identify, evaluate, and eliminate zombie projects, inspired by Intel’s breakthrough question.

Prerequisites

Before applying this framework, ensure your organization has:

  • Leadership commitment to data-driven decisions over emotional attachments.
  • A clear inventory of all active projects, including resource allocation (budget, personnel, time).
  • Defined success metrics for each project (e.g., revenue milestones, market traction, technical feasibility).
  • A cross-functional review team that can evaluate projects objectively.

Step-by-Step Instructions

1. Identify Zombie Projects

Zombie projects are those that haven’t met their targets but are kept alive due to inertia, fear of sunk costs, or political loyalty. They often exhibit these signs:

  • Consistently missed milestones without consequences.
  • Low team morale or high turnover.
  • No clear path to profitability within a reasonable timeframe.
  • Leadership attention is required repeatedly to unblock progress.

Action: Create a project dashboard with key indicators: time since launch, budget spent vs. allocated, market feedback (if any), and alignment with strategic priorities. Flag any project that has been active for more than 18 months without significant traction.

2. Apply the “New CEO” Test

The core question from Intel’s story is: “If a new CEO took over tomorrow, what would they do?” This removes emotional bias and forces objectivity. For each zombie project, ask:

  • Would a new leader with no personal history choose to continue, pivot, or kill this project?
  • What evidence exists that this project can succeed if resourced differently?
  • If you had to present this project to a skeptical board, could you make a compelling case?

Action: Run a workshop where the review team role-plays as a fresh executive. Document answers for each project.

3. Evaluate Resource Allocation

Every dollar and person-hour spent on a zombie project is a dollar not spent on a promising alternative. Use a simple resource allocation matrix:

Project | Budget | Headcount | Time Spent | Strategic Fit | Success Probability
--------|--------|-----------|------------|---------------|--------------------
Alpha   | $500k  | 5 people  | 24 months  | Medium        | Low
Beta    | $200k  | 2 people  | 12 months  | High          | Medium
…

Action: Rank projects by potential ROI and alignment with strategic priorities. Identify the top 10% of resources committed to low-priority projects.

4. Make the Decision to Kill or Pivot

Based on the evaluation, classify each project into one of three categories:

  • Kill: Low success probability, weak strategic fit, and significant resources consumed. End cleanly.
  • Pivot: Interesting technology or team but wrong application. Redirect to a different market or use case.
  • Continue: Strong evidence of progress and clear path to value. Provide additional resources if needed.

Action: Hold a formal decision meeting with senior leadership. Use a voting mechanism (e.g., dot voting or ranked choice) to avoid deadlock. Communicate the outcome transparently to all stakeholders.

5. Implement Transition Teams

Research shows that dedicated transition teams reduce demonstration failure rates by around 50%. These teams are responsible for managing the wind-down, redeploying talent, and capturing lessons learned.

Action: For each killed or pivoted project, assign a transition lead. Their duties include:

  1. Documenting intellectual property and technical artifacts.
  2. Conducting exit interviews with team members.
  3. Recommending where freed-up resources should go.
  4. Reporting on common failure patterns to the broader organization.

Common Mistakes

Emotional attachment to founders or inventors: It’s easy to let the person behind a project influence the decision. Use the “New CEO” test to neutralize this.

Fear of admitting failure: Killing a project is not an admission of failure; it’s a strategic choice. Celebrate learning, not just success.

Insufficient data: Decisions based on gut feeling or partial information lead to zombie persistence. Invest in measurement upfront.

Ignoring sunk costs: What’s spent is gone. Only future potential should matter.

Summary

Intel’s pivotal question—“What would a new CEO do?”—offers a powerful tool for cutting through inertia. By systematically identifying zombie projects, applying objective tests, reallocating resources, and making decisive kills or pivots, organizations can free up energy for truly transformative innovation. The result is a leaner portfolio, faster decision cycles, and a culture that values action over activity.

Tags:

Related Articles

Recommended

Discover More

Reviving the Apple Lisa: An FPGA-Based Tribute to a Pioneering ComputerStar Wars Battlefront 2 Player Count Spikes as 'Resurgence Day' Returns, Reigniting Calls for SequelBreaking: In-Utero Surgery Performed on Fetus, AI Agent Wipes Database in 9 Seconds, Universe's End Predicted SoonerWhy Big Exchanges Want Regulators to Target Hyperliquid: Key Questions AnsweredGitHub’s Code Search Suffers Complete Outage in April; Audit Log Service Also Hit