I remember sitting in a windowless boardroom back in 2011, surrounded by a team of exhausted IT managers. We were staring at a flowchart that looked more like a blueprint for a nuclear reactor than a service desk manual. One manager, let’s call him Dave, slammed his pen down. “We keep talking about stages,” he said, “but the customer doesn’t care what stage we’re in. They just want the service to work.”

Dave was right. The old way of talking about ITIL encouraged people to think in hand-offs and silos. In today’s world of AI, rapid-fire deployments, and instant customer expectations, that mindset feels a bit like trying to run a marathon in a suit of medieval armor.

If you’ve landed here because you searched for “What are the 5 stages of ITIL?”, you aren’t alone. Thousands of professionals still ask that question. But here’s the shift that matters now: in itil5, the better answer is not five old lifecycle stages. It’s the 5 Components of the ITIL Value System. That’s the model modern teams are actually working with, and it’s far more useful if you’re exploring itil 5 foundation training online live australia or trying to make sense of how ITIL fits a fast-moving environment. [AC-ITIL-EVOLUTION]

What are the “5 Stages” in ITIL 5?

Strictly speaking, itil5 does not organise service management around the old v3 lifecycle stages. So when someone asks about the “5 stages” today, the most practical modern answer is to point them to the 5 Components of the ITIL Value System.

These five components explain how value is created, directed, delivered, and improved across the organisation. They are not a straight line. They work together, often all at once, which is exactly why they make more sense in real-world service environments. [AC-LEGACY-STRUCTURE]

1. Guiding principles
   Think of these as the common-sense rules you come back to when things get messy. Principles such as focusing on value, progressing iteratively, and collaborating help teams make good decisions without waiting for a 200-page manual.
2. Governance
   Governance keeps IT aligned with business priorities. It sets direction, clarifies accountability, and makes sure decisions are not just fast, but sensible.
3. Value chain
   This is the operating model inside the ITIL Value System. It connects activities across the organisation so an opportunity, demand, or idea can be turned into something customers actually value.
4. Management practices
   These are the capabilities teams rely on every day. Incident management, service desk, change enablement, problem management, and many others sit here. In other words, this is where strategy becomes day-to-day action.
5. Continual improvement
   This is not something you save for the end of a project. It runs through everything. Teams using itil5 are always asking: what worked, what slowed us down, and what should we improve next? [AC-ITIL5-COMPONENTS]

The Shift to ITIL 5: Why the “Stages” Question Changed

The problem with the old “stages” mindset is that it encouraged teams to think in neat boxes while customers were living in messy reality. The strategy people planned. The delivery people delivered. The support people cleaned up the fallout. Everyone was busy, but value still got stuck in traffic.

That’s why itil5 moved the conversation away from rigid sequence and toward a holistic Value System. The price of admission in modern IT is speed, visibility, and adaptability. You need a model that works when priorities shift on Tuesday morning, not one that assumes everything can be mapped months in advance.

The Modern Lifecycle View: 8 Activities That Move a Service Forward

If you still want a practical way to picture how a service moves through its life, this is where itil5 becomes much more useful. Instead of relying on outdated v3 stage language, you can think in terms of 8 lifecycle activities:

1. Discover
   What problem are we actually solving? This is where teams explore needs, outcomes, risks, and real user demand.
2. Design
   Here, the solution takes shape. Processes, experience, technology choices, and service requirements are thought through before money and effort are wasted.
3. Acquire
   Not everything needs to be built from scratch. Sometimes the smartest move is to source the right platform, partner, tool, or capability.
4. Build
   This is where ideas become something tangible. Teams configure, develop, test, and prepare the service components for use.
5. Transition
   The service is moved into a live environment in a controlled way. This includes readiness, communication, training, and managing the risk of change.
6. Operate
   Once live, the service has to function reliably. Monitoring, managing events, and maintaining stability all sit here.
7. Deliver
   Deliver is about making sure the service actually reaches the customer in a way that creates value. Not just “it exists,” but “it works for the people paying for it.”
8. Support
   When something breaks, confuses users, or needs attention, support steps in. This is also where a lot of practical insight is gathered for the next round of improvement. [AC-LIFECYCLE-8-ACTIVITIES]

Think of these less like stations on a train line and more like rooms in a busy workplace. You move between them constantly. A support issue might send you back to design. A delivery failure might uncover a problem in acquire. That’s normal, and frankly, it’s far closer to how modern service organisations actually operate.

Does that sound more complex? Maybe on paper. In practice, it’s more human. It reflects how Agile, product, and service teams really work, which is one reason so many professionals are now looking at itil 5 foundation training online live australia to make sense of the shift.

The “Earned Secret”: Why Most Teams Fail the Transition

One client I worked with recently was obsessed with “Process Design.” They had 400-page manuals for every one of the old 5 stages. They were “compliant,” but their customer satisfaction scores were in the basement.

The secret? They were so busy following the process that they forgot the purpose.

The transition to itil5 requires a mindset shift. You have to stop asking “Did we follow the stage?” and start asking “Did we co-create value with the customer?”

If your team is still thinking in outdated lifecycle labels instead of value system components and lifecycle activities, you’re likely experiencing:

• Bottlenecks: Because work gets treated like a hand-off instead of a shared flow of value.
• Friction: Between the people discovering needs, designing services, delivering outcomes, and supporting customers.
• Stagnation: Because continual improvement gets talked about politely instead of built into everyday decisions.

How to Start Ranking for the Future

If you want your IT department to be more than just a “cost center,” you need to bridge the gap. Start by reframing the conversation. Don’t train people to memorise outdated stage labels. Train them to understand the itil5 Value System and how the 8 lifecycle activities show up in real work.

What does that look like in practice?

• Stop the “Hand-off” Culture: Get your support staff involved in discover and design. They know the friction points better than anyone.
• Map Value, Not Department Boundaries: Look at how work flows across the value chain and through the 8 lifecycle activities. You can learn more about getting started with value stream mapping to see where your “hidden” delays are.
• Ask Better Questions: Can your team explain how governance shapes decisions? Do they understand which management practices enable delivery? Can they identify where continual improvement should happen this week, not next quarter?
• Focus on the Human Element: Technology is easy; people are hard. Modern ITSM is about getting your support team obsessed with service.

The Reward: A Practical Path Forward

You don’t need to throw away everything you know about ITIL. What matters is updating the lens. In itil5, the real conversation is about the 5 Components of the ITIL Value System and the 8 lifecycle activities that move a service from idea to outcome.

If you’re ready to stop living in the 2011 “Dave” era and start leading a team that can handle the complexity of 2026, you need a different kind of training. You need something that isn’t just a slide deck and a test, but a real-world application of these concepts.

We’re running our ITIL 5 Foundation – Online Live training specifically for the Australian market. If you’ve been searching for itil 5 foundation training online live australia, this is designed to help you understand the value system, the modern lifecycle activities, and how to use them in your current role.

Check out our upcoming training dates on the HDAA Training Calendar

Final Thoughts: The Long Game

Whether you are looking up the “5 stages of ITIL” for an exam, a team workshop, or a quick sanity check at work, remember this: the framework exists to serve the business, not the other way around.

The modern answer is clearer than most people realise. In itil5, think about the 5 Components of the ITIL Value System. Then think about the 8 lifecycle activities that show how a service actually moves through discovery, design, acquisition, build, transition, operation, delivery, and support.

If your team can answer a few simple questions, you’re on the right track:

• Are we clear on the value we’re trying to create?
• Do our governance decisions support business outcomes?
• Can we see where work is stuck across the lifecycle activities?
• Are we improving continuously, or just talking about it?

That’s the long game. Less nostalgia. More clarity. More value.

For more insights on building high-performing teams, check out our piece on moving from fractured to functional.

Keep improving. Keep delivering. And most importantly, keep focusing on the value. [AC-CLOSING-SUMMARY]