# Start where you are

> Source: Courseiva IT Certification Glossary — https://courseiva.com/glossary/start-where-you-are

## Quick definition

Start where you are is a principle that says you should begin your IT or process improvement journey using what you already have. You do not need to wait for the perfect tool, the newest software, or a complete understanding. This helps you avoid delays and build confidence step by step.

## Simple meaning

Imagine you want to get fit. You might think you need a fancy gym, expensive shoes, and a personal trainer before you start. But the best time to exercise is right now with whatever you have. You can do pushups on your floor, walk around your block, or use a water bottle as a weight. Starting where you are means you do not stall because your situation is not ideal. In IT, learners often feel they need to know everything before they apply for a job or start a project. This principle tells you: use your current computer, your existing knowledge of one programming language, or your basic understanding of networking. Begin there. In IT service management, the phrase comes from the ITIL framework, which encourages organizations to assess their current processes honestly and build improvements from that baseline. You do not need a complete overhaul on day one. You simply need to know where you stand, accept it, and take the first small step. This approach reduces fear of failure, prevents procrastination, and leads to continuous improvement. Over time, small steps done consistently produce major results. In exams, this concept reminds you that you can pass by mastering core topics first, even if advanced concepts feel overwhelming at the start.

## Technical definition

In the context of ITIL 4 and the ITIL continual improvement model, 'start where you are' is the first guiding principle. It is formally defined in the ITIL Foundation syllabus as: 'Do not start from scratch and build something new without considering what is already available. Use what is already in place as the foundation for improvement.' The ITIL guiding principles are universal recommendations that guide organizations in adopting service management practices. Start where you are is specifically linked to the 'continual improvement' practice and the Deming Cycle (Plan-Do-Check-Act). The technical application involves conducting a current state assessment, also known as a baseline measurement. This baseline includes existing processes, roles, technologies, KPIs, and performance data. For example, an IT service desk might have a current average resolution time of 8 hours. Instead of scrapping the entire ticketing system and buying a new one, the team uses that 8-hour baseline to identify bottlenecks, such as slow escalation procedures or outdated knowledge articles. The improvements are then designed to incrementally reduce that time. This principle directly opposes the 'big bang' approach, where an organization tries to implement a completely new system or process all at once. The risks of ignoring this principle include wasted resources, resistance to change from staff who see their work devalued, and loss of historical data that could inform better decisions. In technical implementation, start where you are means leveraging existing investments in infrastructure, such as legacy servers, custom scripts, or network configurations, rather than forcing a full migration. It also encourages measuring current performance using tools like IT monitoring dashboards (e.g., Nagios, Zabbix, SolarWinds) to establish a baseline. Once the baseline is clear, the team applies incremental changes, measures the new output, and compares it to the baseline. This iterative approach is fundamental to DevOps, Agile, and ITIL practices alike. For IT certifications, you must understand that this principle does not mean accepting poor performance indefinitely. It means using current reality as the launchpad, not the destination.

## Real-life example

Think about learning to cook a new dish, like homemade pizza. You watch a video from a professional chef who uses a wood-fired oven, imported Italian flour, and a special pizza stone. You do not have any of those things. If you wait until you buy a wood-fired oven, you might never make pizza. Instead, you start where you are. You have a regular home oven, all-purpose flour, a baking sheet, and some shredded mozzarella. You make your first pizza. The crust is a bit thick, the cheese browns unevenly, but it tastes good. You learn that next time you can heat the baking sheet first, or add a little olive oil to the dough. Each attempt improves. The same principle applies in IT. A junior network administrator might feel intimidated because they do not have a Cisco lab at home. But they probably have a laptop, a free network simulator like Packet Tracer, and access to online documentation. Starting where you are means opening Packet Tracer today, building a simple network with two PCs and a switch, and pinging between them. That small success builds confidence. Over time, they add routers, VLANs, and routing protocols. They do not need a physical rack of equipment to become proficient. The exam boards test this mindset because employers want professionals who can solve problems with available resources, not people who complain about lacking perfect tools.

## Why it matters

In practical IT environments, budgets are limited, timelines are tight, and legacy systems are everywhere. A project that demands a complete rewrite of existing code or a rip-and-replace of network hardware often fails because it ignores the current state. 'Start where you are' matters because it promotes realistic planning. For example, an IT manager trying to move from on-premise email to Microsoft 365 cannot simply delete the old Exchange server on day one. They must assess the current mail flow, user mailbox sizes, integration with Active Directory, and compliance requirements. Starting where you are means documenting the existing setup, identifying dependencies, and planning a phased migration. This reduces downtime and user frustration. For IT professionals, this principle also applies to career growth. A help desk technician wanting to become a cloud engineer might think they need to learn Azure, AWS, Kubernetes, and Terraform all at once. That is overwhelming. Starting where you are means mastering one cloud platform at a time, using the troubleshooting skills they already have as a foundation. They already understand user accounts and permissions from Active Directory; that knowledge transfers to Azure AD. They already understand network basics from supporting VPNs; that helps with virtual networking in the cloud. Organizations that embrace this principle see higher employee morale because staff feel their current contributions are valued, not dismissed. In audits and compliance, starting where you are also means leveraging existing controls before adding new ones, which saves money and reduces complexity.

## Why it matters in exams

The 'start where you are' principle is a core topic in the ITIL 4 Foundation exam, which is a prerequisite for many higher-level IT service management certifications. In the ITIL Foundation syllabus, it is one of the seven guiding principles and appears in the 'Service Value System' section. Exam questions typically present a scenario where a company wants to improve a process, and the correct answer will reflect assessing the current state before making changes. The principle is also relevant in CompTIA Project+ when discussing project initiation and the importance of a current state assessment. In PMP exams, it aligns with the 'planning process group' where you collect requirements and define the baseline. In the Axelos ITIL Managing Professional (MP) modules, especially 'Create, Deliver and Support' and 'Drive Stakeholder Value', the principle is applied to service design and improvement. For the ITIL Foundation exam, question types include multiple-choice where you must select the guiding principle that matches a description. For example: 'A service desk manager wants to improve first-call resolution. What is the first step according to the guiding principles?' The correct answer is 'measure the current first-call resolution rate' which aligns with 'start where you are'. Another common pattern is a 'which one is NOT a guiding principle' question, where three options are actual principles and one is a distractor. Knowing that 'start where you are' is one of them helps eliminate wrong choices. In scenario-based questions, the trap is often a suggestion to completely replace a system without analyzing the current one. Learners who understand this principle will choose the option that recommends a baseline assessment first.

## How it appears in exam questions

Exam questions testing 'start where you are' usually fall into two categories: definition recall and scenario application. For definition recall, you might see: 'Which ITIL guiding principle encourages using existing processes and tools as a foundation for improvement?' The answer is 'start where you are'. Scenario questions are more common. For example: A company wants to improve its incident management process. The current process uses a homegrown ticketing system with limited reporting. The IT manager proposes buying an expensive ITSM tool immediately. According to ITIL best practice, what should the manager do first? The correct answer is 'Assess the current process performance and identify quick wins that can be implemented with the existing tool'. Another pattern involves stakeholders disagreeing. 'The service owner wants to replace the entire knowledge base with a new platform, but the knowledge manager suggests reviewing existing articles first. Which guiding principle supports the knowledge manager's approach?' Answer: start where you are. In the CompTIA Project+ exam, a question might describe a project sponsor wanting to skip the current system analysis phase to save time. The question asks which risk is most likely. The answer is 'the new system may not integrate well with existing data or workflows'. Some questions combine multiple principles. For instance, 'start where you are' is often paired with 'progress iteratively with feedback'. A question might describe a team that first documents their current deployment process (start where you are), then makes small changes (progress iteratively). You need to identify both principles. In advanced ITIL exams like 'Create, Deliver and Support', you may be asked to design an improvement plan and must demonstrate that the first step is to gather baseline metrics like current average time to resolve incidents or current availability percentage. Failing to include this step in your answer would result in a loss of marks.

## Example scenario

A small IT team manages 200 users. Their password reset process is manual: users call the help desk, the technician verifies identity verbally, then resets the password in Active Directory. The average time for this process is 12 minutes. The IT manager wants to implement a self-service password reset (SSPR) tool. The new tool costs $10,000 per year and requires integration with Azure AD. The team is excited but feels pressured to buy the tool immediately. According to 'start where you are', the team should first analyze the current process. They discover that 40% of password reset calls come during lunch breaks, and 70% of users are already verified using a knowledge-based question that could be automated. Instead of buying the full SSPR solution right away, the team implements a simple change: they enable security questions in the phone system so users can verify themselves without speaking to a technician. This reduces the average time to 6 minutes. Later, they deploy a free password reset portal integrated with on-premises Active Directory, which reduces time further to 3 minutes. After gaining confidence and proving the need, they finally invest in the paid SSPR tool. This step-by-step approach saved money in the short term, built user trust, and provided data to justify the larger purchase. In an exam, the correct answer would highlight that the team did not ignore their existing process but used it as a baseline for incremental improvements.

## Common mistakes

- **Mistake:** Thinking 'start where you are' means you should never upgrade tools or processes.
  - Why it is wrong: The principle is about using the current state as a starting point, not as a permanent condition. Improvement is still the goal, but you do not need a perfect foundation to begin.
  - Fix: View it as 'measure first, then improve incrementally', not 'stay as you are forever'.
- **Mistake:** Confusing 'start where you are' with 'do nothing until you have everything'.
  - Why it is wrong: That is the opposite of the principle. Start where you are encourages action with available resources, not waiting for ideal resources.
  - Fix: List what you already have-skills, tools, data-and use them to take one small step today.
- **Mistake:** Assuming 'start where you are' applies only to technology, not people or processes.
  - Why it is wrong: The principle covers all aspects: people's current skills, existing process documentation, and current toolset. Ignoring the human element leads to resistance to change.
  - Fix: When applying the principle, include a skills assessment and a process walkthrough, not just a technology inventory.
- **Mistake:** Believing that 'start where you are' means you should not measure or document anything before starting.
  - Why it is wrong: Accurate measurement of the current state is essential. Without it, you cannot show improvement. The principle requires you to know where you are, not just act blindly.
  - Fix: Always capture at least three baseline metrics before making any change, even a small one.
- **Mistake:** Using 'start where you are' as an excuse to avoid learning new concepts for an exam.
  - Why it is wrong: The principle is about leveraging existing knowledge, but you still need to fill gaps. For example, if you know networking basics, you can start studying security concepts from that foundation, but you must still study the new material.
  - Fix: Map your current knowledge to the exam objectives, identify what you still need to learn, and begin with the topics closest to what you already know.

## Exam trap

{"trap":"A question describes a company that has a broken, inefficient process and asks what the first step should be. The wrong answer options include 'immediately buy a new tool' and 'start where you are by ignoring the problem'. The correct answer is 'assess the current process', but learners often pick 'ignore the problem' because they misinterpret 'start where you are' as acceptance of the mess.","why_learners_choose_it":"Learners sometimes think 'start where you are' means you accept defects and do nothing. They confuse acceptance with assessment. The phrase 'where you are' sounds passive to them.","how_to_avoid_it":"Remember that assessment is an active step. You are not ignoring the problem; you are measuring it. The principle always begins with measuring the current state, not with resignation. Look for keywords like 'measure', 'assess', 'evaluate', 'baseline' in the question stem."}

## Commonly confused with

- **Start where you are vs Focus on value:** Focus on value is about ensuring every improvement directly benefits stakeholders and the customer. Start where you are is about the starting point of that improvement journey. They work together: you assess your current state (start where you are) and then ensure your changes deliver value (focus on value). (Example: If you are improving password reset, start where you are measures current time, focus on value ensures the improvement saves users time, not just IT time.)
- **Start where you are vs Progress iteratively with feedback:** Progress iteratively with feedback describes how you move forward (in small steps with checks), while start where you are describes where you begin. You start where you are, then you progress iteratively. They are complementary, not the same. (Example: You document your current deployment process (start where you are), then make one small change and test it (progress iteratively).)
- **Start where you are vs Keep it simple and practical:** Keep it simple and practical is about avoiding unnecessary complexity in solutions. Start where you are is about avoiding the urge to start from scratch. A simple solution might still require a complete rebuild if the current state is too messy, but start where you are would still recommend a phased approach using existing components where possible. (Example: A simple solution to slow server response might be to upgrade RAM, but start where you are would first check if current memory usage is actually the bottleneck.)

## Step-by-step breakdown

1. **Identify the current state objectively** — Measure existing performance, processes, and resources. Do not assume you know everything. Use data from monitoring tools, surveys, or process walkthroughs. This sets the baseline.
2. **Document what works and what does not** — List strengths (e.g., skilled team, reliable network) and weaknesses (e.g., slow ticket routing, outdated documentation). This prevents you from breaking what already works.
3. **Select one small improvement target** — Based on the gap between current state and goal, choose the smallest change that can deliver a noticeable benefit. For example, reduce ticket assignment time by automating email notification.
4. **Implement the change using existing tools first** — Before buying new software, see if your current tools can support the change. Many ticketing systems have built-in automation that is underused. Using existing tools reduces cost and learning curve.
5. **Measure the result and compare to baseline** — After implementation, measure the same metric you recorded in step one. If ticket assignment time dropped from 20 minutes to 15, you have proof of improvement. This data justifies further changes.

## Practical mini-lesson

In practice, applying 'start where you are' requires honesty and data. As an IT professional, you must resist the urge to propose a complete overhaul because it looks impressive on your resume. Instead, ask: what exactly is the problem right now? For example, if the server team complains about slow deployment, do not automatically suggest Docker and Kubernetes. First, measure how long a deployment takes today, what the failure rate is, and where most delays happen. You might find that 80% of delays come from manual permission approvals, not from the deployment script itself. Starting where you are would mean fixing the approval process first, perhaps by creating a shared group with pre-approved permissions. That change takes two hours and reduces deployment time by 50%. Later, you can introduce version control for scripts, then containerization. What can go wrong? The most common pitfall is that people perceive 'start where you are' as a lack of ambition. Stakeholders might pressure you to 'think big'. As a professional, you need to explain that big results come from small, steady improvements built on a solid baseline. Another risk is incomplete measurement. If you do not have reliable monitoring, you might think the current state is fine when it is actually failing. Always verify your baseline with at least two data points. For exam purposes, remember that this principle is not just for ITIL. It appears in continuous improvement frameworks like Lean and Six Sigma, where it is called 'meeting the customer where they are' or 'current state analysis'. In DevOps, it aligns with the concept of 'measuring everything' to know your flow. When you study for certifications, practice by taking any process you know-like troubleshooting a network issue-and write down the current steps you actually take. Then ask: how could I improve the first step without changing the whole process? That exercise builds the mindset that exam questions test.

## Memory tip

Map: Measure, Assess, Plan. First two letters of each word are MA-P. Start with a MAp of where you are before you travel.

## FAQ

**Can 'start where you are' be applied to studying for a certification?**

Yes. Assess your current knowledge gaps first, then begin studying topics you are weakest in, but using resources you already have like free videos or existing books.

**Does 'start where you are' mean I should never buy new software?**

No. It means you should first evaluate if your existing software can be improved before purchasing. If the current tool cannot meet the requirement, then buying is justified.

**Is this principle only for ITIL?**

No. It is also used in Lean, Agile, DevOps, and project management. Any improvement effort benefits from understanding the current state before making changes.

**What is the biggest mistake when applying this principle?**

Failing to accurately measure the current state. If you guess instead of measure, you will not know if your change actually improved anything.

**How does this principle relate to the Deming Cycle?**

The 'Plan' phase of PDCA includes understanding the current state. Start where you are provides the baseline data needed to plan meaningful improvements.

**Can I use this principle to plan my career?**

Yes. List your current certifications, job experience, and skills. Then choose the next certification that builds on that foundation, rather than jumping to an advanced topic you are not ready for.

## Summary

Start where you are is a foundational ITIL guiding principle that encourages using the current state as the starting point for any improvement. It prevents wasted resources, reduces resistance to change, and promotes realistic progress. In exams, especially ITIL Foundation, you must recognize that the first step in any improvement is to assess and measure the current situation. This principle appears in scenario questions where a manager wants to skip analysis and jump to a solution. The correct choice always involves measurement first. For IT professionals, applying this principle means being honest about current performance, leveraging existing investments, and building improvements incrementally. It is not an excuse to stay stagnant; it is a strategy for sustainable, evidence-based growth. Remember the memory hook 'MAP': Measure, Assess, then Plan. Keep this in mind and you will avoid common traps in exams and in real-world IT projects.

---

Practice questions and the full interactive page: https://courseiva.com/glossary/start-where-you-are