2.10.

The next guiding principle of ITIL 4 is progress iteratively with feedback.

This principle emphasises the importance of breaking work into smaller, manageable pieces.

Rather than attempting large changes all at once, organisations should make incremental improvements.

Each improvement should be evaluated, and feedback should be used to guide the next steps.

Progressing iteratively helps reduce risk and allows organisations to learn and adapt.

Feedback can come from customers, users, partners, and internal stakeholders.

Using feedback ensures that improvements are aligned with real needs and expectations.

This principle supports continuous learning and continual improvement.

---

2. How this applies to TakeCars (car-rental marketplace)

This principle describes how TakeCars should safely evolve without breaking trust or operations.

a) Iteration protects marketplace trust

For TakeCars:

• Large, sudden changes break supplier behaviour
• Big redesigns confuse repeat customers
• Policy overhauls create unintended loopholes

ITIL explicitly recommends:

Small changes, validated by feedback.

This is how you avoid marketplace shock.

---

b) Feedback sources TakeCars should prioritise

ITIL treats feedback as multi-source, not just “user opinions”.

For TakeCars, high-quality feedback includes:

• Post-rental reviews
• Support tickets (especially repeats)
• Refund and dispute patterns
• Supplier response times
• Drop-offs in booking flow

These are signals, not noise.

---

c) Iteration beats opinions

This principle legitimises a powerful rule:

• Test before scaling
• Observe before enforcing
• Learn before locking policy

For example:

• Trial a new deposit rule with one supplier cohort
• Pilot faster payouts in one region
• Test simplified handover instructions on airport rentals

Each iteration reduces risk while increasing learning.

---

3. Key ideas to read right before the exam (high-yield)

This guiding principle is a scenario-question favourite.

Core understanding

“Progress iteratively with feedback” means:

• Break work into smaller steps
• Gather feedback continuously
• Adjust based on learning

If an answer:

• Promotes big, one-time changes → weak
• Emphasises learning and feedback → strong

---

Exam trap to avoid

Wrong answers often:

• Suggest full redesigns
• Ignore stakeholder feedback
• Assume perfect upfront knowledge

Correct answers:

• Emphasise iteration
• Use feedback
• Reduce risk

---

Fast exam shortcut

If a scenario mentions:

• Uncertainty
• Risk
• Change

The correct answer usually includes:

“Make small improvements and gather feedback.”

---

One-line exam anchor

Improve in small steps, guided by feedback.

Keep this sentence in your head during the exam.

---