Employee Communication and Digital Channel Strategy

Digital Communications at Work Summary: Make Channels Coherent

Digital Communications at Work explains how to connect the planning, production, publication, distribution and discussion of employee information so that a collection of channels becomes a useful communication system.

One-Sentence Answer

What The Book Is About

Sharon O'Dea and Jonathan Phillips examine a familiar workplace failure: important information exists somewhere, yet the people who need it still cannot find, understand or use it. Adding another app may produce another place to check without improving the underlying experience. Their subject is the relationship among channels, people, content and responsibility.

The publisher's first-edition record identifies the July 3, 2026 UK release. The authors' book introduction distinguishes the July 28 US date, describes the five-layer model and outlines the practical problems the book addresses. That regional distribution date does not make it a different work.

This guide draws on the authors' substantive Digital Workplace Group interview and full transcript, their published explanation and the edition record. We have not accessed the whole book or reconstructed every chapter. Our channel-audit worksheet and fictional shift-change example are applications developed for this guide. A separate critical reader review by Ana Neves provides useful evidence of professional reader engagement, including practical reservations; it is not a substitute for the authors' account.

The strongest reason to read the book is a concrete information problem across an organization. It can help a communications manager work with IT, HR, managers and employees on a coherent channel strategy. It is less directly useful when the immediate task is writing a persuasive sentence or resolving a particular interpersonal argument. Those tasks need different books and skills, even when a better channel system can support them.

Who Should Read It

Internal communication professionals deciding which channels should do which jobs.
Managers of distributed or frontline teams whose employees receive information unevenly.
HR and digital workplace teams trying to agree on ownership, access and employee needs.
Leaders who want evidence of understanding and useful action rather than a larger announcement count.
Readers choosing software should also obtain current security, accessibility, employment and technical advice; this is a communication guide, not a procurement specification.

Main Summary

O'Dea and Phillips argue that employee communication becomes ineffective when organizations treat each channel as a separate solution. An intranet, email list, collaboration space and employee app can all function technically while producing a confusing experience together. Their five-layer model names the connected work: Plan, Collaborate, Publish, Distribute and Discuss.

Planning establishes the purpose, audience and intended result. Collaboration concerns creating and agreeing the communication. Publication gives information a home. Distribution brings it to the appropriate people, while discussion creates opportunities for interpretation, questions and feedback. The authors explain in their interview that organizations often stop at publication. A document being available does not establish that its intended audience has received or understood it.

Discovery should precede the choice of platform. What employees need depends on their tasks, access, timing and working conditions. The same channel mix will not serve every organization or every employee group. A useful strategy examines gaps, overlaps and unclear responsibilities across the layers instead of assuming that a particular product fixes communication.

The book also shifts attention from launch to adoption. A new channel creates value when it becomes useful in employees' work. Measurement should therefore move beyond visits and opens toward the communication outcome being sought. Those activity measures can answer limited questions, but they cannot by themselves establish understanding, trust or action.

Governance becomes especially important when AI enters the system. In the authors' account, automation can assist more than writing: it can support planning, distribution and the interpretation of feedback. However, the information it draws on still needs accuracy, context and clear ownership. Human judgment remains necessary. The reader's practical task is to design a system in which reliable information reaches people, can be discussed and can be improved, rather than merely producing more content faster.

Key Ideas

1. Diagnose the connection between layers before buying another channel

The five-layer model is useful because it separates activities that can otherwise disappear inside the vague instruction to communicate. A team may be excellent at producing approved material but weak at helping employees find it. Another may distribute messages widely while leaving no clear place for a corrected version. The problem needs a more precise description than low engagement.

Use the model to examine one information journey. Our fictional Harbor Foods team is changing its shift-swap process. The policy team has agreed the rules, a PDF is on the intranet and a manager believes the task is finished. Employees still ask whether a swap needs approval because some never saw the email, and others have an older printed version.

Map what actually happens under each layer. Who sets the objective? Who checks the draft? Which copy is authoritative? How does each shift learn about it? Where can a worker ask a question and receive an answer that updates the shared guidance? Missing answers reveal different problems requiring different interventions.

This audit is our application of the authors' model, not a diagnostic instrument supplied by the book. It does not establish that one channel should perform only one function. A platform can support several layers, and several channels can support one layer. The aim is understandable responsibility and continuity: each necessary activity happens, and the handoffs work for the people using the information.

2. Start discovery with the employee's task and working conditions

In their interview, the authors emphasize understanding who people are, what they do and what they need before designing the channel mix. Existing technology and vendor demonstrations are an incomplete starting point. They can make a team debate features before agreeing on the problem those features should solve.

For Harbor Foods, an office-based planner and a night-shift worker may need the same policy but encounter it differently. The planner can search a desktop intranet during work. The worker may share a terminal, have a short break or need an answer before the supervisor changes shift. A message that reaches both accounts has not necessarily given both people a workable opportunity to use it.

Our discovery worksheet asks for a recent example of the task, the question the employee needed to answer, the point at which they needed it and the constraints around access. Observe the actual route where possible. Ask where people go when the official route fails. An informal workaround can reveal a useful practice or a gap; it is not automatically evidence of employee resistance.

Then compare groups without reducing everyone to a demographic label. A role, location, disability, language need or contractual boundary may affect the communication experience, but a category alone does not tell you the solution. Test proposed changes with affected employees and appropriate specialists. Discovery supports a better decision; it does not replace consultation, accessibility work or the responsibilities attached to a formal policy change.

3. Give reliable information a home, and design how it will travel

Publication and distribution are distinct layers. O'Dea and Phillips argue that communication often fails when organizations stop after making content available. The useful question is both where the information lives and how the appropriate person will encounter it at a relevant moment.

Harbor Foods could maintain one current shift-swap explanation with a named owner and a visible revision date. A supervisor briefing, an email and a notice beside the shared terminal might each point people toward that explanation. This is our hypothetical design, not a recommendation to use those exact channels in every workplace. The choice depends on the discovery findings and on what employees can actually access.

Consistency does not require identical wording everywhere. A short reminder may serve a different purpose from detailed instructions. However, the reminder should not quietly alter the rule, omit an important exception or send people to an obsolete document. Before distribution, check which facts must remain consistent and who can approve a correction.

A practical test is to ask an employee to find the answer to one ordinary question without coaching them through the route. Note where uncertainty arises. If the reminder is clear but the destination is inaccessible, rewriting the reminder will not solve the access problem. If the destination is current but several competing copies circulate, ownership and maintenance need attention. Treat the whole journey as the unit of improvement, while keeping necessary offline and accessible alternatives available.

4. Make discussion and feedback part of delivery

The Discuss layer gives employees a way to make sense of information, not simply react to a finished announcement. In the authors' model, questions and feedback are connected to the wider system. They can reveal that an explanation has not met a user need and should influence later planning.

Imagine that Harbor Foods workers repeatedly ask whether a swap between departments is permitted. The policy owner may think the wording is obvious. Repetition is nevertheless evidence that the present explanation is not working for those employees. A useful response includes answering the question, checking whether the underlying rule is settled and improving the shared explanation when appropriate.

Our suggested feedback record contains the question, the responsible person, the answer's status and the place where the eventual answer will be made available. Keep a distinction between a question requiring clarification and a request to change the policy. The communication team should not promise a policy change it cannot authorize, but it can explain how the request will reach the decision-maker.

Open comment boxes are not the only form of discussion. Small-group briefings, manager conversations, accessible questions channels or representative structures may be more suitable. Confidential or sensitive concerns may require a protected route instead of a public thread. The test is whether employees have a usable way to raise relevant uncertainty and whether the organization closes the loop honestly. Counting comments without examining what happened to the questions gives an incomplete picture.

5. Measure useful adoption and protect the information behind automation

O'Dea and Phillips distinguish launching a channel from creating value through its use. Their discussion also challenges the assumption that a platform dashboard measures the communication outcome an organization actually needs. Visits and opens can describe activity without showing whether employees can do their work more effectively.

For the shift-swap example, Harbor Foods might examine whether workers can find the current process, explain when approval is required and complete an ordinary request correctly. These are our proposed learning measures. They would need an appropriate baseline and a fair way to distinguish communication problems from confusing rules, staffing constraints or technical defects. A change in a number alone does not identify its cause.

The same discipline matters when adding AI. A tool that summarizes several inconsistent policy copies may reproduce the confusion more fluently. The authors emphasize the importance of accurate source material and governance. Before relying on generated explanations, identify the authoritative information, its owner, its review cycle and the route for correcting an error.

Do not treat automation as a substitute for a person who can answer an unresolved question. In a consequential employment situation, a plausible response can still be wrong or incomplete. Keep human review and appropriate specialist advice available. A smaller, well-maintained information base with clear accountability may be more useful than a larger pile of material that nobody is responsible for maintaining. Adoption and automation both depend on that underlying usefulness.

Practical Takeaways

Select one recurring employee question and map its actual journey through all five layers.
Ask employees to demonstrate how they find an answer instead of relying only on reported satisfaction.
Record the working conditions that affect access, including shared devices, shift timing and accessible formats.
Name the authoritative information source and the person responsible for keeping it current.
Check that each short announcement points toward a usable and current explanation.
Assign a route and owner for unanswered questions before distributing a consequential message.
Pair activity measures with a specific task or understanding check appropriate to the communication goal.
Review source accuracy and correction procedures before using AI to summarize employee information.

How To Apply It

A small audit of one information journey

Begin with a bounded problem, such as employees misunderstanding a new shift-swap rule. Avoid starting with a proposal to replace every communication channel. Write the decision or action employees need to take, which groups are affected and what currently prevents them from doing it.

Use five rows headed Plan, Collaborate, Publish, Distribute and Discuss. For each row, identify the work being done, the owner, the employee-facing result and the handoff to the next activity. Include the route back from questions to a revised explanation. Ask people from the affected roles to check whether this map resembles their experience.

Choose one gap that can be improved within the team's authority. For example, the current policy may need a clearer route from a printed reminder to an accessible authoritative copy. Test that route with several affected employees and record what you learn. A successful small test supports further investigation; it does not establish that every employee group has been served.

After a defined review period, compare the same task and question with the baseline. Record unresolved problems that belong to policy, systems or management decisions rather than claiming that communications can repair them alone. The point of this exercise is to coordinate useful work and learn from its effect.

Limits and companion reading

The authors offer a strategy for employee channels, not a universal platform ranking. Software capabilities, security requirements and employment obligations vary and need current specialist assessment. Their enthusiasm about AI should also be read alongside the conditions they emphasize: sound information, ownership, judgment and governance.

For the sentences inside a message, Writing for Busy Readers is a more focused companion. For the conversational part of a briefing, The Surprising Science of Meetings addresses another part of the employee experience. Better channels can support those practices; they do not make clear writing or thoughtful meetings unnecessary.

Notable Ideas — paraphrased

A channel becomes useful through the information journey it supports.
Making something available is different from helping people use it.
Employee questions can improve the next communication plan.
Automation needs dependable source information and accountable people.

Best Related Books

Writing for Busy Readers — a closer look at making a particular message easier to understand and act on.
The Surprising Science of Meetings — useful when discussion and briefings are an important part of the channel mix.
Listening Well — a companion for the attention and understanding required when receiving employee concerns.
The Art of Gathering — relevant to designing purposeful occasions for people to meet and make sense of information together.

Internal Links

See all recommended communication books