Certified: The ITIL Foundation Version 5 Audio Course

In this episode, we take up one of the most grounded and surprisingly powerful ideas in Information Technology Infrastructure Library (I T I L), a principle that sounds modest on first hearing but can completely change how improvement work is approached. New learners often assume progress begins with replacement, as if better service must always come from throwing out the current state and starting over with something new, cleaner, and more exciting. That assumption feels natural because frustration creates impatience, and impatience often makes the present state look worthless even when parts of it still carry real value. The principle of starting where you are pushes back against that impulse and asks for a more disciplined kind of thinking. It reminds you to understand the current environment before redesigning it, because improvement is far more effective when it builds on what already works instead of destroying useful strengths in the name of change. Once you hear the principle in real service situations, it becomes clear that it is not cautious for the sake of being cautious. It is practical, respectful of reality, and deeply connected to creating value without wasting effort.

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.

At its core, start where you are means do not ignore the current state simply because it is imperfect, old, or frustrating. The principle asks you to observe, assess, and understand what exists right now before deciding what should be changed, removed, preserved, or expanded. That does not mean the current service is already good enough, and it does not mean organizations should cling to familiar ways of working forever. It means the present state contains information, capability, relationships, and working elements that deserve attention before reinvention begins. Some parts of the current service may already support users well, even if other parts cause real pain. Some processes may look old on the surface but quietly contain hard won lessons about what users need, what dependencies exist, and what kinds of change create confusion. Starting where you are is really a discipline of seeing clearly before acting boldly. It protects organizations from confusing dissatisfaction with understanding, which is a mistake that leads to a great deal of waste.

One reason this principle matters so much is that reinvention often feels more attractive than careful assessment. New systems sound impressive, transformation language creates energy, and leaders may feel pressure to show visible action rather than patient investigation. Teams can also become emotionally tired of current pain and start to believe that anything new must be better than what they already have. Yet this is exactly when disciplined service thinking matters most, because strong feelings about the current state can distort judgment. An organization may replace a platform when the deeper problem was unclear ownership, weak communication, or poorly designed workflows. It may launch a complete redesign when users really needed a smaller number of targeted improvements in navigation, timing, or confirmation messages. Reinvention can sometimes be necessary, but when it becomes the default response, the organization starts mistaking drama for progress. The ITIL principle helps counter that by saying, in effect, do not let frustration erase your ability to see what is already valuable, functional, or worth learning from before you begin changing things.

Imagine a community college that wants to improve its digital student portal because registration periods create stress, support requests spike every semester, and many students say they do not know which deadlines matter most. Leaders are under pressure to act because the portal affects student trust, staff workload, and the college’s overall reputation for being organized and supportive. One group argues that the entire platform is outdated and should be replaced as quickly as possible with a modern all in one experience. Another group believes the main problem is not the platform itself but the way information is spread across departments, the way reminders are triggered, and the way students are told what to do next. Both groups may have part of the truth, but the principle of starting where you are tells the college not to jump straight into a full rebuild simply because the current experience feels messy. It asks the college to understand what students are actually struggling with, what staff are doing repeatedly, what parts of the portal already work reliably, and what the real sources of confusion are before a decision as large as replacement is made.

That first stage of understanding is much more than a quick review or a collection of opinions from the loudest voices. Starting where you are means looking at the current service honestly and from multiple angles so that improvement work begins with evidence rather than assumption. The college would need to examine how students move through registration, where they pause, what information they miss, which support questions repeat, how advisors work around gaps, and which parts of the portal perform consistently without creating trouble. It would also need to understand the human side of the experience, because a frustrating service journey is often shaped by communication habits, role confusion, training gaps, or policy complexity rather than by software alone. This kind of assessment is not delay disguised as responsibility. It is the foundation of responsible change. Without it, reinvention becomes guesswork wearing a project plan. With it, the organization can begin separating what feels broken from what is actually broken, and that difference matters more than many people realize when improvement pressure is high.

Once the current state is examined carefully, useful strengths often come into view that were invisible when frustration was driving the conversation. The student portal may have a stable login process that students already understand well. The advisor handoff process may be clearer than expected, even if the deadline communication is weak. The reminder engine may function reliably, but the messages it sends may be too vague to help students make good decisions. Support staff may have built effective informal knowledge that helps students recover when they get lost, even though that knowledge has never been organized clearly. These are not trivial details. They are valuable building blocks that can reduce cost, shorten learning time, lower risk, and preserve trust during improvement. Starting where you are helps organizations find those strengths before they destroy them by accident. It reminds you that a service is rarely all bad or all good. Real improvement begins when you can tell the difference between the elements that need redesign and the elements that already deserve protection or extension.

This principle also matters because value is not created only by novelty. In service management, value comes from helping people achieve useful outcomes with acceptable cost, manageable risk, and an experience they can trust. If the college replaces the portal with a completely new system that introduces a prettier interface but breaks familiar workflows, confuses staff, and disrupts reliable access during peak registration periods, the service may become less valuable even though it looks more modern. Starting where you are supports value by respecting the fact that the current environment contains not only defects but also stability, habits, capabilities, and trust relationships that users depend on, even if they do not describe them explicitly. A student who complains about deadline confusion may still be relying heavily on the current sign in flow or the predictable location of certain course tasks. A redesign that fixes one pain point while removing several working elements may reduce overall value instead of improving it. This is why the principle is not timid. It is value focused in a very practical way.

A common beginner mistake is to hear the phrase current state and assume it refers only to existing technology. Technology is important, but starting where you are is much broader than looking at software screens or system architecture. The current state also includes people, roles, habits, supplier relationships, unwritten workarounds, communication patterns, training quality, and process flows that shape how the service actually feels in daily life. A portal may appear weak because the interface is cluttered, yet the deeper friction may come from three departments sending contradictory instructions at different times. A support service may seem slow because the tool is old, while the real problem may be unclear ownership and repeated escalation loops. If an organization studies only the technical layer, it may reinvent the wrong thing and preserve the real cause of frustration beneath the new surface. Starting where you are means taking the whole service seriously, not just the most visible technical element. That is one reason the principle aligns so well with thinking and working holistically across the full service experience.

At the same time, the principle does not mean protecting bad systems simply because they are familiar. Starting where you are is not nostalgia, fear of change, or loyalty to outdated decisions. It does not tell you to admire legacy systems for surviving this long, and it does not require you to preserve inefficient work just because people are used to it. The principle asks you to understand before you act, not to avoid action. Sometimes the honest assessment will show that a platform is too brittle, too fragmented, or too poorly aligned with current needs to remain the foundation of the service. Sometimes current processes create so much delay and confusion that a more substantial redesign is justified. Starting where you are still matters in those situations, because even major transformation should be informed by what the organization has learned from the present state. You may choose large scale change, but you will do it with clearer reasoning, stronger evidence, and a better grasp of which current strengths should be carried forward into the future rather than erased.

This principle becomes even more powerful when connected to the other guiding principles around it. Focusing on value helps you decide which parts of the current state matter most to preserve or improve. Progressing iteratively with feedback works naturally with start where you are because it encourages manageable change based on observed reality rather than one giant leap based on optimism. Collaborating and promoting visibility help different groups compare their understanding of the current service so hidden strengths and hidden pain points can surface before design decisions are locked in. Keeping it simple and practical protects the organization from overreacting with large, expensive reinvention when a smaller improvement could create more value with less disruption. Optimizing and automating also become smarter when the organization first understands what is already working and why. If you automate confusion, you simply accelerate confusion. If you optimize a broken flow without questioning it, you may make bad work faster without making the service better.

Consider a second scenario in a neighborhood health clinic that is trying to improve digital appointment booking and patient reminders. Complaints are rising because some patients miss follow up instructions, some reminders arrive at confusing times, and staff still spend hours handling routine phone questions that people thought digital tools would reduce. Under pressure, clinic leaders may be tempted to purchase a whole new patient communication platform and declare that the transformation itself will solve the problem. Yet a careful current state review might show something different. The booking tool may actually handle scheduling fairly well, while the real problems lie in message wording, inconsistent patient preferences, weak handoffs between clinical and administrative teams, and incomplete testing of reminder timing. Starting where you are would help the clinic preserve the stable booking elements, improve the communication logic, clarify staff responsibilities, and adjust the service in targeted ways before committing to full replacement. That approach is not less ambitious than wholesale reinvention. It is simply more intelligent, because it matches the scale of change to the evidence rather than to the emotional appeal of starting fresh.

Another important part of this principle is establishing a clear baseline. If you do not understand the current state in measurable and observable terms, it becomes very hard to tell whether improvement has actually occurred. The college needs to know how many students are contacting support during registration, where they are getting stuck, how often reminders are ignored, and which steps create the most confusion. The clinic needs to know how many missed appointments are tied to reminder failures, which messages generate repeat calls, and where patients lose confidence in the process. Starting where you are means building improvement on a real baseline instead of a general feeling that things need to be better. Without that baseline, any new solution can be praised or criticized based on mood rather than on meaningful evidence. A modern interface might feel like progress while hiding persistent confusion underneath. A smaller targeted change might seem modest while actually reducing friction in the most important part of the service journey. Baselines help separate symbolic change from genuine improvement.

There are several traps that can pull organizations away from this principle. One trap is novelty bias, where new technology feels automatically superior to existing capability whether or not the evidence supports that belief. Another is frustration bias, where repeated pain causes teams to assume every part of the current service must be flawed beyond repair. A third trap is leadership pressure for visible change, where the appearance of transformation becomes more important than the quality of the outcome. There is also the trap of partial analysis, where one department studies its own pain points and then proposes reinvention without understanding the wider service journey. Starting where you are helps resist all of these because it asks for a fuller and more disciplined picture before big decisions are made. That does not guarantee the organization will choose perfectly every time, but it does improve the odds that change will address real needs, preserve real strengths, and avoid wasting effort on replacing things that were never the true problem in the first place.

For learners preparing to think clearly about service management, this principle is valuable because it teaches restraint without passivity and realism without pessimism. It reminds you that good service decisions begin with understanding the present, not with escaping it. In real organizations, the most responsible form of improvement is often not the most dramatic one. It is the one that studies the current experience carefully, respects working strengths, identifies genuine causes of friction, and then changes what needs changing at the right scale. That can mean targeted improvement, phased redesign, or even major transformation, but whatever path is chosen, it is grounded in the current reality rather than in the fantasy that starting over automatically creates value. Once you understand the principle that way, it becomes easier to hear why it belongs so centrally in ITIL. Services improve more reliably when organizations learn from what already exists before trying to invent something entirely new.

By the end of this discussion, start where you are should feel like a practical discipline for better judgment rather than a conservative excuse to keep old systems alive. It tells you to examine the current state honestly, identify what already works, understand where real friction comes from, and build improvement on evidence rather than on impatience. It respects the fact that value can already exist inside an imperfect service, and that careless reinvention can destroy strengths users depend on even while promising progress. At the same time, it leaves room for significant change when the evidence truly supports it. The real lesson is not keep everything or replace everything. The real lesson is understand everything well enough to know which parts deserve preservation, which parts need refinement, and which parts should finally be left behind. That is the kind of thinking that turns improvement into a disciplined value creating activity instead of a cycle of expensive reaction, and it is exactly why this principle matters so much in modern digital product and service work.