Scaffolding is never an event
Why workshop decisions collapse, and what holds them in place.
A room full of people agrees on prioritisation criteria. They build an ownership map. They drop two initiatives. They write entry criteria for new work. They leave with shared language, visible commitments, and a list of experiments to run in the next two weeks.
Within a planning cycle, most of it is gone.
Not because the people forgot. Not because the work was weak. Because the urgency that created the original problem returned, and there was nothing holding the new behaviour in place when it did.
This is the part most interventions skip. The workshop gets designed. The follow-up doesn’t. And the follow-up is where the scaffolding either holds or quietly collapses.
What happens without a rhythm
I’ve watched this pattern enough times to describe it almost to the week. Week one after the workshop, energy is high. People use the new language. They reference the criteria. They push back on a request using the entry filter. It feels like something has shifted.
Week two, a senior stakeholder sends a message marked urgent. The request doesn’t meet the entry criteria, but nobody is confident enough to send it back. The ownership map says the team lead should make that call, but the team lead wasn’t in the workshop and doesn’t know the map exists. The request enters the system. The criteria get bypassed. Nobody says anything because nobody wants to be the person who says “we agreed to something different three weeks ago.”
By week four, the shared language has thinned out. The experiments that were supposed to run got absorbed by delivery pressure. The Conflict Wall is still on the wall, but nobody references it. The prioritisation criteria sit in a shared drive somewhere.
Nothing failed. Nothing was rejected. The system simply reasserted itself, because the system operates every day and the workshop happened once.
What a follow-up rhythm actually looks like
A prioritisation follow-up rhythm is a structured one-hour session, repeated weekly, where the decisions made in a workshop get pressure-tested against real operating conditions. It is the structure that makes workshop decisions stick.
It is not a check-in call. It is not a retrospective. It is not a status update where people report what they did.
It is a structured container where the decisions made in the workshop meet real operating conditions for the first time. One hour. Small group. People invited based on where friction has actually appeared, not based on who attended the original session.
I remember one session where the first ten minutes surfaced a request that had arrived on Tuesday, bypassed the entry criteria entirely, and displaced two agreed priorities by Thursday. The team hadn’t pushed back. They hadn’t known they could. That ten minutes did more for the ownership map than the original workshop had.
The hour has a simple flow. Ten minutes on what has happened since the last session: what held, what collapsed, what surprised you. Fifteen minutes on a live prioritisation case: a real decision the team is facing right now, worked through using the criteria and ownership map from the workshop. Fifteen minutes on one intake or ownership tension: a request that arrived mid-cycle, an ownership question that surfaced, a WIP issue that became visible. Ten minutes of decision support: the group makes a call together, using the shared language, in real time. Ten minutes on commitments for the next week.
That is not coaching in the traditional sense. It is three things woven together, and I went back and forth on the labels before settling on these.
Coaching: reflective. What held. What collapsed. What the team learned about how their system responds to the new behaviour under real pressure.
Mentoring: developmental. Building the confidence and capability of the people inside the organisation who will run these conversations after the external support ends. Not teaching them a framework. Giving them reps.
Decision support: applied. Decision support in prioritisation means working through a real live case using the artefacts the team built, and making an actual call in the room. This is the ingredient most follow-up models miss entirely. The team isn’t reflecting on past decisions or planning future ones. They are making a decision, together, right now, with the criteria and ownership map in front of them. That is what builds muscle memory.
Why four sessions matters
Four sessions across four weeks is not arbitrary. It matches a planning cycle. Most teams operate in monthly, six-week, or quarterly rhythms. Four weekly sessions means the new prioritisation behaviour gets pressure-tested across an entire cycle before the team is on its own.
Week one catches the first urgency override. The senior request that arrived without meeting the entry criteria. The team brings it to the session, works through how it should have been handled, and agrees on what to do differently next time.
Week two catches the first ownership gap. The re-sequencing that happened without the right person being asked. The team uses the ownership map to clarify who should have been involved and adjusts the map if it was wrong.
The urgency hasn’t changed. The scaffolding is being tested.
Week three catches the first signs of decay. The criteria being referenced less. The entry filter being softened. The session names what is slipping and why, and the group decides what to reinforce.
Week four is a review. What has changed. What has held. What the team can now sustain on its own. This session is not a celebration. It is an honest assessment of what the system will hold without external support and what still needs internal attention.
The exit strategy is internal ownership
Internal enablers are the people inside the organisation who can run prioritisation follow-up conversations after external support ends. Building this capability from the first session is the only exit strategy that works.
The follow-up rhythm has a built-in expiry. Four sessions, then it stops. The question is what remains after it does.
The answer is internal enablers. People inside the organisation who can run these conversations themselves. Not because they’ve been trained on a framework, but because they’ve been in the room while the conversations happened. They’ve watched how a live case gets worked through. They’ve seen how a conflict gets surfaced and resolved using the shared language. They’ve had practice facilitating parts of the session with support.
The best enablers are not the most senior people. They are the people who volunteered. In this engagement, change champions self-selected after the first workshop by choosing to attend the second session in an active facilitation role. They weren’t assigned. They raised their hands. That self-selection is the strongest predictor of whether the capability transfers.
The enablers don’t need to run every exercise from the original workshop. They need to run the conversations that matter most: the live case, the intake tension, the ownership check. Those three conversations, repeated weekly or fortnightly, are what prevents the scaffolding from being temporary.
What to do if your workshop outputs are already decaying
Don’t run another workshop. Run a one-hour session with the people closest to the friction.
Put three things on the table: one live prioritisation case the team is facing right now, one intake or ownership tension that has surfaced since the workshop, and the criteria and ownership map from the original session.
Work through the case together. Use the tools. Make a decision. Then ask: did the criteria help? Did the ownership map hold? What needs adjusting?
That one hour will tell you more about whether the scaffolding is working than any survey or retrospective. And it will reinforce the behaviour more effectively than reminding people what they agreed to.
Scaffolding is not an event. It is a rhythm.
If you’ve run a workshop that produced real energy and then watched it quietly thin out over the following month, I’d be curious to hear where the decay started. That is usually where the rhythm needs to live.
This is the sixth in a series on the structures underneath good prioritisation by Kubair Shirazee, architect of the Decision System Tune-Up, a contained prioritisation intervention for cross-functional teams. Previously: Prioritisation is a scaffolding problem, What your team knows about prioritisation, The wall where the hidden rules live, The criterion you’re already using, and Who can say yes, and does everyone know it?. Next: nail it before you scale it.