Here's a pattern every experienced IT person has watched: an organisation buys an excellent new system — best-in-class, properly licensed, competently installed — and the project still fails. Nobody was trained. The team that should run it is understaffed. The supplier contract doesn't cover support hours anyone actually works. The old process was simply lifted onto the new tool, chaos included. ITIL 4 formalises the lesson into its first major model: every service stands on four dimensions, and neglecting any one of them produces exactly this kind of expensive failure.
The four legs of the table
- 1. Organisations and people. Who does the work: staffing, skills, roles, culture, and how decisions get made. The dimension where "we bought the tool but nobody knows how to drive it" lives — and, harder, where culture lives. A monitoring platform in a culture where alerts are routinely ignored is furniture.
- 2. Information and technology. The obvious one — the systems, the data, the infrastructure — but note it's information and technology: the knowledge base, the configuration records, and the data quality matter as much as the servers. A service desk with great software and a rotten knowledge base limps.
- 3. Partners and suppliers. Almost no service is delivered alone anymore: cloud providers, internet carriers, software vendors, outsourced support. This dimension asks the questions people forget until an outage: what exactly did we contract for, who supports what, and does their service level actually underpin the one we promised? (A later post on SLAs digs into that trap.)
- 4. Value streams and processes. How work actually flows from demand to value: the steps, the handoffs, the approvals. The dimension where "our tool is fine but tickets bounce between four teams for a week" lives.
How to actually use the model
The four dimensions earn their keep as a diagnostic checklist. Service struggling? Walk the legs: do we have the right people and skills (1)? Is the technology and its data sound (2)? Are suppliers holding up their end (3)? Is the workflow itself sane (4)? The discipline is valuable precisely because technical people reflexively investigate dimension 2 and stop there — while the majority of real service failures, in most practitioners' honest experience, live in 1, 3, and 4. The tool gets blamed; the missing training, the expired contract, or the seven-step approval loop was the culprit.
Exam tip and real-life tip in one: when any scenario asks "what went wrong here?", identify which dimension was neglected. And when planning anything new — a service, a tool, even a process tweak — spend one minute per dimension asking "what could compromise this from here?" That sixty-second habit is the entire model, applied.
The four dimensions are the static view — what a service stands on. The next two waypoints cover ITIL's dynamic views: the principles that guide decisions, and the value system that turns demand into value. Together they form the skeleton of modern ITIL; everything after is muscle.