Here is a sentence of the kind Slack and email are full of:
We experienced a database indexing latency issue that resulted in temporary query discrepancies.
Nobody reads that to the end. It is dense, hedged, and written to avoid exposing anything, which is exactly why corporate writing like it gets skimmed and ignored.
This is downstream of something larger than style: a shift in how people relate to their own thinking.
What we were actually measuring
For centuries we made a specific mistake: we treated intellect as identity. Schools, companies, and hierarchies got built around the analytical brain — we measured a person’s worth by their capacity to calculate, accumulate data, build logical systems, and process information quickly. You can see it in how we ran performance reviews, how we hired, and how we sorted kids in school.
Then we built a machine that does all of that better.
AI is what tested that assumption, and the assumption did not hold up. What we called “intellectual supremacy” turns out to have been, in large part, a sophisticated recording-and-recombination system — the kind of work a computer does without sleep, without burning out, without a coffee break. That is not a comfortable thing to sit with if your whole self-image was built on being the smart one in the room.
I do not think that is a crisis. I think it clarifies something.
The machine won the productivity race, and in doing so it drew a clean line around what is left to us. It runs in a loop of constant output. What it cannot do is pause, step outside that loop, and simply be present rather than process.
So the sentence about the database is a human imitating that loop: producing output, exposing nothing, transmitting data at someone. That is a losing game in a world already saturated with machine-generated text.
The alternative is to become what I will call Attention Engineers: people who design communication that does more than transmit data — that gives the listener room to actually be present instead of merely processed at.
Six stages, and only one of them does any work
Most communication is linear: it moves a set of facts from one head to another. What I am describing is closer to a loop. The goal is to lower the listener’s guard, open a gap of silence, and leave something behind that they actually took in rather than just heard.
The cycle runs through six stages, and they group into three movements.
Dismantling the defences
1. The intellectual hook: people defend their rational mind. Say something that contradicts what they already believe, and their analytical guard goes up immediately — they start scanning for the flaw in your logic before you have finished the sentence. So speak to that rational mind first, in clear, structured, logical language, and earn their attention before you get to the part that matters. A coherent intellectual frame keeps the analytical part of the mind occupied: it has something to evaluate, so it does not start arguing with you before you have made your point.
2. The cognitive tension build: once the intellect is engaged, build toward something specific. Introduce a narrative, a parable, or a logical premise, and lead the listener through it step by step, cause to effect. People look for patterns, and a clear progression makes the brain predict where it is going, which narrows attention and raises the expectation of a payoff.
3. The cognitive interrupt: just as the tension peaks, break it with a sudden, illogical 180-degree turn — the unexpected punchline, the contradiction, the twist that violates what the listener’s mind just predicted. When a pattern breaks that abruptly, the analytical mind has nothing prepared for it and stalls for a moment. The listener laughs, gasps, or simply stops, and in that moment the guard drops.
The pivot
4. The silent gap: the three stages above exist to produce this one. Words mostly matter for what they set up: the pause that comes after them. In speech, that is the sudden, unannounced pause mid-sentence. In writing, it is telegraphic phrasing and deliberate whitespace.
The mind was primed to expect the next logical piece. A gap where that piece should be catches it off guard, and for a moment it stops running ahead of you. The listener is simply there, in the pause, instead of already composing a response.
Doing this on purpose is harder than it sounds. Most people fill silence out of reflex, the moment it opens.
Planting the seed
5. The seed of communion: with the mental noise quieted, you can state the thing plainly instead of arguing for it — communication becomes something closer to communion. Put the core insight, or the actual direction you want people to take, into that open space. Because the interrupt already lowered the listener’s guard, they take in the point directly instead of immediately auditing it for holes. It lands as something obvious rather than something to be argued with.
6. The witness integration: the cycle closes by bringing people back to the practical task, changed by having been in the pause, rather than leaving them there. Bridge back from the quiet gap into whatever the message needs to accomplish. The listener returns to ordinary thinking, but they have had a moment of being present rather than reacting on autopilot. Do this consistently over many exchanges, and it builds a team that trusts each other more and reacts less defensively.
Running the cycle on a screen
None of this survives contact with Slack, Teams, and email unless you rewrite how you show up in those channels. Slack in particular rewards immediacy, and immediacy is exactly what erodes attention.
Writing between the lines means leaving room for the reader, not filling every line. Four rules do most of the work.
Rule 1: whitespace is the visual silence
Density is the enemy of attention on a screen. A colleague who sees a wall of text on Slack reads it as a chore before reading a word of it, and starts skimming defensively.
Treat your whitespace the way Osho treated his spoken pauses. Keep paragraphs to one or two sentences. Force a line break.
Let your key points sit alone, surrounded by empty space. It makes the reader’s eye stop, which gives the point room to land instead of blurring into the rest of the message.
Rule 2: address the questioner, not the question
When someone asks a frantic question at work — “Why is this project delayed?” — they are rarely only asking for data. They are usually projecting their own anxiety and their need for reassurance.
Look past the literal text to the person behind it. If a stakeholder is panicking, do not open with a spreadsheet. Address the underlying state first: “I hear the pressure we are under for this release. Let’s look at how we can protect your team’s sanity while we solve this.” Naming the pressure directly tends to lower the defensiveness faster than answering the literal question does.
Rule 3: every word costs $100
Verbose writing tries to justify its own length. Clear writing does not need to. Edit your emails as if every word cost you a hundred dollars out of your own pocket. Cut the corporate padding — the delvings, the touching bases, the important to notes. Get the message down to what it needs to say, and say that plainly.
Rule 4: deploy the unexpected punchline
Corporate writing is full of the same tired pleasantries, and people read past them without registering a word. So break the expectation: use self-deprecating humor, direct honesty, or a sudden change in register to make people actually read what you wrote.
Which brings us back to the database sentence at the top. Here is the same outage, written by someone running the cycle:
Our team spent six hours analyzing our database architecture yesterday, only to discover we have been querying the wrong server for three weeks. The good news is, we now know we have a world-class endurance for staring at blank screens. Here is how we are fixing the routing today.
Same facts. The difference is that this one gets read.
What is left
As AI keeps automating the parts of work that are purely intellectual, the value of pure processing keeps dropping. What is left is the most present person in the room, not the smartest one. We do not need to keep competing as second-rate logical machines.
Practicing this cycle is a practice in presence: dropping the reflexive armor, stepping out of the script, communicating from somewhere less mechanical. Do it consistently and you get more than better messages — you get teams that trust each other, because they have actually been listened to. That is an edge, not a nice-to-have: whether the next report lands, whether the next hire trusts you, whether the team actually moves when you ask it to.
Find your silent gaps. Let the machine do the talking.