{"id":55,"date":"2026-01-08T10:37:50","date_gmt":"2026-01-08T07:37:50","guid":{"rendered":"https:\/\/ruck.nz\/?p=55"},"modified":"2026-01-08T10:41:32","modified_gmt":"2026-01-08T07:41:32","slug":"3-3","status":"publish","type":"post","link":"https:\/\/ruck.nz\/?p=55","title":{"rendered":"3.2."},"content":{"rendered":"\n

The next guiding principle of ITIL 4 is think and work holistically<\/strong>.<\/p>\n\n\n\n

This principle encourages organisations to consider the whole system rather than focusing on individual parts.<\/p>\n\n\n\n

Services are complex and involve many components, teams, and stakeholders.<\/p>\n\n\n\n

Optimising one part of the system in isolation can create problems elsewhere.<\/p>\n\n\n\n

Thinking holistically helps organisations understand how different elements interact and depend on each other.<\/p>\n\n\n\n

This principle supports better decision-making and more sustainable improvements.<\/p>\n\n\n\n

By considering the entire service, organisations can avoid unintended consequences and improve overall performance.<\/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 explains why local optimisations often backfire in marketplaces<\/strong>.<\/p>\n\n\n\n

a) Local optimisation breaks global value<\/h3>\n\n\n\n

For TakeCars, common mistakes include:<\/p>\n\n\n\n

    \n
  • Optimising supplier payouts \u2192 suppliers happy, customers angry<\/li>\n\n\n\n
  • Optimising refund resistance \u2192 short-term cash, long-term trust loss<\/li>\n\n\n\n
  • Optimising conversion \u2192 support overload later<\/li>\n<\/ul>\n\n\n\n

    ITIL\u2019s warning is clear:<\/p>\n\n\n\n

    \n

    Improving one part in isolation can damage the whole system.<\/p>\n<\/blockquote>\n\n\n\n

    \n\n\n\n

    b) TakeCars is a system, not a set of features<\/h3>\n\n\n\n

    A holistic TakeCars view includes:<\/p>\n\n\n\n

      \n
    • Customer expectations<\/li>\n\n\n\n
    • Supplier behaviour<\/li>\n\n\n\n
    • Support capacity<\/li>\n\n\n\n
    • Legal exposure<\/li>\n\n\n\n
    • Brand trust<\/li>\n\n\n\n
    • Cash flow timing<\/li>\n<\/ul>\n\n\n\n

      Changing any<\/em> one element (e.g. deposits, cancellation rules) affects all others.<\/p>\n\n\n\n

      Good decisions consider second- and third-order effects<\/strong>.<\/p>\n\n\n\n

      \n\n\n\n

      c) Holistic thinking improves strategy, not just ops<\/h3>\n\n\n\n

      Applied well, this principle helps TakeCars:<\/p>\n\n\n\n

        \n
      • Avoid feature-driven roadmaps<\/li>\n\n\n\n
      • Design policies that scale<\/li>\n\n\n\n
      • Balance growth, risk, and trust<\/li>\n\n\n\n
      • Prevent \u201cfix one thing, break two\u201d cycles<\/li>\n<\/ul>\n\n\n\n

        This is leadership-level thinking, not just operational hygiene.<\/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 appears in system-design and optimisation scenarios<\/strong>.<\/p>\n\n\n\n

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

        \u201cThink and work holistically\u201d means:<\/p>\n\n\n\n

          \n
        • Consider the entire service<\/li>\n\n\n\n
        • Understand interdependencies<\/li>\n\n\n\n
        • Avoid siloed optimisation<\/li>\n<\/ul>\n\n\n\n

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

            \n
          • Optimises one area without considering impact \u2192 weak<\/li>\n\n\n\n
          • Considers system-wide effects \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
            • Focus on one team or process<\/li>\n\n\n\n
            • Ignore downstream effects<\/li>\n\n\n\n
            • Treat services as linear and simple<\/li>\n<\/ul>\n\n\n\n

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

                \n
              • Consider multiple components<\/li>\n\n\n\n
              • Acknowledge dependencies<\/li>\n\n\n\n
              • Aim for overall value<\/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
                • Conflicting improvements<\/li>\n\n\n\n
                • Unexpected side effects<\/li>\n\n\n\n
                • Siloed teams<\/li>\n<\/ul>\n\n\n\n

                  The correct answer usually involves:<\/p>\n\n\n\n

                  \n

                  \u201cTaking a holistic view of the service.\u201d<\/p>\n<\/blockquote>\n\n\n\n

                  \n\n\n\n

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

                  Optimising parts does not guarantee optimising the whole.<\/p>\n<\/blockquote>\n\n\n\n

                  Keep this sentence in your head when answering system-level 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 covering the systems-thinking core<\/strong> of ITIL \u2014 an area where exam questions reward maturity of understanding rather than memorisation.<\/p>\n","protected":false},"excerpt":{"rendered":"

                    The next guiding principle of ITIL 4 is think and work holistically. This principle encourages organisations to consider the whole system rather than focusing on individual parts. Services are complex and involve many components, teams, and stakeholders. Optimising one part of the system in isolation can create problems elsewhere. Thinking holistically helps organisations understand how […]<\/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-55","post","type-post","status-publish","format-standard","hentry","category-1"],"_links":{"self":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/55","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=55"}],"version-history":[{"count":2,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/55\/revisions"}],"predecessor-version":[{"id":64,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/55\/revisions\/64"}],"wp:attachment":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=55"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=55"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=55"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}