Discourse has weather

I learned to read weather before I learned to read a room.

I grew up around people who watched the sky for a living — fishermen, pilots, farmers — and the language they used for clouds was nothing like the language meteorologists use on TV. It was anatomical. A "scud" was a low ragged cloud running ahead of a front. A "mackerel sky" meant rain in 36 hours. "Mare's tails" meant wind change. It wasn't poetry. It was working vocabulary, sharpened by people who paid the cost when the forecast was wrong.

Years later, I started to notice the same kind of vocabulary missing from the other thing I do, which is post into the internet for a living. Most of the people I know who write online — including me, on most days — operate without weather vocabulary. We post into the discourse and then squint at the engagement and try to reverse-engineer what just happened. The post died. The post hit. The post was right but landed wrong. We invent narratives after the fact because we don't have language for the conditions we wrote into.

So here's a working claim: discourse has weather. And until we can name it, we can't read it.

The shape of the claim

By "weather" I mean something specific. Discourse around any category — a topic, a product, a public conversation — is in motion. It has pressure gradients (some ideas pushing into others). It has fronts (places where one set of beliefs meets another and conditions change fast). It has prevailing winds (the direction the conversation tends to drift in the absence of effort). It has saturation states (conditions where adding more material does nothing because the medium is already full). It has dispersion states (conditions where everything you say bounces off in different directions because there's no shared frame yet).

A conversation at 9am Tuesday and the same conversation at 3pm Friday are in different weather. The participants might be the same. The category might be the same. The arguments on the table might be the same. But the conditions for a post landing — for a piece of writing to reach the people it's for and do the thing it's supposed to do — those conditions are different.

This is not a metaphor I'm reaching for. It's a description of what already happens, every day, that we lack the vocabulary to name.

What changes when you can name it

A few things change immediately.

You stop confusing a headwind for a bad idea. If you write a piece during a dispersion front — when the discourse is fragmenting and there is no shared frame to land in — your post will not perform the way it would in a more coherent moment. That's not the post's fault. It's the weather. Without the vocabulary, you'll read the analytics and conclude the idea is wrong. With the vocabulary, you'll conclude the timing is wrong, save the piece, and ship it when the front passes.

You stop confusing a tailwind for a great idea. This is the symmetric mistake, and it's worse, because it scales bad ideas. A mediocre post into saturated discourse can perform well because the category is in a state where almost anything moves. You'll mistake the conditions for a signal about the work and double down on patterns that won't survive a weather change.

You start picking moments. Once you can read the weather, you can pick the window. You don't need to ship every post into whatever conditions happen to exist on the day you finished writing it. You can hold a piece for the front to pass. You can ship a quick reaction when the pressure is right. You can pre-build for predictable saturation cycles. The cost of waiting is a few hours or a few days. The cost of shipping into the wrong weather, repeatedly, is a slow erosion of trust that the work matters.

You start choosing forms. Different weather wants different forms. A short, declarative post into a dispersion front lands differently than a long, structured argument. A long argument into a saturated category will be skimmed and forgotten. The form is a function of the weather, not just a function of the content.

How operators already do this

The interesting thing about all of this is that good operators already do it. They just don't have the vocabulary, so they can't teach it cleanly to the next person.

I have watched experienced editors decline to publish a piece on a Tuesday afternoon because "the timing's off" — and not be able to explain what they meant, except by reaching for analogies. I have watched community managers know which days a question will land and which days it will dissolve, and call that "instinct." I have watched founders sense, three sentences into a meeting, that the room had already foreclosed on the idea, and pivot — and never be able to articulate the cue they read.

This is weather-reading. It's just unnamed.

The cost of it being unnamed is that it doesn't scale. The editor can't hand off what they're doing to a new editor. The community manager can't train the team. The founder hires people who reproduce the words but not the judgment, and then wonders why nothing lands the same way.

Naming the weather is the move that turns shoulder-feel into a teachable craft.

A short field vocabulary

Here are the terms I've started using out loud. None of these are final. I'm publishing them so the words can break under contact with other operators' shoulders.

- Front. A place where two sets of beliefs are colliding and conditions are changing fast. Posts into a front are amplified or dismissed faster than usual; nothing lands neutrally. - Saturation. A state where the discourse is already full. Adding material does not move the conversation; it gets absorbed without trace. New entrants lose against established framings by default. - Dispersion. A state where there is no shared frame yet. Every post bounces in a different direction because the audience is not aligned on what the conversation is about. Long arguments fragment; short, declarative pieces sometimes land because they offer a frame to grab onto. - Prevailing wind. The direction the discourse drifts in the absence of effort. Going with it is cheap and forgettable. Going against it costs more energy but produces durable signal. - Pressure gradient. Where ideas are pushing into each other. The interesting writing happens at the gradient, not at either pole. - Squall. A short, intense weather event — a viral controversy, a news cycle, a model release — that overwrites whatever was happening before. Posting into a squall is risky; the squall itself becomes the frame.

I expect this list to be wrong in places. The point is not the list. The point is the move: making weather nameable.

Why this matters for any group trying to ship work into a category

I'm writing this from the position of someone whose work is to help groups land their ideas into the conversations they care about. The recurring pattern I see is this: a team has a smart claim, a clear voice, and decent distribution, and the work still does not land — and they cannot tell whether the problem is the claim, the voice, or the distribution.

It's almost always the weather, and they can't see it.

Once we start reading the weather together, the pattern shifts. We stop debating whether to post and start debating whether to post now. We stop publishing every finished piece on the day it's done and start holding pieces for the right window. We stop interpreting an underperforming post as a verdict on the idea and start treating it as one data point about timing. The team's confidence stops being volatile against a single post's performance, because the team has more variables under its control.

This is not a productivity claim. It's an epistemic one. Weather-reading changes what you think you know about your own work.

What's still open

I don't know yet what the reliable forecasting signals are. I have some candidates — the velocity of references, the direction of frame-shift in adjacent categories, the presence or absence of a recent squall — but they are early, and they will improve under contact with other people's experience.

I also don't know how to publish the vocabulary without it ossifying into the kind of jargon that becomes its own discourse weather, which is the failure mode of most coined terms.

The invitation here is simple. If you already do this — if you already feel the weather and pick your moments — I'd like to compare notes. What words do you use? What signals do you read? What's the equivalent, in your craft, of a mackerel sky?

The vocabulary will be better when more shoulders have weighed in.