First, list every change and who asked for it
Go back through the quarter and write down every change to the plan: work added, dropped, moved or resized, budget moved between lines, objectives reworded. For each, note the date, who asked, the reason given and what it displaced. Messages, meeting notes and the work board usually hold enough to rebuild the list in an hour.
Then sort the list into two groups. Changes made because an assumption failed, a result came in, or the market or the business moved are healthy, provided they were made deliberately. Everything else is churn: work added because someone senior asked, a reshuffle after a meeting nobody can recall the reason for, or a cut forced because the plan was already over-full. The ratio between the two groups is the first finding, and the churn group, read by requester and by reason, usually points at one or two of the causes below.
Finally, compare what the plan said at the start of the quarter with what was delivered. A large gap with few recorded changes means the plan was quietly abandoned rather than changed, which points to visibility and review rather than to intake.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Plan breaks within weeks; work slips and is cut, not reprioritised | Planned work against available hours, by skill, at the start of the quarter | Plan agreed without a capacity check | Replan to capacity with a buffer; draw the line visibly |
| Every new request is justified by "it supports objective X" | Count of objectives and whether each has one primary measure | Too many objectives | Cut to a small set, each with one primary measure |
| Changes cluster around senior requesters, often by direct message | Requester and route for each churn change | Senior requests bypassing intake | One route for all requests; displaced work made visible |
| Budget moves after every good or bad week | Whether reallocation rules exist: rhythm, threshold, step size | No agreed rules for moving budget or effort | Write reallocation rules before the quarter starts |
| Team members cannot say what the plan contains | Where the plan lives and when it was last opened | Plan held in a deck, not in a shared calendar | Make the calendar a live view of the planned work |
| Changes happen in corridors and chats on any day | Whether checkpoints are scheduled and where changes are recorded | No review rhythm | Fixed checkpoints where the plan may change; a change log |
Fix, verify and prevent each cause
A plan that never fitted the team's capacity
A plan built from a ranked list without a capacity line is a wish list, and it starts to break the first week a designer is busy elsewhere. What looks like changing priorities is the plan being trimmed to reality one crisis at a time. The capacity step in running a quarterly planning session is where this is prevented.
Fix: take the remaining weeks of the quarter, estimate the hours available by skill after recurring work and a buffer for reactive requests, and redraw the line through the current plan. Move what falls below it to the backlog openly.
Verify: at the next checkpoint, the work above the line is on track and no item has been silently dropped.
Prevent: do not publish a plan until the capacity line has been drawn in the room, and compare planned with delivered work each quarter to size the next buffer. Where the plan fits but too much of it is started at once, the guide to limiting work in progress keeps accepted work in a queue until there is room to finish it.
More objectives than anyone can prioritise against
A plan with many objectives cannot refuse anything, because almost any request serves one of them. The result is a plan that changes to accommodate whoever asks. The objectives and KPIs guide sets out how to derive a few objectives from the business goal and give each a single primary measure (KPIA metric tied directly to an objective.). PR Smith's SOSTAC model, which the SOSTAC framework page summarises, also asks for a few measurable objectives with dates rather than a list.
Fix: cut the quarter's objectives to the few that most move the business goal, and park the rest explicitly.
Verify: the next few requests can be scored as in or out against the reduced set without debate.
Prevent: cap the number of objectives at planning time and require each to name one measure and its source.
Senior requests that skip the queue
The most common churn pattern is a request from a senior colleague that goes straight to a team member and displaces planned work without anyone deciding it should. Each one is reasonable; together they replace the plan. The intake and escalation sections of prioritising work and capacity describe the single front door and the route for genuinely urgent work.
Fix: route every request, whoever it comes from, through the same intake, and when a senior requester wants planned work displaced, show them what it displaces and let them make the trade-off openly.
Verify: the change list for the next month shows requests entering through intake, each with the item it displaced.
Prevent: report displaced work by requester at the monthly review, so the cost of bypassing the plan is visible to the people who bypass it.
No rules for moving budget or effort
When nobody has agreed in advance how and when money moves between lines, every good week invites more spend on the winner and every bad week invites a cut, and the plan's budget becomes a running argument. The reallocation rules in the budget allocation guide set a rhythm, a threshold, a step size and protected floors, written before results arrive.
Fix: agree those rules for the remainder of the quarter, including which lines are protected and where the testing reserve sits, and apply them only at the agreed review.
Verify: the next reallocation is made at the review, within the step size, with the evidence recorded.
Prevent: write the reallocation rules into the plan itself, so they are agreed alongside the objectives and the expected return (ROIProfit relative to cost.) rather than after the first surprise.
A plan that lives in a deck
A plan presented once and filed as slides cannot guide daily choices, because nobody looks at it when a request arrives. The team then plans from the work board, the inbox and memory, and the written plan drifts out of date without anyone deciding to change it. The work management and marketing calendars guide explains how to make the calendar a live view of the work system, with a planning layer for agreed campaigns.
Fix: load the plan's initiatives into the work system as planned items with owners and dates, and give stakeholders read access to the calendar view.
Verify: team members and requesters can find any planned initiative and its status without asking.
Prevent: treat the calendar as the plan of record and the deck as a summary of it, never the other way round.
No fixed moment when change is allowed
If the plan can change on any day, it will change on most of them. The quarterly marketing planning playbook nests a weekly, a monthly and a quarterly cadence and treats the monthly checkpoint as the only place the plan itself changes; the control section of SOSTAC likewise names in advance how often progress is reviewed and what result triggers a change.
Fix: schedule the remaining checkpoints now, state that changes outside them need the plan owner's explicit approval, and start a change log.
Verify: at the end of the next month, most recorded changes carry a checkpoint date and a reason.
Prevent: publish the checkpoint dates with the plan and open each checkpoint by reading the change log.
A prevention routine for a stable quarter
A plan holds when it is small, sized, visible and changed on purpose. Before the quarter, check four things: the objectives are few and each has one primary measure; the work above the line fits the hours available by skill with a buffer; the reallocation rules are written; and the checkpoint dates are in calendars. During the quarter, keep one change log with the date, the requester, the reason and what each change displaced, and read it at every monthly checkpoint. Read the churn share of changes as a health measure: a rising share means intake or seniority is overriding the plan. At the end of the quarter, compare planned with delivered work and use the gap to size the next buffer; if early-stage work across the FunnelModel of the customer journey stages. was cut repeatedly to fund late-stage requests, say so, because that pattern starves the next quarter. Keep a record of what was deliberately cut at planning, so those items cannot return mid-quarter as quick extras. Share the change log with the people who made the requests; seeing their own changes in a list is often the most effective prevention of all.
A software company's quarter that would not hold
A business software company's marketing team of 9 rebuilt its quarterly plan 4 times in 11 weeks. The change list held 31 changes; 7 followed evidence, such as a webinar format that clearly outperformed, and 24 were churn, of which 17 came from 3 senior colleagues by direct message. The plan had 8 objectives and had been written without a capacity check: planned work needed about 1,900 hours against 1,450 available. For the next quarter the head of marketing cut to 3 objectives, drew the capacity line with a buffer of about a fifth, routed every request through one form, published monthly checkpoint dates and shared the change log with leadership. The following quarter recorded 9 changes, 6 of them at checkpoints, and 85% of planned work was delivered.
Common mistakes
Calling every change agility. Planning to full capacity. Accepting requests by direct message because the requester is senior. Moving budget weekly on noisy results. Keeping the plan in a deck. Rewriting the plan instead of recording why it changed.
