Thirteen clients couldn't teach me how to run the room

I signed up for boot camp in a market where nobody had heard of EOS®. Not "heard of it and wasn't sure," genuinely never heard of it.

There was no easy nod of recognition when I brought it up in conversation, no shortcut past the "what exactly is this" question. Every geography since has had it easier in one specific way: the name itself does some of the work now. Mine didn't. I had to prove the market before I could prove myself in it.

Before I ever sat in a boot camp seat, there was a program called Basecamp. It's had two names since (it's the Academy now, third iteration), but back then it was Basecamp: videos Gino recorded himself, a stack of Implementer guides, and a prescription for what to do next if you wanted to walk into boot camp with something real already built. I didn't know if any of it would work. I decided to trust it anyway and do exactly what it told me to do, one step at a time, without much evidence beyond the fact that it had worked for the people who came before me.

There was no community holding my hand through that part either. I wasn't trading notes with other Implementers in my area, because there weren't any. I wasn't fielding warm introductions from people who already understood what EOS® was, because nobody in my market did. It was closer to cold conversations, one at a time, explaining a framework from scratch to people who had no reference point for it and no reason yet to trust me with it. Basecamp told me what to do. It didn't make the doing any less solitary.

By the time boot camp actually started, I had thirteen clients lined up. Thirteen real companies who had agreed to let me run their EOS® practice before I had run a single official session.

That's not a brag. It's the setup for how humbling the next part was.

Getting the 90 wrong anyway

Thirteen clients should have made me feel ready. It didn't, not entirely, and boot camp has a way of finding exactly the gap you didn't know you had.

There's a tag-team exercise where new Implementers practice running an L10™ with each other. Ninety minutes, live, in front of your peers and your trainer.

I still call it "the 90," and everyone who has been through it knows exactly what those two words mean. You know the agenda, you've watched it modeled, you've read the guide: none of that fully prepares you for running it yourself with the clock actually moving.

I got it wrong.

Not because I didn't know the sequence, I actually conflated my Issues List with something it wasn't. And once you're thirty minutes into a live ninety-minute exercise, there is no quiet way to undo that. You just keep going and hope it resolves itself before the clock runs out. It didn't.

That's the part I didn't expect walking in with thirteen signed clients in my back pocket. I had assumed that having the pipeline solved meant I was mostly there. Boot camp has a specific way of showing you that building a pipeline and running a room are two entirely different competencies, and having proven one tells you almost nothing about the other.

The correction

Paton was running my boot camp, and he was quick to tell me exactly what I'd done. Not unkind about it, but direct: here's what happened in that room, here's what that actually was, versus what you thought it was.

There's a particular kind of exposed feeling in having thirteen real clients waiting for you on the other side of boot camp, and realizing in that room that you have real work still to do before you're the Implementer those thirteen companies think they hired. I had proven I could build. I had not yet proven I could run the session itself, and the gap between those two things was suddenly very visible, to me and to everyone watching.

I could have argued with the feedback, found a reason it wasn't quite fair, chalked it up to nerves. I didn't. I let it land, because arguing with correct feedback doesn't make you less wrong, it just makes you slower to fix it.

The lesson that never left

I've trained something like two hundred Implementers since that boot camp, and I've been back with new cohorts as recently as last week. What I keep noticing, cohort after cohort, has nothing to do with content. Everybody gets the same guides, the same videos, the same prescription I got from Basecamp. What actually separates people isn't what they walked in knowing. It's whether they trust the process enough to throw themselves into it, mistakes included, and whether they take the correction when it comes instead of managing it.

That's the same thing that got thirteen clients through my own boot camp week and out the other side intact. Not that I had it figured out going in, I didn't. It's that I'd done the preparation I was given, and when I got the 90 wrong in front of everyone, I let Paton's correction land instead of protecting myself from it.

Ten years and thirteen hundred sessions later, that's still the whole job, just applied to different things at this stage instead of the tag-team exercise. The conditions keep changing. The room is never quite the same twice. What Peyton corrected in me during a ninety minute practice round is not so different from what shows up in a real session a decade in, just wearing a different costume. Do the work you're given before you're told to do it. Take the correction when it comes, however it arrives. Then go run the next one.

---

This article is based on Episode 5 of the newly launched Practice Builder Podcast, featuring Expert Implementer Ted Bradshaw in conversation with Chris Beer. You can listen to the full episode on Spotify and Apple Podcasts, or watch the full conversation on YouTube.