IT Strategy and Business Alignment
From business strategy to IT strategy
IT strategy should be derived from, and traceable to, the organisation's business strategy. The chain runs: business objectives → IT capabilities required → IT initiatives and investments → measurable outcomes. Candidates must understand strategic alignment as a two-way relationship: IT enables business change, and business priorities shape IT investment.
Concepts to name in answers
- Business-IT alignment maturity: from ad hoc to optimised, with governance, communication, competency and partnership dimensions.
- Enterprise architecture: the bridge between strategy and execution, describing business, data, application and technology layers.
- IT portfolio management: balancing run-the-business, grow-the-business and transform-the-business investment.
- Value streams and capability mapping: linking what the business needs to what IT provides.
- Demand management: ensuring the pipeline of IT work reflects strategic priorities, not the loudest voice.
- Benefits realisation: defining expected benefits and measuring them after delivery.
Traps to watch
- Treating IT strategy as a technology roadmap. A roadmap is an output; the strategy explains why.
- Assuming alignment means the business approves the IT plan. Alignment is continuous and reciprocal.
- Confusing enterprise architecture with solution architecture; EA spans the whole organisation.
- Ignoring shadow IT and unmanaged demand, which erode strategic control.
- Selecting an answer that maximises IT efficiency when the question is about strategic responsiveness.
Worked example / rule of thumb
A retailer's strategy is to grow online sales by 30%. The IT strategy should trace initiatives (e-commerce platform, inventory integration, analytics) to that objective and define measures (conversion rate, fulfilment time). Rule of thumb: every IT initiative should be traceable upward to a business objective and downward to a measurable benefit. If either link is missing, alignment is weak.