---

Constraints are factors that limit or restrict the way a service can be used.

Constraints may be related to policies, regulations, technology, resources, or skills.

Removing or reducing constraints can increase the value of a service.

However, some constraints are necessary to manage risks or comply with legal and regulatory requirements.

Service providers should understand which constraints affect service consumers and how these constraints impact outcomes.

Balancing constraints and freedom of use is essential for effective service management.

---

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

This video explains why friction exists and how it should be handled deliberately, not accidentally.

a) Constraints in TakeCars terms

Constraints are not always failures. They are often intentional.

Common TakeCars constraints:

• Age limits
• Deposit requirements
• Mileage limits
• Geographic restrictions
• Insurance exclusions
• Time-bound pickups and returns

These constraints shape how the service can be used.

---

b) Good constraints vs bad constraints

Necessary constraints

• Protect vehicles and hosts
• Manage insurance risk
• Ensure legal compliance
• Reduce fraud and misuse

Examples:

• Minimum driver age
• Identity verification
• Damage liability rules

These constraints preserve warranty.

---

Harmful or accidental constraints

• Overly complex rules
• Hidden exclusions
• Manual approvals that delay pickups
• Poorly explained policies

These constraints destroy:

• Utility (cannot use the service as intended)
• Perceived value (frustration outweighs benefit)

---

c) Constraint removal as a value lever

Increasing value at TakeCars often means:

• Removing unnecessary steps
• Simplifying rules
• Making constraints visible and predictable

Examples:

• Clear upfront deposit explanation
• Standardised pickup instructions
• Default policies instead of case-by-case decisions

This aligns directly with ITIL’s guidance.

---

d) Exam-critical insight

If the exam asks:

“What is the role of constraints in service management?”

Correct logic:

• Constraints limit service use
• Some constraints reduce value
• Some constraints are necessary for risk and compliance
• Balance is required

Answers implying “constraints should always be removed” are incorrect.

---

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

Constraints definition (high probability)

• Factors that limit or restrict service use
• Can be technical, legal, policy-based, or resource-based

---

Exam traps

• All constraints reduce value → False
• Constraints should be eliminated → False
• Constraints are always negative → False

Look for balanced wording:

• “Remove unnecessary constraints”
• “Manage constraints appropriately”

---

One-line memory hook

Constraints shape how a service is used; the goal is balance, not elimination.