The Meaning of IT - in 2026

What does the IT in ITIL® stand for? The historical answer is “information technology.” ITIL originated as the Information Technology Infrastructure Library, although today ITIL is used as the framework’s name rather than spelled out.

But that simple answer raises a more interesting question: What do we actually mean when we say “IT”?

When I first explored this question in 2012, the concern was that people used the same term to mean different things. That concern still matters. Cloud services, digital products, automation and artificial intelligence have made the boundaries even less obvious.

ITIL (Version 5) brings a broader perspective through digital product and service management. It also gives us a good reason to revisit an old question: When someone says, “That belongs to IT,” does everyone understand the same thing?

One Term, Several Meanings

The following are practical ways people use the term IT in everyday conversations. They are overlapping perspectives, rather than formal ITIL categories.

• IT as technology: The hardware, software, networks and other technical components used to process, store and exchange information. A laptop, operating system or network device fits this perspective.

• IT as information systems: The connected technologies, information and workflows that support organizational activities. A customer relationship management system, for example, supports how people manage customer information and interactions.

• IT as a technology environment: The collection of applications, infrastructure, cloud services, integrations and platforms an organization depends on. That environment may span internal teams and multiple external providers.

• IT as a place: People may still say something is “in IT” when they mean a data center, equipment room or technology support location. With cloud and distributed services, the technology supporting a service may operate across many locations.

• IT as an organizational function: The people and teams responsible for particular technology capabilities. Depending on the organization, this might include development, operations, cybersecurity, architecture, support, data management and other responsibilities.

None of these perspectives tells the whole story. Problems arise when we move between them without realizing it.

“IT owns the system,” for example, might mean that a technology team maintains the platform. Someone else might interpret it as responsibility for the information, business decisions, funding, user experience and every outcome associated with that system. Those are very different expectations.

Where Does the IT Department Begin and End?

There is no single organizational chart that defines an IT department for everyone.

Some organizations bring application development, infrastructure, support, security and digital product teams together. Others distribute those responsibilities across departments, business units and suppliers. A marketing team may administer its own platform. A finance team may manage a cloud application. A product team may include both technical and business specialists.

This creates familiar questions:

• Does ITIL apply to application development when developers report outside the IT department?

• Who is responsible for a service that depends on several internal teams and external providers?

• Who decides whether a technically successful change has improved the user experience?

• Who governs an AI capability purchased by a business unit?

The reporting structure alone cannot answer these questions. We need to understand the work, the decisions, the relationships and the outcomes involved.

What ITIL (Version 5) Adds to the Conversation

ITIL (Version 5) addresses digital product and service management across the organization, connecting strategy and everyday work. Its scope extends beyond the boundaries of a department called IT.

That perspective helps us consider how people contribute throughout the digital product and service lifecycle. Understanding a need, designing a solution, delivering it, supporting its use and improving it require connected responsibilities.

Value streams help make those connections visible. Following the work from a need to an outcome can reveal handoffs, delays and unclear ownership that an organizational chart does not show.

For example, a customer portal might depend on a product owner, developers, a cloud provider, cybersecurity specialists, a service desk and customer-facing employees. Each contributes something essential. Calling the portal “an IT responsibility” is not enough to explain how those contributions should work together.

Applying ITIL guidance does not require moving everyone into the same department. It requires agreement about how the relevant people and teams will collaborate, make decisions and improve results.

AI Makes Clear Responsibilities Even More Important

Consider a business team introducing an AI assistant through an existing software subscription. The team may see it as a productivity feature. Technology specialists may see an integration to support. Security and privacy teams may see information risks. Users may see a new source of answers they are expected to trust.

Each perspective is useful, but none is sufficient on its own.

Before assuming that “IT will handle it,” the organization needs to clarify who approves its use, who manages access, who evaluates its outputs and who responds when something goes wrong. It also needs to establish whether the capability is producing the intended benefits.

The technology may be new. The need for shared understanding and clear accountability is familiar.

Start with a Better Conversation

If your organization uses the term IT without a shared understanding, try asking a few practical questions:

• When we say IT, do we mean technology, systems, people or a particular department?

• Which digital products and services are we discussing, and who uses them?

• Who is accountable for outcomes, and who contributes to achieving them?

• Where do responsibilities cross team or supplier boundaries?

• Which decisions and handoffs need clearer agreement?

Capture the answers in language people can use. Apply that understanding to service descriptions, responsibilities, working agreements and improvement discussions. Revisit it as the organization changes.

The question I raised in 2012 still holds up: What do we mean by IT? With ITIL (Version 5), we can take that conversation further by connecting technology, people and responsibilities to the value created through digital products and services.

A shared definition will not resolve every challenge. It will give people a clearer place to start.

Explore ITSM Academy’sITIL Foundation training to build a common language for improvement, or visit our All Things ITIL hub for practical guides and information about ITIL (Version 5).