You open Stripe at 9:14 a.m. The number is what it is. Three days lower than the same time last week. The brain, in a quarter-second, has already finished a calculation: if this trend continues for the rest of the year…. It hasn't continued for the rest of the year. It happened for three days. The brain doesn't care. It serves the forecast hot, and the body, three days into a partial pattern, is now responding to a twelve-month catastrophe that exists nowhere except in the forecast.
Maybe most of the data running your nervous system isn't data at all. Maybe it's prediction wearing data's clothes — and the body has been treating predictions as prophecies for so long it can no longer feel the difference between what happened and what might.
Carissa Véliz has a frame for this.
The question: Can I run my work for seven days treating every prediction I encounter — from metrics, from peers, from my own anxiety — as a provocation rather than a fact?
The hypothesis: most of the data driving one-person business anxiety isn't data. It's prediction. The Stripe dashboard shows yesterday's revenue; the brain converts it to a forecast of the year. The Instagram drop shows last week's algorithm; the brain converts it to a verdict about the future. The 3 a.m. what if loop is a forecasting session, not a problem-solving session. If I treat each prediction as a provocation — something to defy, not obey — anxiety will lose its grip, because anxiety is the response to a prediction being treated as inevitable truth.
The signal: by day seven, my emotional baseline is more stable across the week than it usually is. At least three predictions clearly named, and at least one defied with action.
What you do for 7 days
- Morning, before first screen. One sentence. "What prediction am I likely to encounter today — from a metric, from someone else, from my own mind?"
- At first screen check. When you open analytics, email, or social metrics, name the prediction your brain is forming. Write it down. "This number is predicting that ___."
- At prediction-moment, the Joe Frazier question. "What would I do if I treated this as a provocation rather than a prophecy?"
- Evening, two minutes. Log:
What this experiment grows
It is not denial. It is the muscle of separating data from forecast. Data is what happened. Forecast is a story the brain tells about what's going to happen, presented to the body as already-real. The body doesn't argue with what feels real. So the body responds to the forecast — and three days of dipped revenue produce twelve months of physiological strain. Naming the prediction explicitly, before the body has metabolized it, gives you a small window to choose which story the body will respond to.
Curiously, the defiance doesn't have to be dramatic. Stripe is down for three days; the prediction is that the year is bad; the defiance is that I will run my afternoon as if next week's revenue is normal — that's a defiance. It changes nothing about the metric. It changes a lot about how the afternoon goes. By day five, the forecasts start arriving with less authority. The brain is still making them. The body has stopped automatically obeying.
Where it pairs
This experiment walks with the morning anxiety pain — the wake-up where the body has already started responding to twelve months of imagined data before the day begins. Naming the prediction is the small daily move that reverses the order. The Reflection Bot workflow is the daily companion — three questions that, when a prediction lands hot, separate what is actually happening from what the brain is forecasting.
It is one week. Predictions named, predictions defied. The body, slowly, learning the difference.