The pitch for AI was time back. Less grinding, more thinking. And in narrow terms, it delivered.
What it also did was raise the floor for everyone at once. Your clients adopted the same tools. So did the people you're competing with. The baseline for what counts as thorough, fast, and considered moved upward without a formal announcement, and most people are still catching up to what that actually means for how they work.
What "thorough" used to mean
Three years ago, a strategic deliverable that synthesised ten sources, pulled clean data, ran sensitivities, and returned with a one-page summary was considered thorough. It took a week. The thoroughness was partly the analysis and partly the implicit message: I spent the time.
Now the same output takes a day and a half, and anyone can do it. Which means it no longer means what it used to mean. You can't get credit for thoroughness by doing the thing that used to look thorough. The work has to be recognisably better than what a diligent mid-tier professional could produce in the same window with the same tools — and that window and those tools keep getting more generous.
"Considered" faces the same inflation. An email that clearly shows care now arrives in an hour instead of a day. A proposal that anticipates objections now comes with three-scenario financial modelling built in. A memo that reads as thoughtful now also reads as comprehensive. The floor on each of these dimensions has moved independently, and the people you're being compared against are being compared against the same new floor.
What Csikszentmihalyi actually found
Mihály Csikszentmihalyi spent most of his career studying people who performed at a high level for a long time, across disciplines that had nothing in common except that staying near the top of them was hard. Flow is what his work is famous for. The less-cited finding is about what lets people stay in flow across years rather than burning out in months.
The differentiator wasn't effort. It was recovery.
Recovery in his sense isn't rest, though rest is part of it. It's the capacity to absorb pressure without degrading. To come back to a difficult problem the next morning sharper rather than blunter. To end a hard week at the same quality you started it. That capacity isn't a personality trait you either have or don't. It's a developed function — maintained with deliberate attention, eroded without it.
The people who perform for decades aren't the ones who could push hardest in their twenties. They're the ones whose recovery function was still intact in their forties.
The solo operator's problem
There's no buffer when you work alone. Every acceleration in the environment lands directly. No org chart to smooth the load. No ops team absorbing the admin that would otherwise drain your week. No manager modulating the pressure for you. The floor moves and you feel the whole distance in one step.
Which means the real constraint was never output volume. It was always the quality of the person generating it, and whether that person is being maintained like the core asset they are.
Most self-employed people will tell you the business is the main thing. The business is downstream of them, and they're treating it as if the causal arrow goes the other way. When their output is strong they credit the business for working. When it's weak they try to fix the business. The obvious fact that the output tracks the operator's state almost perfectly is the last thing they're willing to act on, because acting on it means admitting they're the bottleneck and the fix lives inside their own life.
What maintenance actually looks like
There's a version of this essay that would now tell you to sleep, meditate, and walk more. That version is true and not useful. It's been written ten thousand times and changed nothing, because it describes the output of the maintenance function, not its design.
Design, for the people who actually do this well, looks more like the following.
They know which few decisions per week are the ones that require real cognitive load, and they protect the conditions around those decisions — not their whole calendar. They've picked the clients, projects, and commitments that reward their edge rather than tax it, and they've said no to the rest, usually later than they should have. They treat their own energy as a budget they manage actively rather than a resource they dip into until it's gone. They have a small number of people who see the full version of what they're working on, and they don't have the exhausting job of pretending everywhere else. They've given up on the fantasy that the right productivity system will recover time they never spent well to begin with.
None of this is glamorous. None of it photographs. It's design.
The ones who look unhurried
Is there someone in your network who seems unhurried despite clearly being in demand? Not slow — unhurried. Returning work at the pace they choose, not the pace the market demands of them. Delivering at a standard that assumes they thought about it, not reacted to it.
Worth paying attention to how they've structured things. What they've said no to. Who they've stopped trying to impress. How they've decided what deserves their real capacity and what gets the tidy competent version that anyone could produce.
That's not personality. That's design.