Food for thought
The Operating Rhythm, AI-Native
The same rhythm, on AI-native rails.
The original three parts of this guide were written tool-agnostic on purpose. Pen and paper, docs, calendar, Slack. The operating rhythm runs on whatever your team already uses. In recent years the tools have been shifting under all of us: every block of the day now has an AI version waiting to be installed. The principles still hold. What changes is where the friction lives.
This update runs in three parts: the principles re-cast as AI workflows, what mutates underneath them, and the open question of running the rhythm at organizational scale.
Replicate: the five principles, AI-native
Every principle below maps to a small AI workflow. Call it a skill, a prompt template, a custom GPT, a Gem, whatever your tool calls “reusable instructions you save and call by name.” The goal isn’t one giant agent that does your job; it’s five small tools you reach for at predictable moments. The examples below are illustrative, not canonical. Start there, edit for your context, write your own once you see the pattern.
1 · Day 1 Answer, as a skill
The principle: write the answer you’d give if forced to deliver today, in one paragraph, before doing the work. The AI move is a small skill that takes your draft and stress-tests it: three alternative hypotheses you didn’t pick, the strongest counter-argument to the one you did. You write the paragraph; the skill does the breaking. Don’t let the AI write your draft, or you skip the part that makes you trusted.
Example: Day 1 Answer stress test
2 · Ghost deck, as a prompt
The principle: draft the final artifact first, titles only, in delivery order. Then plan the work to fill it. The AI move is a one-shot prompt: you supply the project and a one-line success criterion; the model returns eight to twelve slide titles, in order. You edit the result, not a blank page. The slide your audience will fight over is the one you write yourself, by hand, before any other.
Example: Ghost deck
3 · “So what?” as a check
The principle: an observation isn’t an insight. Ask “so what?” of every sentence until the answer either elevates or you cut. The AI move is a check on any draft before sending: paste, run, get a line-by-line readout. The friction that drops is the editing pass. The friction that stays is deciding which so-what matters most to this reader, this decision. The model gives you a plausible implication for every line; your job is choosing.
Example: So-what check
4 · MECE, as a check
The principle: when you break a problem into pieces, the pieces shouldn’t overlap, and together they should cover the space. The AI move is a short check against any structure you’ve drafted, looking for the overlap and the missing fourth. This one is underrated for one reason: you wrote three; you’ve stared at three; you can’t see the fourth. The model hasn’t bonded to your structure yet. Run the check before the structure leaves your machine.
Example: MECE check
5 · BLUF, as a rewrite
The principle: lead with the answer. Then the reasons. Then the supporting detail. The AI move is a rewrite skill: paste any draft and ask for the three-sentence BLUF version. If the rewrite is shorter than yours and still says what you meant, the draft was buried; ship the rewrite. If the rewrite reads weaker, your answer is weaker than you think. You can compress an answer you have; you can’t compress one you’re still avoiding.
Example: BLUF rewrite
Mutate: what’s actually shifting
If “Replicate” answered can the rhythm survive the new tooling, “Mutate” answers what changes in the underlying disciplines when it does. Five shifts, one per principle.
- Day 1 Answer goes from “pick a hypothesis” to “choose among ten.” Generating hypotheses was the slow part. Now it’s curating. The skill is judgment about which of ten plausible answers fits this reader, this decision, this week.
- The ghost deck stops being a forcing function and becomes the default unit of work. When drafting the final artifact costs nothing, every project starts with one. The discipline shifts to spending the saved time on the slide that actually matters.
- “So what?” stops being a discipline and becomes the whole job. Observations are infinite and free; insights still aren’t. Most of what made a junior analyst valuable just got automated. The leap to so what for this decision is now where seniority shows.
- MECE externalizes from your head into the loop. You stop holding the structure in your head and auditing it by hand: write a draft, run the check, fix what comes back. The operators who are MECE in five years build it into the workflow now.
- BLUF becomes a filter, not just a writing rule. When the world produces infinite words, the operator who compresses what they hear into three sentences wins by default. Compression is the only filter that scales.
Two common takes both miss. AI changes everything; throw out the playbook. AI changes nothing; the tools are toys. The principles were always about judgment, not typing speed. AI raised the floor on output volume by the same amount it raised the ceiling on judgment. The rhythm is what closes the gap.
The open frontier
When the rhythm meets the org chart
Everything above is about one operator on AI rails. The harder question is what happens when a whole organization tries it at once. I don’t think anyone has answered that yet. What follows isn’t a framework. It’s the set of questions I’d be working on if I were running a large team into this.
Start with why small feels magical. A team of one, two, or three moves at a stunning pace right now because the coordination cost rounds to zero. Nobody to sync with, nothing to hand off, no meeting to schedule. That is the whole trick, and it is also why it doesn’t obviously scale. Organizations are coordination machines. The moment you have fifty people each moving at agent-speed on their own thread, the old sync points start to buckle. The standup, the weekly review, the shared cadence that made the rhythm portable, all of it was built for human-paced work.
So the question isn’t whether AI makes individuals faster. It plainly does. The question is what cadence holds a hundred agent-accelerated people together without the whole thing falling out of beat. Four hypotheses I’m carrying, none of them settled.
1Sync goes from time-based to state-based.
When work is produced continuously, not daily, the calendar is the wrong clock. You sync when a piece of work crosses a threshold, not when the hour says so. The cadence becomes a set of triggers.
2Judgment becomes the bottleneck.
Output is infinite and nearly free; senior review isn’t. Everything queues behind the few who can say “so what” for this decision. The rhythm’s new job is rationing that capacity on purpose.
3Three tempos, designed not assumed.
Agent-time is continuous, peer-time is human-paced, senior review is the scarce high-judgment beat. The design problem is interleaving them without the fast tempos drowning the slow one.
4The shape is a lattice, not one beat.
Scale may not mean one synchronized organization but many small agent-augmented pods, each running the same portable micro-rhythm, loosely federated rather than centrally timed.
We know how to make an individual AI-native. We don’t yet know how to make an organization AI-native without it losing the beat. That, not the tooling, is the work of the next few years.