IT strategy alignment is one of those concepts that everyone agrees is important and most organizations do poorly. The symptom is recognizable: the IT function is busy, productive by its own measures, and increasingly disconnected from the problems the business is actually trying to solve. Projects get completed that do not move business metrics. Capabilities get built that no one uses. Business leaders make strategic decisions without considering technology implications, and technology decisions get made without reference to strategic direction. The 90-day framework I use is designed to break this pattern and build a structural connection that sustains itself.
Days 1-30: Listen Before Planning
The first thirty days are entirely diagnostic. Interview every business unit leader. Not about IT — about their business. What are they trying to achieve? What is preventing them from achieving it? Where do they feel their operations are exposed? What competitive pressures are they responding to? Listen for the places where technology is enabling them and the places where it is a constraint. Listen particularly for frustrations they have given up expressing because previous conversations with IT went nowhere.
Run a parallel assessment of the current IT portfolio: what projects are in flight, what systems are in operation, and what the IT team is spending its time on. Map this against what you heard in the business interviews. The gaps — IT activity with no clear business connection, business problems with no IT support — define the alignment problem.
Days 31-60: Build the Connection
Use the findings from the first phase to create a business-IT alignment map: each strategic business priority linked to the IT capability it requires, the current state of that capability, and the gap between current state and required state. Share this map with business leaders and validate it. This shared artifact — a single picture that both business and IT leadership recognize as accurate — is the foundation for aligned planning.
Days 61-90: Restructure the Conversation
The final phase is about changing how IT and business leadership interact, not just about producing a plan. Establish a cadence of joint business-IT reviews where projects are evaluated and prioritized against business outcomes, not technical merit. Create the mechanism by which new business initiatives trigger IT assessment before commitments are made. Build the habit of IT participation in strategic planning and business participation in technology governance. These structural changes are what make alignment sustainable rather than a one-time exercise.