Engage

Engage is the value chain activity that faces outward. It is where the organization listens to customers and users, works with suppliers and partners, and maintains the relationships through which value is co-created. Lesson 3 described engage as the main interface between the value chain and its stakeholders. This lesson looks at what engage involves in practice: understanding needs, consolidating demand, communicating transparently, managing relationships across different stakeholder groups, and turning feedback into action.

The purpose of engage

In plain terms, the engage activity provides a good understanding of stakeholder needs, transparency, continual engagement and good relationships with all stakeholders. Each part of that purpose matters. Understanding needs means going beyond the literal request to the outcome the stakeholder wants. Transparency means stakeholders can see what is happening with their requests and why decisions were made. Continual engagement means the relationship does not stop when a request is closed. Good relationships mean trust on both sides, which makes co-creation of value possible.

Engage applies to all stakeholders, not only customers. Users, sponsors, suppliers, partners, regulators, employees and the wider community all interact with the organization. Each group needs a different kind of engagement.

Inputs and outputs of engage

Engage receives demand and opportunities from outside the value chain, along with feedback from customers and users, information about third-party components from suppliers, and inputs from the other activities: plans and portfolio decisions from plan, product and service descriptions from design and transition, knowledge and information about components from obtain/build, and information about service performance from deliver and support.

Its outputs include consolidated demands and opportunities for plan; product and service requirements for design and transition; user support tasks for deliver and support; improvement initiatives and feedback for improve; change or project initiation requests; contract and agreement requirements; and knowledge and information about third-party services for the other activities.

From request to requirement

A stakeholder rarely states a requirement in a form that can be designed and built. A sales manager might ask for "a dashboard". The underlying need might be to spot deals at risk of slipping before the quarter ends. Engage translates the request into the outcome sought, the users involved, the constraints and the measures of success. That translation is what design and transition needs.

Consolidating demand

Demand arrives through many channels from many stakeholders. Engage consolidates it so that plan can see the whole picture. Without consolidation, the same need may be requested five times by five departments and fulfilled five different ways, or conflicting requests may be accepted by different teams. Consolidation involves grouping similar requests, identifying common underlying needs and presenting them to plan with their sources and value.

Transparency and communication

Transparency builds trust. Stakeholders should be able to see the status of their requests, understand why priorities were set as they were, and know what to expect. Practical tools include self-service portals showing request status, published service catalogues, clear service level agreements, regular reports and honest communication during incidents. Engage also communicates decisions that stakeholders may not like: deferrals, rejections and changes in scope.

Transparency does not mean overwhelming stakeholders with data. A customer usually wants a short, meaningful summary: Are we getting the outcomes we need? What is changing? What do you need from us? Engage tailors communication to each audience.

Relationship management

The relationship management practice supports engage by establishing and nurturing links between the organization and its stakeholders at strategic and tactical levels. ITIL-110 introduced the spectrum of relationships from basic through cooperative to partnership. Engage adapts its approach to the relationship type. A basic relationship with a commodity supplier may need little more than contract monitoring. A partnership with a strategic customer needs joint planning, shared goals and regular senior-level conversations.

Engaging users and their experience

Users are the people who actually use services. Their experience shapes whether value is realized. Engage gathers user feedback through surveys, interviews, usability testing and analysis of support contacts. It also recognizes that users may not be the customers who pay or define requirements. A hospital's IT customer may be the chief operating officer, but the users are nurses at 3 a.m. Engage must hear both voices.

Engaging suppliers and partners

Engage is not only about consumers. The organization is itself a consumer of supplier services, and engage handles that side of the relationship too: understanding supplier capabilities and roadmaps, communicating requirements, and managing the relationship alongside the supplier management practice. When a supplier's change will affect customers, engage connects the two conversations so that the impact is understood and communicated. Lesson 11 examines partners and suppliers in depth.

Feedback loops

Engage closes the loop between delivery and improvement. Feedback from users and customers is an input to improve; information about changes and improvements is communicated back to stakeholders. When stakeholders see that their feedback leads to visible change, they give more and better feedback. When feedback disappears without trace, they stop giving it. A simple practice is to tell stakeholders what was changed because of their input, often summarized as "you said, we did".

In Canada, federal services must engage clients in both official languages under the Official Languages Act, and the Policy on Service and Digital expects departments to involve clients in service design. A provider supporting a federal client therefore plans bilingual communication and user research from the start.

Engage in ITIL (Version 5)

Version 5 places strong emphasis on experience, which makes the work of engage even more central. Published course outlines list discover as the first lifecycle activity, which overlaps heavily with what engage does when it explores stakeholder needs and opportunities. Whichever edition you study, the core skills are the same: understanding needs, consolidating demand, communicating transparently and managing relationships.

Engagement during incidents and changes

Engage is especially visible when something goes wrong or something important changes. During a major incident, stakeholders want to know what is affected, what is being done and when to expect an update, even if the cause is not yet known. Regular, honest updates at predictable intervals reduce the volume of calls to the service desk and preserve trust. After the incident, a short summary of what happened and what will be done to prevent recurrence closes the loop.

Planned changes need engagement too. Users affected by a change to a familiar system should hear in advance what will change, when, why and where to get help. A change that is technically perfect but poorly communicated can still create a flood of contacts and a sense that the provider does not care.