What it means
Start where you are means assessing current services, data, practices, controls, skills, and results before replacing them, while refusing to preserve weak arrangements merely because they already exist.
Why it matters
Ignoring existing capability wastes working assets and lessons, but accepting current-state claims without evidence can institutionalize hidden failure and technical debt.
Practical focus
- Establish a measured current-state baseline using observation, records, user feedback, tests, and operational data.
- Separate reusable capability from obsolete design, undocumented workarounds, and unsupported assumptions.
- Define what must be preserved, improved, retired, or independently verified before the target state is approved.
- Preserve this evidence: Retain approved definitions, decisions, operating records, exceptions, test results, and change history that show how Start Where You Are Principle works over time.
- Exercise this failure scenario: A transformation discards reliable controls and operational knowledge, then recreates the same capability at higher cost and lower resilience.
Common mistakes
- Using Start Where You Are Principle as a label without defining its scope, owner, decision criteria, and expected evidence.
- Treating a diagram, policy, tool screen, or meeting as proof that Start Where You Are Principle operates consistently in real work.
- Optimizing for a one-time review while leaving normal operating decisions, exceptions, and handoffs uncontrolled.
- Testing only the expected path and never rehearsing this failure condition: A transformation discards reliable controls and operational knowledge, then recreates the same capability at higher cost and lower resilience.
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: