---

Continual improvement is a core component of ITIL and applies to all levels of the organisation.
It is not something that happens once, but something that should be embedded into everyday activities.

The purpose of the continual improvement practice is to align the organisation’s practices and services with changing business needs through the ongoing identification and improvement of services, service components, and practices.

Continual improvement supports the organisation in improving its products and services, but also the way it works overall.

Improvement opportunities can be identified in many ways.
These include feedback from customers and users, analysis of performance metrics, audits, and assessments.

Not all improvements need to be large-scale initiatives.
Many improvements are small and incremental, but over time they can deliver significant value.

ITIL provides a continual improvement model that can be used to structure improvement activities.
This model consists of several steps that help ensure improvements are effective and aligned with organisational goals.

The first step is to understand the vision.
This means understanding what the organisation is trying to achieve and how improvement supports that direction.

The next step is to assess the current state.
This involves understanding where the organisation is now and establishing a baseline.

Once the current state is understood, the organisation can define where it wants to be.
This includes setting measurable targets.

The next step is to plan how to get there.
This involves identifying improvement actions and prioritising them.

After planning, the organisation takes action and implements the improvements.

Finally, the results are evaluated to ensure that the improvements have delivered the expected value.
Lessons learned are then used to inform further improvement.

Continual improvement should be applied across the service value chain and to all practices.

Everyone in the organisation has a role to play in identifying and contributing to improvements.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

This video maps extremely cleanly onto how a marketplace like TakeCars should operate in reality.

a) Continual improvement ≠ big projects

For TakeCars, this means:

• Not “redesign the whole platform”
• But constant micro-improvements, such as:
  • One less step in host onboarding
  • Clearer pickup instructions
  • Faster refund handling
  • Better default messaging templates

These compound over time.

b) Sources of improvement opportunities (very concrete for TakeCars)

ITIL sources → TakeCars equivalents:

• Customer feedback
  • Reviews complaining about pickup confusion
  • Support tickets about deposits
• Performance metrics
  • Search → booking conversion rate
  • Time to confirm booking by host
  • Cancellation reasons
• Audits / assessments
  • Manual review of failed bookings
  • “Why did this turn into a WhatsApp mess?”
• Staff / founder insight
  • You noticing the same question answered 20 times a week

c) Continual Improvement Model → TakeCars example

1. What is the vision?

• “Fast, low-friction car rental with trusted local hosts”

2. Where are we now?

• Hosts respond slowly
• Guests ask repetitive questions
• Support load is high

3. Where do we want to be?

• 90% bookings confirmed in < 1 hour
• 30% fewer support tickets per booking

4. How do we get there?

• Auto-reminders to hosts
• Mandatory pickup instructions field
• Pre-written FAQ snippets injected into chat

5. Take action

• Implement one automation or rule at a time

6. Did it work?

• Measure response times
• Measure ticket volume
• Adjust again

This is pure ITIL, even if you never call it that.

d) Key mindset shift for a marketplace founder

• Continual improvement is not “ops work”
• It is core product strategy
• Every friction point is an improvement opportunity

---

3. Key Things to Read / Remember Right Before the Exam

High-probability exam points from this video

• Continual improvement applies to ALL practices and the entire service value chain
• Improvement can be:
  • Large or
  • Small and incremental (exam loves this wording)
• Everyone has a role in continual improvement (not just managers)

Continual Improvement Model – Memorise the flow

You do not need perfect wording, but the logic order matters:

1. Understand the vision
2. Assess the current state
3. Define the target state
4. Plan how to get there
5. Take action
6. Evaluate results

If stuck in an exam question:

“Which step comes next?”
→ Think baseline → target → plan → act → review

Common exam traps

• ❌ “Continual improvement is a one-off initiative” → False
• ❌ “Only senior management is responsible” → False
• ❌ “Only services can be improved, not practices” → False

One-line memory hook

Improve everything, all the time, in small steps, aligned to the vision.

---

When you are ready, upload the next SRT file.
I will continue seamlessly and, if you want later, produce:

• A single consolidated exam cheat sheet
• Or a TakeCars-specific ITIL operating model built from all videos