how execution actually takes root …
and where it quietly breaks down.
Most execution problems start in one of two places.
The first is at the very beginning — when the vision itself isn’t clear. What are we actually trying to accomplish? What does success look like when we get there? If the owner and manager don’t share the same answer to those questions, expectations will never align — no matter how well everything else is executed.
The second is in the how. Even when the destination is clear, the path often isn’t. How are we going to do this, in this office, with this team? That breakdown can come from communication that was never designed, or from new workflows being built on top of old ones that were never fully understood to begin with.
Most of what goes wrong lives in one of those two places. That’s where this work begins.
What I do is organized around three phases that mirror the execution process: Ready, Set, and Go. Each phase has a different job. Each one depends on the ones before it. And running through all three is communication — not as a separate track, but as the foundational layer that determines whether any of it works the way it was intended.
PHASE 1: READY – where the work begins
Before any workflow is drawn or expectations are set, the planning team needs to share the same understanding of the goal and what it actually means in the real work. Without that shared understanding, the design work becomes chaotic, shaped by individual interpretations rather than a common picture. What gets designed may still become one plan … but a flawed one, built on assumptions that were never surfaced or tested.
Ready is where questions are encouraged. Questions lead to shared understanding, and shared understanding leads to a realistic plan. Not a plan built around the idea, but one built around the people and the work that will actually live it and bring it to life.
This is not about moving slowly. It’s about preventing false speed.
And when the work has already launched — or already drifted — this is still where the diagnosis begins. Retrospective problem solving starts at the same place: shared understanding of what we were actually trying to accomplish.
Communication in this phase isn’t announcement — it’s alignment. The question isn’t whether the goal was shared. It’s whether everyone in the room sees the same picture.
PHASE 2: SET – Building the structure
Once direction is clear, the work has to be designed — not assumed. Who owns what. What has to happen before the next step can move. Where the system will strain when real volume arrives. What a decision looks like at the front line, when the person making it doesn’t have time to ask.
Set is where execution gets its architecture. Workflow becomes traceable. Responsibilities become clear enough that people can act without guessing. The gaps that looked invisible in planning become visible before they cause problems.
At this phase, communication is design. The question isn’t whether the manager communicated the plan. It’s whether the plan was built so that the people doing the work could understand it the same way across every role.
PHASE 3: GO – bring the work to life then protect it
Go-Live is not a finish line. And it’s not just a date on the calendar.
The days leading into a launch matter as much as the launch itself. Training needs to be completed and understood, not just delivered. The team needs to know what is changing, what is staying the same, and exactly who to go to when something isn’t clear. Leadership needs to be visible and prepared before the first day begins, not reactive after it ends.
When that preparation is in place, the designed structure has a real chance of surviving first contact with the real work. When it isn’t, small workarounds begin immediately. The design starts eroding before anyone realizes it. What worked on paper starts drifting from the original intent.
Go is where presence matters. Not hovering but supporting and stabilizing. Where early disruption gets treated as feedback, not incompetence. Where the front-line team gets additional training or tools before they’re left to figure it out on their own.
The first 90 days after launch determine where the work survives or drifts.
In closing
The expectations around new vision or change are rarely complicated. Bring the ship in.
What makes that possible isn’t calm seas. It’s a vessel built well enough to handle the rough ones. Ready builds the foundation. Set designs the structure. Go protects it once the real work begins.
If any of this sounds familiar, whether you’re about to launch something new, in the middle of something that’s already straining, or simply know that things could be running better than they are, I’d welcome a conversation.
“Don’t tell me how rocky the sea is, just bring the ship in.”
Lou Holtz
Connie StClair | Operations Readiness 