All skills

comms-audit

Audit organizational communications — channel effectiveness, message clarity, overload, and actionable improvement plans.

Use this skill

  1. Read the full skill below — it’s all right here on this page. When you like it, hit copy.
  2. Paste it into a chat with Muse and add: “Please use this skill whenever I ask about comms audit. Remember it for our future conversations.”
  3. That’s it. Muse follows the playbook for relevant tasks, and you approve anything it does.
View raw on GitHub ↗

The full skill

Overview

A communications audit systematically evaluates how an organization communicates: which channels work, where messages get lost, how overloaded people are, and what to fix. This skill covers running audits — stakeholder interviews, channel inventories, message testing, overload measurement — and turning findings into prioritized improvements.

A communications audit systematically evaluates every channel, message, and audience touchpoint: what is being sent, to whom, how often, and to what effect. It exposes redundancy, gaps, off-brand messaging, and compliance risks — and produces a prioritized roadmap for fixing them. Organizations should audit annually; fast-growing ones, twice a year.

When to use

  • Diagnosing communication breakdowns

  • Reducing information overload

  • Evaluating channel effectiveness

  • Preparing for reorganization or tool changes

  • Improving leadership communications

  • Justifying comms investments

  • Preparing for a rebrand or messaging refresh

  • Diagnosing why employees feel uninformed (or overwhelmed)

  • Consolidating tools after mergers

  • Meeting regulatory communication requirements

  • Post-merger communications integration

Core concepts

Channel inventory. Catalog every channel: purpose, audience, owner, frequency, and volume. Most organizations discover 2–3x more channels than leaders thought existed — and massive overlap. The inventory alone often reveals the problem.

Effectiveness dimensions. Reach (does the message arrive?), comprehension (is it understood?), action (does it drive behavior?), efficiency (cost in time/attention), and satisfaction (do people value it?). A channel can have great reach and terrible comprehension — measure all five.

Overload measurement. Volume per person per channel, interruption frequency, after-hours load, and perceived overload (surveys). Quantify: "the average engineer receives 47 notifications daily across 6 channels" makes the case for change.

Message testing. Sample real communications: can recipients state the key point? The required action? The deadline? Test with 5–10 people per major message type. Most organizational messages fail basic comprehension tests.

Stakeholder interviews. Talk to senders (leaders, teams) and receivers across levels and functions. Ask: what works, what's noise, what's missing, what would you kill? Patterns emerge fast — 12–15 interviews usually suffice.

Governance gaps. Who owns each channel? Who can broadcast? What are the norms? Audits typically reveal governance vacuums — channels with no owner, no rules, and no measurement.

Channel inventory. List every channel (email lists, Slack channels, intranet, town halls, newsletters, signage, push, SMS) with: owner, audience, cadence, purpose, and metrics. Most organizations discover 30–50% more channels than leadership believed existed — shadow comms run by well-meaning teams. The inventory alone usually reveals the biggest wins: duplicate newsletters, orphaned channels, conflicting messages. Message effectiveness. Sample recent communications per channel and score: clarity (one main point?), relevance (right audience?), actionability (clear next step?), tone (on-brand?), timing (right moment?). Pair with audience surveys: which channels do you read? Which do you ignore? What do you wish you knew? Perception data beats assumption every time. Compliance and risk. Check: opt-in records for marketing messages, accessibility of critical communications, record-keeping for regulated industries, data privacy in distribution lists, and crisis communication readiness. Audits frequently surface quiet compliance gaps — fix them before regulators or incidents do.

Practical workflow

  1. Scope. Which org unit, which channels, what questions to answer. Timebox: 3–4 weeks for a focused audit. Get sponsor commitment to act on findings.
  2. Inventory channels. List everything: email lists, chat channels, meetings, newsletters, dashboards, all-hands, wikis. For each: purpose, owner, audience, frequency, volume.
  3. Gather data. Analytics (volumes, open rates, attendance), surveys (perceived effectiveness, overload), interviews (12–15 across levels), and message testing (comprehension checks on real messages).
  4. Analyze. Map findings to dimensions: reach/comprehension/action/efficiency/satisfaction. Identify: redundant channels, overloaded audiences, broken messages, governance gaps, and missing communications.
  5. Recommend. Prioritized actions: quick wins (kill dead channels, fix top 3 message templates), structural (consolidate overlapping channels, establish governance), and strategic (new channels, leadership comms cadence). Each with owner and timeline.
  6. Implement and re-measure. Execute quick wins immediately (builds momentum), phase structural changes, and re-audit key metrics in 6 months. Audits without implementation are expensive theater.

Audit report structure: executive summary → methodology → channel inventory → findings by dimension → overload analysis → recommendations (prioritized) → implementation roadmap → appendix (data).

Audit process (4–6 weeks): week 1–2: inventory channels and collect samples → week 3: stakeholder interviews (15–20 across levels) + audience survey → week 4: analysis and scoring → week 5: findings workshop with leadership → week 6: prioritized roadmap with owners and timelines. Roadmap prioritization: quick wins (consolidate duplicate newsletters, fix broken subscriptions) → structural fixes (governance, ownership, calendars) → strategic shifts (new channels, rebranding). Report progress quarterly — audits without follow-through breed cynicism about the next one.

Common pitfalls

  • Audit without mandate. Findings ignored because no sponsor committed to action. Secure commitment upfront.
  • Only surveying. Surveys show perception; combine with analytics and message testing for reality.
  • Boiling the ocean. Auditing everything at once. Scope tightly; go deep on what matters.
  • No baseline metrics. Can't prove improvement without before-data. Measure first, then change.
  • Recommendations without owners. "Someone should fix email." Named owners and deadlines, or nothing happens.
  • Ignoring culture. Recommending tools/processes the culture won't adopt. Fit recommendations to how people actually work.
  • One-and-done. Auditing once, never following up. Re-measure to prove value and catch regression.
  • Audit as blame exercise. Using findings to punish channel owners. Frame as system improvement — blame guarantees the next audit gets stonewalled.
  • Boiling the ocean. Trying to fix everything at once. Three prioritized initiatives per quarter is the sustainable pace.
  • Ignoring shadow comms. Auditing only official channels. The unofficial ones often reach more people — bring them into governance or shut them down deliberately.
  • One-and-done. Auditing once and shelving the report. Build the audit cadence into operating rhythm.
  • Survey bias. Only surveying engaged employees. Stratify samples — the silent majority's view matters most.
  • Recommendations without owners. Findings with no accountability. Every recommendation gets an owner and deadline.
Source: GitHub ↗License: MITAuthor: awesome-muse-skills