Your last leadership program got high ratings. Day one ran hot — energy in the room, people swapping war stories, trying a new framework. Day two ended with personal action-plan templates: write down what you'll do differently, share it with your manager, we'll check in. Three months later you checked in. Maybe a third of the cohort could tell you what was on their plan; a handful had actually changed how they showed up. The spark in the room turned out to be bright for thirty seconds, then gone.
Running the workshop again with a better facilitator wouldn't fix that, because the workshop was never the problem. Two facilitated days are the easy part. The next eight weeks — back with a team, an inbox at 200, a calendar that didn't get any thinner — are where someone actually starts leading differently, or doesn't. That stretch rarely gets designed, and the parts that change behaviour don't happen on their own. This article is about designing them.
Workshop ratings measure the wrong thing
A leadership workshop almost always rates well. People walked out happy and told their boss it was great. That's a genuinely different question from whether anyone now leads any differently — whether the people who work for them get clearer feedback, more room to act, better decisions.
And the second question is the one that matters, because you're not in the business of making participants happy. You're in the business of making the people around them better led. A high score can sit comfortably on top of a program where nothing downstream changed at all. So treat ratings as a read on the room, not on the result — and design for the result.
The workshop is the anchor, not the program
Picture a leadership program as fifty weeks plus two days in a room. Almost everyone designs the two days. Almost no one designs the fifty weeks — but the fifty weeks are the program.
That's the whole shift: the workshop isn't where the change happens, it's where the change gets pointed at. The day after, each participant leaves with a real, specific commitment for the week. Their manager already knows what it is and is going to ask. Six weeks in, five of them are on a call with no facilitator, working through a problem they all share. After the last day, development doesn't stop — they pick the next thing to practise and start it on Tuesday. The room lights the spark; the weeks around it decide whether it catches. So design the three stretches most programs leave to chance: the week after, the weeks between, and everything after the last day.
Design the week after each workshop
The highest-leverage design isn't in the room — it's the morning after. Instead of "send us your action plan," the participant gets a structured bridge: who exactly will you try this with this week, what's it about, when will you do it? A vague intention becomes a booked, specific act.
The other half is the manager. The manager is the single biggest predictor of whether a participant tries anything back in the real job — so a day or two later, their manager gets a short, parallel nudge: your team member is trying this out this week; just ask how it went. Not the slide deck, not homework — one question they can drop into a 1:1 they were already having. Getting that manager track right is its own craft, and involving managers walks through it.
Design the weeks between — the peer group
Between workshops is where most of the leading-differently actually happens, and where most programs go quiet. They say "meet your peers" and rely on hope; a few book the call, most don't. What's missing isn't enthusiasm — it's scaffolding, and making peer groups actually meet covers how to build it in.
What's worth adding here is what the group is for in a leadership program. Five managers, no facilitator, taking turns on a real problem from the last two weeks — I gave feedback, she got defensive, now what? — same, mine shut down completely — and working each other through it. It's where the judgement a workshop can't hand out actually gets built: people with the same problem helping each other, instead of a consultant explaining concepts. Each leaves with something concrete to try before the next time.
The last workshop is a start, not a finish
Most programs end the final day with five minutes for an action plan and a goodbye. Supporting twenty different paths by hand is hard, so the answer is usually nothing, and hope handles the rest. But the last workshop is exactly where self-directed development can begin.
Keep it going with a short, self-chosen focus on one behaviour — feedback, delegation, a difficult conversation, whatever would move the hardest thing on their plate — a few minutes a week for about a month: a prompt, help breaking a real situation down, do it for real, reflect. When that focus is a shared one, Knowly can run it as a peer sprint on-demand — a small group practising the same behaviour together, set up with you. The manager keeps getting the same one-question-a-week support, now aimed at the new behaviour. Try, reflect, adjust, then pick the next one. Two years on, someone has practised six things, all of their own choosing — a leader developing under their own steam, pick by pick.
One Swedish logistics company built exactly this for new production managers — hard schedules, no patience for fluff — around three workshop days across half a year, with I-message feedback as the core skill and eighteen five-minute activities in the weeks around them. By the third workshop, the opening question had changed. What have you tried since we met? used to be the awkward one, met with shifting chairs and silence. Now, as the customer put it, "it's not silent anymore — everyone has something to tell." That's the difference designing the fifty weeks makes: the workshop stops being the program and starts being the spark the rest is built to catch.