After kickoff, alignment does not maintain itself. Execution is the discipline of setting a cadence for client, team, and firm, one that keeps the work in step rather than ordered by the most urgent request of the day.
Illustrated module guide · the complete walkthrough · companion to the Quick ReferenceIn Module 7, kickoff created alignment across the team and client. A few weeks into execution, if nothing actively maintains it, what happens to that alignment?
The pattern
The pattern is familiar. The kickoff lands well. The team understands the plan. The client feels confident. A few weeks later, something is different. The team is busy, but priorities are unclear. Questions that should have been decided are still open. Progress is slower than it should be. Nothing has failed. But the project has lost its rhythm, and when rhythm disappears, alignment quietly erodes behind it.
Strong PMs do not rely on momentum. They run the project on a rhythm they set, so the work stays in step rather than ordered by the most urgent request of the day.
Execution is a system the PM operates. That system has a specific shape.
The system
A project carries three kinds of value at once, to the client, the team, and the firm. Each is protected by its own rhythm. A project manager who runs all three keeps the project in step. A project manager who drops one lets that value slip without anyone deciding to let it go.
Maintains engagement and decision flow. The PM pushes information before confusion appears, without waiting to be asked.
Maintains clarity and focus. Each week the team knows what matters most, who owns it, and what is in the way.
Maintains financial visibility. Effort stays aligned to the plan, and drift becomes visible while it is still small.
The pattern from Module 1 holds here: the PM is the integrator of all three. A rhythm that serves the client and ignores the firm’s economics is not rhythm. A rhythm that keeps the team busy and leaves the client without information is not rhythm either. Each one protects one kind of value at the expense of another.
The cadence
The three rhythms share one cadence. Weekly keeps the work moving. Monthly keeps confidence and money visible. Each phase resets expectations for what comes next.
| Cadence | Client rhythm | Team rhythm | Business rhythm |
|---|---|---|---|
| Weekly | Share key developments and surface upcoming decisions. | Set the week’s priorities, owners, and blockers. | Check effort against plan and watch early financial signals. |
| Monthly | Concise client update: headlines, progress, risks, indicators. | Step back: is the project on track to the milestone? | Review margin, burn, and forecast against the budget. |
| Phase | Reconfirm the client experience and expectations. | Reset focus for the next phase’s priorities. | Reconcile the phase financially before the next begins. |
The habit
Rhythm is maintained by a small weekly habit. Before each week begins, the PM runs a quick self-check across the three domains. If any answer is unclear, rhythm is weakening, and that is the signal to act before the week, not after it.
?Pause & predict.
A coordination conflict surfaces on Tuesday. The PM notes it to raise at Thursday’s standing meeting. Meanwhile two disciplines keep working around the conflict. What did waiting cost, and what should the PM have done?
The control tool
The single most important execution control tool is the decision log. Most projects slow for a reason other than difficult work. They slow when a decision sits with someone, invisible, and no one is tracking it. The log makes every pending decision and its owner visible, so a delayed decision becomes obvious while there is still time to pursue it.
?Pause & predict.
Which of the three rhythms does the decision log most directly serve, and why does an out-of-date log threaten the whole project?
The close
A PM who runs on reaction answers whatever arrives first that day and calls it busy. A PM who runs on rhythm decides in advance what each week, month, and phase must produce, and the urgent items then land inside a system that can absorb them. The difference is not effort. The difference is whether the PM sets the cadence or the project sets it.
This week, run the weekly PM diagnostic on one live project. For any answer that is not a clear “yes,” take one action before the week starts, and open or update the project’s decision log if you do not have one.
?Challenge · from memory.
From memory: name the three execution rhythms and the value each protects, and name the primary execution control tool.
The one idea
Execution is a rhythm, not a reaction. The PM sets the cadence of communication that keeps client, design, and delivery in step.