{"id":74,"date":"2026-01-08T10:46:19","date_gmt":"2026-01-08T07:46:19","guid":{"rendered":"https:\/\/ruck.nz\/?p=74"},"modified":"2026-01-08T10:46:19","modified_gmt":"2026-01-08T07:46:19","slug":"4-2-continual-improvement-model","status":"publish","type":"post","link":"https:\/\/ruck.nz\/?p=74","title":{"rendered":"4.2. Continual improvement model"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Let\u2019s now look at the <strong>continual improvement model<\/strong> in ITIL 4.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The continual improvement model provides a structured approach for identifying and managing improvements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It helps organisations understand where they are now, where they want to be, and how to get there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The model consists of several steps that guide improvement activities.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These steps help ensure that improvements are planned, measured, and aligned with organisational objectives.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The continual improvement model can be applied to services, practices, and the organisation as a whole.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Using the model helps organisations make consistent and effective improvements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Understanding the continual improvement model is important for applying continual improvement in practice.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">2. How this applies to <strong>TakeCars<\/strong> (car-rental marketplace)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This section explains <strong>how TakeCars can turn \u201cwe should fix this\u201d into a repeatable improvement discipline<\/strong> instead of reactive firefighting.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">a) The continual improvement model = structured learning loop<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In TakeCars terms, the model forces clarity:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Where are we now?\n<ul class=\"wp-block-list\">\n<li>High dispute rate on deposits<\/li>\n\n\n\n<li>Slow supplier confirmations<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Where do we want to be?\n<ul class=\"wp-block-list\">\n<li>Fewer disputes<\/li>\n\n\n\n<li>Faster confirmations<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>How do we get there?\n<ul class=\"wp-block-list\">\n<li>Policy refinement<\/li>\n\n\n\n<li>Automation<\/li>\n\n\n\n<li>Supplier segmentation<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Without this structure, improvements remain opinion-driven.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">b) Preventing \u201crandom optimisation\u201d<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Marketplaces often:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Fix what is loudest<\/li>\n\n\n\n<li>Optimise what feels urgent<\/li>\n\n\n\n<li>Chase symptoms instead of causes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The ITIL model forces:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Baselines<\/li>\n\n\n\n<li>Targets<\/li>\n\n\n\n<li>Measurable outcomes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">For TakeCars, this means:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Measuring dispute resolution time before changing rules<\/li>\n\n\n\n<li>Tracking confirmation speed before automating<\/li>\n\n\n\n<li>Comparing cohorts before rolling out changes<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">c) Making improvement scalable<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">As TakeCars grows:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Founders cannot decide every improvement<\/li>\n\n\n\n<li>Support cannot invent fixes ad hoc<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The continual improvement model:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Creates shared language<\/li>\n\n\n\n<li>Enables delegation<\/li>\n\n\n\n<li>Preserves consistency<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This is how improvement survives growth.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">3. Key ideas to read <strong>right before the exam<\/strong> (high-yield)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The continual improvement model is often tested as a <strong>\u201cwhat is its purpose?\u201d<\/strong> question.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Core understanding<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The continual improvement model:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Provides a structured approach<\/li>\n\n\n\n<li>Supports planning and managing improvements<\/li>\n\n\n\n<li>Helps move from current state to desired state<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If an answer:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Mentions structure and alignment \u2192 strong<\/li>\n\n\n\n<li>Mentions ad-hoc improvement \u2192 weak<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Exam trap to avoid<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Wrong answers often:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Confuse the model with the guiding principles<\/li>\n\n\n\n<li>Treat it as a single step<\/li>\n\n\n\n<li>Limit it to IT only<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Correct answers:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Emphasise structured improvement<\/li>\n\n\n\n<li>Apply broadly<\/li>\n\n\n\n<li>Align with objectives<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Fast exam shortcut<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If the question asks:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u201cHow does ITIL structure improvement?\u201d<br>\u2192 <strong>Continual improvement model<\/strong><\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">One-line exam anchor<\/h3>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">The continual improvement model provides a structured path from current state to desired state.<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Keep this sentence in mind \u2014 it resolves most related exam questions instantly.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Let\u2019s now look at the continual improvement model in ITIL 4. The continual improvement model provides a structured approach for identifying and managing improvements. It helps organisations understand where they are now, where they want to be, and how to get there. The model consists of several steps that guide improvement activities. These steps help [&hellip;]<\/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-74","post","type-post","status-publish","format-standard","hentry","category-1"],"_links":{"self":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/74","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=74"}],"version-history":[{"count":1,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/74\/revisions"}],"predecessor-version":[{"id":75,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/74\/revisions\/75"}],"wp:attachment":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=74"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=74"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=74"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}