Fluent emptiness and the missing Tuesday morning

The draft that read well and went nowhere

The Withings draft was a masterclass in fluent emptiness. Every paragraph moved logically to the next. The sentences were varied. The vocabulary was precise. It read like a health journalist's sidebar on smart scales.

It was also completely devoid of anything that had actually happened to me. The AI had written a plausible article about a hypothetical person who owned a scale.

That gap between how right it sounded and how little it said is the useful part.

The fake lesson vs the real one

The draft ended with a tidy conclusion: daily weighing had “taught me to trust the process over the number.” It sounded profound and responsible.

It was also not true.

Daily weighing did not teach me to trust the process. Daily weighing taught me that the number is mostly water and that I should ignore it until Friday. That is a much less elegant sentence, but it is what actually happened. The AI chose the generic lesson because it is culturally available. I chose the specific truth because I lived it.

This is one of the tells of fluent emptiness: the moral of the story arrives pre-polished, before the story ever shows up. If the “lesson” could live in a self-help book without changing a word, it probably did not come from a real Tuesday morning in your kitchen.

Details are where reality sticks

Once I started looking, the lack of reality in the draft was obvious. There were no numbers, no dates, no model names.

• It said “my smart scale” instead of “the Withings Body+.”
• It said “over several months” instead of “from January to June.”
• It said “a noticeable trend” instead of “a 2.3 kg drop in the 7-day average.”

The absence of specifics was the giveaway. Real experience is sticky with detail. Generated experience is smooth like a river stone.

This is not about dumping your notebook into the post. It is about the difference between:

I wrote about this earlier in What Six Months of Daily Weigh-ins Can and Cannot Prove.

• “I started to see progress” and
• “My 7-day average finally dipped under 80 kg and stayed there.”

One of those can be written by someone who has never seen your scale. The other requires you to have stood on it more than once.

Authority voice vs honest voice

The tone of the draft was calibrated for authority, not honesty. It used phrases like “research consistently shows” and “the data revealed.” It sounded like it was defending a thesis.

I do not write like that. I write like a guy who stepped on a scale every morning and got confused when it went up after a softball game. My concern was not “what the literature says about weight variability.” My concern was “why did my weight spike after three hours of running around in the outfield and sweating through a jersey.”

The authoritative tone is another form of smoothness. It pushes the writing toward generality and away from the actual mess: the missed days, the weird spikes, the time you weighed yourself after a late dinner and decided that was a mistake.

When a post about your own life sounds like it is trying to impress a peer reviewer, something has gone wrong. Authority is not the problem. The problem is when the performance of authority replaces the part where you tell the truth.

The adjective test

The Withings draft taught me a simple check: the adjective test. If a post about my own life contains more adjectives than proper nouns, it is probably AI-generated.

The draft was full of phrases like “significant progress” and “improved recovery.” My actual notes look more like:

• “114g protein”
• “Whoop score went from yellow to green”

“Significant” is a judgment word. “Improved” is a judgment word. They are cheap to produce and easy to agree with. “114g protein” is a number. “Whoop” is a product. Those are hard to fake without accidentally saying something checkable.

The adjective test is not scientific. It is just a fast way to ask: am I describing what happened, or am I describing how I want it to sound?

More on this in my article GEO vs SEO in 2026: What Actually Moved For My Clients.

Using fluent emptiness as a tool

I now use the Withings draft as a negative case study in my content pipeline review. If a piece sounds right and says nothing, it goes back to the notes stage.

“Sounds right” usually means:

• The structure is clean.
• The sentences are smooth.
• The lesson lands neatly in the last paragraph.

“Says nothing” usually means:

• No concrete nouns that would let someone fact-check or visualize it.
• No dates, ranges, or quantities that anchor it in time.
• No moments where something confusing or inconvenient happens.

When I hit that combination, I do not try to fix the prose. I assume the prose is fine and the problem is upstream. I go back and ask:

• What actually happened?
• On what day?
• With which device, app, or person?
• What number was on the screen?
• What did I misunderstand at the time?

Then I look for the places where those answers can replace the smooth phrases. “My smart scale” becomes “the Withings Body+.” “Over several months” becomes “from January to June.” “A noticeable trend” becomes whatever the graph actually did.

When the notes are thin

The interesting part of the Withings draft is that the AI did not invent specific numbers or dates. It stayed in the safe zone of generality. The problem is that I had not given it much to work with, and it filled the gaps with cultural defaults.

This is the other use of fluent emptiness: as a mirror for your notes. If the draft comes back vague, it might be because the source material was vague. “I weighed myself for a while and it was helpful” is not enough to build a real story. You either need to go back and reconstruct what happened, or accept that this one will be an essay about general principles, not a personal account.

Read also The boring training week I can actually repeat.

Both are fine. The trouble starts when you pretend one is the other.

Let it sound slightly wrong

The Withings draft sounded right because it sounded like everything else. That is the trap. The way out is to let your writing sound slightly wrong: too specific, too narrow, too obviously about your actual Tuesday morning.

“Ignore the number until Friday” is not a universal principle. It is a hack that fell out of watching a graph bounce around for a few months. It is also the part of the story that feels like it belongs to a real person.

If the choice is between a smooth, generic lesson and a lumpy, specific truth, I will take the lump every time.