---

Problem management is the practice of identifying and managing the causes of incidents.

A problem is a cause or potential cause of one or more incidents.

The purpose of problem management is to reduce the likelihood and impact of incidents by identifying and addressing root causes.

Problem management includes activities such as root cause analysis and the creation of known error records.

Problem management may involve both reactive and proactive activities.

---

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

This practice explains how TakeCars stops the same failures from happening again, rather than just fixing them repeatedly.

a) Problem vs incident at TakeCars (critical distinction)

• Incident
  • A host cancels today
  • A car breaks down on a trip
• Problem
  • A specific host cancels repeatedly
  • A vehicle model has recurring mechanical issues
  • Pickup instructions are consistently unclear in one city

Incident management fixes today.
Problem management fixes tomorrow.

---

b) Reactive problem management at TakeCars

Triggered after incidents occur repeatedly.

Examples:

• Multiple last-minute cancellations by the same host
• Repeated “no-show” incidents at the same pickup location
• Frequent payment failures with one provider

Actions:

• Root cause analysis
• Policy changes
• Host restrictions or removal
• Process redesign

---

c) Proactive problem management at TakeCars

Looks for risks before incidents spike.

Examples:

• Identifying hosts with declining response times
• Detecting seasonal risk patterns
• Reviewing near-miss incidents

Proactive work reduces future incident volume.

---

d) Known errors and workarounds (exam nuance)

Once a root cause is known:

• A known error is recorded
• A workaround may be documented

For TakeCars:

• “This host often cancels; avoid same-day bookings”
• “This location needs manual confirmation during holidays”

This supports faster incident resolution until a permanent fix is applied.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of problem management?”

Correct logic:

• Identify and manage causes of incidents
• Reduce likelihood and impact of future incidents
• Focus on root causes

Answers focusing on restoring service quickly belong to incident management.

---

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

Problem management (very high probability)

• A service management practice
• Addresses causes of incidents
• Uses root cause analysis
• Reduces future incidents

---

Incident vs problem (must be crystal clear)

• Incident = unplanned interruption
• Problem = underlying cause

If an answer mentions “root cause”, it is problem management.

---

Common exam traps

• Problem management restores service → False
• Problems are the same as incidents → False
• Problem management is only reactive → False

---

One-line memory hook

Problem management removes the causes so incidents stop recurring.

---

---

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 restoring service, not on identifying root causes.

Incidents should be recorded, prioritised, and resolved according to agreed procedures.

---

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

This practice is one of the most operationally critical for TakeCars because incidents directly destroy customer outcomes and trust.

a) What an “incident” is at TakeCars

Incidents are unplanned disruptions, such as:

• Host cancels last minute
• Car is not available at pickup
• Vehicle breaks down during a trip
• Payment fails after confirmation
• Customer cannot access booking details
• Support is unreachable when needed

These are not routine requests; they are service failures.

---

b) Incident management goal: restore service fast

Key ITIL point:

• Incident management is about speed and restoration, not blame or analysis

For TakeCars this means:

• Get a replacement car
• Fix access to booking
• Rebook or refund quickly
• Keep the trip going if possible

Root cause analysis comes later (problem management).

---

c) Prioritisation is essential in a marketplace

Not all incidents are equal.

Example prioritisation:

• Customer at pickup location with no car → highest priority
• Booking confirmation delay for future date → lower priority

Incident management ensures:

• Urgency and impact are considered
• Resources are focused where value loss is greatest

---

d) Recording and procedures matter

Why ITIL insists on recording incidents:

• Patterns become visible
• Repeated host failures are detected
• Improvement opportunities emerge

Without records:

• Same failures repeat
• “Heroic” fixes hide systemic issues

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of incident management?”

Correct logic:

• Restore normal service operation quickly
• Minimise negative impact
• Focus on resolution, not root cause

Answers mentioning root cause identification belong to problem management.

---

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

Incident management (very high probability)

• A service management practice
• Handles unplanned interruptions
• Focuses on quick restoration
• Minimises impact on service

---

Incident vs problem (classic exam trap)

• Incident management
  • Restore service quickly
• Problem management
  • Identify and remove root causes

Do not confuse them.

---

Common exam traps

• Incident management identifies root causes → False
• Incidents are planned events → False
• Incident management focuses on long-term fixes → False

---

One-line memory hook

Incident management restores service quickly to minimise impact.

---

---

Measurement and reporting is the practice of supporting good decision-making through the collection, analysis, and reporting of data.

Its purpose is to provide relevant, timely, and accurate information to stakeholders.

Measurement and reporting helps organisations understand performance and identify improvement opportunities.

Metrics should be aligned with organisational objectives and stakeholder needs.

Reports should be clear, appropriate, and fit for their intended audience.

Measurement and reporting supports continual improvement across the organisation.

---

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

This practice explains how facts replace opinions, which is essential for operating and scaling a marketplace.

a) Measurement and reporting at TakeCars = decision support

At TakeCars, this practice answers questions such as:

• Where are trips failing?
• Which cities or hosts create the most issues?
• Which improvements actually reduced incidents?
• Where is money being lost quietly?

Without measurement, decisions become anecdotal.

---

b) Metrics aligned to outcomes, not noise

Poor metrics at TakeCars:

• Number of emails sent
• Tickets closed per agent
• Listings added per week

Strong, ITIL-aligned metrics:

• Trips completed without incident
• Host cancellation rate
• Time to confirm booking
• Time to resolve pickup issues
• Refund completion time

These directly reflect value and warranty.

---

c) Stakeholder-specific reporting

Different stakeholders need different views:

• Leadership
  • Trends, risk indicators, profitability signals
• Operations
  • Daily exceptions, bottlenecks, repeated failure patterns
• Hosts
  • Their response times, cancellations, reliability ranking

Same data, different presentation.

---

d) Measurement as a driver of continual improvement

Measurement and reporting:

• Reveal where improvement is needed
• Confirm whether changes worked
• Prevent repeating the same mistakes

If improvement is not measurable, it is not controllable.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of measurement and reporting?”

Correct logic:

• Support decision-making
• Provide relevant and accurate information
• Enable continual improvement

Answers focusing only on data collection or compliance are incomplete.

---

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

Measurement and reporting (high probability)

• A general management practice
• Supports decision-making
• Provides relevant, timely, accurate information
• Aligns metrics with objectives and stakeholder needs

---

Common exam traps

• Measuring everything is good practice → False
• Reports are one-size-fits-all → False
• Measurement is only for auditing → False

---

One-line memory hook

Measurement and reporting turn data into decisions and improvement.

---

Service request management is the practice of handling predefined, user-initiated requests for services.

Service requests are usually routine, low risk, and pre-approved.

The purpose of service request management is to support agreed quality of service by handling service requests efficiently and effectively.

Service requests may include requests for information, access, or standard changes.

Clear procedures and workflows help ensure service requests are fulfilled consistently.

Automation can be used to improve efficiency where appropriate.

---

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

This practice maps directly onto a large share of TakeCars’ daily operational load.

a) What a “service request” is at TakeCars

Service requests are not incidents. They are normal, expected asks such as:

• Change pickup time
• Add an additional driver
• Request child seats or extras
• Extend a booking
• Ask for invoice or receipt
• Update contact details

These are routine and predictable.

---

b) Why separating requests from incidents matters

If TakeCars treats everything as an “incident”:

• Support costs rise
• Response times slow
• True emergencies get lost

Service request management exists to:

• Standardise common requests
• Handle them quickly
• Reduce cognitive load on support staff

---

c) Predefined, low-risk, pre-approved

ITIL explicitly states service requests are:

• Known in advance
• Approved by default
• Low risk

For TakeCars this means:

• Clear rules for extensions
• Fixed pricing for extras
• Automated approval where possible

Anything that requires investigation or blame is likely an incident, not a request.

---

d) Automation as a force multiplier

High-impact automation examples:

• Self-service booking changes
• Automatic price recalculation
• Pre-approved extension flows
• Template-based responses

Automation improves:

• Speed
• Consistency
• Customer satisfaction

But only after workflows are clear.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of service request management?”

Correct logic:

• Handle predefined, user-initiated requests
• Ensure consistent, efficient fulfilment
• Support agreed service quality

Answers confusing requests with incidents are incorrect.

---

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

Service request management (high probability)

• A service management practice
• Handles predefined, routine requests
• Requests are user-initiated
• Usually low risk and pre-approved

---

Common exam traps

• Service requests are incidents → False
• Service requests require investigation → False
• Service requests are always high risk → False

---

One-line memory hook

Service request management fulfils routine user requests quickly and consistently.

---

Architecture management is the practice of providing a shared understanding of how an organisation’s systems, processes, and services are structured.

Its purpose is to ensure that the organisation’s architecture supports its strategy and objectives.

Architecture management helps guide change by defining standards, principles, and models.

It supports consistency, interoperability, and efficiency across the organisation.

Architecture management should consider both current and future states.

---

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

Architecture management is often misunderstood as “enterprise IT only”, but it is highly relevant for a growing marketplace.

a) What “architecture” means at TakeCars

Architecture is not just servers or code. It includes:

• How bookings flow end to end
• How data moves between components
• How decisions are automated vs manual
• How support, payments, and hosts interact

If this is not understood, scaling becomes chaotic.

---

b) Current vs future state (critical ITIL idea)

At TakeCars:

• Current state
  • Some manual checks
  • Some automations
  • Mixed host quality
• Future state
  • More automation
  • Clearer data ownership
  • Predictable exception handling

Architecture management exists to guide movement between these states without breaking the service.

---

c) Standards, principles, and models in TakeCars terms

Examples:

• One source of truth for booking data
• Standard pickup and return flow
• Clear separation between:
  • Booking logic
  • Payment logic
  • Support logic

Without standards, every new feature increases complexity and risk.

---

d) Why architecture management matters for reliability

Poor architecture leads to:

• Data inconsistency
• Manual workarounds
• Support errors
• Fragile integrations

Good architecture:

• Improves availability and continuity
• Reduces incident volume
• Makes improvement faster and safer

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of architecture management?”

Correct logic:

• Provide shared understanding
• Support strategy and objectives
• Guide change using standards and principles
• Consider current and future states

Answers focusing only on technology diagrams are incomplete.

---

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

Architecture management (moderate–high probability)

• A general management practice
• Provides shared understanding of structure
• Guides change
• Aligns architecture with strategy

---

Common exam traps

• Architecture management is only about IT infrastructure → False
• Architecture management focuses only on current state → False
• Architecture management replaces design work → False

---

One-line memory hook

Architecture management provides structure and standards so change supports strategy instead of breaking services.

---

Workforce and talent management is the practice of ensuring that the organisation has the right people with the right skills and competencies.

Its purpose is to support organisational objectives by developing and retaining a capable workforce.

Workforce and talent management includes workforce planning, recruitment, development, and retention.

It helps ensure that roles and responsibilities are clearly defined.

Workforce and talent management supports continual improvement and service quality.

---

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

This practice explains how people capability underpins service quality, even in a technology-heavy marketplace.

a) “Workforce” at TakeCars is broader than employees

For TakeCars, workforce includes:

• Founders and core team
• Support agents (internal or outsourced)
• Operations contractors
• Moderators or dispute handlers
• Engineers or platform partners

Service quality is constrained by the weakest capability in this chain.

---

b) Right people, right skills, right time

Key TakeCars examples:

• Support staff
  • Need judgment, empathy, policy knowledge
  • Not just ticket-closing speed
• Operations
  • Need pattern recognition
  • Ability to spot systemic issues with hosts or cities
• Leadership
  • Needs prioritisation and trade-off skills
  • Portfolio and risk awareness

Hiring fast without capability alignment increases incidents.

---

c) Roles and responsibilities clarity

Many marketplace failures stem from:

• Unclear ownership of disputes
• Overlapping responsibilities
• Decisions escalated too late or too often

Workforce and talent management ensures:

• Clear role boundaries
• Known escalation paths
• Consistent decision-making

---

d) Link to continual improvement

Skilled people:

• Identify better improvement opportunities
• Implement changes correctly
• Reduce rework and firefighting

This is why ITIL links talent management to service quality.

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of workforce and talent management?”

Correct logic:

• Ensure the organisation has the right people and skills
• Support organisational objectives
• Improve service quality

Answers focusing only on hiring are incomplete.

---

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

Workforce and talent management (high probability)

• A general management practice
• Focuses on people, skills, and competencies
• Includes planning, recruitment, development, retention
• Supports service quality and continual improvement

---

Common exam traps

• Talent management is only HR administration → False
• Workforce planning is static → False
• Skills are less important than tools → False

---

One-line memory hook

Workforce and talent management ensures the right skills are available to deliver and improve services.

---

---

Project management is the practice of initiating, planning, executing, and controlling projects.

Its purpose is to ensure that projects are completed successfully and deliver the intended outcomes.

Projects are temporary initiatives designed to achieve specific objectives.

Project management helps manage risks, resources, and stakeholder expectations.

Projects should be aligned with organisational strategy and contribute to value creation.

---

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

Project management explains how change is delivered, as opposed to how services are run day to day.

a) What is a “project” at TakeCars

A project is any time-bound change, such as:

• Launching a new city
• Introducing a new insurance product
• Reworking host onboarding
• Migrating payments or pricing logic
• Implementing a new support tool

Once completed, the result becomes part of normal operations.

---

b) Project management vs continual improvement

Important distinction:

• Project management
  • Temporary
  • Has a defined start and end
  • Delivers a specific change
• Continual improvement
  • Ongoing
  • Incremental
  • Never “finished”

TakeCars needs both:

• Projects for structural change
• Continual improvement for daily optimisation

---

c) Managing risks and expectations in TakeCars projects

Typical project risks:

• Feature shipped too late for peak season
• Policy change confusing hosts
• Incomplete rollout causing inconsistent behaviour

Project management helps by:

• Defining scope clearly
• Assigning ownership
• Managing dependencies
• Communicating expectations

---

d) Exam-critical insight

If the exam asks:

“What is the purpose of project management?”

Correct logic:

• Ensure projects deliver intended outcomes
• Manage risks, resources, and expectations
• Support value creation

Answers suggesting project management runs ongoing services are incorrect.

---

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

Project management (high probability)

• A general management practice
• Manages temporary initiatives
• Delivers defined outcomes
• Supports value creation and strategy

---

Common exam traps

• Projects are ongoing → False
• Project management replaces service management → False
• Projects exist independently of strategy → False

---

One-line memory hook

Project management delivers temporary change that creates lasting value.

---

---

Portfolio management is the practice of ensuring that an organisation has the right mix of programmes, projects, products, and services to achieve its objectives.

Its purpose is to ensure that resources are allocated appropriately and that investments deliver value.

Portfolio management helps organisations evaluate, prioritise, and balance initiatives.

It supports decision-making by providing visibility of current and planned work.

Portfolio management should align initiatives with organisational strategy and goals.

---

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

Portfolio management is often misunderstood as “enterprise-only”, but it is highly relevant even for founder-led marketplaces.

a) What the “portfolio” is at TakeCars

The portfolio includes:

• Cities and regions
• Vehicle categories (economy, family, premium)
• Product initiatives (new pricing rules, insurance options)
• Operational initiatives (host vetting changes, support tooling)

You already manage a portfolio; ITIL just gives it a name.

---

b) Why portfolio management matters for TakeCars

Without portfolio discipline:

• Too many initiatives run at once
• Resources are spread thin
• High-impact improvements are delayed
• Low-value work continues by inertia

Portfolio management forces trade-offs.

---

c) Practical portfolio decisions at TakeCars

Examples:

• Invest in Auckland reliability vs expanding to a new city
• Improve host quality vs launching a new feature
• Reduce cancellations vs increase supply volume

Portfolio management ensures:

• Choices align with strategy
• Resources follow value, not noise

---

d) Exam-critical insight

If the exam asks:

“What is the purpose of portfolio management?”

Correct logic:

• Ensure the right mix of initiatives
• Allocate resources effectively
• Align investments with strategy
• Deliver value

Answers implying portfolio management is only about IT projects are incorrect.

---

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

Portfolio management (high probability)

• A general management practice
• Manages programmes, projects, products, and services
• Aligns investments with strategy
• Supports prioritisation and value delivery

---

Common exam traps

• Portfolio management manages only projects → False
• Portfolio management is operational execution → False
• Portfolio management ignores services → False

---

One-line memory hook

Portfolio management ensures resources are invested in the right mix of value-creating initiatives.

---

Service financial management is the practice of planning and managing an organisation’s budgeting, accounting, and charging activities.

Its purpose is to support effective financial management and decision-making.

Service financial management helps ensure that services are delivered within budget and provide value for money.

It supports transparency and accountability for service-related costs.

Service financial management applies to all services and practices.

---

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

This practice explains how money is made visible and controlled, which is critical for a marketplace operating on thin margins and variable demand.

a) What service financial management means at TakeCars

It is not just bookkeeping. It includes:

• Understanding cost per booking
• Understanding cost per incident
• Knowing which services or cities are profitable
• Deciding where to invest and where to stop

Without this, growth can destroy value.

---

b) Budgeting, accounting, and charging in TakeCars terms

Budgeting

• Support staffing levels for peak seasons
• Marketing spend per city
• Platform and infrastructure costs

Budgets should reflect demand patterns, not averages.

---

Accounting

• Tracking platform fees
• Refund leakage
• Dispute-related costs
• Supplier fees (payments, insurance)

Poor accounting hides unprofitable behaviour.

---

Charging

• Platform commission structures
• Fees for extras or protection
• Penalties for cancellations or misuse

Charging decisions directly influence behaviour and risk.

---

c) Value-for-money perspective

ITIL emphasises value for money, not cost minimisation.

At TakeCars:

• Cheap support that fails causes cancellations
• Over-investment in features that do not reduce incidents wastes money

Service financial management exists to align spend with outcomes.

---

d) Exam-critical insight

If the exam asks:

“What is the purpose of service financial management?”

Correct logic:

• Support budgeting, accounting, and charging
• Enable informed decision-making
• Ensure value for money

Answers focusing only on cost cutting are incomplete.

---

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

Service financial management (high probability)

• A general management practice
• Covers budgeting, accounting, and charging
• Supports value for money
• Applies to all services

---

Common exam traps

• Financial management is only for finance teams → False
• Financial management focuses only on reducing costs → False
• Financial management applies only to IT services → False

---

One-line memory hook

Service financial management makes service costs visible so value-for-money decisions can be made.

---

---

Risk management is the practice of identifying, assessing, and controlling risks.

Its purpose is to ensure that the organisation understands and effectively manages risks related to its objectives.

Risk management helps organisations balance risk and opportunity.

Risks may arise from uncertainty and can have positive or negative effects.

Risk management should be integrated into all organisational activities and decision-making.

---

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

Risk management is core operating logic for a marketplace, even if it is never formally labelled as such.

a) What “risk” looks like at TakeCars

Typical risks include:

• Host cancellations
• Vehicle breakdowns
• Fraud or identity misuse
• Insurance gaps
• Payment failures
• Regulatory or consumer law exposure
• Reputational damage from bad trips

Each risk threatens outcomes, warranty, or trust.

---

b) Identifying, assessing, and controlling risks

Identify

• Where trips fail
• Where disputes occur
• Where support escalations cluster

Example:

• Repeated last-minute host cancellations in one city

---

Assess

• Likelihood (how often does this happen?)
• Impact (how bad is it when it happens?)

A rare breakdown is different from frequent cancellations.

---

Control (treat)

Risk treatment options in TakeCars:

• Prevent
  • Host vetting
  • Mandatory instructions
• Reduce
  • Deposits
  • Backup vehicles
• Transfer
  • Insurance
• Accept
  • Low-impact edge cases

ITIL does not require eliminating all risk.

---

c) Balancing risk and opportunity

Avoiding all risk would mean:

• No new hosts
• No new cities
• No flexibility

Taking unmanaged risk leads to:

• Support overload
• Trust collapse

Risk management exists to balance, not block, growth.

---

d) Exam-critical insight

If the exam asks:

“What is the purpose of risk management?”

Correct logic:

• Identify, assess, and control risks
• Support achievement of objectives
• Balance risk and opportunity

Answers implying “eliminate all risk” are incorrect.

---

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

Risk management (high probability)

• A general management practice
• Identifies, assesses, and controls risk
• Supports objectives
• Balances risk and opportunity

---

Common exam traps

• Risk management removes all risk → False
• Risk management is reactive only → False
• Risk management applies only to threats → False

---

One-line memory hook

Risk management balances uncertainty and opportunity to protect objectives.

---