When conversation starts sounding like PowerPoint

The temptation is to frame this as a loss of storytelling craft, which is partly true. It's also an easy framing that misses what's actually going on. Bullet-point speaking isn't just about efficiency. It's about defensive communication. Bullets protect the speaker from being misquoted, from committing to a position, from revealing too much structure in their thinking. Stories invite interpretation, which invites disagreement, which invites effort to defend. The move away from stories is partly a move away from vulnerability, and the corporate environment rewards exactly that.

What bullets optimise for

Bullets optimise for immediate comprehension at the cost of retention. User-research measurements on the same technical content presented two ways consistently show the pattern. Bullets win at forty-eight minutes: people can name what was said. Narratives win at forty-eight hours: people remember the meaning. The 'efficiency' of bullets is an artefact of measuring comprehension instead of learning. Most corporate communication is measuring the wrong thing, and so rewards a format that fails the longer purpose.

The same inversion shows up in professional writing. Bulleted FAQs rate as less useful than narrative help content when users are doing complex tasks. The reason is structural - a bullet list is a collection of disjoint facts, while a narrative carries relationships and causal ordering. For a reader who needs to understand how to do something, the relationships matter more than the facts. Writing teams keep producing bullet-heavy content because it's faster for the writer, not because it's better for the reader. That's a misalignment between producer and consumer incentives, and it's the quiet driver of most corporate-communication frustration.

The register-switching skill

The leaders I respect most share a specific communication skill that is rarely taught and rarely described: they switch registers fluently depending on context. Bullets in a board meeting, stories in a 1:1 coaching session, narrative in a town hall, terse facts in an incident-response call. Each format fits a specific purpose, and the register shift happens naturally. This isn't about having a rich vocabulary - it's about reading the context and selecting the appropriate communication mode.

The collapse to a single register - almost always bullets, because that's the dominant corporate register - is what happens when a leader loses situational awareness about communication. It's diagnostic of more than just bad communication habits. A leader who has only one mode has usually stopped noticing that different audiences need different things, which is a leadership failure in several dimensions at once. The bullet-point creep into casual conversation, which the original observation points at, is a specific symptom of this broader loss.

The historical pattern

Every communication medium has compressed language toward its own grain. Telegraph cost per word made messages shorter and more procedural. Email threading made responses shorter and more transactional. PowerPoint made reasoning fragment-shaped. SMS made words abbreviated. Now AI-assisted drafting is creating a new register that is already distinguishable - smooth, confident, slightly generic, with a characteristic hedging cadence. Each new medium adds a register to the possible repertoire, and what gets lost is usually the register of the previous era. The problem isn't any single medium - it's letting any one of them dominate your full range of expression.

The corrective is deliberate practice in registers that aren't being rewarded by your daily environment. If you spend most of your week in slide decks and exec summaries, the conversation over dinner, the blog post on a Sunday afternoon, the long letter to a friend - these are not leisure activities, they're training. They keep the storytelling register operational. Without them, it atrophies, and the atrophy is invisible until the moment you notice yourself delivering bullet points in a setting that called for a story.

A leader with only one register has usually stopped noticing that different audiences need different things.

The strategy-consulting observation

There's a sharp version of this critique that applies specifically to strategic thinking. Bullet-pointed strategy decks are often a symptom of not having a complete argument yet. A complete argument flows naturally from premise to conclusion with connective tissue that bullets strip out. Bullets let you list your points without doing the work of connecting them, and they let you present a conclusion without having to defend the reasoning in order. The best strategy work I've seen starts as essays, gets reduced to bullets for presentation, and retains a through-line that can be reconstructed on request. The worst starts as bullets and stays there, because the thinking never required full connective prose and therefore never happened at the level of narrative.

The diagnostic question for any strategic work you're producing: could I rewrite this as a coherent essay? If the answer is 'yes, trivially', the bullets are a compression of a complete argument and they're fine. If the answer is 'no, because the logic doesn't quite connect', the bullets are hiding the incompleteness. This test is uncomfortable because it surfaces thinking gaps that the bullet format was camouflaging. It's also the test I try to apply to my own work, which is partly why I write long-form pieces like this one - the essay form doesn't let me hide from missing logic the way bullets would.

The counter-practice

If you want a specific counter-practice, try this one in meetings. Once per status call, insist that someone tells a story about a project rather than listing status. The story includes who did what, why it mattered, what changed, what surprised them, and what they're doing next. It takes three minutes. Rotate weekly. The quality of information transfer improves measurably, because the story carries context and causation that bullet-point status reports systematically remove. I've run this in two different engineering organisations with the same result. It's not complicated. It requires a small amount of leadership authority to protect the story-time from the efficiency reflex that will try to kill it.

The bigger point is that storytelling is a craft that requires maintenance. If you stop doing it professionally, you stop doing it personally - and the moment you notice yourself speaking in bullets at dinner is the moment the craft needs active attention. The fix is not nostalgia for 'how we used to talk'. The fix is deliberate practice in modes your professional environment no longer forces you into. Nobody will prompt this for you. It has to be a conscious decision, renewed weekly, to keep the storytelling muscle active. Otherwise you become, quietly and without intending to, someone whose conversations sound like slide decks.