DEV Community: Noēs (25h)

Why I chose not to use urgency

Noēs (25h) — Tue, 02 Jun 2026 16:41:15 +0000

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.

Nine months without a rewrite

Noēs (25h) — Wed, 27 May 2026 21:19:08 +0000

When was your company's MVV last rewritten?
At 25h, it has stayed untouched for nine months.
Not because it is unfinished.

What it means to not rewrite

Nine months.

That is how long 25h has run on the same MVV.

The words written on June 11, 2025 still sit where they were placed. Same location, same shape.

The fact of not rewriting is itself worth writing down.

The day it was decided

June 11, 2025.

In the first week of founding 25h, the first piece of work was to formulate the MVV.

I described my background, my temperament, and my values to an AI, and we shaped the language through dialogue. Mission, vision, values.

It was decided that same day.

"Efficiency for the sake of preserving margin."
"Margin for the sake of working on what is essential."

Something settled the moment those words appeared. The journal records that.

It also records the response — "That landed deeply."

That core has not shifted since. May 2026 looks at it and finds the same shape.

Systematization is a means

That day, "systematization" was proposed as one of the values.

I caught the discomfort immediately, and put it into words.

"Systematization is only one means."
"It is not a value."
"Whether to systematize, stop systematizing, or change it — all of them are means."

This correction mattered.

Being sensitive to the granularity of values. Refusing to conflate means and ends.

That itself was already an expression of the 25h thinking style.

In the final values, the word "systematization" does not appear. What remains instead is an orientation toward the freedom of choice.

Nine months of asking

After the MVV was formulated, many efforts unfolded.

We named the 25h production process. We hypothesized a management team composed only of AI.

We deepened the idea that margin is not consumed but produced. We defined failure as anything short of fatal.

Each time, the work was checked against the MVV.

"Does this align with the Mission?"
"Does this contradict Time is Autonomy?"

After the check, every effort connected back to the MVV.

The thing that did not change

There is a narrative that says the MVV evolved over nine months.

A story of refinement through trial and error.

It is half true.

There was refinement of expression. Each concept was extracted as an atomic note. A guardian clause was added. Operation as a judgment standard began.

But the core did not move.

What was put into words on June 11, 2025 still runs today. "Efficiency for the sake of preserving margin" points in the same direction as the highest principle of 25h now.

What February 20, 2026 meant

The confirmed MVV file was created on February 20, 2026.

This was not the day the MVV was completed.

It was the day on which the MVV had been sufficiently demonstrated to function as a judgment standard.

Not declared first as a manifesto, then enforced. Verified through actual judgments, then formalized.

That sequence matches the design style of 25h.

The guardian clause was added on the same day. "Does this produce someone's hour?"

That question became the gate every output passes through.

The MVV graduated, on that day, from thought to operational rule.

A fixed core allows the derived to move

There is value in the core of the MVV not moving.

As derived efforts multiply, the consistency of judgment is what gets tested. "Why am I doing this?" "Is this 25h-like?"

Those questions need a place to return to. That place is the MVV.

Expression evolves. It gets decomposed into atomic notes, structured as a wiki, embedded into each agent.

But the core stays still. If the core moves, every derived effort wavers.

Because there is an axis that does not move, derivation can stay free.

A question

How many years ago was the core of your own thinking put into words?

And has it changed since.