Things start with energy and die in silence. An initiative kicks off, gets worked for a while, then quietly stalls, no decision to stop it, no completion, just a slow fade as the next urgent thing pulls attention away.
Over time the organization accumulates a graveyard of half-done work: projects at sixty percent, commitments everyone vaguely remembers, initiatives important enough to start but never important enough to finish. Nobody can say with confidence what is actually done, status lives in people's heads, and because finishing competes with starting and starting always wins, the pile of in-progress work grows while the pile of completed work does not. This guide installs the discipline that carries committed work to done: it defines what done means, makes the state of every initiative visible, installs the cadence that drives work forward and surfaces blockers, fixes accountability to named owners, and tracks throughput so you can see, and improve, how much you actually finish.
Plan two to three hours to define done, inventory in-flight work, and stand up the cadence, then the recurring cadence itself. Bring the owners of the work. Cadence without them becomes a status theater no one trusts.
If nothing finishes because there is simply too much in flight at once, fix capacity first in Capacity and Workload Management; a cadence cannot rescue an overloaded system. If the work that stalls is specifically client-facing delivery, the deeper work is in delivery and client experience. If initiatives stall because no one agrees they are the priority, settle that in Priority Clarity and Alignment.
Work stalls partly because "done" is ambiguous, so initiatives drift in a permanent almost-finished state no one can confirm or close. Define, for your common work types, the explicit set of conditions that must be true for something to count as complete: the deliverable produced, the acceptance criteria met, the result handed off or deployed, the loop closed with whoever needed it. Set this as a reusable standard, so completion is judged against criteria rather than opinion. The test of a good definition is that two different people would agree on whether a given initiative meets it.
Open the Definition of Done Standard →You cannot run a meaningful status rhythm over work whose status is invisible. Inventory every initiative and significant commitment currently in flight, and place each on a single shared tracker showing what it is, who owns it, its state from not-started through in-progress to done, whether it is blocked and by what, and the next action that moves it forward. Judge each initiative's state against the definition of done, not against effort spent. This view typically reveals the truth the organization has been avoiding: far more is in progress than anyone realized, several things are blocked and have been for a while, and a number have quietly stalled with no owner moving them.
Open the Initiative Tracker →Completion is not an event; it is the product of a cadence that returns to the work at a regular interval and asks, every time, what moved, what is stuck, and what happens next. Stand up a short, regular execution review, commonly weekly, with a tight structure: walk the tracker, confirm and clear what reached done, assign each blocker an unblock action with an owner and a date, and confirm the single next action for each active initiative. This is deliberately not a status recital; it is a forward-driving session. Pair it with the work-in-progress discipline from capacity work: new initiatives enter only as completed ones clear. Where you already have a meeting rhythm, this cadence slots into it as the progress-and-blockers review rather than becoming yet another meeting.
Open the Execution Cadence Template →Shared accountability is no accountability. For every active initiative, confirm one named owner, not a team, not "we," one person accountable for moving it to done and for reporting its status into the cadence. For every blocker, assign a named owner of the unblock action with a date. Capture commitments where they are visible and reviewable, so each cadence checks whether last cycle's committed actions happened, and names it plainly when they did not. The shift this produces is that "I'll handle it" becomes a visible, owned action rather than a good intention that evaporates. Keep the tone constructive: the point is to clear stuck work, not to assign blame.
Open the Accountability and Action Log →Measure how much you actually finish, so completion becomes a tracked, improvable number rather than an impression. Track a small set of signals over time: how many initiatives reach done per cycle, how long work takes from start to done, how much is in progress at once, and how many items are blocked and for how long. Throughput rising and cycle time falling means the discipline is taking hold; in-progress climbing or blocks lingering means it is slipping. Review the signals on a regular interval, treat a persistent stall as a problem to solve rather than a number to note, and use the trend to tune your work-in-progress limits. This is also where backsliding shows up first.
Open the Throughput Tracker →You can say, at any time and from one place, what is done, what is in progress, and what is blocked. Initiatives reach a defined done and get cleared rather than fading at almost-finished, blockers surface in the cadence and get an owner and a date, every active initiative has one accountable owner and a known next action, and throughput is a number you watch and it is moving in the right direction (Systems: Level 2 to 3 and 4, Communication and Measurement: Level 2 to 3).
If the team now completes work but individuals still cannot find focus to do their part, move to Individual Effectiveness and Focus. If the cadence keeps choking because too much is still in flight, return to capacity. Individual Effectiveness and Focus →