Merko

The Pre-Read That Actually Gets Read

Fri, 18 Sep 2026 09:00:00 +0200

Everyone agrees a meeting pre-read is a good idea. Nobody reads them. Both of those things have been true for as long as the practice has existed, and the second one is not a discipline problem.

A pre-read competes for a slot that does not exist. The reader’s calendar is full up to the meeting, the document arrives in an inbox that has forty other things in it, and reading it produces no visible output — nobody can tell, at 10:59, whether you did. The document has to be built for those conditions rather than for a reader who has an unhurried twenty minutes.

Nobody Read Your Document: A Recovery Procedure

Wed, 16 Sep 2026 09:00:00 +0200

You spent two days on it. You posted it on Tuesday. It is Friday and there are no comments, no replies, and one emoji reaction from someone in a different department.

This post is the recovery. Not how to write a better document next time — how to get people to read your document this time, this afternoon, with the one you have already sent. Four diagnoses, four re-send messages you can paste, and a fifth case where no re-send is the answer.

Writing Up for a Skip-Level Who Has Nine Minutes

Mon, 14 Sep 2026 09:00:00 +0200

Assume your skip-level will read about nine minutes of your writing this quarter. Not per document — in total. Nine minutes across thirteen weeks, in fragments, mostly on a phone, mostly while something else is happening.

The number is invented and the constraint is not. Work out roughly how many people report into someone two levels above you, multiply by the documents each of them produces, and the arithmetic gets grim quickly. Whatever the true figure is, it is small, it is fixed, and it is yours to spend. Most people spend it on a comprehensive document, which is a way of spending it all at once on nothing.

The Async Standup That Doesn't Become a Second Standup

Fri, 11 Sep 2026 09:00:00 +0200

Most written standups die the same way. They start as three lines in a channel, they work for about six weeks, and then someone suggests a short weekly call to go over what people have been posting. Within a month you have the posts and the call, which is more overhead than the standup you replaced.

Reporting Red Before Anyone Asks

Wed, 09 Sep 2026 09:00:00 +0200

You already know the date is not going to hold. Nobody has asked. There is a review in eleven days where somebody will ask, and between now and then you get to decide whether this is news you delivered or news that was extracted from you.

Status Updates Nobody Reads: Four Reasons, Four Fixes

Mon, 07 Sep 2026 09:00:00 +0200

You write a good update. It is short, it has dates in it, the ask is in the first paragraph. You send it every Monday. Nobody replies, nobody references it, and in the retro someone says they had no visibility.

Your Weekly Update, Written for Someone Who Skims

Fri, 04 Sep 2026 09:00:00 +0200

Your manager reads the first line of your weekly update. Sometimes the second. If something in those two lines suggests a problem they own, they read the rest; otherwise they scroll.

This is not a character flaw and you should stop writing as though it were. They have nine of these. They are reading yours on a phone between two meetings, and the useful question is not how to make them read more — it is what has to be in the part they definitely read.

The Status Update That Replaces the Standup

Wed, 02 Sep 2026 09:00:00 +0200

The standup is gone and nobody told you what replaces it. That is the actual situation. Somebody decided the fifteen minutes were not earning their keep, the invite disappeared, and the expectation that you all know what each other is doing stayed exactly where it was.