The Four Dimensions

The four perspectives every product and service needs — organizations and people, information and technology, partners and suppliers, value streams and processes — and the external factors that shape them.

Why four perspectives?

A few years ago, Kestrel Energy launched a feature in its mobile app that let customers submit their own meter readings with a photo. The development team did excellent work: the app recognized the digits, the application programming interface (API) was fast, the tests were green. Three weeks after go-live the feature was quietly switched off.

What went wrong had nothing to do with the code:

  • The customer contact center had not been told about the feature. Agents could not answer questions about rejected photos, and nobody had decided which team owned those disputes.
  • The image-recognition service came from an external supplier. The contract covered a test volume, not hundreds of thousands of photos at the end of each month, and the bill came as a shock.
  • Readings that failed recognition landed in a shared mailbox. There was no defined path from "photo rejected" to "corrected bill", so customers waited weeks.

The project had looked at one dimension only: technology. ITIL names four, so that a team planning or changing a product or service asks the questions this project forgot. Together they are the four dimensions: four perspectives that each must be considered for a product or service to deliver value. In ITIL (Version 5) they are called the ITIL Four Dimensions of Product and Service Management.

The four dimensions drawn as four quadrants around a product or service in the middle: organizations and people at top left, information and technology at top right, partners and suppliers at bottom left, value streams and processes at bottom right. A dashed frame around everything represents the external factors, PESTLE. Organizations and people culture, roles, skills, structure, leadership Information and technology data, tools, platforms, security, AI sourcing, contracts, integration Partners and suppliers workflows, handovers, procedures, controls Value streams and processes Product or service External factors (PESTLE)
The four dimensions surround every product and service; the external factors surround all of them. The quadrants touch the center on purpose: each dimension shapes the same product.

Organizations and people

The organizations and people dimension covers everyone involved in creating, running and using a product or service, and how they are organized: culture, roles and responsibilities, skills, structure, leadership and communication. Technology does nothing on its own; people decide, build, operate, support and use it.

Questions this dimension asks, in Kestrel terms:

  • Roles: who owns the outage-notification feature once it is live? Who may approve a change to it?
  • Skills: can the network operations center (NOC) staff read the new dashboards? Does the service desk know how to answer questions about it?
  • Structure: do the app team and the billing team talk to each other, or only through tickets?
  • Culture: is it safe to report a mistake? Teams that hide errors fix them later and at higher cost.

AI tools change this dimension too: when a virtual agent answers simple questions, service desk roles shift toward harder cases, and people need new skills, such as checking and correcting what the AI produced.

Information and technology

The information and technology dimension covers the information and knowledge a product or service needs and produces, and the technologies that support it: applications, databases, platforms, networks, cloud services, monitoring and the tools the IT team itself uses.

Typical questions:

  • Data: what information does the billing system hold, who may see it, and how long must it be kept? Customer data falls under privacy law such as the General Data Protection Regulation (GDPR).
  • Tools: which tools record incidents, changes and configuration items? Does the monitoring tool raise a ticket automatically?
  • Platforms: does the app run in the cloud, in the colocation data center, or both? What does that mean for backups and failover?
  • Security: how is the information protected, and how quickly could the service be restored after an attack?

This is also where AI sits as a technology. Study material for ITIL (Version 5) places the ITIL AI Capability Model in this dimension: the kinds of things AI can do for an organization, and how much oversight each needs. The page AI in service management covers that model; the people and process side of AI belongs to the other dimensions.

Partners and suppliers

The partners and suppliers dimension covers the organization's relationships with other organizations involved in designing, building, delivering and supporting its products and services. Almost no organization does everything itself. Kestrel uses a cloud provider for the customer portal, a data center company for colocation of the billing servers, and a telecom carrier for the links between offices.

The central question is what to do yourself and what to buy. Factors that push the decision one way or the other include:

  • Focus: is this something that sets Kestrel apart (its customer app) or a commodity (email, office network links)?
  • Expertise and capacity: does Kestrel have the skills, and enough people, to run it well at 3 a.m.?
  • Cost and risk: what does it cost over several years, and what happens if the supplier fails or raises prices? (See Deployment models on vendor lock-in.)
  • External constraints: regulation can limit where data may be stored or who may handle it.

Buying a service does not remove the responsibility. When the carrier's link goes down, Kestrel's customers still call Kestrel. That is why contracts, shared incident procedures and clear contact points matter, and why services from several suppliers have to be integrated into one working whole. The page Knowledge, supplier and relationship management covers how that is managed day to day.

Value streams and processes

The value streams and processes dimension covers how the parts of the organization work together: which steps turn a demand into value, in what order, with which handovers and controls. A value stream is the end-to-end path for one kind of demand; a process is a defined set of activities within it, with inputs and outputs.

In the meter-reading story, this dimension was the missing path from "photo rejected" to "corrected bill". Questions to ask:

  • What triggers the work, and who picks it up?
  • Where does the work wait, and for whom? (Waiting time is usually much longer than working time.)
  • Which steps could be automated, and which need a person?
  • How do we know the work is finished, and who checks it?

The page The Product and Service Lifecycle explains value streams and how to map them.

External factors and PESTLE

All four dimensions are shaped by forces the organization does not control. ITIL groups them with PESTLE: political, economic, social, technological, legal and environmental factors. PESTLE is a general strategy tool, not invented by ITIL; it is a checklist so that nothing important in the outside world is overlooked.

Factor What it covers Kestrel example
Political Government policy and priorities A government energy price cap that must appear on every bill from the first of next month
Economic Interest rates, inflation, the state of the market Higher interest rates make large investments costlier and more customers fall behind on payments, so payment plans in the app become urgent
Social How people live, work and expect to be served Staff work from home three days a week; customers expect to arrange everything in the app, outside office hours
Technological New and changing technology Moving the customer portal to the cloud; AI assistants that answer billing questions
Legal Laws and regulation in force Energy regulation on billing and switching suppliers; as an energy company, Kestrel falls under cybersecurity rules such as NIS2 (the EU directive on network and information security) (in the Netherlands: the Cyberbeveiligingswet), with duties to manage risk and report serious incidents
Environmental Climate, energy use, sustainability Reporting the energy use of its own data centers; choosing a cloud region that runs on renewable power

The difference between political and legal is timing: political factors are the direction government is taking, legal factors are the rules that already apply. A political debate about price caps today can become a legal obligation, with a deadline, next year.

Each factor can touch every dimension. A new reporting duty under a cybersecurity law needs people (who reports, with what training), information and technology (logs that show what happened), partners (suppliers must report to Kestrel quickly) and processes (a defined path from incident to notification).

Thinking holistically

The four dimensions are not four separate checklists to tick off by four separate teams. Their value is in showing how a decision in one changes the others. Moving the billing system from the colocation data center to the cloud (information and technology) changes the supplier contracts (partners and suppliers), the skills the operations team needs (organizations and people) and how a change gets deployed (value streams and processes).

Neglecting one dimension does not make its questions go away; it only means they are answered by accident, often during an outage. This connects directly to the guiding principle Think and work holistically.

A simple way to use the dimensions in practice:

  1. Write the planned change or new service at the top of a page.
  2. Under four headings, list what it needs and what it changes in each dimension.
  3. Run through the six PESTLE factors and note anything that could force a change of plan.
  4. Give every open question an owner before work starts.