ruck.nz

Author: admin

  • 9.5. Supplier management

    Supplier management is the practice of ensuring that the organisation’s suppliers and their performance are managed appropriately.

    Its purpose is to ensure that suppliers and their services are managed to support the organisation’s goals and service delivery.

    Supplier management includes selecting suppliers, managing contracts, and monitoring supplier performance.

    Effective supplier management helps ensure value for money and reliable service delivery.

    Supplier relationships should be reviewed regularly to ensure they remain effective.

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

    For TakeCars, supplier management is not a back-office concern; it is central to service quality and scalability.

    a) Who “suppliers” are in TakeCars

    Suppliers are not only traditional vendors. They include:

    • Vehicle hosts and fleet partners
    • Insurance providers
    • Payment processors
    • Identity verification services
    • Cloud and infrastructure providers

    Each supplier directly affects customer outcomes.

    b) Supplier management vs relationship management

    • Supplier management
      • Performance, contracts, reliability, value for money
    • Relationship management
      • Trust, alignment, long-term collaboration

    At TakeCars, both apply to hosts, but with different emphasis:

    • Supplier management ensures hosts meet minimum standards
    • Relationship management builds loyalty and cooperation

    c) Practical supplier management activities at TakeCars

    Selection

    • Vetting hosts and partners
    • Insurance and compliance checks
    • Capability and reliability assessment

    Performance monitoring

    • Host cancellation rates
    • Response times
    • Incident frequency
    • Dispute patterns

    Poor supplier performance directly reduces warranty.

    Review and action

    • Coaching or restricting underperforming hosts
    • Renegotiating terms with providers
    • Replacing suppliers that no longer support goals

    Supplier management is not static.

    d) Exam-critical insight

    If the exam asks:

    “What is the purpose of supplier management?”

    Correct logic:

    • Ensure suppliers support organisational goals
    • Ensure reliable service delivery
    • Manage performance and contracts

    Answers focusing only on cost reduction are incomplete.

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

    Supplier management (high probability)

    • A general management practice
    • Manages suppliers and their performance
    • Supports value for money and service delivery
    • Includes selection, monitoring, and review

    Common exam traps

    • Supplier management is only about contracts → False
    • Supplier management applies only to external vendors → False
    • Supplier management replaces relationship management → False

    One-line memory hook

    Supplier management ensures suppliers reliably support service delivery and organisational goals.

  • 9.4.Relationship management

    Relationship management is the practice of establishing and nurturing links between an organisation and its stakeholders.

    Its purpose is to establish and maintain good relationships with stakeholders at strategic and tactical levels.

    Relationship management helps ensure that stakeholder needs and expectations are understood and managed.

    It supports collaboration, trust, and mutual understanding.

    Effective relationship management contributes to value co-creation and long-term success.

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

    This practice is foundational for marketplaces, where success depends more on relationships than on assets.

    a) Relationship management vs service relationship management

    Important distinction:

    • Relationship management (this practice)
      • Strategic and tactical relationships
      • Long-term alignment
    • Service relationship management
      • Day-to-day service interactions

    Both exist at TakeCars, but they operate at different levels.

    b) Key stakeholder groups for TakeCars

    Relationship management focuses on:

    • High-value hosts and fleet partners
    • Strategic suppliers (insurance, payments)
    • Key customer segments (corporate, long-term renters)
    • Regulators or industry bodies (where applicable)

    These are not “support tickets”; they are ongoing relationships.

    c) What good relationship management looks like at TakeCars

    Understanding expectations

    • What hosts expect from the platform
    • What TakeCars expects from hosts
    • Where incentives and risks sit

    Misalignment here causes churn.

    Trust and collaboration

    • Predictable rules
    • Fair enforcement
    • Two-way feedback

    Trust reduces:

    • Disputes
    • Support load
    • Opportunistic behaviour

    Strategic value

    Strong relationships enable:

    • Priority supply in peak seasons
    • Early access to new cities or vehicle types
    • Willingness to pilot new features or policies

    This is long-term leverage.

    d) Exam-critical insight

    If the exam asks:

    “What is the purpose of relationship management?”

    Correct logic:

    • Establish and maintain relationships
    • Understand stakeholder needs and expectations
    • Support trust and collaboration
    • Enable value co-creation

    Answers that limit it to customers only are incorrect.

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

    Relationship management (high probability)

    • A general management practice
    • Focuses on stakeholders
    • Operates at strategic and tactical levels
    • Builds trust, collaboration, and understanding

    Common exam traps

    • Relationship management is only operational → False
    • Relationship management applies only to customers → False
    • Relationship management replaces service management → False

    One-line memory hook

    Relationship management builds long-term stakeholder trust that enables value co-creation.

  • 9.3. Information security management

    Information security management is the practice of protecting information needed by the organisation to conduct its business.

    Its purpose is to ensure that information is appropriately protected in accordance with its importance and sensitivity.

    Information security management supports confidentiality, integrity, and availability of information.

    The practice should balance the need for security with the need for usability and access.

    Information security risks should be identified, assessed, and treated.

    Information security management applies to all services and practices.

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

    This practice is quietly critical for marketplaces, because trust collapses instantly when information is mishandled.

    a) What “information” means at TakeCars

    Information is not just passwords or servers. It includes:

    • Customer identity details
    • Driver licence data
    • Payment and transaction data
    • Booking history
    • Host contact details
    • Dispute and incident records

    Loss or misuse of any of these directly damages trust and creates legal exposure.

    b) Confidentiality, integrity, availability (CIA) in TakeCars terms

    Confidentiality

    • Customer data is not exposed to other renters
    • Hosts only see information required for the booking
    • Support access is role-based

    Failure example:

    • Sending booking details to the wrong host

    Integrity

    • Booking details are accurate and not altered incorrectly
    • Payment amounts and dates are correct
    • Dispute records reflect what actually happened

    Failure example:

    • Manual edits causing incorrect charges or dates

    Availability

    • Customers and hosts can access bookings when needed
    • Support can retrieve records during disputes
    • Platform access during peak travel periods

    Failure example:

    • System outage during holiday pickups

    c) Balancing security and usability (very ITIL-specific)

    Too much security:

    • Overly complex verification
    • Excessive manual checks
    • Friction that blocks bookings

    Too little security:

    • Fraud
    • Data leaks
    • Regulatory violations

    ITIL explicitly requires balance, not maximum lockdown.

    d) Exam-critical insight

    If the exam asks:

    “What is the purpose of information security management?”

    Correct logic:

    • Protect information
    • Based on importance and sensitivity
    • Support confidentiality, integrity, and availability
    • Apply across all services

    Answers focused only on technology are incomplete.

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

    Information security management (high probability)

    • A practice
    • Protects organisational information
    • Based on CIA:
      • Confidentiality
      • Integrity
      • Availability
    • Balances security and usability

    Common exam traps

    • Information security is only an IT responsibility → False
    • Maximum security is always best → False
    • Information security applies only to data storage → False

    One-line memory hook

    Information security protects confidentiality, integrity, and availability while remaining usable.

  • 9.2. The continual improvement practice

    The continual improvement practice supports ongoing improvement of products, services, and practices.

    Its purpose is to align services and practices with changing business needs.

    Continual improvement uses feedback, measurement, and analysis to identify improvement opportunities.

    Improvements may be small and incremental or larger initiatives.

    The continual improvement model provides a structured approach to improvement activities.

    Continual improvement applies across the entire organisation and to all practices.

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

    This video revisits continual improvement, now explicitly as a practice, not just a concept.

    a) Continual improvement as a TakeCars operating habit

    At TakeCars, continual improvement should be:

    • Built into weekly operations
    • Driven by real signals, not opinions
    • Focused on friction removal

    Examples:

    • Repeated pickup issues in one city
    • Hosts with consistently slow response times
    • Support tickets clustering around the same topic

    Each is an improvement trigger.

    b) Feedback sources at TakeCars (exam-aligned)

    ITIL mentions feedback, measurement, and analysis.
    Concrete TakeCars equivalents:

    • Feedback
      • Reviews
      • Support conversations
      • Host complaints
    • Measurement
      • Cancellation rates
      • Confirmation times
      • Ticket volume per booking
    • Analysis
      • Root cause reviews
      • Journey mapping
      • City-by-city comparison

    c) Small improvements compound fastest

    Examples of high-leverage small improvements:

    • Mandatory pickup instructions field
    • Automated host reminders
    • Clearer deposit explanations
    • Default dispute resolution steps

    ITIL explicitly states that improvements do not need to be large.

    d) Exam-critical insight

    If the exam asks:

    “What does the continual improvement practice do?”

    Correct logic:

    • Aligns services with changing needs
    • Uses feedback and measurement
    • Applies across all practices

    Answers limiting continual improvement to projects or departments are incorrect.

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

    Continual improvement practice (high probability)

    • A practice
    • Ongoing, not one-off
    • Uses feedback and metrics
    • Applies organisation-wide

    Common exam traps

    • Continual improvement is optional → False
    • Continual improvement is only large projects → False
    • Continual improvement applies to services only → False

    One-line memory hook

    Continual improvement continuously aligns services with changing needs using feedback and measurement.

  • 9.1. ITIL defines 34 management practices.

    Practices help organisations perform work in a consistent and effective way.

    ITIL defines 34 management practices.

    These practices are grouped into three categories: general management practices, service management practices, and technical management practices.

    Not all practices are required in every organisation.

    Practices should be adapted based on organisational context, size, and needs.

    The value of a practice depends on how well it supports value creation.

    Practices can be combined and used together to support service value chain activities.

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

    This video sets the frame for the practice-heavy part of ITIL, and the key message is adaptation, not completeness.

    a) TakeCars does not need “all 34 practices”

    For TakeCars:

    • Implementing all practices formally would be wasteful
    • What matters is whether practices support value creation

    Early-stage or scaling marketplaces succeed by:

    • Using a small number of practices well
    • Keeping them lightweight and outcome-focused

    This is fully aligned with ITIL 4.

    b) Practices as capability bundles, not bureaucracy

    Each practice is a reusable capability:

    • People
    • Rules
    • Data
    • Tools
    • Partners

    For example, at TakeCars:

    • Incident management exists even without a ticketing system
    • Service level management exists even without formal SLAs
    • Relationship management exists even without account managers

    The exam recognises this implicit adoption.

    c) Selecting the right practices for TakeCars

    High-impact practices for a car rental marketplace typically include:

    • Incident management
    • Service request management
    • Problem management
    • Service level management
    • Relationship management
    • Supplier (partner) management
    • Information security management
    • Continual improvement

    Others may remain minimal or informal.

    d) Exam-critical insight

    If the exam asks:

    “How should practices be applied?”

    Correct logic:

    • Practices should be adapted
    • Not all practices are mandatory
    • Context matters

    Answers implying:

    • All practices must be fully implemented
      Are incorrect.

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

    Practices overview (high probability)

    • ITIL defines 34 practices
    • Grouped into three categories
    • Adapted to organisational context
    • Support value creation via the service value chain

    Common exam traps

    • Practices are prescriptive → False
    • All practices must be used → False
    • Practices operate independently → False

    One-line memory hook

    Practices are adaptable capability sets that support value creation, not a mandatory checklist.

  • 8.16. Service relationship management

    Service relationship management is the practice of establishing and nurturing the links between a service provider and its consumers.

    The purpose of service relationship management is to maintain positive and productive relationships with service consumers.

    Service relationship management focuses on communication, collaboration, and trust.

    It helps ensure that both the service provider and the service consumer understand their responsibilities.

    Effective service relationship management supports value co-creation and long-term success.

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

    This video brings together many earlier concepts and explains how they are sustained over time in a marketplace environment.

    a) Service relationship management is the “trust engine” of TakeCars

    TakeCars does not succeed by single transactions.
    It succeeds by:

    • Repeat bookings
    • Long-term hosts
    • Reduced disputes
    • Predictable behaviour on all sides

    Service relationship management is what enables this.

    b) What service relationship management looks like in TakeCars

    Communication

    • Clear, consistent messaging
    • No surprises in rules or pricing
    • Timely updates when issues occur

    Poor communication destroys trust faster than technical failure.

    Collaboration

    • Hosts treated as partners, not inventory
    • Customers guided, not blamed
    • Support empowered to resolve issues, not just close tickets

    Collaboration directly affects outcome quality.

    Trust

    • Fair dispute resolution
    • Consistent rule enforcement
    • Transparent decisions

    Trust is cumulative and fragile.

    c) Responsibilities must be understood by all parties

    Many TakeCars problems come from:

    • Guests not understanding their obligations
    • Hosts misunderstanding platform rules
    • Platform expectations not being explicit

    Service relationship management exists to prevent this confusion.

    d) Exam-critical insight

    If the exam asks:

    “What is the purpose of service relationship management?”

    Correct logic:

    • Maintain positive, productive relationships
    • Support communication, collaboration, and trust
    • Enable value co-creation

    Answers that focus only on contracts or enforcement are incomplete.

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

    Service relationship management (high probability)

    • A practice
    • Focuses on relationships, not transactions
    • Emphasises communication, collaboration, and trust
    • Supports long-term value co-creation

    Common exam traps

    • Relationship management is optional → False
    • Relationship management is one-way → False
    • Relationship management replaces SLAs → False

    One-line memory hook

    Service relationship management sustains trust so value can be co-created over time.

  • 8.15. Service level agreements

    Service level agreements should focus on outcomes, not just activities.

    Defining service levels based only on activities can lead to services that appear busy but do not deliver value.

    Outcome-based service levels help ensure that services support customer objectives.

    Service level agreements should be realistic, measurable, and clearly understood by all parties.

    Regular review of service level agreements helps ensure they remain aligned with business needs.

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

    This video reinforces a core ITIL principle that is especially relevant for marketplaces: measuring the right thing.

    a) Activity-based vs outcome-based SLAs at TakeCars

    Activity-based SLAs (weak):

    • Number of emails sent
    • Tickets closed per day
    • Messages replied to

    These can be met while customers remain unhappy.

    Outcome-based SLAs (strong):

    • Percentage of bookings confirmed within X time
    • Percentage of trips completed without incidents
    • Refunds completed within Y days
    • Customer satisfaction after trip completion

    These reflect real value.

    b) Why TakeCars must avoid activity-only thinking

    A support team can:

    • Close tickets quickly
    • Send many messages

    And still fail to:

    • Resolve pickup issues
    • Prevent cancellations
    • Restore trust

    ITIL explicitly warns against this trap.

    c) Practical TakeCars examples

    • SLA: “Support responds within 2 hours”
      Activity-based, weak on its own
    • SLA: “Pickup issues resolved before rental start time in 95% of cases”
      Outcome-based, value-focused

    The second aligns directly with customer objectives.

    d) Exam-critical insight

    If the exam asks:

    “What should SLAs focus on?”

    Correct answer:

    • Outcomes
    • Value
    • Customer objectives

    Answers focused only on effort or activity are incorrect.

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

    Outcome-based service levels (high probability)

    • SLAs should focus on outcomes
    • Activities alone do not guarantee value
    • Measurable and realistic targets matter

    Common exam traps

    • More activity equals better service → False
    • SLAs should measure effort → False

    Always choose:

    • Outcome-oriented wording

    One-line memory hook

    Busy services do not equal valuable services; outcomes define success.

  • 8.14. Service agreements

    Service level agreements are only one type of service agreement.

    Other types of service agreements may include operational level agreements and underpinning contracts.

    Operational level agreements are agreements between different parts of the same organisation.

    Underpinning contracts are agreements with external suppliers that support service delivery.

    All types of service agreements should be aligned to ensure consistent service performance.

    Clear alignment between agreements helps avoid gaps or conflicts in service delivery.

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

    This video explains why SLAs alone are not enough and why alignment across agreements is critical in a multi-party marketplace like TakeCars.

    a) Three agreement layers in TakeCars terms

    Even if not formally documented, all three exist.

    1. Service Level Agreements (SLA)

    Between:

    • TakeCars and customers
    • TakeCars and hosts (implicitly)

    Examples:

    • Confirmation time expectations
    • Refund handling promises
    • Support availability

    These define what customers expect.

    2. Operational Level Agreements (OLA)

    Internal agreements within TakeCars.

    Examples:

    • Support team response targets
    • Escalation timelines
    • Engineering response to incidents

    If internal teams cannot meet these, external SLAs will fail.

    3. Underpinning Contracts (UC)

    Agreements with external suppliers.

    Examples:

    • Payment processors
    • Insurance providers
    • Cloud hosting
    • Verification services

    These underpin TakeCars’ ability to meet its SLAs.

    b) Alignment failure is a common marketplace problem

    Typical failure pattern:

    • SLA promises refunds in 3 days
    • Payment provider settles in 5 days
    • Support team is blamed

    This is an underpinning contract misalignment, not a support failure.

    c) Why alignment matters more as TakeCars scales

    As volume increases:

    • Small mismatches turn into systemic failures
    • Manual workarounds stop working
    • Customer trust erodes quickly

    ITIL’s emphasis on alignment is very practical here.

    d) Exam-critical insight

    If the exam asks:

    “Why must service agreements be aligned?”

    Correct logic:

    • To ensure consistent service delivery
    • To avoid gaps and conflicts
    • To support achievement of service levels

    Any answer implying SLAs operate in isolation is incorrect.

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

    Types of service agreements (must be recognised)

    • Service Level Agreements (SLA)
    • Operational Level Agreements (OLA)
    • Underpinning Contracts (UC)

    Know who they are between.

    Alignment principle (high probability)

    • All agreements must support each other
    • Misalignment causes service failure
    • Alignment supports consistent performance

    Common exam traps

    • SLAs are the only service agreement → False
    • OLAs are external → False
    • Underpinning contracts are optional → False

    One-line memory hook

    SLAs promise value, OLAs enable delivery, and underpinning contracts make it possible.

  • 8.13. Service level agreement

    Service level agreements are documented agreements between a service provider and a service consumer.

    Service level agreements describe the services to be provided and the agreed service levels.

    They define responsibilities and expectations for both the service provider and the service consumer.

    Service level agreements may include targets, metrics, roles, escalation paths, and review mechanisms.

    Service level agreements should be clear, realistic, and aligned with business needs.

    They should be reviewed regularly and updated when requirements or circumstances change.

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

    This video clarifies what SLAs are and what they are not, which is essential in a marketplace where formal contracts are often lightweight or implicit.

    a) SLAs at TakeCars are mostly implicit but still real

    Even without a signed PDF called “SLA”, TakeCars operates with SLAs embedded in:

    • Terms and conditions
    • Help centre articles
    • Booking confirmation messages
    • Host onboarding rules

    Customers and hosts behave as if SLAs exist, whether you formalise them or not.

    b) What an SLA looks like in TakeCars terms

    A TakeCars-style SLA typically defines:

    • What service is provided
      • Platform access
      • Booking handling
      • Support availability
    • Service levels
      • Confirmation time
      • Support response time
      • Refund turnaround
    • Responsibilities
      • What TakeCars does
      • What hosts must do
      • What customers must do
    • Escalation
      • When issues are escalated
      • Who makes final decisions

    Lack of clarity in any of these leads directly to disputes.

    c) Realistic and business-aligned SLAs matter

    Over-promising creates:

    • Support overload
    • Host churn
    • Customer dissatisfaction when promises are missed

    Under-promising creates:

    • Lost conversions
    • Perception of low quality

    ITIL’s emphasis on “clear and realistic” is especially important for TakeCars.

    d) Review and adaptation in a marketplace

    As TakeCars evolves:

    • New cities
    • New host types
    • Seasonal demand spikes

    SLAs must evolve as well. Static expectations break under growth.

    e) Exam-critical insight

    If the exam asks:

    “What do SLAs do?”

    Correct logic:

    • Document agreed service levels
    • Clarify responsibilities and expectations
    • Support consistent service delivery

    Answers implying SLAs:

    • Guarantee outcomes
    • Eliminate disputes
      Are incorrect.

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

    Service level agreements (high probability)

    • Documented agreements
    • Between provider and consumer
    • Define services, service levels, and responsibilities
    • Reviewed and updated as needed

    SLA vs service level management

    • SLA: the document
    • Service level management: the practice that manages and reviews SLAs and performance

    Do not confuse the two.

    Common exam traps

    • SLAs are permanent → False
    • SLAs guarantee value → False
    • SLAs replace service level management → False

    One-line memory hook

    SLAs document expectations; service level management ensures they are met.

  • 8.12. Service level management

    Service level management is the practice of setting clear business-based targets for service performance.

    The purpose of service level management is to ensure that service levels are achieved and that services deliver value to customers.

    Service level management involves negotiating, agreeing, monitoring, and reporting on service levels.

    Service level management helps align service performance with customer expectations and business needs.

    It supports continual improvement by identifying gaps between agreed service levels and actual performance.

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

    This video moves from what service levels are to how they are actively managed, which is critical for scaling a marketplace.

    a) Service level management at TakeCars = expectation control

    In TakeCars terms, service level management is about:

    • Deciding what reliability looks like
    • Communicating it clearly
    • Measuring whether it is achieved
    • Acting when it is not

    Without this, expectations drift and dissatisfaction grows.

    b) Practical service level management activities in TakeCars

    Negotiating and agreeing

    • Defining realistic confirmation times
    • Setting host response expectations
    • Clarifying support availability

    Even if not a formal SLA, this happens through:

    • Terms
    • Help pages
    • Booking confirmations

    Monitoring

    • Booking confirmation time
    • Host cancellation rates
    • Support response times
    • Refund turnaround time

    These metrics must reflect business impact, not just activity.

    Reporting

    • Internal dashboards for operations
    • Host performance summaries
    • Trend reports to identify deterioration

    Reporting without action has no value.

    Acting on gaps

    • Coaching or restricting underperforming hosts
    • Improving automation
    • Adjusting policies if targets are unrealistic

    This links directly to continual improvement.

    c) Exam-critical insight

    If the exam asks:

    “What is the purpose of service level management?”

    Correct logic:

    • Ensure agreed service levels are achieved
    • Align performance with customer and business needs
    • Support continual improvement

    Answers focusing only on documentation or reporting are incomplete.

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

    Service level management (high probability)

    • A practice, not just an agreement
    • Sets, monitors, and reports on service levels
    • Ensures services deliver value
    • Supports continual improvement

    Service levels vs service level management

    • Service levels: performance targets
    • Service level management: the practice that manages them

    This distinction is frequently tested.

    Common exam traps

    • Service level management is only about SLAs → False
    • Service level management is reactive only → False
    • Service level management is purely technical → False

    One-line memory hook

    Service level management actively aligns service performance with expectations and value.