Study guide
12.2 Communication Channels: One-Way, Two-Way, Lean and Rich
APMG Change Management Foundation Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: The v3 Foundation Exam and the Organisational Context
1.1 Exam Structure, the Five Syllabus Areas and the Certification Path 1.2 Scene Setting: External and Internal Factors Shaping Change 1.3 Change Management, Benefits and Dis-benefits
2 Chapter 2: Understanding the Change Context
2.1 Kelman's Three Levels of Adoption 2.2 VUCA and the Cynefin Framework 2.3 Planned Change versus Emergent Change 2.4 Systems Thinking in Change 2.5 Organisational Culture and Its Three Levels
3 Chapter 3: Diagnosing and Structuring the Change Approach
3.1 Lewin's Force Field Analysis 3.2 Co-Design 3.3 The ADKAR Model 3.4 Evolving the n-Step Process and Kotter's Eight Accelerators
4 Chapter 4: Delivery Strategy, Agile Practices and the Change Strategy
4.1 Delivery Strategy: Big Bang, Phased, Voluntary and Iterative 4.2 Agile Practices and Agile Change Practices 4.3 The Continuous Change Management Cycle 4.4 The Change Strategy
5 Chapter 5: People and Change — Individual Difference and Response
5.1 Differences in People and Personality Preferences 5.2 Neuroscience and Change: SCARF, Mindset and Insight 5.3 The Change Curve 5.4 Bridges' Transition Model
6 Chapter 6: Motivation, Resilience and Learning
6.1 Rewards, Punishment and Pink's Three Motivators 6.2 Positive Psychology, Resilience and Appreciative Inquiry 6.3 The Beckhard-Harris Change Formula and Schein's Two Anxieties 6.4 Competence, Learning and the Learning Dip 6.5 Learning Preferences: Kolb, Honey and Mumford
7 Chapter 7: Key Roles in Change Leadership
7.1 Key Roles in the Change Process 7.2 The Role of the Change Sponsor 7.3 The Change Agent's Role and Personal Influence 7.4 The Role of Local Leadership in Change
8 Chapter 8: Psychological Safety, Leadership and Culture
8.1 Psychological Climate and Psychological Safety 8.2 Carolyn Taylor: How Leadership Shapes Culture 8.3 Leadership Styles and Organisational Climate
9 Chapter 9: Teams and Change
9.1 Team Structures and Change Agent Networks 9.2 Tuckman's Stages of Team Development 9.3 Lencioni: Assessing and Growing Team Effectiveness 9.4 Harvesting the Value of Team Diversity
10 Chapter 10: Stakeholder Identification, Analysis and Engagement
10.1 Stakeholder Definition and Identification 10.2 Stakeholder Analysis, Segmentation and Empathy Mapping 10.3 Stakeholder Mapping and Sources of Power 10.4 Barriers to Engagement 10.5 Planning Stakeholder Engagement
11 Chapter 11: Communication Theory, Messaging and Emotional Connection
11.1 Communication Theory and the Communication Process 11.2 Barriers to Communication and Cognitive Biases 11.3 Messaging: Setting Context and the Tell, Sell, Include Approach 11.4 Appealing to Hearts and Minds
12 Chapter 12: Communication Channels and Planning
12.1 Ways of Communicating and VARK Language Style Preferences 12.2 Communication Channels: One-Way, Two-Way, Lean and Rich 12.3 Communications Planning
13 Chapter 13: Assessing Change Impact and Severity
13.1 Change Management as Risk Management and the Two-Step Assessment 13.2 Step 1: Categorising Impacts and Identifying Impact Areas 13.3 Step 1 Continued: Gap Analysis, Impact Profiles and Monitoring 13.4 Step 2: Change Impact Severity
14 Chapter 14: Resistance to Change
14.1 Causes of Resistance and Oreg's Four Neural Factors 14.2 Common Reasons for Resistance and How to Deal With Them 14.3 Building a Strategy to Manage Resistance
15 Chapter 15: Change Analytics and Exam Readiness
15.1 Measurement Types and the Change Delivery Scorecard 15.2 Building a Change Analytics Strategy 15.3 Exam Technique and Final Revision
12.2 Communication Channels: One-Way, Two-Way, Lean and Rich
Key Takeaways Explain This Topic AI
A channel is termed lean or rich depending on multiple cues, variety and format of information, and level of interactivity
Synchronous interaction happens at the same time and is faster and more dynamic, while asynchronous interaction has responses at different times
Leaner channels suit the tell and sell approaches, such as emails, bulletins, newsletters and broadcast announcements
Two-way, richer channels are required to fully engage people and have them participating
- Rich channel examples include discussion forums, lean coffee sessions and collaborative co-design workshops
- Last updated: September 2026
Communication channels differ along two related dimensions: whether they are one-way or two-way , and whether they are lean or rich .
What makes a channel lean or rich
A channel is termed lean or rich depending on three factors :
- Factor What it means
- Multiple cues How many signals travel alongside the words — tone, facial expression, gesture, immediacy
Variety and format of information Whether the channel can carry different kinds of content: text, image, demonstration, discussion
Level of interactivity Whether and how quickly the receiver can respond
Multiple cues is the factor most often tested. An email carries words and nothing else; a face-to-face conversation carries words, tone, facial expression, posture and immediate reaction. That is why difficult messages delivered by email land so badly — the receiver has only the words, and the words alone can support the most negative available interpretation.
Synchronous and asynchronous
Within interactivity, CM3 distinguishes:
- Synchronous — interaction can happen at the same time, is faster, dynamic
- Asynchronous — is interaction, but with responses at different times
Note that asynchronous channels are still interactive. A discussion forum where people reply over several days is genuinely two-way; it is simply slower. Asynchronous channels have a real advantage for reflectors and for people in different time zones, who can consider a response rather than having to react.
The channel spectrum
Leaner Richer
Examples Emails, bulletins, newsletters, broadcast-type announcements Discussion forums, lean coffee sessions, collaborative co-design workshops
- Cues Words only Multiple cues
- Interactivity Low or none High
- Reach per unit effort High — one message reaches thousands Low — a workshop reaches a room
- Suits Tell / Sell Include — fully engaging people and having them participating
CM3 states the mapping explicitly: leaner channels are appropriate for the tell/sell approach — emails, bulletins, newsletters, broadcast-type announcements. Two-way, richer channels are required to fully engage people and have them participating , such as discussion forums, lean coffee sessions and collaborative co-design workshops.
Choosing a mix
The operative word is mix . Neither end of the spectrum is better; they do different jobs.
Lean channels are efficient and necessary. You cannot run a workshop for 3,000 people, and much change information genuinely is broadcast information — dates, availability, where to find things. Using a rich channel for simple factual content wastes everyone's time.
Rich channels are the only way to achieve certain outcomes. Genuine participation, surfacing concerns, working through resistance, co-design and building commitment all require two-way interaction with multiple cues. A programme that tries to achieve engagement through newsletters has chosen a channel that cannot do the job, however well written.
The practical failure mode is using lean channels for rich purposes because they are cheaper and easier to evidence. "We sent twelve communications" is measurable; "we changed how people feel about this" is not, and the measurable activity displaces the effective one.
Matching channel to message
A workable set of rules:
- Message type Channel guidance
- Routine factual updates, dates, logistics Lean is appropriate and efficient
Explaining reasons and benefits to a broad audience Lean-to-medium, repeated, supported by richer sessions for those who want them
- Anything with significant personal impact Rich, and delivered by the immediate supervisor
- Bad news of any kind Rich, synchronous, never by broadcast email first
- Gathering ideas, co-design, working through resistance Rich and two-way; lean channels cannot achieve this
- Checking whether the message landed Two-way, whether synchronous or asynchronous
The rule about bad news is worth stating plainly. A restructure announced to affected staff by all-staff email removes every cue that would let people read the intent, gives them no route to ask the question they urgently need answered, and signals that the sender did not want to face them. The cost in trust exceeds anything saved in effort.
One-way and two-way
Richness and directionality are related but not identical. A channel can be rich and still one-way — a well-produced video message carries tone, expression and visuals but offers no route to reply. A channel can be lean and two-way — a comment thread on an intranet post is words only, but it is interactive.
The practical consequence is that adding interactivity is often cheaper than adding richness. A written update that ends with a named person and a real invitation to reply, where replies are genuinely read and answered, converts a one-way lean channel into a two-way one at almost no cost. Given that the fourth purpose of communication planning is checking how communication is being received, the cheapest available upgrade to most change communication plans is a working return path.
Sequencing channels
Channel choice is not a single decision per message; it is usually a sequence. A well-handled significant announcement typically runs:
Brief line leaders first, richly and in person , so they can answer questions rather than broadcast doubt
Deliver the announcement synchronously where the audience size allows, so people hear it directly and can react
Follow immediately with a lean written record , so the facts are available to re-read and cannot drift
Open a two-way route — sessions, forums, or a named contact — for the questions that surface after people have absorbed it
Return through rich channels for the groups whose impact is greatest
Getting the order wrong is more damaging than getting any single channel wrong. Publishing the written record before line leaders are briefed is the most common sequencing error, and it puts middle managers in the position of hearing about their own team's change at the same moment their team does.