The 13-week execution plan: turning priorities into scheduled work

Why a due date at the end of the quarter guarantees week-eleven panic, and how to schedule work across weeks so week one has something in it.

7 min read · All guides

Key takeaways

A deadline at the end of the quarter produces work at the end of the quarter. Scheduling across weeks moves effort forward.
Breaking a commitment into weeks surfaces the capacity conversation while there is still time to act on it.
Weekly marks build a record that distinguishes never-worked from worked-and-blocked — two completely different problems.
Week four is the checkpoint that matters; by week eight a failing quarter is usually unrecoverable.

The deadline problem

Give a busy owner a commitment due at the end of the quarter and the work will start somewhere around week nine. This is not laziness; it is how attention allocates itself against competing urgent demands. The quarterly commitment is important and never urgent, right up until it becomes both.

The result is predictable: two commitments finish in a rush, one finishes badly, and one does not finish at all. Then the look-back concludes the team over-committed, when what actually happened is that nothing scheduled the work.

Scheduling as a capacity conversation

Ask which weeks a commitment will actually be worked, and something useful happens immediately: the room discovers that three of the five priorities all want weeks two through five, and that one owner is on every single one of them.

That conversation is worth having on planning day, when the response can be to sequence differently or re-owner something. Having it in week six, when it emerges as a series of missed marks, costs half a quarter.

What a good weekly breakdown looks like

Front-loaded where possible. Something in week one, always, even if it is small.
Honest about gaps. A commitment nobody will touch in weeks five and six should show that, not pretend to continuous progress.
Owner-aware. One person's weeks should be legible across all their commitments at once.
Ending before week thirteen. Due week eleven or twelve leaves room for the thing that always goes wrong.

The plan does not need to be accurate. It needs to be specific enough that a deviation is visible.

Marks, and what they tell you

A weekly mark is a ninety-second act: was this worked on or not. It sounds trivial and it produces the single most useful artifact in the whole process — a record of effort rather than only outcome.

When a commitment fails, the marks answer the question that determines your response. Never worked means an attention or ownership problem. Worked every week and still not done means an estimation or blocker problem. Same failed commitment, completely different coaching conversation, and without marks you are guessing.

Week four is the checkpoint that matters

By week four the pattern is set: either the quarter has traction or it does not. Nine weeks remain, which is enough to recover a commitment that has not started, re-scope one that is too big, or park one that reality has overtaken.

By week eight the same information is nearly useless. The arithmetic no longer works and the honest response is to salvage one commitment rather than half-deliver three. Almost every rescued quarter we hear about was rescued in week four or five.

Recommit, re-scope, or park

When something is drifting, there are exactly three legitimate responses, and all of them are decisions rather than drift. Recommit means the work is still right and attention gets reallocated. Re-scope means the outcome is right and the size was wrong. Park means reality changed and this is no longer the best use of the quarter.

Write down which one you chose and why. Next quarter’s look-back is dramatically more useful when it can distinguish a parked commitment from a failed one — and clients are far more honest in planning when they know parking is a legitimate move rather than an admission of defeat.

Where QuarterOS fits

QuarterOS puts every commitment on a thirteen-week grid with an owner and a due week, and the weekly marks build the record automatically — so week four is a glance rather than an investigation.

See 13-week execution →

FAQ

Questions this raises.

Is this not just project management?

No. There are no dependencies, resource levelling or task hierarchies here. It is a coarse weekly map of a handful of commitments, at the altitude an owner actually thinks about them. Anything more detailed stops being used within a month.

Who does the weekly marking?

The commitment owner, in under two minutes. The coach's job is to look at the marks before the check-in, not to collect them.

What if a quarter is clearly lost by week six?

Salvage one commitment properly rather than half-delivering three, and be explicit that this is what is happening. A quarter with one real win and two honestly parked items is a better outcome — and a much better look-back — than three vague partials.