ruck.nz

Category: Practices

  • 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.

  • 5.5. Technical management practices

    Let’s now take a closer look at technical management practices in ITIL 4.

    Technical management practices are focused on the technical resources and capabilities required to deliver and support services.

    These practices are typically carried out by teams with specialised technical expertise.

    Examples of technical management practices include infrastructure and platform management, software development and management, and deployment management.

    Technical management practices ensure that the technical environment is reliable, secure, and capable of supporting services.

    They support the service value chain by enabling the design, build, and operation of technology solutions.

    Understanding technical management practices helps organisations manage the technical aspects of service delivery effectively.

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

    This section explains why TakeCars’ technology is not the service, but it enables the service.

    a) Technical practices are enablers, not value by themselves

    For TakeCars, technical management practices include:

    • Platform infrastructure and uptime
    • Payment system reliability
    • Messaging and notification systems
    • Integrations with suppliers or partners
    • Deployment of new features and fixes

    Customers never “experience” these directly — they experience what breaks when they fail.

    ITIL’s framing is correct: technology enables value; it does not define it.

    b) Reliability beats novelty

    From an ITIL lens, technical management practices should prioritise:

    • Stability
    • Security
    • Predictability

    For TakeCars this means:

    • Fewer failed payments
    • No lost bookings
    • No duplicate charges
    • Safe handling of customer data

    A boring but reliable platform creates far more value than a feature-rich but unstable one.

    c) Technical practices must align with service priorities

    ITIL explicitly links technical practices to the service value chain.

    For TakeCars:

    • Deployment timing must align with support readiness
    • Infrastructure scaling must match booking peaks
    • Automation must reflect real service flows

    When tech decisions are made in isolation, service quality suffers.

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

    Technical management practices are tested as enablers of services, not as ends in themselves.

    Core understanding

    Technical management practices:

    • Focus on technical resources and capabilities
    • Support the delivery and operation of services
    • Require specialised expertise

    If an answer:

    • Treats technology as the service → wrong
    • Positions it as an enabler → strong

    Exam trap to avoid

    Wrong answers often:

    • Overemphasise tools
    • Ignore alignment with services
    • Assume technology alone creates value

    Correct answers:

    • Link technical practices to service support
    • Emphasise reliability and security
    • Support value creation indirectly

    Fast exam shortcut

    If the scenario mentions:

    • Infrastructure
    • Deployment
    • Technical platforms

    The answer likely involves:

    Technical management practices

    One-line exam anchor

    Technical management practices enable services by managing technology effectively.

    Keep this sentence in mind — it resolves most technology-related ITIL questions.

    This completes the practices overview

    You have now covered:

    • General management practices
    • Service management practices
    • Technical management practices

  • 5.3. Service management practices

    Let’s now take a closer look at service management practices in ITIL 4.

    Service management practices are focused specifically on the management and delivery of services.

    They help organisations design, deliver, and improve services that meet customer needs.

    These practices support interactions between service providers and service consumers.

    Examples of service management practices include incident management, service request management, and service level management.

    Service management practices play a key role in ensuring consistent and reliable service delivery.

    They support value co-creation by enabling effective communication and coordination.

    Understanding service management practices helps organisations manage services more effectively.

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

    This section describes the operational heart of TakeCars — where customer experience is actually won or lost.

    a) Service management practices = customer reality

    For TakeCars, service management practices show up as:

    • Incident management
      • Car not available
      • Breakdown during rental
      • Late pickup
    • Service request management
      • Date changes
      • Extension requests
      • Add-ons (child seats, insurance)
    • Service level management
      • Response times
      • Resolution expectations
      • Supplier SLAs

    This is where customers feel the platform, not in the UI.

    b) Consistency beats heroics

    ITIL positions these practices as repeatable systems, not ad-hoc fixes.

    For TakeCars:

    • A consistent incident response builds trust
    • Clear service levels reduce disputes
    • Structured requests prevent support chaos

    Heroic one-off fixes feel good — but practices scale.

    c) Service practices enable value co-creation

    These practices:

    • Align expectations
    • Clarify responsibilities
    • Reduce misunderstandings

    For TakeCars, this means:

    • Fewer arguments
    • Faster resolutions
    • More predictable outcomes

    This is value creation in action.

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

    Service management practices are commonly tested in scenario-based questions.

    Core understanding

    Service management practices:

    • Focus on service delivery and support
    • Manage provider–consumer interactions
    • Enable consistent service outcomes

    If an answer:

    • Focuses on customer interaction → strong
    • Mentions coordination and reliability → strong

    Exam trap to avoid

    Wrong answers often:

    • Confuse service practices with technical tools
    • Treat them as purely internal
    • Ignore the customer-facing aspect

    Correct answers:

    • Emphasise service quality
    • Support value co-creation
    • Focus on delivery and improvement

    Fast exam shortcut

    If the scenario mentions:

    • Customer issues
    • Requests
    • Expectations

    The answer likely involves:

    Service management practices

    One-line exam anchor

    Service management practices manage how services are delivered and supported.

    Keep this sentence in mind — it resolves most practice-identification questions quickly.

  • 5.1. General management practices

    Let’s now take a closer look at general management practices in ITIL 4.

    General management practices are applicable to all types of organisations, not just IT service providers.

    These practices support the overall management of the organisation and its services.

    They help ensure that the organisation is well governed, well planned, and effectively managed.

    Examples of general management practices include risk management, information security management, and project management.

    These practices are essential for creating a stable and controlled environment in which services can operate.

    General management practices support value creation by enabling effective decision-making and coordination.

    Understanding these practices helps organisations manage services in a consistent and structured way.

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

    This section explains why TakeCars’ success depends as much on “boring management” as on product or growth.

    a) TakeCars already runs on general management practices

    Even if unnamed, TakeCars relies heavily on them:

    • Risk management
      • Deposits
      • Insurance rules
      • Supplier eligibility
    • Information security
      • Customer data
      • Payment data
      • Identity verification
    • Project management
      • Feature launches
      • Policy changes
      • Supplier onboarding waves

    Without these practices, the marketplace would collapse under its own risk.

    b) These practices create the “safe container” for growth

    ITIL frames general management practices as enablers, not bureaucracy.

    For TakeCars:

    • Risk management enables trust
    • Information security enables payments
    • Project management enables predictable change

    Growth without these practices results in:

    • Fraud
    • Legal exposure
    • Chaotic releases
    • Support overload

    c) Why founders often underestimate this layer

    Marketplaces often over-focus on:

    • Acquisition
    • Conversion
    • Features

    ITIL reminds us:

    Value creation requires a stable management foundation.

    TakeCars’ long-term defensibility depends on invisible but disciplined management practices.

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

    General management practices are tested as broad organisational enablers, not technical tools.

    Core understanding

    General management practices:

    • Apply to all organisations
    • Support governance and control
    • Enable effective service management

    If an answer:

    • Limits them to IT only → wrong
    • Applies them broadly → strong

    Exam trap to avoid

    Wrong answers often:

    • Treat these practices as optional
    • Confine them to operational teams
    • Ignore their role in value creation

    Correct answers:

    • Emphasise organisational-wide applicability
    • Link them to stability and coordination
    • Support strategic alignment

    Fast exam shortcut

    If a question asks:

    • “Which practices apply beyond IT?”
      → General management practices

    One-line exam anchor

    General management practices support the organisation as a whole.

    Keep this sentence in mind — it resolves most high-level practice questions.

  • 4.3. Practices

    Let’s now take a closer look at practices in ITIL 4.

    Practices are sets of organisational resources designed for performing work or accomplishing an objective.

    They include people, processes, information, and technology.

    Practices replace the concept of processes from earlier versions of ITIL.

    ITIL 4 includes three categories of practices: general management practices, service management practices, and technical management practices.

    Practices are designed to be flexible and adaptable to different organisational contexts.

    They support the service value chain and help organisations perform work consistently and effectively.

    Understanding practices is important for applying ITIL concepts in real-world situations.

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

    This section explains why TakeCars should think in “practices” rather than rigid processes or tools.

    a) Practices reflect reality better than processes

    For TakeCars, real work is never just a flowchart.

    A TakeCars “practice” includes:

    • People: support agents, ops managers, supplier contacts
    • Processes: booking, dispute handling, refunds
    • Information: booking data, photos, messages, history
    • Technology: platform, payments, messaging, automation

    ITIL deliberately moved away from “process-only” thinking because it ignores how work actually gets done.

    b) Why this matters in a marketplace

    Marketplaces break when:

    • Tools change but behaviours don’t
    • Policies change but data doesn’t support them
    • Processes exist but people bypass them

    Practices force TakeCars to ask:

    “Do people, tools, data, and rules actually work together?”

    That is the real unit of execution.

    c) Flexibility without chaos

    ITIL practices are:

    • Not prescriptive
    • Not one-size-fits-all
    • Adaptable to context

    For TakeCars:

    • Supplier management practice differs by country
    • Incident handling differs by severity
    • Payment handling differs by risk profile

    Thinking in practices allows variation without losing coherence.

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

    Practices are a core ITIL 4 concept, often tested conceptually rather than by memorisation.

    Core understanding

    A practice:

    • Is a set of organisational resources
    • Includes people, processes, information, and technology
    • Supports work and objectives

    If an answer:

    • Treats practices as just processes → wrong
    • Includes multiple resource types → strong

    Exam trap to avoid

    Wrong answers often:

    • Use “process” language only
    • Ignore people or technology
    • Treat practices as rigid

    Correct answers:

    • Emphasise resources working together
    • Highlight flexibility
    • Link practices to value creation

    Fast exam shortcut

    If the question asks:

    • “How does ITIL organise work?”
      → Practices, not processes.

    One-line exam anchor

    Practices combine people, processes, information, and technology.

    Keep this sentence in mind — it resolves most practice-related questions quickly.