{"id":106,"date":"2026-01-08T11:00:56","date_gmt":"2026-01-08T08:00:56","guid":{"rendered":"https:\/\/ruck.nz\/?p=106"},"modified":"2026-01-08T11:00:56","modified_gmt":"2026-01-08T08:00:56","slug":"6-7","status":"publish","type":"post","link":"https:\/\/ruck.nz\/?p=106","title":{"rendered":"6.7."},"content":{"rendered":"\n

Here is another example question.<\/p>\n\n\n\n

Which ITIL 4 guiding principle emphasises the importance of making progress in small steps and learning from feedback?<\/p>\n\n\n\n

A. Focus on value
B. Start where you are
C. Progress iteratively with feedback
D. Think and work holistically<\/p>\n\n\n\n

The correct answer is C: progress iteratively with feedback<\/strong>.<\/p>\n\n\n\n

This guiding principle encourages organisations to break work into smaller pieces and use feedback to guide improvement.<\/p>\n\n\n\n

It helps reduce risk and supports continual learning and adaptation.<\/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 question reflects how TakeCars should evolve without damaging trust or operations<\/strong>.<\/p>\n\n\n\n

a) Small steps protect a live marketplace<\/h3>\n\n\n\n

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

    \n
  • Big policy changes confuse suppliers<\/li>\n\n\n\n
  • Large UI changes confuse repeat customers<\/li>\n\n\n\n
  • Sudden automation creates edge-case failures<\/li>\n<\/ul>\n\n\n\n

    ITIL\u2019s guidance is explicit:<\/p>\n\n\n\n

    \n

    Change in small steps, observe results, then adjust.<\/p>\n<\/blockquote>\n\n\n\n

    This is exactly how a marketplace avoids self-inflicted outages.<\/p>\n\n\n\n

    \n\n\n\n

    b) Feedback sources that actually matter<\/h3>\n\n\n\n

    In TakeCars, feedback is not just opinions:<\/p>\n\n\n\n

      \n
    • Repeated support tickets<\/li>\n\n\n\n
    • Dispute patterns<\/li>\n\n\n\n
    • Drop-offs in booking flow<\/li>\n\n\n\n
    • Supplier response times<\/li>\n\n\n\n
    • Refund escalation rates<\/li>\n<\/ul>\n\n\n\n

      Using these signals iteratively is far more reliable than \u201cbig redesigns\u201d.<\/p>\n\n\n\n

      \n\n\n\n

      c) Why the other options are wrong (TakeCars lens)<\/h3>\n\n\n\n
        \n
      • A (focus on value)<\/strong>
        \u2192 Important, but not about iteration<\/li>\n\n\n\n
      • B (start where you are)<\/strong>
        \u2192 About assessment, not improvement cadence<\/li>\n\n\n\n
      • D (think and work holistically)<\/strong>
        \u2192 About system-wide view, not step size<\/li>\n<\/ul>\n\n\n\n

        Recognising intent<\/em> is the key exam skill here.<\/p>\n\n\n\n

        \n\n\n\n

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

        This question tests guiding-principle recognition<\/strong>.<\/p>\n\n\n\n

        Core takeaway<\/h3>\n\n\n\n

        \u201cProgress iteratively with feedback\u201d means:<\/p>\n\n\n\n

          \n
        • Small improvements<\/li>\n\n\n\n
        • Frequent feedback<\/li>\n\n\n\n
        • Learning-driven change<\/li>\n\n\n\n
        • Reduced risk<\/li>\n<\/ul>\n\n\n\n
          \n\n\n\n

          Fast exam elimination rule<\/h3>\n\n\n\n

          If the question mentions:<\/p>\n\n\n\n

            \n
          • Small steps<\/li>\n\n\n\n
          • Feedback<\/li>\n\n\n\n
          • Learning<\/li>\n\n\n\n
          • Adaptation<\/li>\n<\/ul>\n\n\n\n

            The correct answer is almost always:<\/p>\n\n\n\n

            \n

            Progress iteratively with feedback<\/strong><\/p>\n<\/blockquote>\n\n\n\n

            \n\n\n\n

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

            Improve in small steps, guided by feedback.<\/p>\n<\/blockquote>\n\n\n\n

            Keep this sentence in mind \u2014 it resolves almost all iteration-related exam questions instantly.<\/p>\n","protected":false},"excerpt":{"rendered":"

            Here is another example question. Which ITIL 4 guiding principle emphasises the importance of making progress in small steps and learning from feedback? A. Focus on valueB. Start where you areC. Progress iteratively with feedbackD. Think and work holistically The correct answer is C: progress iteratively with feedback. This guiding principle encourages organisations to break […]<\/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-106","post","type-post","status-publish","format-standard","hentry","category-1"],"_links":{"self":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/106","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=106"}],"version-history":[{"count":1,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/106\/revisions"}],"predecessor-version":[{"id":107,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/106\/revisions\/107"}],"wp:attachment":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=106"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=106"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=106"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}