The story went up eleven minutes after the council meeting ended. By evening it carried two corrections and a note explaining what the first version got wrong. The traffic was respectable. The credibility was not.

That sequence repeats in newsrooms everywhere, and it usually gets blamed on one reporter having a bad day. It is rarely that. It is the predictable output of a workflow that treats publication as the finish line and checking as an obstacle on the way there. Speed has become the default virtue in digital media, and a slogan borrowed from software culture has quietly become an editorial standard. In this work, the things you break are facts, and someone else has to live with the damage.

The Mantra Came From a World With an Undo Button

Software ships early because a broken build can be patched tonight, and the people affected can file a bug report. A published claim is different. It travels: screenshotted, aggregated, translated, quoted in group chats, cited by people with an agenda. A corrected version rarely catches up with the original. The borrowed slogan imports an assumption that does not hold here — that the cost of being wrong is small and temporary. In media, being wrong is expensive and permanent, and no dashboard measures it.

Speed Is Still an Asset, Just a Narrow One

Be fair to the instinct. Some stories genuinely reward speed: a scheduled vote, a weather warning, a court ruling, a match result. When a fact can be confirmed in one step and delay causes real harm, publish quickly and update in the open.

The trouble is that the same reflex gets applied to stories where nothing confirms in one step — an allegation in a leaked document, a figure lifted from a summary, a claim about a treatment, a description of what happened in a conflict zone. Those are the pieces where one more call changes the story, and also the ones where a correction costs the most. A useful habit: before you assign, ask what speed buys you. If the answer is a few hours of search traffic, it probably isn't worth the risk. Anything touching defamation, privacy or confidential material deserves a lawyer's eye before it goes live, not after.

Verification-First Is a Pipeline, Not a Personality Trait

Verification gets talked about as a quality some people have. It isn't. It's a set of decisions made in advance, so nobody has to be brave at eleven at night. Build it like a production line: every story has a path, and the path has checkpoints.

  1. Set the evidentiary bar before reporting starts. For an allegation that usually means the document plus someone who can speak to it; for a number, the original source rather than a summary of it.
  2. Keep what you know separate from what you've been told. Drafting in two columns helps. The second column is often the better story, and the one that produces a correction if you let it slide into the first.
  3. Write the blank into the draft. Put the unconfirmed point in a sentence, then go find it. Publishing around a hole you can see is a choice, not an accident.
  4. Give one person the job of being unimpressed. A second reader whose only task is to ask "how do we know that" catches more than a room full of people who all want the story to hold.
  5. Timestamp everything: when the document was created, when the call happened, when the record was updated. Timestamps turn arguments into checks.
  6. Say what you don't know. "The ministry did not respond" is stronger than a vague attribution, and it is honest about the state of the reporting.

None of this is slow in the way editors fear. It is slower on the first pass and much faster across a month, because you spend your time reporting instead of cleaning up.

Write the Policy Before You Need It

Newsrooms now handle tools that generate text, images, audio and video at a quality that fools people. Whether you use them lightly or heavily, audiences will assume something, and the assumption is usually worse than the truth. A short public policy beats a long internal argument.

  • What is used, and for what. If software helps with transcription, translation or research summaries, say so plainly.
  • What it is never used for: quotes, sources, images presented as documentary, anything that misleads readers about what happened.
  • Who is accountable. A named role, not "the newsroom." If a tool-assisted error runs, a person still answers for it.
  • How synthetic material is labelled — one phrase, used every time, in the same place, so readers learn to recognise it.
  • How other people's work is handled. Scraped material, rivals' reporting and readers' photographs all need rules. Write them down.
  • How corrections and complaints work: a visible address, a real response time, no quiet deletions.

Transparency Is a Product, Not a Press Release

Readers don't need a white paper. They need a page they can find in two clicks, written like a good explainer, with a last

Photo: Somogro Bangladesh / Pexels