The IT-Business Alignment Problem: Still Unsolved After 30 Years

In 1993, John Henderson and N. Venkatraman published "Strategic Alignment: Leveraging Information Technology for Transforming Organizations" in the IBM Systems Journal. The paper introduced what became known as the Strategic Alignment Model, and it mapped four domains that needed to work together: business strategy, IT strategy, organizational infrastructure and processes, and IT infrastructure and processes. The argument was that firms create more value when these four domains reinforce each other rather than pulling in different directions. When business strategy is moving one way and IT infrastructure cannot support it, value leaks out of the gap between them.

Thirty years later, this is still one of the most cited frameworks in IS. And "aligning IT with the business" is still consistently among the top concerns in surveys of CIO priorities. The problem that Henderson and Venkatraman named has not been solved. I think it is worth asking why.

Part of the answer is structural. IT planning and business planning run on different timescales. IT projects tend to be long. A major infrastructure investment, an ERP implementation, a platform migration, these take twelve to twenty-four months to complete, often longer. Business strategy, particularly in competitive markets, can pivot in a quarter. The company decides to enter a new market. A competitor launches something unexpected. A regulatory change shifts the compliance requirements. By the time the IT project designed to support the original strategy is delivered, the strategy has moved. The system is technically done. The business no longer needs it in exactly that form.

This is not a failure of project management, though it often gets treated as one. It is a fundamental mismatch between the pace at which IT systems can be built and the pace at which organizational needs change. Henderson and Venkatraman understood this, which is why the model emphasizes ongoing alignment rather than a one-time alignment exercise. The common mistake, as Chan and Reich (2007) noted in their review of alignment research in the Journal of Information Technology, is treating alignment as an event rather than a process. You cannot align IT with the business in a planning cycle and then assume the alignment will persist. The business keeps moving. The alignment requires continuous management.

The language gap makes this harder. IT leaders and business leaders often describe the same organizational reality in completely different vocabularies. The IT leader talks about technical debt, integration complexity, API dependencies, and infrastructure capacity. The business leader talks about market share, customer experience, revenue targets, and competitive positioning. Both are describing real things. They are not naturally speaking the same language, and the translation is not automatic. When an IT organization cannot translate its technical constraints into revenue and risk terms that business leaders understand, the business leader defaults to treating IT as a black box. The black box gets managed on cost rather than on strategic value. Alignment becomes harder because the conversation that would enable it is not happening.

There is a deeper conceptual issue in the model that I find interesting. The alignment frame implicitly treats IT as a follower of business strategy. Business decides where to go; IT figures out how to support it. That was a reasonable assumption in 1993, when business strategy was mostly technology-independent and IT was genuinely a support function. It is a less defensible assumption now. Technology increasingly enables business strategies that would not be possible without it. Amazon's logistics operation is inseparable from the software systems that run it. Google's advertising revenue depends entirely on technology capabilities that did not exist when the company was founded. In these cases, the business strategy and the technology strategy are not separate things that need to be aligned. They co-evolved into something that cannot be cleanly separated.

Bharadwaj, El Sawy, Pavlou, and Venkatraman (2013) made this point explicitly in their MIS Quarterly paper on digital business strategy. They argued that the traditional separation between IT strategy and business strategy has collapsed in digitally-intensive firms. The strategy is digital through and through. You cannot have a business strategy conversation and then separately have an IT strategy conversation. The two are one thing. This is a significant departure from the original SAM framework, and it suggests that alignment, as a concept, may be the wrong frame for the most technology-intensive industries. The relationship is not IT following business. It is both co-evolving, which is a different and harder problem.

That said, for the majority of large organizations that are not technology-native, the original alignment problem is still very much alive. A hospital, a manufacturing company, a government agency, these are not digital-native organizations. Their IT systems support their operations but do not define their core business model. For them, Henderson and Venkatraman's framework is still a useful diagnostic. When IT projects consistently fail to deliver strategic value, when technology investments do not produce the business outcomes that justified them, the alignment model gives a structured way to ask where the gap is. Is the business strategy not clearly communicated to IT? Is the IT strategy not credible to business leaders? Is the organizational infrastructure not set up to support the technology being deployed? Is the IT infrastructure not capable of supporting the business processes it is supposed to enable?

The reason the problem persists is that the answer to "where is the alignment gap" changes constantly. Organizations are not static. Leadership turns over. Strategy pivots. Technology options evolve. Maintaining alignment is a continuous management task, not a project that reaches completion. The organizations that handle it best, by most accounts, are the ones that treat IT-business alignment as an ongoing conversation, not a planning artifact. Shared decision-making bodies, CIOs with genuine strategic authority, and IT leaders who can speak in business terms rather than technical ones. None of that is a technology solution. It is a governance and people solution to what looks like a technology problem.