ITIL 4 Practitioner: Relationship Management flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Relationship management purpose

To establish and nurture the links between an organization and its stakeholders at strategic and tactical levels, ensuring mutual value and alignment with the service value chain's engage activity.

Stakeholder mapping axes

Power or influence plotted against interest or impact; high-power high-interest stakeholders are managed closely, while low-power low-interest stakeholders are monitored with minimal effort.

Trust components

Competence, benevolence, and integrity; a relationship is strengthened when the provider is seen as capable, well-intentioned, and consistent in its behavior over time.

Relationship lifecycle phases

Establish, maintain, review, and exit; each phase has distinct activities, records, and decision points, and the exit phase should be planned rather than left to chance.

Relationship register

A documented record of stakeholders, their needs, preferences, communication cadence, agreed engagement approach, and review history; it is a living artifact updated each cycle.

Customer satisfaction formula

Perceived value minus expectation; relationship management can raise satisfaction by increasing delivered value or by setting and managing realistic expectations through clear communication.

Relationship types

Service provider to consumer, peer or partner, internal between teams, and multi-supplier; each type carries different governance, escalation paths, and communication norms.

Emotional dimension

Relationship management addresses sentiment, communication style, and organizational culture, not only contractual terms; ignoring emotion undermines even well-drafted agreements.

Stakeholder identification activity

Systematically discovering all parties affected by or affecting the service, including customers, users, suppliers, regulators, and internal teams, and recording them in the relationship register.

Complaint handling flow

Acknowledge, record, classify severity, investigate, resolve, communicate the outcome, and analyse trends for root cause; each step has an owner and a target timeframe.

Escalation path definition

Agreed triggers, timeframes, named contacts, and authority levels for both parties; paths must be defined in advance so that issues do not stall unresolved.

Relationship review meeting

A scheduled operational or strategic meeting using agreed metrics such as satisfaction scores, SLA performance, open issues, and value realized to assess and improve the relationship.

Feedback mechanisms

Surveys, interviews, focus groups, and service review boards; each yields different depth and frequency, and combining them gives a fuller picture of stakeholder sentiment.

Communication plan

A document defining audience, message, channel, frequency, and owner for each stakeholder group; it is a key output of the relationship management practice.

Joint improvement plan

A record of agreed actions from relationship reviews, with owners and dates, tracked to closure; it converts feedback into measurable service and relationship improvements.

Relationship data governance

Relationship records must be accurate, current, and accessible under information security and privacy policies; data quality directly affects the quality of engagement decisions.

Practice owner role

Accountable for the relationship management practice's strategy, capability, and continual improvement; typically a senior relationship or customer experience manager.

Relationship manager role

Assigned to specific stakeholders or accounts; owns register entries, the engagement plan, and the review cadence, and acts as the primary point of contact.

Service owner collaboration

Service owners and product owners work with relationship managers to translate stakeholder needs into service requirements and to validate that delivered services meet expectations.

Service desk touchpoint

The service desk is a primary relationship touchpoint; its agents execute day-to-day engagement and capture first-line complaints and feedback for analysis.

RACI for engagement

Relationship manager is often Responsible for engagement, practice owner Accountable, service owners Consulted, and stakeholders Informed; the matrix must be agreed and published.

Organizational models

Centralized, distributed, and hybrid; centralization gives consistency, distribution gives local responsiveness, and hybrid balances both but requires clear coordination.

Escalation authority matrix

Defines who may commit resources, approve exceptions, or accept risk on behalf of the organization during an escalation; it prevents delays caused by unclear authority.

Relationship competencies

Communication, negotiation, empathy, commercial awareness, conflict resolution, and data literacy for satisfaction metrics; these should be defined in role descriptions.

Role definition alignment

Roles must be documented in the organization's role descriptions and aligned with ITIL 4 practice guidance, rather than left implicit or informal.

Practice in value chain

Relationship management sits primarily in the engage activity and contributes to improve; it consumes outputs from plan and design and transition activities.

Key practice interfaces

Service level management for agreements, supplier management for partner relationships, service desk for touchpoints, and continual improvement for feedback loops and corrective actions.

Information dimension

Relationship data is a configuration item type; it must be governed by information security management and data privacy rules to remain trustworthy and compliant.

Technology support

CRM, ITSM, survey, and analytics tools support the practice; integration is needed to give a single, consistent view of each stakeholder across systems.

Partner relationships

Relationship management extends to external partners; contracts define obligations, but relationships govern behavior, trust, and collaborative problem solving beyond the contract.

Guiding principles relevance

Collaborate and promote visibility, focus on value, and start where you are are especially relevant; they shape how relationship management is applied in practice.

Four dimensions impact

Organizations and people, information and technology, partners and suppliers, and value streams and processes each shape relationship capability and must be considered together.