
Every department in your business is telling a story.
It isn’t just reporting data. It’s telling a story about what’s happening in its corner, and about what’s happening to the whole company. Sales has one: customers want more, and product is too slow to deliver it. Product has one: sales keeps promising things that don’t exist. Finance has one about discipline. Operations has one about everyone else’s deadlines. Marketing has one about a brand nobody else protects.
Each story is grounded. Each has heroes and villains. And each is told with complete conviction, usually in rooms the other departments aren’t in.
None of them is the company’s story.
An organization can’t run on six stories at equal volume. When every narrative carries the same weight, people follow the one they heard most recently, or the one that flatters their team. Sales chases deals product can’t support. Product builds features marketing can’t explain. Everyone works hard. Nobody moves together. You get activity instead of momentum.
The leader’s job isn’t to referee. It’s to edit.
An editor doesn’t average the drafts on the desk. An editor decides which sub-stories stay in and which get cut, what gets emphasis and what gets a single line. Hardest of all, an editor finds where the threads converge: the point where the sales story and the product story turn out to be the same story, told from two ends.
That’s the difference between a story and a summary. A summary collects what everyone knows. A story gives people something to believe and a part to play in it. Nobody rallies behind a summary. People rally behind a story they can see themselves in and can repeat without notes.
When Alan Mulally arrived at Ford in 2006, the company was heading toward the worst loss in its history, most of it in North America. Yet in his early weekly business plan reviews, executives color-coded their charts almost entirely green. Every division was telling a story in which it was fine.
Mulally’s work was editorial. He made it safe to bring the red charts into the room, and he replaced a dozen regional stories with one: One Ford. One team, one plan, one goal. Every region could find itself in that story. Not every region’s preferred version survived it.
That last part is the cost most leaders avoid. Editing means telling some departments that their story is a subplot. It means cutting threads people care about. So leaders hand the job to consensus, which keeps every story and commits to none. Or they hand it to process, which produces documents nobody finishes. Or they skip the story and issue directives, which land as arbitrary because nobody can see why this and not that.
Deciding is the easy part. The hard part is understanding each department’s story well enough to know where it’s true, where it’s self-serving, and where it meets the others.
You can’t automate that. You can’t hand it to a committee. It’s the job.
Every department will keep telling its story. The only question is whether anyone is editing.