Topic 8.2 — Communications & Engagement

Communication and engagement are the craft that turns a well-planned digital change into something patients and staff understand, trust, and actually use — and in health and care, poor communication is a safety, equity, and public-trust failure, not merely a missed message.

Why this matters in health and care#

A digital change that is technically sound can still fail because nobody explained why it mattered, nobody listened to the people it affected, or a rumor outran the facts. In health and care the stakes are unusually high: a nurse who misunderstands a new e-observations workflow can miss a deteriorating patient; a community that distrusts how its data will be used can opt out of a shared care record en masse; a poorly worded outage notice can send anxious patients to an already-overwhelmed emergency department. Communication is therefore woven into clinical safety (see Topic 1.6 — Clinical Safety & Risk Management) and public trust (see Topic 1.8 — Data Ethics, Consent & Public Trust), not bolted on at launch.

Public-sector communication also carries a distinct duty of honesty. You are spending public money, you are accountable to patients who cannot easily take their custom elsewhere, and you operate in a media and political environment where any misstep — a delayed rollout, a data incident, a controversial supplier — can dominate local headlines. Health and care audiences are diverse in language, digital confidence, and trust in institutions, so a single broadcast message rarely reaches everyone equitably (see Topic 1.9 — Digital Inclusion & Accessibility). Getting this right is a leadership responsibility, not something to delegate wholesale to a communications team at the last minute.

This topic is deliberately distinct from Topic 8.1 — Change Management. Change management is the model for how an organization moves from a current state to a future state; communications and engagement are the practiced craft of messages, channels, narrative, and listening that make that movement land with real people. You need both, and they must be planned together.

Core concepts#

Strategic communication is the purposeful use of communication by an organization to reach a defined goal — here, to help a digital change succeed. It starts from objectives and audiences, not from a list of messages you want to send.

Stakeholder engagement is the process of involving the people affected by a decision so they can genuinely influence it. Engagement sits on a spectrum, often summarized as inform, consult, involve, collaborate, and empower; only the informing end is one-way. Real engagement means stakeholders shape the outcome, not just hear about it.

Stakeholder mapping identifies who is affected and how, typically along axes of interest and influence, so you can tailor effort. Related to it is audience segmentation, drawn from market segmentation: dividing a broad population — staff, patients, carers, the public — into meaningful groups with shared needs, so the same change can be explained differently to a ward sister, a GP practice manager, and an 80-year-old with limited internet access.

Storytelling and narrative give a change meaning. People remember and act on a clear story about why this matters for patients and staff far more than on a feature list or a benefits-realization table. A good narrative names the problem, the change, and the better future in language the audience already uses.

Internal communications is the discipline of communicating with staff, and it is tightly bound to employee engagement — an engaged workforce adopts change; a disengaged one endures or resists it. This is distinct from external and public communications aimed at patients, carers, and citizens, which carries different regulatory, accessibility, and trust considerations.

Participatory design, often called co-design, involves the people affected in shaping the change itself, blurring the line between engagement and design (see Topic 3.0 — User Research & Service Design). It is the strongest antidote to the broadcast-only mindset.

Crisis communication is the sub-discipline for communicating during incidents and outages — protecting safety and trust when something goes wrong (see Topic 3.8 — Service Management & Live Operations and Topic 3.9 — Business Continuity & Disaster Recovery). It intersects with the wider craft of public relations and with countering misinformation and rumor, which spread fastest when official information is absent.

Finally, sentiment analysis and other listening methods let you measure not just reach but understanding and feeling — did the message land, and how do people feel about it? And nudge theory reminds you that how you frame and time a message shapes behavior, which brings both power and an ethical obligation to use it honestly.

Best practices#

1. Start from objectives and audiences, not messages. Before drafting anything, be explicit about what behavior or understanding you need to change, and in whom. Write a short communications and engagement plan that names each audience segment, what they currently think and feel, what you want them to think, feel, and do, and how you will know it worked. A plan built from "what do we want to announce" produces noise; a plan built from "who needs to do what differently" produces adoption.

2. Map stakeholders and segment audiences deliberately. A ward clerk, a consultant, a caseworker, a patient with a learning disability, and a local councillor are not one audience. Map who is affected by interest and influence, then segment by need, channel, digital confidence, and language. Tailor the message and the medium to each segment — the same change becomes a two-minute team-brief for staff, a plain-language leaflet co-produced with a patient group, and a factual briefing for the local authority.

3. Lead with a clear narrative about why it matters for patients and staff. People act on meaning, not mandates. Craft a simple story: the problem today, the change you are making, and the better outcome for patients and for the staff doing the work. Anchor it in something concrete — fewer missed results, less duplicate data entry, faster referrals — and use the words your audience uses, not internal program jargon or acronyms. Test the narrative on a few real staff and patients before you scale it.

4. Shift from broadcast to genuine two-way engagement. A cascade of emails and posters is informing, not engaging. Build in structured listening — drop-in sessions, floor-walking, staff and patient panels, co-design workshops — and show visibly that you changed something because of what you heard. When people see their feedback alter the design or the rollout plan, trust and adoption rise; when engagement is theater, cynicism sets in and spreads.

5. Choose channels and cadence for the audience, not for your convenience. Match the channel to the segment: intranet and team huddles for staff, but also print, text, community groups, and trusted intermediaries for patients who are digitally excluded. Set a predictable cadence so people know when to expect updates, and repeat key messages across channels — most people need to hear something several times, in several forms, before it registers. Silence is itself a message, and usually the wrong one.

6. Work with professional communications and engagement teams early. Your organization's communications, patient-experience, and engagement colleagues bring brand, accessibility, media-handling, and audience expertise you do not have. Bring them in at planning, not at launch, and give them the clinical and technical substance they need. Equally, do not outsource ownership: leaders and delivery teams must supply the honest content and stand behind it.

7. Plan incident and outage communications before you need them. When a system fails, the communications vacuum fills with rumor and anxiety within minutes. Pre-agree who speaks, through which channels, how fast, and with what holding message; pre-draft templates for common scenarios; and rehearse them alongside your business-continuity plans (see Topic 3.9 — Business Continuity & Disaster Recovery). During an incident, tell people what you know, what you don't yet know, what you are doing, and when you will next update them — even if the answer is still "we don't know yet."

8. Confront resistance, rumor, and misinformation directly and honestly. Resistance often carries real signal — a workflow that genuinely doesn't fit the ward, or a legitimate fear about workload or safety. Listen for the truth in it, address it, and correct false information quickly with facts, named sources, and a calm tone rather than defensiveness. The fastest way to let misinformation win is to say nothing; the fastest way to lose trust for good is to be caught spinning.

9. Measure understanding and sentiment, not just volume. Opens, clicks, and attendance tell you reach, not effect. Add measures of comprehension (can people explain the change back?), sentiment (how do they feel?), and behavior (are they actually using the new service?). Use surveys, pulse checks, listening in forums, and sentiment analysis of free-text feedback, and feed what you learn back into the plan so communication becomes a loop, not a broadcast.

10. Hold honesty and transparency as non-negotiable. In public services, trust is your scarcest and most valuable asset, and it is destroyed far faster than it is built. Do not overclaim benefits, hide delays, or bury bad news; acknowledge trade-offs, admit when a rollout has gone wrong, and be clear about how patient data is used. Honest communication may be uncomfortable in the moment, but it is the only foundation that survives contact with scrutiny, and it makes every future message more credible.

Questions to discuss with your team#

1. Who are our real audiences for this change, and how does what we say and how we say it differ for each? It is tempting to treat "staff" and "the public" as two blocks, but a digital change lands on a caseworker, a night-shift nurse, a carer, and a patient with limited English very differently. Debate whether you have genuinely segmented your audiences or are relying on a single all-staff email and a press release. Consider who is easy to reach and therefore over-communicated to, and who is hard to reach and therefore ignored — often the same people who are already digitally excluded. A good answer names specific segments, the channels and intermediaries that actually reach each, and the different framing each needs, and it is honest about where you currently have blind spots. Watch for the failure of designing all your communication for the audiences most like yourselves.

2. Where on the spectrum from informing to empowering is our engagement really sitting — and where should it be? Many programs claim to engage while in practice only informing, running consultations after the key decisions are already made. Discuss, for each major decision in this change, how much influence patients and staff genuinely have, and whether that matches what you are implying to them. Surface the tension between the time real co-design takes and the delivery pressure to move fast, and be honest that pretend-engagement is worse than none because it breeds cynicism. Consider concrete mechanisms — co-design workshops, patient panels, staff reference groups — and what you will visibly change as a result. A strong answer distinguishes where you will genuinely share power from where you are only informing, and commits to being truthful about the difference rather than dressing one up as the other.

3. If a serious incident or outage hit this system tomorrow, are we ready to communicate within the hour — honestly and to everyone affected? Incident communication is where trust is won or lost fastest, yet it is the part teams rehearse least. Walk through a realistic scenario — the system is down across every ward at 2pm — and ask who has authority to speak, what the holding message is, which channels reach staff and patients (including those offline), and how you will keep updating. Debate the tension between the instinct to say nothing until you know everything and the reality that silence breeds rumor and unsafe workarounds. Consider how you would correct misinformation on social media, and how honest you are willing to be about what went wrong. A good answer points to pre-agreed roles, rehearsed templates tied to your business-continuity plans, and a shared commitment to say what you know, what you don't, and when you will next speak.

4. What is our single, honest story about why this change matters — and would a nurse or a patient recognize themselves in it? Programs accumulate messages, benefits tables, and slide decks, but people act on a clear narrative, not a feature list. Discuss whether you can state, in two plain sentences, the problem today, the change you are making, and the better outcome for patients and for the staff doing the work — and whether that story uses the words your audiences actually use rather than program jargon. Surface the tension between a narrative that is compelling and one that is truthful: it is easy to craft an inspiring story that quietly overpromises, and in health and care an overclaimed benefit erodes the trust you need for the next change. Test whether the story survives contact with a skeptical ward sister or a wary patient group, and whether front-line staff would tell it to a colleague unprompted. A good answer produces a narrative that is concrete, tested on real people, and honest about trade-offs, and it names who owns and stewards that story so it stays consistent across every channel.

5. How will we know our communication actually worked — beyond opens, clicks, and attendance? It is comfortable to report that an email reached ten thousand inboxes and reassuring to count workshop attendees, but reach is not understanding, and neither is behavior change. Debate what evidence would genuinely tell you the message landed: can staff explain the change back in their own words, how do people feel about it, and are they actually using the new service as intended? Consider the practical methods — comprehension checks, pulse surveys, listening in team forums, sentiment analysis of free-text feedback — and be honest about the effort and the risk that you measure what is easy rather than what matters. There is a real tension between wanting flattering numbers to show a board and wanting uncomfortable signals early enough to act on them. A good answer commits to a small set of measures spanning understanding, sentiment, and behavior, names who reviews them, and closes the loop by feeding what you learn back into the next round of communication.

6. Where are we tempted to overclaim, soften, or delay bad news — and what will keep us honest when the pressure is on? Trust is the scarcest asset in public services and it is spent far faster than it is earned, yet the daily pressures of funding bids, board confidence, and political scrutiny all pull towards optimistic messages and buried delays. Discuss specifically where this change is vulnerable: a benefit that may not fully materialize, a slipping timeline, a contentious supplier, or a sensitive question about how patient data is used. Surface the tension between managing legitimate reputational risk and the temptation to spin, and be clear that being caught overclaiming or concealing does more lasting damage than the bad news itself would have. Consider what structures keep you honest — a named senior owner for difficult messages, a habit of acknowledging trade-offs openly, transparency about data use, and permission for staff to raise concerns without blame. A good answer identifies the specific honesty risks in this program and the concrete commitments and guardrails that will hold when it becomes uncomfortable to tell the truth.

In practice: a health & care example#

An integrated care system (ICS) is rolling out a shared care record that lets clinicians across acute, community, mental health, GP, and social care see a single view of a person. The technology is ready; the risk is trust and adoption. A previous national data-sharing initiative in the region had collapsed under public suspicion, and local staff remember it.

The program director does not start with a launch date. She commissions a communications and engagement plan built around audiences: front-line clinicians in each setting, practice managers, social workers, the local Healthwatch, community and faith groups in the most under-served neighbourhoods, and the general public. Each segment gets its own narrative. For staff, the story is "stop asking patients to repeat themselves and stop chasing results across five systems." For the public, co-produced with a patient panel and translated into the area's main community languages, the story is "your care team can see the information they need to keep you safe — and here is exactly who can see what, and how to opt out." She works hand-in-glove with the ICS communications team and the patient-experience lead from week one.

Engagement is two-way and visible. Co-design workshops with community groups surface a specific fear — that immigration status or mental-health history could leak to non-clinical bodies — and the program changes its access model and its public materials in response, then says so publicly. Staff floor-walking reveals that the log-in flow adds clicks on busy wards; that feedback reshapes the rollout sequencing and a fix is prioritized. Cadence is predictable: a fortnightly staff bulletin, monthly public updates, and standing panels.

When, three weeks after go-live, the record is unavailable for four hours during a supplier incident, the pre-agreed crisis plan activates. Within forty minutes a holding message goes to every clinical team through the intranet, team huddles, and a text cascade, explaining the outage, the paper-based fallback, and the next update time; a plain-language notice reassures patients that their data is safe and no appointments are affected. A false claim on local social media that "the whole NHS system has been hacked" is corrected within the hour with a calm, factual statement from a named director. Trust holds, because the groundwork of honesty had already been laid, and opt-out rates stay low. The program measures not just how many staff logged in, but whether they can explain what the record does and how they feel about it — and feeds that back into the next round of messages.

Sector lenses#

Startup#

A small digital-health company has a founder-led, fast, informal communications style and little budget for a dedicated engagement function. Its strength is speed and authenticity — the clinical lead can speak directly and credibly to early-adopter clinicians. Its risk is over-claiming to win contracts and then failing to communicate honestly when the product breaks, which in a small market destroys reputation quickly. The founders should invest early in a simple, honest narrative, a basic incident-communications template, and disciplined listening to their first customers, because word of mouth among a handful of NHS trusts can make or break them.

Small business#

An established small provider — a GP practice, a community pharmacy, a care home, or a single-site clinic introducing a new digital system — has real patients and staff but no communications team, and the practice manager or registered manager typically absorbs engagement alongside everything else. The audiences are small and personally known, which is an advantage: a team huddle, a noticeboard, a letter to patients, and a conversation with the patient participation group can reach most people directly and authentically. The constraint is time and reach, not brand — thin cover means incident and outage messages fall to whoever is on shift, so a one-page pre-agreed script for "the system is down" and a simple way to reach housebound or digitally excluded patients matter far more than a polished campaign. The same duties of honesty, accessibility, and data-use transparency apply as to a large trust, but must be met with a fraction of the resource, so borrowing plain-language materials and channels from the wider ICS is usually wiser than building your own.

Enterprise#

A large NHS trust or ICS has a professional communications and engagement team, an established brand, media relationships, and statutory patient-engagement structures such as a patient panel or Healthwatch link. The challenge is scale and coordination: many simultaneous changes competing for the same audiences, message fatigue among staff, and the risk that central communications feels remote from the ward. Governance and sign-off can slow responsiveness, which hurts during incidents. The winning pattern is a clear operating rhythm between program teams and the communications function, segmented channels that reach the front line, and genuine engagement structures rather than tokenistic consultation.

Government#

A national or local public body — NHS England, a devolved government, the Department of Health and Social Care, or a local authority — communicates at the highest scale and under the most scrutiny, with political oversight, freedom-of-information exposure, and national media attention. Public trust in data use is a defining issue, and past failures such as poorly explained national data programs cast long shadows. Communication must be scrupulously honest, accessible, and equitable across the whole population, and engagement must be demonstrably real because it will be examined. The premium is on transparency, plain language, and building long-term trust that survives changes of policy and leadership (see Topic 9.1 — Working with Local & National Governments).

Common failure modes#

• Launch-day communications. Treating communication as a go-live announcement rather than a sustained program; by launch, opinion has already formed.
• Broadcast masquerading as engagement. Sending information one way, calling it consultation, and changing nothing as a result — which breeds cynicism worse than silence.
• Jargon and acronym soup. Talking to patients and front-line staff in program language they don't share, so the message never lands.
• The engagement blind spot. Communicating well to the audiences most like you and neglecting the digitally excluded, the seldom-heard, and those who most need the service.
• Incident silence. Having no rehearsed crisis-communications plan, so a vacuum fills with rumor and unsafe workarounds within minutes.
• Vanity metrics. Measuring emails sent and opens, never understanding, sentiment, or behavior change.
• Overclaiming. Promising benefits that don't materialize or hiding delays, spending trust you cannot easily earn back.
• Communications as an afterthought team. Bringing the professional communications and engagement function in only at the end, after the messages are already wrong.

Maturity model#

Checklist#

• A written communications and engagement plan exists, built from change objectives and audiences, not from messages.
• Stakeholders are mapped and audiences segmented by need, channel, language, and digital confidence.
• A clear narrative explains why the change matters for patients and for staff, tested on real people.
• Two-way engagement mechanisms are in place, and you can show what changed because of feedback.
• Channels and cadence are chosen for the audience, including reaching the digitally excluded.
• The professional communications and engagement team is involved from planning, not launch.
• An incident and outage communications plan is pre-agreed, templated, and rehearsed with business-continuity plans.
• A method exists to detect and correct rumor and misinformation quickly and honestly.
• Measures cover understanding and sentiment, not just reach and volume.
• Honesty is explicit: no overclaiming, delays acknowledged, data use transparent.

Key sources#

• NHS England — Communications and engagement guidance and the NHS Identity/brand guidelines.
• NHS England — Working in partnership with people and communities: statutory guidance (patient and public engagement duties for ICBs).
• Consultation Institute / IAP2 — Spectrum of Public Participation (inform → consult → involve → collaborate → empower).
• GOV.UK — Government Communication Service (GCS) strategy and the OASIS campaign-planning framework.
• Government Communication Service — Crisis and incident communications guidance.
• Design Council — Framework for Innovation (Double Diamond) for co-design and discovery.
• The Health Foundation / NHS England — evidence on co-production and involving people in service change.
• Chartered Institute of Public Relations (CIPR) and Institute of Internal Communication (IoIC) — professional standards for public and internal communications.

References#

1. Strategic communication — Wikipedia — https://en.wikipedia.org/wiki/Strategic_communication
2. Stakeholder engagement — Wikipedia — https://en.wikipedia.org/wiki/Stakeholder_engagement
3. Market segmentation — Wikipedia — https://en.wikipedia.org/wiki/Market_segmentation
4. Storytelling — Wikipedia — https://en.wikipedia.org/wiki/Storytelling
5. Internal communications — Wikipedia — https://en.wikipedia.org/wiki/Internal_communications
6. Employee engagement — Wikipedia — https://en.wikipedia.org/wiki/Employee_engagement
7. Participatory design — Wikipedia — https://en.wikipedia.org/wiki/Participatory_design
8. Crisis communication — Wikipedia — https://en.wikipedia.org/wiki/Crisis_communication
9. Public relations — Wikipedia — https://en.wikipedia.org/wiki/Public_relations
10. Misinformation — Wikipedia — https://en.wikipedia.org/wiki/Misinformation
11. Sentiment analysis — Wikipedia — https://en.wikipedia.org/wiki/Sentiment_analysis
12. Nudge theory — Wikipedia — https://en.wikipedia.org/wiki/Nudge_theory
13. Working in partnership with people and communities: statutory guidance — NHS England — https://www.england.nhs.uk/publication/working-in-partnership-with-people-and-communities-statutory-guidance/
14. Government Communication Service (GCS) — Cabinet Office / GOV.UK — https://gcs.civilservice.gov.uk/
15. IAP2 Spectrum of Public Participation — International Association for Public Participation — https://www.iap2.org/page/pillars
16. Framework for Innovation: the Double Diamond — Design Council — https://www.designcouncil.org.uk/our-resources/the-double-diamond/