Quantifying the hidden cost of repetitive communication

Repetitive communication almost never shows up labelled as waste.

Nobody announces "we're going to repeat ourselves now." It hides inside alignment meetings, inside "let me just double-check that," inside the third time the same person explains the same context. Because no step in the process is called repetitive communication, it never appears in any cost category either.

The result: everyone feels that communicating is exhausting, and nobody can produce a number.

Three shapes it takes

Break it apart first, because each shape is measured differently.

1. Alignment cost. Something two people could have settled between themselves instead needs a four-person meeting. The cost isn't the meeting's length. It's that the context switch of N people gets billed to it.

2. Reconfirmation cost. The same thing gets confirmed more than once. The usual trigger is blurry ownership — the person confirming isn't sure their confirmation counts, so they find someone else to confirm it too.

3. Repeated-context cost. The same background gets explained again to a different audience. This one is the most expensive, because what it consumes is the team's scarcest resource: the time of the people who actually hold the full context.

Why it usually can't be calculated

Because it isn't a category anyone collects. You won't find a "repetitive communication" line in the books, and you can't survey your way to it — ask people how much of their day goes to repeated communication and the answer depends on how their morning went.

There is a workaround: structure can be computed from metadata, and structure happens to track repetition closely.

The key premise is metadata only — who interacted with whom, when, through which channel, how often. No message content is needed to compute the three measures below.

Three measures that fall out of structure

1. Round-trip ratio

The ratio of interactions in each direction between the same pair.

In healthy collaboration, A reaching out to B and B reaching out to A are roughly balanced (ratio near 1). When that ratio leans hard to one side over time, the other side is usually absorbing rather than collaborating.

When both directions are high — the pair trading messages many times a day — that is the case most worth looking at. More often than not it doesn't mean the two get along well; it means the work is bouncing between them. The usual cause is that neither has decision authority, or the acceptance criteria were never made explicit.

2. Hop length

How many hands a piece of information passes through, from originator to the person who acts on it.

Ideally this is 1 or 2. At 4 or more, every hop introduces distortion and delay — and nobody along the way is deliberately stalling. That's just what the structure grew into.

3. Redundant coverage

The same information reaching the same person through several channels at once.

A change gets emailed, posted in the group chat, and mentioned in the meeting. Each channel looks reasonable on its own — who knows which one people check. Together it's triple the cost.

Redundant coverage isn't automatically bad: three-way delivery for a critical change is prudent. The test is whether the change's importance justifies the coverage. Everyday low-impact syncs running on triple coverage is pure waste.

Turning it into time: a workable formula

Structural measures alone aren't enough. Managers want hours.

The conversion is simple:

time cost ≈ number of interactions × per-item handling time

Per-item handling time includes reading, thinking, replying — plus the part most often forgotten, the context switch. Add those up and instant-messaging channels land around 2 to 3 minutes, email around 4 to 5, and meetings at full duration. Handling costs differ by channel, which is why the same message carries a different price in chat than in email.

A realistic example:

A 12-person team. One module owner receives roughly 30 messages a day from the same sub-group. The diagnosis shows about 60% of them are reconfirming things already confirmed.

18 messages × 3 minutes ≈ 54 minutes per day

That's around 11% of a working day — and it's fragmented 11%, which is more expensive than the same total in one block, because it breaks the continuity deep work needs.

This person spends close to two and a half days a month doing work they have already done. That number appears on no report anywhere.

From cost to action

Once the numbers exist, the actions tend to be clearer than expected. Three shapes, three moves:

• Lopsided round-trip ratio → check where decision authority sits. Most back-and-forth isn't a communication problem, it's an unresolved question of who decides.
• Overlong hop length → add a direct edge so the originator and the executor connect, instead of inserting a coordinator between them.
• Excessive redundant coverage → tier your channels. Define which changes require multi-channel delivery and which need only one.

None of these require anyone to change their attitude or ability. They are structural changes — and once made, the frequency of repetitive communication should drop measurably within a month. That's also how you verify the change worked.