Episode 13 — Bring Experience and Sustainability Into the Conversation About Value
In this episode, we are expanding the idea of value in a way that helps modern Information Technology Infrastructure Library (I T I L) sound much more realistic and much more human. Many new learners begin by thinking of value mainly in terms of whether a service helps someone get a result, and that is an important starting point, but it is not the whole picture. A digital product or service can help produce an outcome and still create weak overall value if the experience is frustrating, confusing, or exhausting for the people who depend on it. It can also create weak value if it cannot be sustained over time without waste, strain, or decisions that slowly damage trust, resilience, or responsible use of resources. That is why modern service thinking brings experience and sustainability into the conversation about value instead of treating them as optional extras. Once you understand that broader view, you begin to hear value as something lived over time rather than something declared at the moment a service appears to work.
Before we continue, a quick note: this audio course is a companion to our course companion books. The first book is about the exam and provides detailed information on how to pass it best. The second book is a Kindle-only eBook that contains 1,000 flashcards that can be used on your mobile device or Kindle. Check them both out at Cyber Author dot me, in the Bare Metal Study Guides Series.
A good place to begin is with experience, because experience is one of the clearest ways people actually judge whether a service is helping them. A service may exist, be technically available, and even produce the intended outcome in a narrow sense, but the experience can still feel heavy, slow, uncertain, or irritating. When that happens, people often do not describe the service as valuable, even if it technically completed the task. Experience includes how clear the path feels, how much confidence people have while using the service, how easy it is to recover from a problem, and whether the overall interaction supports the person rather than making the work harder than it needs to be. Modern ITIL pays attention to this because services are not consumed as diagrams or technical plans. They are lived as journeys. People remember whether the journey felt dependable, understandable, and respectful of their time and effort, and those lived impressions have a major effect on whether value is actually created.
A simple example makes this easy to picture. Imagine an online student enrollment system that allows learners to register for courses, review schedules, and confirm payment. From one angle, the outcome looks successful if students can eventually complete registration. But if the screens are confusing, the steps are unclear, the error messages make little sense, and support is hard to reach when something goes wrong, then the experience weakens the value of the service even though the final action may still be possible. Some students may complete the process and still come away stressed, unsure, or frustrated enough to avoid self-service options in the future. That is why experience matters. It shapes trust, willingness to use the service again, and the total effort required to get to the outcome. Modern ITIL wants learners to notice that a service is not truly valuable just because it can be forced to work. It is more valuable when people can use it with enough ease and confidence that the path to the result feels worthwhile.
Experience also matters because it influences adoption, and adoption influences whether the service can produce value at scale. A provider may design what seems like a useful service, but if the experience feels confusing or unreliable, people may avoid it, resist it, or create workarounds around it. Those workarounds often increase cost, reduce consistency, and create hidden risks elsewhere in the environment. A service with a poor experience may therefore weaken value in multiple directions at once. It can frustrate the direct user, burden support teams, reduce trust in the provider, and make leaders question whether the investment was worthwhile. By contrast, a service with a strong experience often builds momentum. People are more likely to use it correctly, rely on it with confidence, and give helpful feedback that supports future improvement. This is one reason experience belongs inside the value conversation. It does not only affect satisfaction in a soft or decorative sense. It shapes whether the service becomes a dependable part of how people get work done.
When modern ITIL brings experience into value, it is not asking organizations to chase comfort or style at the expense of discipline. It is asking them to recognize that experience is one of the ways value is felt in real life. A service can be secure, structured, and technically strong while still respecting the user’s time, reducing unnecessary confusion, and making support easier to reach when needed. Experience is not about making everything feel effortless all the time. Some services are naturally complex because the work they support is serious or detailed. But even in those cases, the experience can still be clearer, calmer, and better guided rather than chaotic or needlessly burdensome. This matters because a beginner may hear experience and assume it only refers to attractive design or surface-level convenience. The modern service view is broader than that. Experience includes the emotional and practical reality of relying on a service, and that reality strongly influences whether people see the service as useful, trustworthy, and worth continuing to use.
Sustainability brings a different but equally important dimension into the conversation. In plain language, sustainability is about whether something can continue in a responsible, workable, and healthy way over time instead of delivering short-term benefit while quietly creating longer-term damage or strain. In a service context, this means asking whether the value being created today is being supported in a way that can endure. A service might appear valuable in the short term because it delivers fast results, but if it requires unsustainable effort from staff, constant manual correction, growing technical fragility, or irresponsible use of resources, then the long-term value picture is much weaker. Modern ITIL includes sustainability in value thinking because digital products and services are not meant to exist for one moment only. They are meant to support ongoing outcomes, and that requires decisions that preserve viability, resilience, and responsible stewardship rather than chasing immediate wins without regard for what those wins cost later.
Sustainability can be understood in several connected ways, and all of them matter. It can refer to whether the service can be maintained, supported, improved, and governed without exhausting the people responsible for it. It can refer to whether the service uses resources wisely instead of building avoidable waste into the way it operates. It can refer to whether the design choices made today support long-term reliability and adaptability instead of creating technical debt or operational drag that grows heavier with time. It can also refer to broader organizational and social responsibility, such as avoiding careless use of energy, infrastructure, or supporting practices that damage trust or create unfair burdens elsewhere. The key lesson is that sustainability is not a separate moral lecture attached to service management after the real work is done. It is part of the real work. A service that cannot be sustained responsibly is not creating the kind of durable value modern ITIL wants organizations to pursue.
A strong way to connect sustainability to value is through the idea of balance across time. Earlier lessons have already shown that real value depends on outcomes, costs, and risks. Sustainability adds another layer of maturity by asking whether that balance still works not just today, but later as the service continues to operate and evolve. A service might deliver strong outcomes right now, but if its operating cost is rising uncontrollably, if its support model depends on heroic effort every week, or if its architecture is becoming harder to change safely, the service may be consuming its future in order to look successful in the present. That is not sustainable value. Sustainable value means the service continues to support useful outcomes in a way that remains manageable and responsible over time. It does not require perfection, and it does not mean change is avoided. It means the organization makes decisions with enough long-term awareness that today’s value does not become tomorrow’s burden through neglect, haste, or shortsighted design.
A helpful example might be an internal analytics platform used by managers across a company. The outcome may be better visibility into performance, faster reporting, and quicker decision-making. The experience side asks whether managers can actually find what they need, understand what they are seeing, and trust the platform enough to use it without constant confusion or repeated requests for manual help. The sustainability side asks whether the platform can continue to deliver that value without requiring endless spreadsheet cleanup, emergency fixes, and a small group of exhausted specialists carrying the whole system through personal effort rather than stable design. If the experience is poor, managers may not rely on the platform even if the data exists. If the sustainability is weak, the platform may appear successful for a while and then begin failing under the weight of its own maintenance burden. In both cases, the value story changes significantly once experience and sustainability are included rather than ignored.
Experience and sustainability are also closely linked to trust. People trust a service more when it feels clear, dependable, and well supported, and they trust it less when the path through it feels unpredictable or burdensome. They also trust it more when they sense that the service is being managed responsibly rather than being held together by hidden strain and short-term improvisation. Trust matters because it affects whether people adopt the service, whether they rely on it during important work, and whether they continue engaging with it when the environment becomes more demanding. A service with weak trust may still technically function, but the value it creates will often be smaller because people do not feel confident enough to depend on it fully. Modern ITIL brings experience and sustainability into the value conversation partly because both of them influence trust. Experience shapes trust in the moment of use, while sustainability shapes trust across time, and together they help determine whether the service feels like a dependable part of the larger system or an uncertain burden people tolerate only when they have no better option.
This wider view of value also improves the way organizations make design and improvement decisions. If leaders think only about immediate outcomes, they may be tempted to add features quickly, push work faster, or reduce certain costs in ways that quietly damage the experience or weaken sustainability. If they think more broadly, they start asking better questions. Will this change make the service easier or harder to live with. Will it reduce recurring friction or simply move that friction somewhere less visible. Will it help the service remain stable and supportable, or will it create a heavier long-term burden for teams and stakeholders. Those questions reflect a more mature view of value because they look beyond visible delivery and into the reality of what it takes for a service to keep helping people over time. Modern ITIL encourages this kind of judgment because digital service management is not only about getting something into use. It is about making sure what enters use can remain genuinely valuable rather than becoming a source of hidden waste and frustration.
Another reason experience and sustainability belong together is that poor experience often creates sustainability problems, and poor sustainability often creates experience problems. If users keep getting confused, support volume rises, rework grows, and the service becomes heavier to maintain. If the service depends on unstable structures, manual interventions, or overworked teams, the user experience often degrades through delays, inconsistent responses, and growing uncertainty. In other words, the two ideas reinforce each other across the lifecycle of a service. A better experience can lower support burden, increase adoption, and make value easier to sustain. A more sustainable service can provide steadier support, clearer improvements, and more reliable performance, which improves experience in turn. This connection is important because it helps beginners stop treating these concepts as unrelated add-ons. They are deeply connected dimensions of real value. Modern ITIL wants you to hear that connection, because doing so makes the framework sound much less like a list of separate concerns and much more like one coherent way of thinking about healthy digital service relationships.
For everyday service work, this broader value mindset can be translated into practical questions. How does this service feel to use when people are busy, uncertain, or under pressure. Does the path through it support confidence, or does it create avoidable hesitation and rework. Can this service continue to operate and improve responsibly over time, or is it slowly becoming heavier, riskier, and harder to sustain than it appears on the surface. Those are not advanced questions reserved for senior leaders alone. They are part of good judgment at every level of digital product and service work. A support team noticing repeated confusion is seeing an experience signal. A product owner noticing rising maintenance pain is seeing a sustainability signal. A manager seeing growing dependence on manual rescue effort is seeing a sustainability problem that will eventually affect experience too. Modern ITIL encourages people to notice those signals early because that is how value is protected before frustration, waste, or fragility grows into a much larger problem.
This topic also matters on the exam because answer choices may sometimes sound too narrow if they define value only through direct outcomes or simple delivery. A stronger answer often reflects the broader modern view that value includes how stakeholders experience the service and whether the service can continue supporting outcomes in a responsible and workable way over time. If two options both mention usefulness, the better one may be the one that reflects the lived experience or longer-term viability of the service rather than immediate output alone. This is one of the ways ITIL tests understanding rather than memorization. A learner who sees value only as result delivery may miss the framework’s wider intent. A learner who understands that experience and sustainability both shape real value will be better prepared to recognize the answer that fits the modern mindset being taught throughout the course.
By the end of this lesson, the most important thing to carry forward is that value becomes more accurate and more meaningful when experience and sustainability are part of the conversation. Experience matters because people judge services through real use, through trust, clarity, support, and the overall feeling of depending on the service to get something done. Sustainability matters because value that cannot be maintained responsibly over time is weaker than it first appears, no matter how impressive the short-term outcome may look. Modern ITIL brings both ideas forward because digital products and services exist in relationships, across lifecycles, and inside environments where short-term usefulness is not enough by itself. Once you hear value in this broader way, you begin to understand why modern service management sounds more mature than simple delivery language. It is not only asking whether the service works. It is asking whether the service feels worthwhile to use and whether it can remain worthwhile over time without creating burdens that quietly cancel out the value it first seemed to promise.
