Why I’d Choose One Rigid Process Over a Flexible Menu Every Time

Case Study

Flexibility feels like the safer choice. It isn’t. It’s usually the choice that quietly loses.

I got asked to weigh in on a redesign recently, a large training program I’ve advised on, rebuilding a fixed block of team time that happens once a year. Five hours, one shot, real budget behind it. Two models were on the table.

Option one was a menu. Teams pick from a set of clinics and labs based on where they are. My first reaction reading it was: yes. Let’s be responsive to varied needs. That felt like the obviously right answer.

Option two was a single sustained process. Same arc for every team, no menu, no picking and choosing. Frame the problem, design a response, refine it, leave with next steps.

I sat with option one a while before I talked myself out of it. What changed my mind wasn’t theory. It was remembering what actually happens after a training like this, both as someone sitting in the room and as the consultant who has to follow up. The variability is the risk. Not variability in the content. Variability in whether anyone actually keeps the work moving once the room empties out. That part almost always gets left to individuals, and individuals get swept up in whatever else is happening that week. Follow-through was never the plan. It was a hope.

The menu breaks on the thing you can’t see coming.

A flexible menu only works if every path through it is run well. That means every facilitator, across every room, has to be calibrated on every module in the menu. In practice, that never happens. Facilitation gets pooled. Some rooms get someone excellent. Some get someone who’s never taught that particular clinic before. The team can’t tell the difference until they’re already living it.

A single process has one thing to calibrate. One protocol, one training, one bar for what “good” looks like. You can actually norm a group of facilitators on one thing. You cannot norm them on six.

That’s the part flexibility hides. It looks like it’s serving the team. It’s actually serving the illusion that variation in delivery doesn’t matter, as long as choice is on offer. It does matter. Choice doesn’t fix a badly run session. It just gives you more ways to have one.

But the real problem was never the five hours.

I’ve watched this exact pattern too many times to count. Five hours of genuinely solid work. A team walks out with a plan on paper, energized, clear on what’s next. Ninety days later, other things have become priorities, or emergencies, and that piece of paper hasn’t been looked at since. Best case, someone finds it again at the end of the year during a review, and not much has actually come of it.

That’s the handoff problem. It’s not a facilitation problem. It’s not even really a content problem. It’s the fact that the event ends and nothing catches what came out of it.

So the fix isn’t a better five hours. It’s a rail underneath it.

Whatever model runs in the room, every team needs to leave with one standardized artifact. Not notes. Not a worksheet. One structured output: the focus they chose, the key insight, two or three next steps with owners and dates attached, and, critically, who else needs to be in on this that isn’t in the room yet.

I’ve built these artifacts with teams myself and used them as a standing agenda item for the work that follows. Sometimes that makes me an accountability partner. Sometimes it just helps a team hold their own focus when the calendar gets loud again. Either way, the artifact only works if it has somewhere to go and someone whose job it is to bring it back up. That’s the difference between a plan and a piece of paper.

This is where most redesigns quietly fail. Leadership fixes the visible thing, the room, the agenda, the facilitator guide, and skips the wrapper around it. A better five hours with no rail underneath is still a nicer version of the same dead end.

The translation for anyone running a leadership program, an offsite, or a training rollout is direct.

Stop treating the session as the product. The session is upstream of the product. The product is one artifact that survives the room and travels somewhere with teeth: a manager’s next 1:1, a coaching conversation, a follow-up that’s built into someone’s job, not optional and not left to memory.

And stop measuring it with a satisfaction score. A room can feel great and still produce nothing ninety days out. Track whether the artifact got produced. Track whether it named an owner and a date. Track whether it actually got picked back up in whatever came next. Those are cheap to measure and they tell you something a smile sheet never will.

Most programs end in a folder of disconnected worksheets, one per activity, none of them built to leave the building. Design for the opposite. One artifact. One place it goes. One person whose job is to pick it up when it gets there.

The room was never the hard part. What happens after the room is.