Operator method · June 2026
The Operating Rhythm
Daily, weekly, and monthly practices from the McKinsey playbook.
“I never trained at a place like McKinsey. How do you operate at that level?”
A question I get from the engineers, founders, and operators I coach.
Hiring smart people is the easy part. The operating rhythm is the harder part: the unglamorous routines that turn capable people into trusted ones, and good work into compounding work. Most companies don’t teach it explicitly. The best ones do.
The answer isn’t talent, and it isn’t hours. It’s a rhythm: a small set of daily, weekly, and monthly routines that compound. This guide is that rhythm, written down.
It’s the operating system most MBB consultants absorb in their first eighteen months, partly by training and mostly by osmosis. That same training is the quiet cause of a familiar reputation: they seem to do more in less time, stay composed when others react, and reach seniority earlier than tenure suggests.
They’re running a rhythm the rest of the world doesn’t see.
I saw the proof of that again and again at McKinsey. You could take six consultants from six cities, half of them strangers to each other, drop them onto a new client in a new city, and within days, sometimes hours, they were running the same cadence. No onboarding, no warm-up. The rhythm was the shared culture, and it was portable. Being able to do that on demand is a remarkable thing.
Read it once end-to-end. Then pick two habits a week and trial them. In two months the rhythm will run you instead of the other way around.
This isn’t a replacement for what’s already working, and it isn’t doctrine. I never ran the full rhythm consistently myself. Adapt it, riff on it, make it your own.
First, five principles
Every practice in this guide grows out of five ideas:
- Carry a Day 1 Answer.
- Back-plan from the end product.
- Ask “so what?” until it hurts.
- Be MECE.
- Lead with the answer.
The parts
If the principles tell you why, the parts tell you how. Three cover execution across daily, weekly, and monthly timescales. A fourth picks up what changes when the work goes AI-native.
Five blocks, one good day. The unit of execution.
Three load-bearing moments. The unit of direction.
Where careers actually compound. The unit of growth.
The same rhythm on AI-native rails, and the open question of running it at organizational scale.
Why this matters now
The rhythm question, now
The rhythm was portable because the beat was shared. The last few years have stress-tested that, and most organizations have been arguing about the wrong variable. Take hybrid. The debate was real estate and headcount; the quieter failure was rhythm. One person is just as productive at home or in the office, but an organization loses something when half the team is in on Tuesday and the other half on Thursday and no two people share a tempo. Individual output holds. Collective output erodes.
Location was never the question. Tempo was.
AI is the next rhythm question, and a far bigger one. “AI-native” still lives at small scale, teams of one, two, three, where the coordination cost rounds to zero. At the scale of a real organization it is unsolved, and it is a rhythm problem before it is a tooling problem. I take that question further, and where I think it’s heading, in the AI-native field update.
That’s how you operate at that level. Not by working harder, by running the rhythm.