Summary of "Maxpert Webinar – ITIL® Version 5: Was sich wirklich ändert!"

Main ideas & lessons conveyed

ITIL’s origin and evolution

What ITIL 5 changes conceptually

Digital product & service management as the first major new aspect

Many services now depend on digital products, for example:

AI also expands the scope of cloud service management into new quality/approach territory.


Diamond Model lifecycle (8 steps) — detailed flow

The video describes the lifecycle for both products and services as following the same phases/logic:

  1. Discover
    • Identify which products and services are needed in the market.
    • Determine target recipients/customers and what they need.
  2. Design
    • Define specifications for:
      • what the service should look like
      • what the product should look like
      • what the organization ultimately wants to offer
  3. Concept
    • Create and implement what you intend to produce.
    • Use outsourcing when components can’t be built internally (via acquisition/procurement responsibilities).
    • Emphasizes flexibility: building/obtaining can happen in different orders depending on what works.
  4. Acquire
    • Procure/obtain the right services/solutions (including infrastructure/service support).
    • Ensure suppliers align with the organizational approach/methodology.
  5. Build
    • Develop what must be created internally (“build the rest”).
    • Includes integration work (“puzzle pieces”) needed for completeness.
  6. Transition
    • Integrate acquired elements into the operational environment.
    • Ensure seamless quality and smooth delivery to customers.
    • Integrate suppliers so the customer doesn’t experience a visible boundary between provider-supplied and supplier-supplied components.
  7. Operate
    • Ongoing daily responsibility:
      • ensure infrastructure/services/products function within defined parameters.
  8. Deliver
    • Provide and control service according to Service Level Agreements (SLAs) agreed with consumers.
    • Includes Service Request Management:
      • fulfill requests
      • ensure customer comfort and answered questions.
  9. Support
    • Handle deviations/incidents/challenges when things don’t work smoothly.
    • Bring the system back toward normal and re-enter the delivery process as needed.

Note: The speaker repeatedly frames this as lifecycle phases and also stresses “stepping stone” flexibility rather than strict linearity.


How activities were reorganized from ITIL v4 to v5


Value System foundations and governance


AI-native approach in ITIL 5


Certification & modules changes (high-level)


Q&A clarifications (conceptual distinctions)

Operate vs Deliver

What “product” means in ITIL 5

Does ITIL 5 start with products rather than services?

Compatibility with agile vs waterfall

Can ITIL 4 and ITIL 5 coexist?

SAFE / PRINCE2 integration

Transformation module prerequisites


Other updates mentioned


Speakers / sources featured

Presenter / speaker (primary)

Organization mentioned

Source being discussed

Additional frameworks/terms referenced

Examples used

Category ?

Educational


Share this summary


Is the summary off?

If you think the summary is inaccurate, you can reprocess it with the latest model.

Video