My son was playing air guitar in the car on the way to camp, with a remix of the Among Us theme coming through the speakers. He had been working on this air guitar for a week, and it was, for the record, excellent.
Then he gave me his theory: “All great songs have triplets.”
The business version of that excitement is the clever AI addition everyone wants to see. The part nobody gets excited about is whether the team can carry it when its builder stops conducting every beat.
I’m borrowing the image, not teaching a music lesson. A flourish catches your attention. What carries the rest of the song is easier to overlook.
Adding the flashy thing is easy. Earning the right to add it is the whole job.
The draft works. Watch what you do around it.
Picture a hypothetical team preparing a short note for a regular coordination meeting. The note pulls together current status, the items needing attention, and enough background for the people in the meeting to make useful decisions.
You lead the department. You have chosen AI help with the first draft. This is real work your team already does, and you can describe what a useful note looks like.
Give the idea a fair chance. In this example, the draft is good. It uses the supplied material, highlights the right items, and gives the work owner something worth checking.
Now watch how it arrives.
You gather the status notes. You put them into your working session. You ask for the draft, read what comes back, and copy it into the meeting material. Then you tell the work owner where to find it.
“I’ve put it in there for you.”
You have shown that AI can help write the note. You have also personally done every little job connecting that help to the meeting.
Here’s the thing. Those little jobs are part of what you built. They just don’t appear on the screen when you demonstrate it.
The part you do without noticing
It is easy to miss work you can do almost without thinking.
You know which status notes are current. You know the meeting material needs updating before people start preparing. You know the work owner will look in the usual folder, not inside your AI conversation.
So you bridge the gaps.
“I’ll just grab those.”
“I’ll paste that across.”
“I’ll let her know.”
Each sentence sounds too small to be a design problem. Together, they make you the delivery system.
The team sees a useful note in a familiar place. You see a working AI addition. Both impressions can be true while the new arrangement still needs you to make it happen.
That is the part to inspect before you call it part of normal work.
You have not necessarily built a bad tool. Let me tighten that. You may have built a useful drafting step and left the rest of its route attached to yourself.
Improving the prompt will not tell the work owner where the next note will appear.
Find the beat the team already keeps
Before adding AI, our imaginary team already had a way to prepare for this meeting. The work owner gathered the status notes, wrote the summary, checked it, and put it with the other meeting material.
That is the ordinary beat.
It does not have to be elegant. It does need to be clear enough that you can follow one occurrence and recognize what the team was trying to finish.
The Prep List gives us two useful questions here. Repeatability asks whether the work comes around in a familiar shape. Definability asks whether you can say what a good result looks like.
For this note, useful means the meeting has current information and knows what needs attention. The team has a place to find it and a point when it needs to be ready.
Hold those things steady while you look at the addition.
The goal is not to make everybody work inside your favorite AI tool. It is to help the team prepare the note it needs. If a person has to learn your private way of gathering and moving things before they can use the help, that learning is part of the change.
Right? The writing got easier. The route still needs a home.
Walk through the next meeting without filling the gaps
Sit with the work owner and talk through the next occurrence.
Start where the work actually starts. The meeting is coming. The status notes are available. What would this person do next?
“I’d wait for you to send the draft.”
There it is.
You do not need to turn this into an absence experiment or let a real meeting fail. You have already found a dependency worth dealing with. The person who used to prepare the note is now waiting for a piece of work you have quietly taken onto yourself.
Keep going far enough to understand it. Are they waiting because you hold the inputs? Because only you know how to start the draft? Because the draft appears somewhere they never use? Or because nobody has agreed who now begins the preparation?
Those lead to different changes.
Stay with our example. Suppose the inputs are already available to the work owner and the drafting method can be used by them. What has been missing is an agreed place for that step in their preparation. You have been doing it for them because you were excited to show it working.
The first correction may be a conversation about who starts it and where the result goes. Another feature is not the first answer to that problem.
Give the addition a place to land
A possible arrangement is straightforward.
The work owner starts from the same approved status notes. The first draft becomes available in the established preparation location. The work owner checks it before the meeting, just as they checked the note they wrote themselves.
Now there is something specific to examine. Can the person do that through the tools and arrangements the team actually has? What would still require you to gather, move, or explain something?
Do not wave away a gap with “we’ll automate that.” Name the job inside the phrase. Moving the draft is work. Keeping the input set current is work. Someone needs a practical way to carry each part.
The Station Plan makes room for the work of routing between responsibilities. Producing a result and getting it into the team’s next step are both part of the arrangement.
And the human check can stay. The person who knows the work still needs to recognize an outdated status or an item the draft misunderstood. Replacing that judgment is not what makes the addition fit.
What should disappear is the unspoken dependence on you as the person who remembers how to connect every ordinary step.
That is a more useful design target than “make the AI do more.”
A clear plan still needs an ordinary working day
You can walk through that arrangement and feel as though the job is finished.
It is a better plan. Now you need to see it happen.
On the next agreed use, watch whether the work owner can prepare and check the note in time for the meeting without you supplying an extra transfer or reminder. Keep the existing way of preparing the note available while the new arrangement is being worked out.
If you step in, record what you had to do. That is useful information. A successful meeting can hide a missing part of the process when an attentive builder keeps rescuing it.
Does that make sense? The meeting went well and the addition still needed help are compatible facts.
Fix the part you actually found. If the work owner cannot locate the draft, address that. If the source notes are unclear, address those. A rewrite of the whole system can wait while you deal with the first thing that stopped ordinary work.
You are looking for evidence that the team can carry this particular routine, with its necessary checks. One clean run is a start, not a promise about every future meeting.
The Monday Move: the Four Count Test
Pick one AI addition you have already chosen. Bring the person who normally carries that work.
Draw the existing routine, then draw it with the addition. Write what starts it, what useful result comes out, where that result goes, and who needs it next. Use as many steps as the work actually has. The four count is an image, not a limit on the drawing.
Ask where the builder still has to gather, carry, remind, or explain.
Choose the first dependency you find. Propose one change that gives that job a clear place in the normal routine. Name who will carry it and what you would need to observe before calling the change useful.
Keep the difference between drawing the route and seeing the team use it.
My son’s flourish stays with me because it is the part you notice. In a business, the clever addition earns its place through all the ordinary work that carries it.
Build it so the team can carry it without you conducting every beat.
Original framework. Distilled from client work.
