McFarlan Strategic Grid

1. What Is McFarlan Strategic Grid?

McFarlan Strategic Grid is an information technology portfolio framework used to assess how important IT is to a business today and how important it is likely to become in the future. In plain terms, it helps leaders distinguish between systems that mainly keep the lights on, systems that can reshape competition, and systems that do both.

Consultants and CIOs use the grid to support decisions about IT investment, governance, resilience, architecture, and innovation. Rather than treating all technology spending as one undifferentiated bucket, the framework forces a more useful question: where does the business need stability, where does it need speed, and where does it need both? In practice, it often becomes a starting point for broader technology consulting when leadership needs to align risk, spending, and ambition.

It is best thought of as a decision-making tool for IT strategy and enterprise architecture, not a mechanical scoring model. Its value comes from structured discussion and clearer choices, especially when different applications or business capabilities require different management approaches.

2. Origin and Background

McFarlan Strategic Grid is associated with F. Warren McFarlan of Harvard Business School and has been in use since at least the early 1980s. It was widely popularized through McFarlan’s 1984 Harvard Business Review article, “Information Technology Changes the Way You Compete,” and through subsequent teaching and information-systems strategy literature.

The framework was created to solve a practical management problem: senior executives were beginning to realize that IT did not play the same role in every business, or even in every part of the same business. Some companies depended on technology primarily for efficient operations, while others were using it to change products, channels, and competitive position. The grid gave leaders a simple way to classify that dependence and tailor management attention accordingly.

One reason the framework can seem confusing is that closely related versions appear in the literature. At the enterprise level, the quadrants are often labeled Support, Factory, Turnaround, and Strategic. In application-portfolio usage, similar logic is sometimes expressed as Support, Key Operational, High Potential, and Strategic. The underlying idea is the same: assess current operational dependence and future strategic impact.

3. How McFarlan Strategic Grid Works

The two core questions

The grid is built on two dimensions. First, how much do current systems matter to day-to-day operations? Second, how much could planned or emerging systems affect future strategy, competitive advantage, or business-model change? Plotting those two dimensions creates a two-by-two view of the role technology plays.

This is what makes the framework useful. It does not ask whether IT is “important” in a generic sense. It separates operational criticality from future strategic potential. A company can be highly dependent on IT operationally without using it to differentiate, or it can have modest current dependence but major transformation ambitions.

The four quadrants

What the grid is really telling you

The most important output is not the label itself. It is the management implication behind the label. Support environments can be governed for efficiency. Factory environments require disciplined operations and low tolerance for outages. Turnaround environments justify experimentation and faster decision cycles. Strategic environments need both robust delivery and close business-technology integration.

Used well, the grid becomes a conversation about fit. Are governance processes too heavy for high-potential initiatives? Are mission-critical factory systems being underinvested in because they are not glamorous? Is the company pretending all systems deserve the same architecture standards, funding logic, and talent model? The grid surfaces those mismatches quickly.

4. When to Use McFarlan Strategic Grid

The framework is especially helpful when leadership needs to decide how differently various IT domains should be managed. Common use cases include annual IT planning, digital-investment prioritization, operating-model redesign, post-merger portfolio review, cyber and resilience prioritization, and application modernization. It is useful in both B2B and B2C settings, particularly in organizations with a meaningful installed base of systems and multiple competing technology demands.

It is most powerful when the question is not simply “Should we spend more on IT?” but “What kind of IT management approach do different systems or business capabilities require?” That is where more detailed architecture services often follow, because the grid reveals where platforms, integration patterns, standards, and governance should vary.

The framework works best when the team has at least a basic fact base: business-process dependence on systems, outage impact, revenue or customer exposure, planned digital initiatives, technology debt, and a view of where competitive advantage may come from. It does not require perfect data, but it does require honest judgments from business and technology leaders together.

It is not a good fit when teams want a precise business case for a specific project, a feature-level product prioritization tool, or a detailed application-retirement model. It can also mislead when applied at too high a level. In many modern companies, one business capability may be firmly in Factory mode while another is genuinely Strategic. Treating the entire company as a single dot can hide that reality.

Modern practitioners also use the grid differently than they did decades ago. In the past, it was often used to classify a whole company. Today, it is usually more valuable when applied by business capability, domain, application family, or product line. Digital businesses, platforms, and ecosystem models are simply too mixed for one company-wide label to be very informative.

5. How to Apply McFarlan Strategic Grid: Step-by-Step

1. Clarify the decision and scope. Start with the management decision the analysis is supposed to support. Are you shaping the IT investment plan, defining resilience priorities, segmenting architecture standards, or reviewing an application portfolio after an acquisition? Set the time horizon and define what is in scope: enterprise-wide, by business unit, by capability, or by application domain.

2. Gather the required inputs and data. Collect both quantitative and qualitative inputs. Useful evidence includes outage history, operational dependency, revenue exposure, customer-impact scenarios, regulatory implications, strategic initiatives, competitive moves, planned product launches, and stakeholder interviews. Workshops with business leaders are often as important as system metrics.

3. Define the units of analysis. Decide what you are plotting. In some cases, it is the enterprise or a business unit. In more practical IT work, the better unit is often a business capability, platform, application family, or major program. The rule is simple: use units that can actually be managed differently afterward.

4. Construct the grid. For each unit, assess current operational dependence and future strategic impact on a low-to-high basis. Do not overcomplicate the scoring. A facilitated leadership discussion supported by evidence is usually better than a false-precision model with too many decimals. Plot the items and note the rationale for each placement.

5. Analyze the patterns. Look for clusters and contradictions. Are systems in the Factory quadrant missing resilience investment? Are high-potential initiatives trapped in slow governance? Are supposedly strategic platforms mostly supporting commodity processes? The value comes from the differences across quadrants, not from proving that one quadrant is inherently better than another.

6. Translate insights into management actions. Define what should change by quadrant: funding rules, governance cadence, architecture standards, service levels, delivery methods, sourcing approach, talent profiles, and risk controls. This is where disciplined application portfolio management becomes essential, because the grid should influence concrete investment and lifecycle choices.

7. Test sensitivities and assumptions. Revisit borderline cases and challenge the judgments behind them. What if the strategic initiative fails? What if customer adoption accelerates? What if a regulatory change makes a support system operationally critical? Good teams test alternative scenarios before locking in conclusions.

8. Align stakeholders and iterate. Socialize the draft with the CIO, business sponsors, architecture leaders, operations teams, and finance partners. Expect disagreement. That is healthy. The point is not perfect consensus on labels; it is agreement on the resulting management posture and investment priorities.

6. Example: McFarlan Strategic Grid in Action

The problem

A $900 million industrial equipment manufacturer had grown through acquisition. Its CIO faced three simultaneous demands: stabilize a fragile ERP landscape, modernize plant systems, and fund a new digital service platform for predictive maintenance. Every business unit claimed its systems were strategic, and the annual planning process had become a political exercise.

Why the framework was selected

The leadership team needed a simple way to separate operational criticality from future growth potential. McFarlan Strategic Grid was chosen because it could classify both the current production backbone and the new digital bets without forcing a one-size-fits-all technology strategy.

How the team applied it

The team defined business capabilities as the unit of analysis: order management, plant scheduling, field service, customer self-service, finance, and the new predictive-maintenance offering. They combined outage data, process criticality, customer-impact analysis, and executive interviews on growth priorities. Each capability was then plotted on the grid.

The insights

Order management and plant scheduling fell into Factory: they were operationally critical but not major sources of differentiation. The predictive-maintenance platform was Turnaround moving toward Strategic: currently small, but central to the company’s service-growth thesis. Finance was Support. Field service sat near Strategic because it was already important to uptime and margins, and management expected digital tools to strengthen customer retention.

The actions that followed

The CIO redirected funding away from low-value customization in support functions and increased resilience spending for the factory systems that were repeatedly causing disruptions. The company also launched an enterprise architecture roadmap for the strategic and turnaround domains, defining integration standards, data flows, and platform decisions needed to scale the digital service business. Within one planning cycle, the technology budget was more clearly tied to business logic rather than internal lobbying.

7. Strengths and Limitations

Strengths

• Clarifies different roles of IT. It separates operational dependence from future strategic ambition.
• Improves governance decisions. It helps leaders vary funding, control, and delivery models by quadrant.
• Creates a common language. Business and technology teams can discuss priorities without getting lost in technical detail.
• Surfaces investment mismatches. It reveals where critical systems are underprotected or where noncritical systems are overengineered.
• Works well in workshops. The framework is simple enough for executives to use but rich enough to drive substantive decisions.

Limitations

• It is inherently high level. The grid does not replace detailed business cases, architecture analysis, or delivery planning.
• Placement can be subjective. Different stakeholders may rate the same system differently, especially on future impact.
• It can be too static. A quadrant label may change quickly in fast-moving markets or during major transformation.
• It may hide variation. A whole-company label is often far less useful than a domain-by-domain view.
• It does not solve implementation. Knowing a system is strategic does not tell you how to modernize it successfully.

8. Common Pitfalls and How to Avoid Them

• Using the wrong unit of analysis. Teams often assess the entire company when the real differences sit within functions or application domains. Use business capabilities or major system families when the goal is to drive differentiated action.
• Confusing spend with importance. Expensive systems are not automatically strategic. Focus on operational dependency and future competitive impact, not budget size.
• Letting politics determine placement. Sponsors may lobby to have their systems labeled strategic. Require explicit criteria, cross-functional discussion, and documented rationale.
• Ignoring future uncertainty. Some high-potential initiatives will fail. Stress-test strategic assumptions and consider multiple scenarios before committing major investment.
• Treating the grid as the answer. The framework is a thinking aid, not a complete decision engine. Follow it with architecture, financial, and delivery analysis.
• Stopping at classification. Many teams build the matrix and never change governance, funding, or standards. Define the management implications of each quadrant before the workshop ends.

9. How McFarlan Strategic Grid Relates to Other Frameworks

McFarlan Strategic Grid sits in the middle of the consulting toolkit. It is more strategic than a technical inventory, but more operational than a broad corporate strategy framework. Its main role is to connect business importance with differentiated technology management.

Before the grid

Business capability mapping is often helpful before using the grid, because it defines the units being assessed. If the scope is poorly defined, the grid quickly becomes vague. Industry and customer strategy frameworks can also inform the “future impact” dimension by clarifying where competitive advantage is expected to come from.

Adjacent frameworks

The framework is closely related to application-portfolio matrices that classify systems as Support, Key Operational, High Potential, and Strategic. Those tools use essentially the same logic but are often aimed more explicitly at individual applications. A later board-governance adaptation, sometimes called the Nolan-McFarlan grid, shifts the emphasis toward reliability versus the need for new strategic IT. That version is particularly useful for boards and audit committees, while the original McFarlan framing is often more practical for CIO planning.

After the grid

Once the quadrants are clear, teams typically move to prioritization, roadmap, and modernization frameworks. The grid tells you where different management postures are needed; portfolio rationalization, target architecture, and sequencing tools tell you what to retire, upgrade, rebuild, or accelerate first. In that sense, McFarlan is best used as a framing device early in decision making, not as the last analytical step.

10. Key Takeaways

• McFarlan Strategic Grid helps leaders distinguish current operational dependence on IT from future strategic impact.
• Its four classic quadrants are Support, Factory, Turnaround, and Strategic; in application use, closely related labels include Support, Key Operational, High Potential, and Strategic.
• It is most useful for shaping IT governance, investment priorities, resilience decisions, and architecture posture.
• The framework works best when applied to manageable units such as capabilities, platforms, or application domains, not just the whole enterprise.
• Its biggest strength is clarity; its biggest weakness is oversimplification if teams skip the follow-through analysis.

11. FAQs About McFarlan Strategic Grid

Is McFarlan Strategic Grid still relevant today?

Yes. It remains relevant because executives still need to distinguish between systems that require reliability, systems that enable transformation, and systems that need both. The main change is that modern teams usually apply it at the capability or portfolio level rather than giving the entire company one label.

What is the difference between McFarlan Strategic Grid and the Nolan-McFarlan grid?

McFarlan Strategic Grid focuses on current operational impact and future strategic impact of IT. The Nolan-McFarlan adaptation is more explicitly a board-governance tool, emphasizing the need for reliable IT versus the need for new strategic IT. They are related, but the later version is narrower and more governance-oriented.

Can small or early-stage companies use McFarlan Strategic Grid?

Yes, but they should use it lightly. A smaller company may not need a formal workshop or detailed scoring model; even a simple discussion of which systems are mission critical today and which could matter strategically tomorrow can improve investment choices. The framework becomes more valuable as the application landscape becomes more complex.

How long does it typically take to apply McFarlan Strategic Grid in a real project?

A focused assessment can be done in a few days if the scope is narrow and stakeholders are aligned. For a larger enterprise with multiple business units, it often takes two to six weeks to gather inputs, run workshops, test assumptions, and translate the findings into a practical roadmap.

What data is needed to use McFarlan Strategic Grid?

At minimum, you need a clear view of operational dependency, outage consequences, and the strategic importance of planned initiatives. The analysis improves with application inventories, business-process mapping, customer and revenue exposure, technology debt assessments, and input from both business and IT leaders.