{"id":51,"date":"2026-01-08T10:36:21","date_gmt":"2026-01-08T07:36:21","guid":{"rendered":"https:\/\/ruck.nz\/?p=51"},"modified":"2026-01-08T10:36:50","modified_gmt":"2026-01-08T07:36:50","slug":"3-1","status":"publish","type":"post","link":"https:\/\/ruck.nz\/?p=51","title":{"rendered":"3.1."},"content":{"rendered":"\n

The next guiding principle of ITIL 4 is collaborate and promote visibility<\/strong>.<\/p>\n\n\n\n

This principle highlights the importance of working together across teams and stakeholders.<\/p>\n\n\n\n

Collaboration helps organisations break down silos and improve communication.<\/p>\n\n\n\n

Promoting visibility means making work, progress, and information visible to everyone involved.<\/p>\n\n\n\n

When people can see what is happening, they can make better decisions and identify issues earlier.<\/p>\n\n\n\n

Transparency builds trust and supports more effective collaboration.<\/p>\n\n\n\n

This principle applies both within the organisation and with external partners and stakeholders.<\/p>\n\n\n\n

By collaborating and promoting visibility, organisations can improve outcomes and reduce misunderstandings.<\/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 directly addresses one of the hardest marketplace problems: hidden information<\/strong>.<\/p>\n\n\n\n

a) Marketplaces fail in the dark<\/h3>\n\n\n\n

For TakeCars, lack of visibility causes:<\/p>\n\n\n\n

    \n
  • Customer anxiety (\u201cIs the car confirmed?\u201d)<\/li>\n\n\n\n
  • Supplier frustration (\u201cWhat did the customer agree to?\u201d)<\/li>\n\n\n\n
  • Support overload (\u201cWhat actually happened?\u201d)<\/li>\n<\/ul>\n\n\n\n

    ITIL\u2019s answer is explicit: make work and status visible<\/strong>.<\/p>\n\n\n\n

    \n\n\n\n

    b) Collaboration across all three sides<\/h3>\n\n\n\n

    \u201cCollaborate\u201d here is not just internal.<\/p>\n\n\n\n

    For TakeCars it means:<\/p>\n\n\n\n

      \n
    • Customer \u2194 TakeCars \u2194 Supplier<\/li>\n\n\n\n
    • Shared understanding of:\n
        \n
      • Pickup time<\/li>\n\n\n\n
      • Location<\/li>\n\n\n\n
      • Insurance terms<\/li>\n\n\n\n
      • Deposit rules<\/li>\n\n\n\n
      • Damage responsibility<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n

        Every hidden assumption becomes a future dispute.<\/p>\n\n\n\n

        \n\n\n\n

        c) Visibility is a trust accelerator<\/h3>\n\n\n\n

        Concrete TakeCars examples:<\/p>\n\n\n\n

          \n
        • Clear booking status (\u201crequested \/ confirmed \/ ready\u201d)<\/li>\n\n\n\n
        • Visible supplier response times<\/li>\n\n\n\n
        • Explicit inclusions\/exclusions in listings<\/li>\n\n\n\n
        • Transparent refund timelines<\/li>\n<\/ul>\n\n\n\n

          Visibility reduces:<\/p>\n\n\n\n

            \n
          • Support tickets<\/li>\n\n\n\n
          • Defensive behaviour<\/li>\n\n\n\n
          • Blame-shifting<\/li>\n<\/ul>\n\n\n\n

            This principle directly lowers cost and<\/strong> increases trust.<\/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 often in communication and coordination scenarios<\/strong>.<\/p>\n\n\n\n

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

            \u201cCollaborate and promote visibility\u201d means:<\/p>\n\n\n\n

              \n
            • Work together across boundaries<\/li>\n\n\n\n
            • Share information openly<\/li>\n\n\n\n
            • Make progress and issues visible<\/li>\n<\/ul>\n\n\n\n

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

                \n
              • Breaks silos \u2192 strong<\/li>\n\n\n\n
              • Improves transparency \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
                • Emphasise individual work<\/li>\n\n\n\n
                • Hide information \u201cfor efficiency\u201d<\/li>\n\n\n\n
                • Treat visibility as optional<\/li>\n<\/ul>\n\n\n\n

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

                    \n
                  • Promote shared understanding<\/li>\n\n\n\n
                  • Increase transparency<\/li>\n\n\n\n
                  • Support early issue detection<\/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
                    • Miscommunication<\/li>\n\n\n\n
                    • Delays<\/li>\n\n\n\n
                    • Surprises<\/li>\n<\/ul>\n\n\n\n

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

                      \n

                      \u201cImproving collaboration and visibility.\u201d<\/p>\n<\/blockquote>\n\n\n\n

                      \n\n\n\n

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

                      Visibility enables better decisions and trust.<\/p>\n<\/blockquote>\n\n\n\n

                      Keep this sentence in mind when choosing answers under time pressure.<\/p>\n\n\n\n

                      \n\n\n\n

                      <\/p>\n","protected":false},"excerpt":{"rendered":"

                      The next guiding principle of ITIL 4 is collaborate and promote visibility. This principle highlights the importance of working together across teams and stakeholders. Collaboration helps organisations break down silos and improve communication. Promoting visibility means making work, progress, and information visible to everyone involved. When people can see what is happening, they can make […]<\/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-51","post","type-post","status-publish","format-standard","hentry","category-1"],"_links":{"self":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/51","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=51"}],"version-history":[{"count":2,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/51\/revisions"}],"predecessor-version":[{"id":54,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/51\/revisions\/54"}],"wp:attachment":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=51"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=51"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=51"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}