Search your inbox for the word "urgent." Count how many of those messages actually were. For most people the ratio runs somewhere between one in ten and one in fifty — and the one time it was real, the failed payment or the contract expiring at midnight, you probably read past it once before it registered, because your eye had already learned to skip that word.
That's not a personal failing. It's what happens to any signal that costs nothing to send and something to ignore.
The boy who cried wolf, at inbox scale
The mechanism is old. Someone discovers that marking a message "URGENT" gets it opened faster. It costs them nothing to add the word, so they add it every time, not just the times it's true. Other senders notice the trick working and copy it. Multiply that by every inbox on earth and you get where things stand now: urgency-as-label is common enough that it has stopped correlating with urgency-as-fact, and readers have adjusted their behavior accordingly — mostly by ignoring it.
The fable is usually told as being about the liar's punishment. The part that gets skipped is the ending: the wolf actually does show up. Crying wolf doesn't just spend down the liar's credibility. It spends down the message that was true, the one time it mattered, because the village had already stopped listening by the time it arrived.
Tone is free, which is why it stopped working
Exclamation marks, ALL CAPS, "ASAP," the red flag icon, the reply-all "sorry to bump this" — none of them cost more to type on an invented emergency than on a real one. A signal that cheap can't carry information, on economic grounds alone, before anyone even gets around to lying with it. If raising your tone were expensive, it would mean something. It isn't, so it doesn't.
AI drafting makes this specific failure worse, not better. An assistant can produce a breathlessly urgent paragraph exactly as fast as a calm one, which means turning up the tone dial got even cheaper right as more messages arrive already composed by something else. Automating a signal that never carried information just means the fake version now ships faster than the honest one used to.
What a checkable claim looks like
Compare urgency to a field that already works. Ask someone for a "decision" versus an "opinion" versus a "review," and the label is checkable afterward — did they actually decide, or did the ask bounce back three rounds of clarifying questions dressed as an answer? People notice when someone's "decisions" never resolve, and they adjust how much weight that person's asks carry next time. How to ask for a decision is built on exactly that kind of accountability.
Urgency has never gotten the same treatment, because it was never a discrete claim. It was a font choice, and font choices don't leave a record. Nobody remembers, three weeks later, whether Tuesday's "URGENT" actually needed same-day attention, because there was nothing to check it against. Make urgency a stated field instead of a tone, and the claim becomes something you can hold against what actually happened afterward — the same way a "decision" gets held against whether one actually got made.
An honest field, not a tone effect
This is the shape a briefing uses: urgency sits next to the response shape — decision, opinion, review — as its own stated field on the ask, not as a property of the prose around it. There's no exclamation mark to reach for, because the structure already asks the direct question: how urgent is this, honestly?
That doesn't guarantee an honest answer. What it changes is the cost of giving one. Writing "not urgent, next week is fine" takes exactly as little effort as writing "need this today," so the only reason left to inflate it is the same reason people always inflated it — except now the claim is specific enough that a reader, or a reader's assistant, can weigh it on its own instead of parsing how breathless the surrounding message sounds. Respecting the reader's time depends on this same honesty: a field only helps if the rest of the message is telling the truth about what it's actually asking for, too.
Structure can't fix a liar
A field is not a lie detector. Nothing stops someone from marking "urgent" on a message that isn't, the same way nothing ever stopped three exclamation marks on a newsletter. What changes is that the claim becomes discrete enough to check — against what actually happened, against how that sender's asks have gone before. That check is a habit, not a piece of software. It takes a reader actually noticing the pattern and adjusting trust accordingly: the unglamorous work of remembering who was straight with them last time.
A system can make honest urgency cheap to state. It can't make anyone want to state it honestly, and it can't do the remembering on a reader's behalf. That part stays cultural, which means it stays on us.
The fix for the boy who cried wolf was never a better wolf-detector. It was a village that kept score. Connect your assistant and give urgency somewhere honest to live — a field it fills in truthfully, not a tone it reaches for.