Communication Plans: Radio Checks Between Basecamps

Opening Scene

Well-run expeditions schedule radio checks between camps at fixed times, regardless of whether anything eventful has happened, because silence on the radio is itself dangerous information, and basecamp needs to know status even on a quiet day. An AI rollout with a genuine communication cadence — regular updates whether or not there’s dramatic news to share — works the same way, and the organizations that skip it tend to find out how much that silence unsettles people only after the fact.

In Plain English

A communication plan for change management is a scheduled, predictable cadence of updates — not just reactive announcements when something goes wrong or unexpectedly right. A predictable cadence builds a kind of trust that ad hoc, purely reactive messaging never quite manages to earn.

The Old Way

Before scheduled communication cadences were standard, updates tended to appear only in response to events:

Updates were reactive, appearing only after a failure needed explaining or a success needed celebrating.
Silence between announcements left people filling the gaps with speculation, usually the worst-case kind.
Communication flowed in one direction, down from leadership, with no reliable channel back up.

A scheduled check-in, held even on an uneventful day, is what actually closes that gap.

What’s Changing (and Why AI Is the Reason)

Regular, scheduled check-ins — even brief ones — are becoming standard practice regardless of whether there’s dramatic news to report.
This connects to the work covered in this content library’s dedicated AI governance and regulation series, since transparent, scheduled reporting on AI system status increasingly overlaps with the governance reporting that series covers.
Because AI tool behavior and capability shift frequently, regular check-ins have also become how organizations catch drift and confusion early, before it compounds into something larger.

The Metaphor, Fully Extended

The Expedition	Change Management Concept
A scheduled radio check at a fixed time, rain or shine	A predictable, scheduled communication cadence
Silence on the radio read as a warning sign	Long gaps between updates read as trouble, even when there isn’t any
A two-way channel, camp to basecamp and back	A communication plan with a reliable channel back up to leadership
Reporting status even on an uneventful day	Sharing routine progress updates, not just wins and failures

For Beginners: What to Actually Do

Notice whether updates about an AI rollout come on a predictable schedule or only when something goes wrong.
Use whatever upward channel exists — a survey, a standing meeting — even just to report routine, uneventful status.
Treat prolonged silence about a rollout as worth asking about directly, rather than assuming the worst quietly.

For Practitioners and Leaders: The Deeper Layer

Build a scheduled communication cadence into the rollout plan from day one, independent of whatever news exists that week.
Establish and actually use a reliable channel for feedback to travel back up to leadership.
Use regular check-ins to catch confusion or tool drift early, before it has a chance to compound.

Quick Recap

A real communication plan runs on a predictable schedule, not reactive announcements alone.
Silence between updates tends to get filled with speculation, not patience.
Two-way channels matter as much as the downward flow of updates.
Scheduled check-ins also help catch AI tool drift and confusion early.

Where This Fits in the Series

Article 6 covered the early adopters whose real experience shapes the rest of the climb. Article 7 covers the communication infrastructure — the radio checks — that carries that experience, and everything else, reliably between camps. Article 8 turns to what those radio checks are often used for: reporting a storm, and figuring out how to handle a genuine setback without losing the team.