ISYS90026 · Concepts In Information Systems
Business-IT Alignment
Business-IT alignment is applying IT in harmony with an organisation's strategy, goals and needs — and the exam-critical point is that it is bidirectional co-design with shared risk, not "IT obeying the business". This chapter is the core of Exam Theme 2: you diagnose a firm's misalignment with Luftman's Strategic Alignment Model (SAM), name the right alignment perspective, and recommend a fix using enablers vs inhibitors. It also covers the IT Value Proposition (identification → conversion → realization), where the lesson is that value almost always leaks at conversion and realization, not at the idea stage.
What this chapter covers
- 011. Defining alignment — co-design, not obedience; shared accountability and joint risk
- 022. IT value: support activity vs strategic component (Blockbuster vs Netflix; Domino's)
- 033. Strategic Alignment Model (SAM) — four domains on a business/IT × strategy/operations grid
- 044. The two SAM links — strategic fit (vertical) and functional integration (horizontal)
- 055. The four perspectives — strategy execution, technology transformation, competitive potential, service level
- 066. Enablers vs inhibitors (Luftman & Brier) — mirror lists topped by senior-executive support
- 077. The twelve components — four boxes of three across the strategic and operational levels
- 088. The IT Value Proposition — identification → conversion → realization + the People-Process-Technology triangle
SAM + perspective + value proposition on an unseen case (Theme 2 essay)
- +4SAM diagnosis: name the four domains (Business Strategy, IT Strategy, Org Infrastructure & Processes, IS Infrastructure & Processes). Hearthstone has a strong Business Strategy (premium personalisation) but no IT Strategy linked to it — IT sits only in the operational corner. The broken link is functional integration at the strategic level (business and IT strategy never connect), with weak strategic fit because the CRM was bought without an IT strategy above it.
- +3Perspective: adopt competitive potential — driver = IT strategy, anchor = business strategy, role of IT = shaper. Hearthstone's personalisation capability should reshape how it competes (as the rival does), not merely execute a fixed plan; it is currently stuck in strategy execution with IT treated as a cost centre.
- +4IT Value Proposition: identification succeeded (they spotted the CRM opportunity). The leak is at conversion (no reskilling, no process redesign, dirty data, so the application never works as intended) and at realization (no measurement of guest value, so benefits are never captured or diagnosed).
- +2Luftman & Brier fix: the case shows the #1 inhibitor — IT and business lack a close relationship (IT never in strategy meetings). Fix it with the mirror enabler: elevate the CIO into senior management, co-design a personalisation roadmap, and share accountability through joint OKRs.
Key terms
- Business-IT alignment
- Applying IT in an appropriate and timely way, in harmony with business strategies, goals and needs — bidirectional co-design with shared accountability and joint risk, not IT simply doing whatever the business asks.
- IT as support vs strategic
- IT can be viewed as a back-office support activity (payroll, email, inventory) or as an essential strategic component that is itself the competitive engine; the value depends on which view managers choose (Blockbuster vs Netflix).
- Strategic Alignment Model (SAM)
- Luftman's framework splitting an organisation into four domains — Business Strategy, IT Strategy, Organisational Infrastructure & Processes, IS Infrastructure & Processes — on a business/IT by strategy/operations grid.
- Strategic fit vs functional integration
- SAM's two links: strategic fit is the vertical strategy-to-infrastructure connection within business or within IT; functional integration is the horizontal business-to-IT connection. True alignment needs both at once.
- Alignment perspectives
- Four routes through the SAM domains, each with a driver and an anchor: strategy execution, technology transformation, competitive potential (IT reshapes strategy), and service level (IT operational excellence).
- Enablers vs inhibitors (Luftman & Brier)
- Mirror-image lists of what helps or harms alignment; the top enabler (senior-executive support / close IT-business relationship) is the exact opposite of the top inhibitor (a distant IT-business relationship).
- Twelve components of alignment
- Four boxes of three detailing what each SAM domain contains — e.g. business scope, distinctive competencies, business governance — split across the strategic and operational levels. Distinct from the six SAMM maturity criteria.
- IT Value Proposition (McKeen & Smith)
- Value is realised in three steps — identification (spot the opportunity), conversion (build it via process redesign and reskilling), realization (capture and MEASURE the value) — underpinned by the People-Process-Technology triangle. Value usually leaks at conversion and realization.
Business-IT Alignment FAQ
Is business-IT alignment just IT doing what the business wants?
No — that is the most common exam trap. Alignment is bidirectional co-design: business needs and technical reality are weighed together with shared accountability and joint risk. IT both supports and helps shape the strategy.
What is the difference between strategic fit and functional integration?
Both are SAM links. Strategic fit is vertical — it connects strategy to infrastructure (within the business side, or within IT). Functional integration is horizontal — it connects the business side to the IT side. Real alignment requires both simultaneously.
Which alignment perspective do exam questions usually want?
Most under-aligned firms are stuck in 'strategy execution' (IT as order-taker). When a case has a strong but untapped IT capability and a stale strategy, the high-value answer is usually 'competitive potential' — letting IT reshape the business strategy rather than just execute it.
Where does the IT Value Proposition usually fail?
Almost never at identification. Value leaks at conversion (no business-process redesign, untrained staff, bad data) and at realization (no measurement or feedback loops). The Target Canada launch is the classic failure of both, made worse by a 'big bang' rollout.
How do I tell the twelve components from the six SAMM criteria?
The twelve components (this chapter) describe WHAT alignment is made of inside each SAM domain. The six SAMM criteria (the next chapter — Communications, Value Measurement, Governance, Partnership, Scope & Architecture, Skills) measure HOW MATURE the alignment is across five levels. Don't cite one for the other's question.
Is this page official or affiliated with the University of Melbourne?
No. This is an independent AskSia study resource for students taking ISYS90026; it is not produced, endorsed by, or affiliated with the University of Melbourne. Always confirm assessment details against the official Canvas subject page and current handbook.
Exam move
Treat Theme 2 as a fixed four-move drill rather than a memory test: diagnose the misalignment with SAM (which domain is strong, which is missing, which link — strategic fit or functional integration — has broken), name the perspective the firm should move to (usually competitive potential or technology transformation), locate where the value leaked using the IT Value Proposition (conversion and realization, not identification), and recommend a fix by turning the #1 Luftman & Brier inhibitor into its mirror enabler. Practise this on short unseen cases and force yourself to pin every claim to a specific case fact while keeping problem, evidence and root cause cleanly separated — that triad is where most marks are won or lost. Finally, keep this chapter's twelve components distinct from the next chapter's six SAMM maturity criteria, because the exam deliberately tests whether you can tell the two models apart.
