It happened again
WORK LOOP 02

Why do I delay difficult messages until they become urgent?

At first, the message only carries uncomfortable information. After enough delay, it also has to explain why the other person had less time, fewer options and no warning.

Serkan Elbasan8 min read

You know the deadline may slip. You know the answer is probably no. You know the scope has changed and someone else needs to hear it.

But the message is uncomfortable, so you wait for more certainty, better wording or a moment when the news feels easier to deliver.

The moment rarely gets easier. It only gets later.

Delay adds a second problem

Visible sequence
01DIFFICULT INFORMATION APPEARS
02I WAIT FOR BETTER WORDING OR CERTAINTY
03THE OTHER PERSON KEEPS PLANNING
04OPTIONS SHRINK
05THE MESSAGE BECOMES URGENT
06NOW I MUST EXPLAIN BOTH THE NEWS AND THE DELAY

The first problem is the information itself: a delay, refusal, mistake or change.

The second problem is created by silence. The other person continues making decisions with an outdated picture.

By the time the message is sent, the cost no longer belongs only to the original issue.

Where it actually turns

The turn appears when complete certainty is treated as a requirement for early communication.

You may not know the final delivery date, exact cause or full solution. But you often know enough to say that the current plan is at risk.

Waiting for the final answer removes the chance to give an early warning.

THE MESSAGE WAS INCOMPLETE. THE WARNING WAS ALREADY USEFUL.

The delay came from treating those as the same thing.

Why rewriting the message does not reduce the real risk

Better wording can improve clarity. Rewriting becomes avoidance when each version postpones the moment the other person can act.

A long explanation can also hide the useful part. Background grows while the changed condition, consequence and next update remain buried.

The first useful message does not need to solve everything. It needs to make the changed reality visible.

OLD RUN
01I SEE A PROBLEM
02I WAIT FOR CERTAINTY
03I KEEP EDITING
04THEIR OPTIONS SHRINK
05I SEND WHEN IT IS URGENT
REPLACEMENT RUN
01I SEE A MATERIAL RISK
02I SEND AN EARLY WARNING
03I NAME WHAT IS KNOWN
04I NAME WHAT IS OPEN
05I SET THE NEXT UPDATE

The move to test

Send the warning before the complete explanation.

Use four parts: what changed, what it may affect, what is still unknown and when the next update will come.

For example: “The Friday delivery is now at risk because the supplier confirmation has not arrived. I do not yet know whether the delay is one day or longer. I will confirm the revised date by 2 p.m. tomorrow.”

This message does not pretend the problem is solved. It gives the other person time and a reliable next point.

Field test

SEND THE FIRST USEFUL VERSION EARLIER.

  1. 1State the changed fact or credible risk in the first sentence.
  2. 2Name the likely consequence without exaggerating it.
  3. 3Separate what is known from what is still open.
  4. 4Give a specific time for the next update.

Do not send speculation as fact. Early warning should make uncertainty explicit, not hide it.

What to observe

OLD

The message is sent only when the issue has become urgent.

MIXED

You warn early, but leave the consequence or next update unclear.

NEW

The other person receives enough information to adjust before the final answer exists.

NOT COMPARABLE

The information is confidential, legally restricted or genuinely too uncertain to communicate responsibly.

THE PRECISE READ

A useful early warning can be incomplete and still be exactly on time.

Your version

Build a next move for your version.

Open Work loops
Author

Serkan Elbasan

Serkan Elbasan is the founder of the Institut für Kognetik and an independent researcher working on recurrence, structural invariance, rule–state separation and the formal conditions under which systems can modify their own rules.

Related field notes