Finding the Lede: What Actually Turns Data Into a Story
why a spreadsheet full of correct numbers isn't a story yet, and what it actually takes to find the one sentence a dataset is trying to tell you.
Turning a chart into an argument someone remembers.
why a spreadsheet full of correct numbers isn't a story yet, and what it actually takes to find the one sentence a dataset is trying to tell you.
why burying the point under three slides of data sourcing and scope notes loses the reader before the story even starts, and what to put first instead.
the same set of facts gets a different opening paragraph depending on which desk it runs on, and why a data story needs the same discipline.
why newsroom copy is written to survive being trimmed from the bottom, and how the same ordering principle protects a data report from being skimmed.
why a headline number without context is just a number, and how the paragraph that follows it is what actually makes a data story matter to anyone.
the narrative device that makes a story stick isn't the number itself, it's the gap between what everyone expected and what actually happened.
why leading with the evidence and explaining it second earns more trust than announcing a conclusion and backfilling proof, and when to use each order.
why cramming five findings into one dense chart produces zero memorable ones, and the newsroom discipline of running one story at a time.
why a single well-chosen number, repeated deliberately, outlasts an entire report in a reader's memory, and how to choose one worth anchoring to.
no story runs without an editor reading it first, and no data narrative should ship without an equivalent review checking the same things a copy desk checks.
an editorial review checks whether the story is well told; fact-checking is the separate, narrower discipline of verifying every claim in it is actually true.
a wire service can run hundreds of reporters' work under one voice because of a shared style guide, and a data team needs the same shared discipline.
a newsroom doesn't quietly edit a published error and hope no one notices; it runs a correction, visibly, and that discipline applies just as much to data.
AI-assisted first-draft narrative generation from raw data is a genuine acceleration of the hardest, slowest part of the job, not a replacement for the reporter.
an AI copy desk automatically traces a generated narrative's claims back to the underlying data, catching a class of error a human reviewer alone would miss at scale.
AI can now generate genuinely personalized narrative framing for different audiences from one underlying dataset, at a speed that makes consistency checking essential.
generating data narratives at real organizational scale, across hundreds of dashboards, requires the same discipline this series covers, just systematized.
the real risk of AI-generated narrative isn't obvious nonsense, it's a fluent, confident claim that sounds exactly as authoritative whether or not it's actually right.
real-time narrative generation for continuously updating data borrows the discipline of a live election-night desk, where the story itself keeps changing underneath the writer.
the lede and the nut graph, the editorial desk and the correction, the wire service drafting fast and the copy desk checking its work, every article's lesson reassembled one last time.