This is not an ITIL exam study guide. It is a translation layer for practitioners who have already been doing the work and need the vocabulary to match what ITIL 4 calls it.

In this episode, Anthony Veltri crosswalks ITIL 4 concepts to real operational patterns you already recognize from service delivery, interface stewardship, and cross-boundary coordination. The goal is simple: close the language gap that creates HR friction and meeting friction, without pretending the work starts with the framework.

You will hear why ITIL 4 is effectively a service federation vocabulary, especially its shift toward value streams, guiding principles, and partner relationships. You will also hear the boundary where ITIL runs out of authority: ITIL assumes you have standing to negotiate service relationships and enforce change control. Federation doctrine covers the terrain where that standing does not exist and never will, because the entities are sovereign and coordination is voluntary.

A key example anchors the lesson: interface failure without fault. Nothing is broken on either side, but the service still fails because the seam had no stewardship agreement, no change notice, and no shared definition of what “working” means across the boundary.

If you have lived this work for years and you are trying to map your instincts to a formal framework, this crosswalk is the bridge.

https://anthonyveltri.com/guide/doctrine-03-companion-itil-4-foundation-a-practitioner-crosswalk/

Sometimes the measurement is correct. The failure is the assumption that the world it was calibrated against is still the world you are living in.

In this field note, Anthony Veltri shows a pattern institutions repeat when measurements conflict with lived reality: first they question the sensor, then they defend the legacy classification, and finally they ignore the anomaly. The better first question is simpler and harder: did the underlying substrate change?

Three stories carry the point. A long trusted ground control point started “drifting,” not because the satellite changed, but because the terrain did. A stable hemlock signal across watersheds degraded over years as the forest itself collapsed. And during Hurricane Katrina, the substrate shifted in hours, with entire neighborhoods physically relocated, making legacy labels meaningless and forcing new anchor points for situational awareness.

The takeaway is practical: when metrics and reality diverge, check the ground before you recalibrate the instrument. Sometimes the system is working and the anomaly is the signal.

Reflection: When your dashboards disagree with the people closest to the work, do you interrogate the sensor first, or do you ask what moved underneath it?

https://anthonyveltri.com/when-the-ground-moves-why-institutions-misread-their-own-sensor-metrics/

• Listen on your podcast app: Search for "The Next Guys" and hit subscribe to get the full serial feed.
• Access the visual archive: Read the text, view the diagrams, or find the physical book at: anthonyveltri.com/thenextguys