Most organisations have a business strategy. Most organisations have an IT department. Most organisations find that the two do not reliably produce the same view of what IT should be doing.
Strategic Alignment is the process that bridges this gap. It translates the organisation’s strategic direction — its goals, its operating model, its sense of how the competitive environment is changing — into a concrete picture of where IT capability needs to go and what investments will take it there.
Let me be clear about what Strategic Alignment is not. It is not a planning exercise that produces a five-year IT strategy document that sits in a drawer. It is not a once-a-year board presentation on technology trends. It is not a CIO writing up their view of the technology landscape and presenting it to executives for endorsement.
Strategic Alignment is a continuous, ongoing conversation between senior business executives and enterprise architects, conducted informally but structured by shared artefacts, that produces two types of output: Business Factors and Business Visions.
Business Factors: the operating rules
Business Factors answer: how does this organisation need to work in relation to IT? The most important type is Principles — substantive statements that genuinely shape planning decisions. A useful Principle has three parts:
Statement
What we do. A concrete, arguable position — not a sentiment. “We prefer standard platforms over custom builds” is a Statement. “We will use appropriate technology” is not.
Rationale
Why we do it. The business or technical reasoning that makes the position defensible when challenged.
Implications
What this means for specific decisions. An architect reviewing an IT Design can read the Implications and determine immediately whether the design complies or deviates. That traceability is what connects strategic intent to delivery decisions.
The test for a useful Principle: Can a reasonable organisation argue against it? If no reasonable organisation would argue against it, it contains no real decision and is trivial. Trivial Principles are worse than useless — they give the illusion of direction while providing none.
Business Visions: the directional plans
Business Visions answer: where is this organisation going and what IT capabilities does it need to get there? The most essential is the Business Capability Model — a structured view of what the organisation can do, not how it does it, heatmapped to show where investment is most urgent. From the Business Capability Model flows a Roadmap: what to build, in what sequence, with what priority.
The Roadmap is not a project plan. It is a direction-setting document. Roadmap entries do not have detailed requirements or confirmed budgets. They have enough information to answer the question “should we fund an initiative in this area?” — and that is all they need.
How to know if it is working
Strategic Alignment is structurally different from the other two Alignment Processes. It is continuous and largely unstructured. You cannot schedule it into quarterly sessions and expect it to work. Enterprise architects who practise it well spend most of their time in conversations, not at their desks. That trust is earned through Initiative Alignment first — through architects demonstrating, project by project, that they add real value.
Two things to measure:
- When IT investment decisions are being made, is the Roadmap in the room? Not as a historical reference — as an active input.
- Ask senior business executives whether they understand what IT is doing and why. If the answers are consistently positive, Strategic Alignment is working. If they are not, no volume of architecture artefacts will compensate.