---

Measurement and reporting are essential components of effective service management.
Without measurement, it is not possible to understand performance or make informed decisions.

The purpose of measurement and reporting is to support decision-making by providing relevant, timely, and accurate information.

Metrics should be carefully selected to ensure they support the organisation’s objectives and stakeholder needs.
Measuring everything is neither practical nor useful.

Different stakeholders require different types of information.
For example, senior management may require high-level metrics, while operational teams need more detailed data.

Metrics should be aligned with the organisation’s goals and the services being delivered.
They should focus on outcomes and value, not just activity.

Reports should be clear, concise, and appropriate for their intended audience.
Poorly designed reports can lead to misunderstanding or incorrect decisions.

Measurement and reporting support continual improvement by providing evidence of performance and identifying areas for improvement.

It is important to regularly review metrics and reports to ensure they remain relevant.
As organisational priorities change, measurement approaches may also need to change.

---

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

This video is pure operational discipline — and extremely relevant for a marketplace business.

a) “If you don’t measure it, you don’t manage it”

For TakeCars:

• Opinions from hosts or customers are useful
• Data decides priorities

Without measurement:

• You chase noise
• You overbuild features
• You fix the wrong problems

b) Measure outcomes, not activity (critical ITIL idea)

Bad metrics (activity):

• Number of support tickets handled
• Number of emails sent
• Number of hosts onboarded

Good metrics (outcomes):

• Tickets per booking
• Booking confirmation time
• Conversion rate search → booking
• Repeat booking rate

Exam loves this distinction.

c) Stakeholder-based reporting → TakeCars reality

Senior / founder view (weekly):

• Gross bookings
• Conversion rate
• Cancellation rate
• Avg host response time

Ops / support view (daily):

• Tickets per active booking
• Top 5 ticket reasons
• Refund turnaround time

Host-facing metrics:

• Response time ranking
• Acceptance rate
• Cancellations caused by host

Same system, different lenses.

d) “Don’t measure everything” → marketplace discipline

Classic early-stage trap:

• Tracking 50 metrics
• Acting on none

ITIL-approved approach:

• Pick 5–10 metrics that drive decisions
• Review them regularly
• Kill metrics that no longer matter

e) Measurement → Continual Improvement loop

This video directly connects to the previous one:

• Metrics show a problem
• Improvement action is planned
• Metrics confirm whether it worked

Example:

• Measure: 40% of tickets are “pickup confusion”
• Improve: mandatory pickup instructions
• Measure again: tickets drop to 18%

That is textbook ITIL.

---

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

Exam-critical points

• Measurement exists to support decision-making
• Metrics must be:
  • Relevant
  • Timely
  • Accurate
• Measuring everything is bad practice

Stakeholder focus (very common exam angle)

If the question asks:

“Why are different reports needed?”

Correct logic:

• Different stakeholders
• Different decisions
• Different levels of detail

Outcomes vs activities (high probability question)

• ✔ Outcomes = value, results, customer impact
• ❌ Activities = effort, volume, busyness

If unsure, choose the option that:

• Mentions value
• Mentions objectives
• Mentions decision-making

One-line memory hook

Measure what helps decisions, not what is easy to count.

---

When you upload video7_6.srt (or the next file), I will continue seamlessly.
After the final video in this block, I strongly recommend doing:

• A single-page ITIL exam cram sheet
• A TakeCars ITIL-lite operating model combining all videos