Status updates fail even before they're read. They're structured for the writer — comprehensive, narrative, ordered by what happened — not for the reader, who has six other tabs open and a decision to make in four minutes.
The caveman board update flips the assumption.
The problem with "professional" updates
Professional updates optimize for completeness. Every context, every nuance, every qualifier. The writer feels thorough. The reader feels nothing — because the signal is buried in the structure.
The format does more harm than the content does good.
When you front-load context, you're asking the reader to do the work. When you explain before you conclude, you're betting that they'll follow you the whole way. Most won't. They'll skim to the bottom, miss the ask, and you'll be back in their inbox tomorrow.
What caveman communication actually is
Strip the sentence to its function.
Not: "Following the delayed delivery from our hardware vendor, which impacted downstream testing cycles, we are now two weeks behind original timeline projections."
Instead: Hardware late. Testing delayed. Two weeks behind.
Same information. Zero noise. Faster decision.
This is the Caveman board update — a compression format where every word justifies its presence. Problem. Status. Impact. Ask. That's the full taxonomy. Anything outside it is autobiography.
It works at any altitude. Exec sync, written async update, Slack message, weekly review. The format scales down; it doesn't scale up into bloat.
Those who need a neutral palette title in a corporate deck could call it the Compressed Business Update (CBU) — and the format has a name worth repeating.
Why operators resist it
It feels underdressed. Leaders worry it signals laziness or lack of depth. So they pad. They add context that wasn't asked for. They soften the risk. They explain the delay before naming it.
The irony: the caveman update requires more thinking, not less. You can't compress what you haven't understood. Vagueness hides in length. Clarity only survives compression.
If you can't reduce your update to four lines, you haven't finished thinking about it.
How to use it
Write your normal update first. Then cut it in half. Then cut it in half again. What remains is what your reader actually needs.
Lead with status. Follow with impact. Close with the ask or next action. If there's a risk, name it directly — don't build to it.
One pass. No hedging. No decoration.
The CBU scale: 1 to 10
Compression isn't binary. There's a dial — and where you set it depends on the audience, the stakes, and the format.
| Level | Name | Shape | When to use |
|---|---|---|---|
| CBU 1–2 | Polished prose | Full paragraphs, complete sentences, context present | Written memos, formal stakeholder reports |
| CBU 3–4 | Structured narrative | Short paragraphs, one idea per sentence, minimal padding | Weekly written updates, async briefs |
| CBU 5–6 | Board update | Bold heading + 1–2 sentences per item. Status, impact, action | Exec syncs, leadership reviews, recurring updates |
| CBU 7–8 | Bold text only | Heading carries the full update. No supporting sentence | High-trust teams, fast async pings, known-context updates |
| CBU 9–10 | Primitive | Near-wordless. Fragments. Real-time signal only | Slack at 11pm, 30-second verbal sync, crisis check-ins |
CBU 5 example:
- Hardware delayed two weeks — Vendor missed shipment. Testing pushed. Timeline risk flagged.
- Budget revised upward — Infra costs underestimated by 15%. CFO aligned. No blocker.
- Hiring on hold — Two dropouts this week. Reposting Monday. No impact to Q2 delivery.
CBU 10 example:
- Hardware late. Two weeks.
- Budget up. CFO knows.
- Two hires gone. Reposting.
Same update. Different density. Neither is wrong — the question is what the moment requires.
Most people operate at CBU 2 when their audience needs CBU 6. The gap between those two numbers is where decisions get delayed, follow-ups pile up, and readers stop reading.
Two angles of compression
The caveman update is usually treated as one thing. It's actually two. And confusing them produces updates that are short but still slow.
| Angle | What it cuts | Failure mode when missing | Example |
|---|---|---|---|
| Simplicity | Word complexity | Clear structure, heavy vocabulary — reader translates before processing | "Experiencing timeline variance" → "Late" |
| Parsimony | Word count | Plain language, too many sentences — right words, wrong volume | Three sentences that say one thing → one sentence |
Both matter. But they fail differently.
An update with simplicity but no parsimony reads like a children's book — clear words, too many of them. An update with parsimony but no simplicity reads like jargon-dense bullet points — short, but still opaque.
The best caveman updates run both levers simultaneously. Plain language, minimal count. Every word a decision.
decision.
Format is compression too
Compression isn't only about words. It's also about structure. The right format removes the need to read everything — it lets the eye land on what matters.
Bold + line. Bold heading. One sentence beneath. The heading names the topic; the sentence delivers the status. Fast to scan. Works when the reader knows the categories and just needs the update.
Hardware delayed — two weeks — testing impacted Vendor missed window. Testing pushed. Risk flagged to leadership.
Bold only. The heading is the update. No sentence beneath. Forces the writer to make the heading carry full weight — topic, status, and implication in one line. Works in high-trust environments where the reader will ask if they need more.
Hardware delayed — two weeks — testing impacted Budget revised upward — CFO aligned Two hires dropped — reposting Monday
Narrative compressed. Full sentences, but one per idea. No build-up, no conclusion paragraph. Reads like a ticker. Works for async updates where some context is genuinely needed but padding is still the enemy.
Hardware vendor missed the shipment window. Testing is pushed two weeks. Budget revised upward 15% — CFO is aligned and there's no blocker. Two candidates dropped this week; reposting Monday with no impact to Q2.
The format isn't decoration. It's a compression mechanism. Choosing the wrong one — narrative prose for a ten-item exec sync — adds cognitive load that the content never recovers from.
Use of compression in communication is not just a tool. Leaders who communicate in compressed, high-signal language train their teams to think the same way. The caveman board update isn't a writing trick. It's an operating norm.