Open the moment it arrives. Act the moment it opens.
That is how the industry has refined itself.
At 25h, I decided not to use urgency.
One morning, a discomfort
One morning, I was reviewing the visual design of a sign-up page.
The AI suggested what you would expect: a depleting capacity bar, a scarcity number, a countdown that nudges the reader to move. Classic, well-tested patterns.
In that moment, I put the discomfort into words.
"No scarcity bar. No urgency-driven visuals."
A few hours later, I rewrote it more clearly.
"Please be careful with how we design email. It is an act that takes time from the recipient. Pushing people to read is off-limits. I would rather say: read this only if you happen to have time to spare. Human review is also necessary."
That posture became the axis of every channel I publish on.
Email, as a medium
Email enters the recipient's time without asking.
The sender chooses when it arrives. The recipient is given no choice about when to read. That asymmetry is built into the medium from the start.
The mainstream of the industry has taken that asymmetry for granted, and refined a design around "open it the moment it arrives, act the moment it opens." Urgency, scarcity, fear of missing out. Thirty years of validation, and it does work.
But working does not, by itself, make it a reason to use it at 25h.
It collides with the principles
At 25h, one question sits at the center.
"Does this generate an hour for someone?"
Writing built on urgency is, by definition, not designed to give time. It is designed to extract a response. The principle and the design point in opposite directions.
It also collides with extracting value from process. Urgency-driven writing aims at the reaction itself, not at what happened, what was considered, what changed. Writing it down quietly is the opposite of what urgency does.
It collides with keeping density high and trimming to the essence. "Don't miss this." "Limited." "Must read." Those phrases carry no information of their own. They simply inflate the text.
Looked at from several angles, not using urgency is the choice that stays consistent with the rest.
Separating facts from urgency
Even so, there are facts that need to be communicated.
Number of seats. Price. Closing date. If those are not shared, the reader assumes the door is always open.
So I drew a line. Stating the facts is fine. Pushing for speed is not.
"There are seats on a first-come basis." A statement of fact, fine.
"Apply now, only a few left!" Urgency, not fine.
"The price is as follows." A statement of fact, fine.
"Special price, today only!" Urgency, not fine.
State the facts. Leave the response to the reader. Do not rush them.
One axis across every channel
Email, newsletter, landing page, X. There are many places to publish from.
If the policy shifts by medium, the tolerance starts to drift. When it drifts, the overall impression turns blurry.
So I applied the same posture across every medium. The look of the landing page, the wording of the newsletter, the cadence of an X post — all decided through the same "no urgency" filter.
The judgment criterion becomes one. There is no need to redesign per medium.
Protect it with structure, not willpower
If the writer's awareness is the only safeguard, the moments where one wants to hurry, or to chase a reaction, will sneak in a small dose of urgency. Designs that depend on willpower break down in the long run.
So I built the safeguard into the structure itself. Before a draft goes out, it is checked mechanically for urgency phrases. "Now." "Limited." "Don't miss this." "Must read." "Only N hours left." If any are flagged, the draft is held.
Not awareness. Structure.
Naming the quiet posture
As a measuring stick, I kept the original phrasing.
"Read this only if you happen to have time to spare."
That distance became the measuring stick for the newsletter's voice. When the writing wavers, I bring the sentence back. "Would someone with time to spare open this, and find themselves reading to the end?" That question becomes the judgment.
The form of the question is the editing axis.
Accepting the cost in reactions
Whether writing without urgency lowers reactions is something to be tested. In theory it likely does. The mainstream has refined itself around urgency for decades.
Even so, 25h takes the no-urgency side.
The reason is simple. A reader who responds to urgency is a reader who responds to urgency. The next message has to keep pushing, or that reader drops away. The only way out is to keep escalating.
A reader who stops and reads is a reader who stops. The next message will be read in the same posture. The dialogue continues at a higher quality.
A short-term reaction, or a long-term dialogue. 25h chooses the latter.
What "human review is also necessary" means
The closing line of that morning message carried another important phrase.
"Human review is also necessary."
The voice of email is not something AI can finalize on its own, at least not yet. For now, AI drafts and I revise, back and forth. Until the voice stabilizes, human judgment stays in the loop as a non-negotiable step.
No rush to full automation. Where AI could drift, structure holds it in place.
Quietly delivered
An email arrives. The reader opens it. Reads to the end. After closing it, something has shifted, a little. That is enough.
No rush. No urgency. State the facts. Leave the judgment.
If you happen to have time to spare, please read.
Top comments (0)