{"id":190,"date":"2026-01-08T11:38:27","date_gmt":"2026-01-08T08:38:27","guid":{"rendered":"https:\/\/ruck.nz\/?p=190"},"modified":"2026-01-08T11:38:49","modified_gmt":"2026-01-08T08:38:49","slug":"9-14-incident-management","status":"publish","type":"post","link":"https:\/\/ruck.nz\/?p=190","title":{"rendered":"9.14. Incident management"},"content":{"rendered":"\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">Incident management is the practice of managing incidents to restore normal service operation as quickly as possible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An incident is an unplanned interruption to a service or a reduction in the quality of a service.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The purpose of incident management is to minimise the negative impact of incidents on service operations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Incident management focuses on restoring service, not on identifying root causes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Incidents should be recorded, prioritised, and resolved according to agreed procedures.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">2. How This Applies to <strong>TakeCars<\/strong> (Car Rental Marketplace)<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">This practice is <strong>one of the most operationally critical<\/strong> for TakeCars because incidents directly destroy customer outcomes and trust.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">a) What an \u201cincident\u201d is at TakeCars<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Incidents are <strong>unplanned disruptions<\/strong>, such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Host cancels last minute<\/li>\n\n\n\n<li>Car is not available at pickup<\/li>\n\n\n\n<li>Vehicle breaks down during a trip<\/li>\n\n\n\n<li>Payment fails after confirmation<\/li>\n\n\n\n<li>Customer cannot access booking details<\/li>\n\n\n\n<li>Support is unreachable when needed<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These are not routine requests; they are service failures.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">b) Incident management goal: restore service fast<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Key ITIL point:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incident management is about <strong>speed and restoration<\/strong>, not blame or analysis<\/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>Get a replacement car<\/li>\n\n\n\n<li>Fix access to booking<\/li>\n\n\n\n<li>Rebook or refund quickly<\/li>\n\n\n\n<li>Keep the trip going if possible<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Root cause analysis comes later (problem management).<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">c) Prioritisation is essential in a marketplace<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Not all incidents are equal.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example prioritisation:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Customer at pickup location with no car \u2192 highest priority<\/li>\n\n\n\n<li>Booking confirmation delay for future date \u2192 lower priority<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Incident management ensures:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Urgency and impact are considered<\/li>\n\n\n\n<li>Resources are focused where value loss is greatest<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">d) Recording and procedures matter<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why ITIL insists on recording incidents:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Patterns become visible<\/li>\n\n\n\n<li>Repeated host failures are detected<\/li>\n\n\n\n<li>Improvement opportunities emerge<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Without records:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Same failures repeat<\/li>\n\n\n\n<li>\u201cHeroic\u201d fixes hide systemic issues<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">e) Exam-critical insight<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the exam asks:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">\u201cWhat is the purpose of incident management?\u201d<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Correct logic:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Restore normal service operation quickly<\/li>\n\n\n\n<li>Minimise negative impact<\/li>\n\n\n\n<li>Focus on resolution, not root cause<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Answers mentioning root cause identification belong to problem management.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">3. Key Things to Read \/ Remember Right Before the Exam<\/h1>\n\n\n\n<h3 class=\"wp-block-heading\">Incident management (very high probability)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A <strong>service management practice<\/strong><\/li>\n\n\n\n<li>Handles unplanned interruptions<\/li>\n\n\n\n<li>Focuses on quick restoration<\/li>\n\n\n\n<li>Minimises impact on service<\/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\">Incident vs problem (classic exam trap)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incident management\n<ul class=\"wp-block-list\">\n<li>Restore service quickly<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li>Problem management\n<ul class=\"wp-block-list\">\n<li>Identify and remove root causes<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Do not confuse them.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Common exam traps<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incident management identifies root causes \u2192 False<\/li>\n\n\n\n<li>Incidents are planned events \u2192 False<\/li>\n\n\n\n<li>Incident management focuses on long-term fixes \u2192 False<\/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 memory hook<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Incident management restores service quickly to minimise impact.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n","protected":false},"excerpt":{"rendered":"<p>Incident management is the practice of managing incidents to restore normal service operation as quickly as possible. An incident is an unplanned interruption to a service or a reduction in the quality of a service. The purpose of incident management is to minimise the negative impact of incidents on service operations. Incident management focuses on [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-190","post","type-post","status-publish","format-standard","hentry","category-practices"],"_links":{"self":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/190","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=190"}],"version-history":[{"count":1,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/190\/revisions"}],"predecessor-version":[{"id":191,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/190\/revisions\/191"}],"wp:attachment":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=190"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=190"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=190"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}