{"id":47,"date":"2026-01-08T10:34:28","date_gmt":"2026-01-08T07:34:28","guid":{"rendered":"https:\/\/ruck.nz\/?p=47"},"modified":"2026-01-08T10:34:28","modified_gmt":"2026-01-08T07:34:28","slug":"2-9","status":"publish","type":"post","link":"https:\/\/ruck.nz\/?p=47","title":{"rendered":"2.9."},"content":{"rendered":"\n

The next guiding principle of ITIL 4 is start where you are<\/strong>.<\/p>\n\n\n\n

This principle encourages organisations to assess their current state before making changes.<\/p>\n\n\n\n

Organisations should not start from scratch without understanding what already exists.<\/p>\n\n\n\n

Existing services, processes, people, and tools should be evaluated and reused where possible.<\/p>\n\n\n\n

Starting where you are helps organisations avoid unnecessary disruption and waste.<\/p>\n\n\n\n

It also allows organisations to build on existing strengths and capabilities.<\/p>\n\n\n\n

This principle supports incremental improvement rather than radical change without context.<\/p>\n\n\n\n

By understanding the current state, organisations can make better decisions about what needs to change.<\/p>\n\n\n\n

\n\n\n\n

2. How this applies to TakeCars<\/strong> (car-rental marketplace)<\/h2>\n\n\n\n

This principle is especially powerful for TakeCars<\/strong>, given its long operational history and accumulated edge cases.<\/p>\n\n\n\n

a) Don\u2019t \u201crebuild\u201d \u2014 evolve<\/h3>\n\n\n\n

For TakeCars, \u201cstart where you are\u201d means:<\/p>\n\n\n\n

    \n
  • Do not throw away existing flows because they are imperfect<\/li>\n\n\n\n
  • Do not assume a greenfield redesign will fix trust issues<\/li>\n\n\n\n
  • Do not ignore tribal knowledge embedded in support decisions<\/li>\n<\/ul>\n\n\n\n

    Your current system encodes years of learned risk management<\/strong>.<\/p>\n\n\n\n

    \n\n\n\n

    b) Existing pain points are signals, not failures<\/h3>\n\n\n\n

    From an ITIL lens:<\/p>\n\n\n\n

      \n
    • Repeated disputes<\/li>\n\n\n\n
    • Manual overrides<\/li>\n\n\n\n
    • Support escalations<\/li>\n<\/ul>\n\n\n\n

      These are not reasons to reset \u2014 they are maps of where value leaks<\/strong>.<\/p>\n\n\n\n

      Example:<\/p>\n\n\n\n

        \n
      • If support frequently overrides deposits \u2192 deposit policy is misaligned with perceived value<\/li>\n\n\n\n
      • If suppliers require constant chasing \u2192 confirmation flow is broken<\/li>\n<\/ul>\n\n\n\n

        ITIL says: observe first, then change.<\/p>\n\n\n\n

        \n\n\n\n

        c) Incremental improvement beats \u201cplatform v2\u201d<\/h3>\n\n\n\n

        Marketplaces die from over-correction.<\/p>\n\n\n\n

        \u201cStart where you are\u201d supports:<\/p>\n\n\n\n

          \n
        • Small changes to handover rules<\/li>\n\n\n\n
        • Progressive supplier automation<\/li>\n\n\n\n
        • Gradual shift from listings to offerings<\/li>\n\n\n\n
        • Controlled experiments, not big bangs<\/li>\n<\/ul>\n\n\n\n

          This is how TakeCars preserves trust while improving flow.<\/p>\n\n\n\n

          \n\n\n\n

          3. Key ideas to read right before the exam<\/strong> (high-yield)<\/h2>\n\n\n\n

          This guiding principle is frequently tested in change and improvement scenarios<\/strong>.<\/p>\n\n\n\n

          Core understanding<\/h3>\n\n\n\n

          \u201cStart where you are\u201d means:<\/p>\n\n\n\n

            \n
          • Assess the current state<\/li>\n\n\n\n
          • Reuse what already works<\/li>\n\n\n\n
          • Avoid unnecessary reinvention<\/li>\n<\/ul>\n\n\n\n

            If an answer:<\/p>\n\n\n\n

              \n
            • Proposes discarding everything \u2192 wrong<\/li>\n\n\n\n
            • Encourages assessment and reuse \u2192 strong<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n

              Exam trap to avoid<\/h3>\n\n\n\n

              Wrong answers often:<\/p>\n\n\n\n

                \n
              • Suggest starting from a blank slate<\/li>\n\n\n\n
              • Promote radical redesign without analysis<\/li>\n\n\n\n
              • Ignore existing capabilities<\/li>\n<\/ul>\n\n\n\n

                Correct answers:<\/p>\n\n\n\n

                  \n
                • Emphasise evaluation<\/li>\n\n\n\n
                • Build on strengths<\/li>\n\n\n\n
                • Support incremental change<\/li>\n<\/ul>\n\n\n\n
                  \n\n\n\n

                  Fast exam shortcut<\/h3>\n\n\n\n

                  If a scenario mentions:<\/p>\n\n\n\n

                    \n
                  • \u201cImplementing ITIL\u201d<\/li>\n\n\n\n
                  • \u201cImproving a service\u201d<\/li>\n\n\n\n
                  • \u201cTransforming operations\u201d<\/li>\n<\/ul>\n\n\n\n

                    The correct answer usually starts with:<\/p>\n\n\n\n

                    \n

                    \u201cAssess the current state first.\u201d<\/p>\n<\/blockquote>\n\n\n\n

                    \n\n\n\n

                    One-line exam anchor<\/h3>\n\n\n\n
                    \n

                    Improvement starts with understanding what already exists.<\/p>\n<\/blockquote>\n\n\n\n

                    Keep this sentence in mind when answering change-related questions.<\/p>\n\n\n\n

                    \n\n\n\n

                    Ready for the next file<\/h2>\n\n\n\n

                    Upload the next SRT when ready.
                    We will continue with the same three-layer structure:<\/p>\n\n\n\n

                      \n
                    1. Exact transcript<\/li>\n\n\n\n
                    2. TakeCars application lens<\/li>\n\n\n\n
                    3. Exam-day compression notes<\/li>\n<\/ol>\n\n\n\n

                      You are now moving through the guiding principles sequence<\/strong>, which is one of the highest scoring sections<\/strong> in the ITIL 4 Foundation exam.<\/p>\n","protected":false},"excerpt":{"rendered":"

                      The next guiding principle of ITIL 4 is start where you are. This principle encourages organisations to assess their current state before making changes. Organisations should not start from scratch without understanding what already exists. Existing services, processes, people, and tools should be evaluated and reused where possible. Starting where you are helps organisations avoid […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-47","post","type-post","status-publish","format-standard","hentry","category-1"],"_links":{"self":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/47","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=47"}],"version-history":[{"count":1,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/47\/revisions"}],"predecessor-version":[{"id":48,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/47\/revisions\/48"}],"wp:attachment":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=47"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=47"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=47"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}