The meeting is cancelled, or you refused it, and now there is a document to write today. It has to reach a specific person, and that person has to act on it.
Merko is about that document. Status updates, decision docs, RFCs and ADRs, briefs, handoff notes, incident comms, the norms for where things get written and how fast anyone has to reply — and what the AI notetaker may record. Not general writing advice, not productivity. The written artifacts of work, and the part after they leave your hands.
What every post has to carry
An AI summary already explains what a good status update contains. That ground is not worth contesting.
So every post here carries something a summary cannot reproduce: the complete artifact, filled in for a specific awkward situation; the version that failed, and why; or the reply you send when the document was ignored and the meeting got booked anyway. A post that only describes a genre does not get published.
The prose is held to the same rule. A site about writing is refuted by its own padding.
Who this is for
- You have to produce the artifact now and want a filled-in example, not a definition.
- You write it well and nothing happens.
- You lead a team and are installing the written default: what must be written, where it lives, who is obliged to reply.
- You have inherited an archive that is stale, contradictory, or written by people who have left, and need triage, not a template.
Everything here assumes limited authority. Advice that only works if you set company policy is not advice.
What this site does not do
It does not treat writing things down as a virtue. Writing goes stale, it is slower than a call, it exists forever, and it can be read as an accusation. Posts say which of those you are paying. Sometimes the honest answer is a meeting, and the post says so.
It does not conclude that a tool solves it. A shared document or a pinned message comes first; the recommendation last.
It does not give legal advice. Recording consent, retention and discovery come up in the notetaker posts, which describe the general shape and name the point at which the question belongs to counsel, without asserting what the law is anywhere. HR advice neither: the practice of documenting something, never the employment consequence.
Nothing is invented. A figure is attributed to whoever published it, by name and year, or omitted. No employer, manager or colleague is identifiable in an anecdote.
Who writes it
Noor ran the documentation and decision process at two companies that called themselves written-first, and saw what that meant: an RFC template nobody filled in honestly, a weekly update read by three people out of forty, a wiki whose top search result had been wrong for eighteen months, a notetaker that joined a compensation conversation because nobody had said it should not. The craft came from editing other people’s documents until they landed, a different skill from writing them.
A document is not finished when it is written. It is finished when it has been acted on.
Not a technical writer. Not a productivity person. No opinion about which wiki you use.