I never feel like you're trying to navigate a bustling city without a map, especially you know, when it comes to you keeping up with the latest in technology and how it helps businesses run. It's really easy to get lost in all the specialized language, sometimes feeling like you need a secret decoder ring just to follow a conversation. Well, today we're sort of handing you that map. We're taking
a deep dive into IT till four. It's the globally recognized framework that's fundamentally changing how organizations deliver value through the services they offer a day in and day out. We've distilled the insights from Clara A. Gutter's It till four Essentials, which is a fantastic guide, really packed with practical wisdom from a true expert. Our mission today is
to give you a genuine shortcut. We want to extract the most important and sometimes surprising nuggets of knowledge so you can walk away feeling well informed and hopefully ready to tackle your next challenge, whether you're directly in it or not. Think of us as your guides on this journey. Will help you understand not just the what, but crucially the why and the how, making sure you grab the core principles and their powerful real world application. So let's
set the stage a bit. I TELL four isn't just another tech ecronym, right, It's more like a journey from potentially outdated, maybe rigid IT processes to a dynamic system that actually delivers business value. So maybe you can walk us through what I TEL four is at its core and why is it such a game changer even if someone's day to day isn't directly in it.
That's a great way to put it. Actually At its heart, ITEL is considered the best practice framework for IT service management, or ITSM. Now, if you're not an IT, just think of ITSM as the discipline of how an organization thoughtfully designs, delivers, manages, and continuously improves the way it provides all its IT services to its users, to its customers. It's not a prescriptive rulebook telling you exactly what to do step by step, but it's more of a flexible framework that guide you.
It started, interestingly enough, in the UK government back in the nineteen eighties. It's evolved through several versions since then, and then I till four arrived in twenty nineteen. This newest iteration, well, it truly focuses on a value system approach. It's really designed to integrate seamlessly with modern ways of working, things like agile and DevOps, you know, those flexible collaborative approaches focused on speed and continueus delivery. You hear so
much about. The main goal is simply to ensure it services don't just function, but they truly deliver with the business needs precisely when it's needed, and do it efficiently and effectively.
And something often highlighted as a key reason for itel's widespread success is its independence, isn't it. It's vendor neutral, so not tied to anyone's supplier or technology, and non prescriptive, meaning organizations can adopt and adapt the bits that work best for them. Plus crucially, it's built unproven best practices gathered from thousands of ITSM practitioners worldwide. That adaptability means it's suitable for well, basically any organization, any size, any.
Sector exactly, and the source material really emphasizes that point. It makes it a far superior alternative to what's called proprietary knowledge, you know, the kind that often build up within organizations, those unwritten rules or maybe undocumented processes that only a few experienced staff members really know that kind of internal knowledge. It isn't consistently documented, it's rarely challenged or improved upon, and it creates a huge risk if
those key staff members leave. Itilrovides a robust shared language instead.
Yeah, that makes sense, and its impact is kind of everywhere, even if we don't always see it. Think about your own daily reliance on tech, whether you're say, smoothly getting cash man ATM, booking tickets online for a trip, or just relying on your phone for work stuff. Itel is often working behind the scenes there, helping make sure that technology works seamlessly and effectively. It's directly supporting an organization's digital transformation strategies. Without it, you'd likely run into a
far more frustrating glitches and delays than you probably already do. So, okay, if IDLE four is all about value, how exactly does it define that concept? Because it seems like it redefines it in quite a fundamental way, moving beyond just the bottom line.
It absolutely does, and this is really crucial to grass. Value in IDLE four isn't just some vague idea floating around. It's precisely defined as the perceived benefits, usefulness, and importance of something. So it's far more than just monetary cost. It encompasses things like saving time, reducing risk, providing peace of mind, or maybe even conveying status. For instance, a new internal IT system might save employees hours each week.
That's time saved, clear value. Or perhaps a robust cybersecurity service prevents a data breach that's massive risk reduction. Service management itself, then is defined as a set of specialized organizational capabilities for enabling value for customers in the form of services.
It's not just an abstract idea that it requires a really deep understanding of the nature of value, who all the stakeholders are, and that's often more people than you think, and how services actually co create that value, not just deliver it.
Co create. That's an interesting term. So value isn't just delivered to consumers exactly, it's actively created with them. That's a core concept here. The book gives a really great example. Imagine you're booking a holiday through a travel agent. You don't just hand over money and say surprise me, right. You need to share your budget, your desired location, activities, you want to do, plan dates, all that vital information The agent then uses other providers hotels, airlines, tour operators
to build that service for you. Together, you co create the value of your trip. But if you, as the consumer withhold key information, or maybe if the agent doesn't truly listen and understand your needs, well the full value just won't be realized. It's definitely a two way street. It requires active participation, clear communication from both sides.
That travel agent analogy makes it so clear. It really highlights that clear communication and active involvement from everyone involved are absolutely key to getting genuine, meaningful value. Are there common missteps or challenges organizations face when trying to actually implement this co creation idea, particularly maybe in a more internal it context.
Well, absolutely, I think the biggest challenge is often just a lack of genuine dialogue, really talking with people, not just at them. Organizations might think they know what their users need based on assumptions or old data, but they don't actively engage them in the design or the improvement process. Or conversely, users might just assume it knows best or just knows what they want, and they fail to clearly
articulate their actual needs and importantly their desired outcomes. What are they trying to achieve bridging that communication gap is just vital. It takes effort.
Right. That whole discussion on co creation really underlines how interconnected everything is. You can't just operate in the silo, can you? So how does ITEL four make sure we're looking at the whole picture, the whole ecosystem. This is where it's four dimensions of service management come in. Isn't it sounds like it helps manage all that complexity.
It definitely does, And this is where IEL four really pushes for a holistic view, you know, recognizing that no single service or process or team stands alone. It helps us answer that critical question, how do we ensure quality and efficiency across the board without missing anything vital that by considering the four dimensions of service management. These are organizations and people, which is all about the structure of the culture, of the skills, the competencies of the people involved.
Then there's information in technology, covering the knowledge, the data, the actual tech infrastructure itself. Also partners and suppliers which encompasses all those external relationships vendors, collaborators, service providers, and finally, value streams and processes, which details how work actually flows. Step by step to create value for the customer. These dimensions are deeply interconnected, They influence each other constantly, and
they must all be considered for every service. The source is quite explicit. Neglecting any one of them can lead to reduced value or maybe even no value at all.
And it's not just internal factors either. Even things completely outside the organization can shape these dimensions, things we might not even think about at first.
That's absolutely right. These dimensions are heavily influenced by external factors. A useful way to think about these is using the pestal framework. It's a common business analysis tool. It stands for political, economic, social, technological, environmental and legal influences. So, for instance, new data privacy laws that's a legal factor might severely limit where an organization is allowed to store
customer information. That directly impacts the information and technology dimension, and it could potentially require different strategies for the partners in suppliers dimension, especially if they use cloud providers based in certain locations. These external forces are constantly shifting and organizations really need to be acutely aware of their potential impact. It makes you realize how many sort of unseen forces are constantly shaping the services we use every day.
Okay, so we've talked about these individual pieces value cocreation, the four dimensions. How does EITEL four bring all of this together into a cohesive, actionable strategy That sounds like where the service value system or SPS comes in. That's the overarching blueprint right Precisely.
The SVS is essentially the grand blueprint. The definition is a model representing how all the components and activities of an organization work together to facilitate value creation. Its core purpose really is to combat silos. You know, those notorious departmental walls that so often hinder organizations, making them less agile, less resilient. Silos limit effective communication, they prevent a shared vision.
A siloed organization, for example, will almost always struggle to act quickly, or optimize resources effectively, or make good holistic decisions because information just isn't flowing freely. The STS actively tries to foster flexibility and a shared vision. It's meant to be more than just a pretty diagram on a slide.
Okay, so what makes up this SVS.
Well, the SVS itself is comprised of several key elements working together. You've got the guiding principles which act as fundamental recommendations for all circumstances. There's governance, which provides a necessary direction and control for the organization. Then the service value chain. This outlines the six core activities and organization performs to create value, things like planning, engaging with stakeholders, designing, obtaining, building,
delivering and supporting and continually improving. You also have the practices, which are essentially sets of organizational resources like people, processes, tools designed for performing work or accomplishing an objective. There are thirty four of them in Idle four. Continual improvement is embedded throughout ensuring ongoing alignment with changing business needs and overarching all this are the inputs and outputs of opportunity,
demand and value. Opportunity and demand trigger activities within the SVS, and the outcomes should always be value. What's really interesting, I think is the emphasis on the service value chain as a flexible operational model. Is not presented as a rigid, linear pipeline, but rather as a set of core activities that can be configured in many different ways. This allows organizations to create specific value streams, tailored sequences of activities for different types of services or products.
That adaptability sounds absolutely key, especially in today's fast paced digital world. And you mentioned the guiding principles of all those SBS components. These really stand out as practical, actionable advice, don't they. They seem like they're constant no matter what else changes in an organization, like an unwavering compass.
Absolutely, they are fundamental recommendations designed to guide you in all circumstances, doesn't matter if your goals change, your strategy shift, or even if management structures are reorganized. They're also designed specifically to allow different ways of working, like traditional waterfall or more modern agile and DevOps approaches, to integrate effectively
within a single coherent service management approach. The book even suggests quite practically putting up posters of these principles in your workplace just to keep them visible on top of mind for everyone.
Makes sense, Could you maybe walk us through a couple of the key ones.
Sure, let's start with the first one. Focus on value. Now, this sounds obvious, right, who wouldn't focus on value? But the source reveals how often organizations actually miss this in practice. They get bogged down in internal metrics or technical details that don't actually resonate with customer needs or perception. For instance, an IT team might proudly report on achieving ninety nine
point nine percent system uptime. Great number, but if the one system critical to a customer's peak sales period goes down during that point one percent downtime, the customer's perception of value just tanks, regardless of the overall uptime stat So it's about deeply understanding the customer experience CX, that's the overall journey and perception a customer has when interacting with your service, and also the user Experience UX, which focuses more on how easy and pleasant it is for
an individual user to interact with a specific product or system. It means constantly asking what truly moves the needle for a customer, what outcomes are they trying to achieve, not just focusing on what we think they want or was easy for us to measure.
That's so crucial. It really challenges us to look beyond our own internal metrics and truly understand their perspective, their experience, their desired outcomes exactly.
Then there's another really powerful one, Start where you are. This principle tells us do not start over without first considering what is already available to be leveraged. Basically, revolution is off often far more disruptive, expensive, and wasteful than evolution. Before making any big change, especially introducing something new, you need to objectively assess what already exists, what tools, processes, skills can be reused or adapted, use measurements, gather data
to really analyze your current state accurately. Don't just rely on assumptions the source share some cautionary tales of companies that spend absolute fortunes on brand new systems, only to find out later their existing infrastructure could have been adapted for a fraction of the cost and effort. It reminds me of that famous Henry Ford quote. If I had asked people what they wanted, they would have said faster horses.
It's a powerful reminder not to reinvent the wheel unnecessarily and to build smartly on existing strengths.
Right, don't throw the baby out with the bathwater, so to speak.
Assess first, precisely, and finally, let's touch on a principle that often sparks a lot of discussion. Optimize and thought a mate. This is where many organizations tend to jump a gun. The source makes a really powerful, almost counterintuitive point here, do not automate chaos. Think of it like this. If your current manual process is a tangled mess of red tape, unnecessary steps, and bottlenecks, what happens if you
just automate it as is? Well, all you're doing is creating a faster, perhaps more efficient, but still fundamentally tangled mess. You absolutely have to optimize first. That means making the process as effective, streamlined, and useful as it needs to be before you even think about automation. The book shares examples of companies that eagerly automated inefficient workflows, only to amplify the existing problems and frustrate users even more because
the bad process just happened faster. You really need to simplify, clarify, and improve the process before automating. Otherwise you risk just well automating an unclear, inefficient mess. As the old it Joe goes, if you automate a mess, you just get an automated mess faster.
That's such a vital distinction optimize then automate. It really highlights that these principles aren't just slogans. They're like a set of wise practical guidelines for almost any project or decision. They help you navigate complexity and where you're always aiming for the best, most efficient outcome, not just the fastest or shiniest solution. Okay, Now, something else significant in ITEL four is the shift in language from processes to practices.
That sounds like a big deal, doesn't. It seems to signal and move away from potential bureaucracy towards something maybe more agile and adaptable. What are the practical implications of that change for organizations?
It certainly is a significant shift, and it raises an important question why the change. Well. Previous ITOL versions maybe V three in particular, sometimes face criticism for being perceived as too rigid or overly processed driven. In some cases, this could potentially imped flow, especially in fast moving, agile environments where flexibility is key. So IDLE four moves beyond just focusing on rigid, step by step process workflows to
embrace a broader, practice based perspective. What this means is that for each of the thirty four IT tool practices, which are categorized into general management, service management, or technical management practices, you're encouraged to consider all Ford dimensions we talked about earlier, So not just the procedures or workflows, but also the people involve, the teams, the culture, the necessary information, the technology that suppliers, the metrics, the interfaces
between practices. Processes are still incredibly relevant. They haven't disappeared, but they are now viewed as just one part of this wider, more holistic, and ultimately more adaptable practice view. It gives organizations much more flexibility to tailor how they actually work.
Okay, so the processes are still there. They're still important, but they're now embedded within this bigger picture, allowing for more flexibility and maybe less of that kind of bureaucratic hurdle that can sometimes actually slow things down.
Exactly. That's a great way to summarize it. The source material even uses a compelling scar tissue analogy. It describes how organizations often react to failures by adding more layers of complex checks, approvals, and controls to processes. Ironically, this can make the process so cumbersome that employees eventually just find ways to work around it, entirely defeating the purpose.
This shift to practices encourages us to keep things simple and practical, to ensure we have just enough processed the right amount to ensure consistency and quality, but not so much that it stifles speed and agility. One vital practice that the book really highlights is continual improvement. It gets quite an in depth study emphasizing that improvement isn't just a one off project you do occasionally. It's an ongoing,
organization wide activity embedded in everyone's role. It involves systematically documenting, assessing, and prioritizing improvement ideas, often using something like a Continual Improvement Register or CIR, and then using various methods like lean, agile or DevOps improvement techniques to implement those enhancements continuously. And just one more key lesson this one from the measurement and reporting practice is the concept of good Heart's law.
Have you heard of that good Heart's law? No? I don't think so.
What's that?
It basically states when a measure becomes a target, it ceases to be a good measure. Think about it. Once everyone knows a specific metric is being used for performance targets or bonuses, people inevitably start optimizing their behavior to hit that specific number, sometimes even gaming the system, even if doing so doesn't actually lead to the originally intended
outcome or improvement. It's a crucial reminder to ensure our metrics truly drive the desired behaviors and outcomes, rather than just becoming a box taking exercise or a target to be manipulated.
Wow, that's a fascinating point. When a measure becomes a target, it stops being a good measure. That makes you really think about KPIs and metrics, doesn't it. This whole evolution really shows that ITEL is arguably more relevant than ever. It offers a flexible form work that genuinely helps organizations respond quickly and effectively to change and foster a culture where efficiency, collaboration, and that crucial continuous learning are paramount.
We've certainly covered a lot of ground today in this deep dive into it TEL four. It's clear how comprehensive yet adaptable this framework really is. We've journeyed from its origins and core concepts like value and cocreation, explored those four essential dimensions of service management, and understood the unifying
service value system. The practical wisdom of those guarding principles like focus on values, start where you are, and the critical optimize then automate and we grasp that crucial shift from rigid processes to a more holistic, flexible practice approach.
Hopefully you listening in now have a much clearer picture of how IDOL four can help pretty much any organization deliver better, more efficient services and foster that vital culture of continuous improvement, giving you that well informed edge we talked about.
Absolutely So maybe for you, our listener, here's a thought to chew on as you go about your week. If I TIL four really champions this idea of co creation of value and collaboration across silos, what's maybe just one area in your own work or your own team we're inviting a new, perhaps unexpected perspective, maybe from a different department or even the customer, could potentially unlock entirely new value that's currently hidden. Something to think about.