Most teams survive. A few actually execute.
- Christy Slanaker
- 3 days ago
- 4 min read
What an MBA capstone, a real client, and two years of strategy work reminded me about the hidden architecture of team execution.
There is a specific quiet that descends in a team meeting when nobody knows who owns the next move. The agenda is on screen. Three people are nodding. Someone says, "yeah, we should figure that out." The meeting ends. Nothing happens.
That silence is expensive. Most teams have it weekly and have stopped noticing.
For the last four months, I have been part of an Executive MBA capstone team at Boise State University. Our client was the Idaho Military Museum. The work was real strategy for a real organization with real constraints, and we delivered the final piece this week.
The deliverable was strong. That is not what I want to write about.
What I want to write about is why some teams produce work that delights a client and most teams produce work that just survives a deadline. After almost twenty years of leading sales organizations, partnership teams, regional teams, and now this capstone team, I am increasingly convinced the difference is not talent. It is not motivation. It is not even strategy.
It is three pieces of operating architecture most teams quietly under-build.
1. Communication that is direct, not diplomatic.
Most teams confuse politeness for professionalism. They soften observations into questions, defer hard conversations until the next meeting, and end up rebuilding work in week six that should have been corrected in week two.
Direct communication is not bluntness. It is the discipline of saying the actual thing in the actual moment. "I do not think this section is working, and here is why" is a sentence most teams cannot say to each other in week three. By week eight, the cost of that unspoken sentence is everywhere.
The teams that execute well learn to compress that timeline. They say the hard thing early, when it is still cheap to say.
2. Roles that are owned, not assumed.
"We will figure it out" is the sound of a team about to miss a deadline.
Most team breakdowns are not strategy failures. They are ownership failures. Two people thought the other one was running with it. Three people had opinions and nobody had the pen. The decision needed to happen on Tuesday and there was no Tuesday meeting.
Effective teams do something deceptively simple. Before the work starts, they name who decides, who delivers, and who advises. Not in a RACI chart that nobody reads. In a five-minute conversation that nobody forgets. Then they protect those lines when pressure arrives, instead of letting them dissolve into "all hands on deck."
Ownership is not a personality trait. It is an artifact a team chooses to create.
3. Steady confidence under pressure.
This is the one most teams cannot manufacture if it is not already there.
When timelines compress and ambiguity grows, most teams default to one of two postures. They get loud and chaotic, or they go quiet and disappear. Both are forms of the same thing, which is being run by the pressure instead of running through it.
Steady confidence is something else. It is not the absence of doubt. It is the presence of a person who can sit with doubt and still make the next decision. It is quiet. It is unflashy. It is the operator at the meeting who says, "okay, here is what we know, here is what we do not know, here is what we do next." Teams with one or two of those people execute differently than teams without any.
Our capstone team had all three pieces of architecture. That is not luck. That is leadership, distributed across people who chose to take the work seriously, including the unglamorous parts that do not show up in the final deliverable.
Where this points
Strategy is the visible part of the work. It is the part that gets presented in decks and discussed at offsites. It is also, in my experience, the easier part.
Execution is the part that actually determines whether anything happens. It is the part where most engagements quietly fail, six weeks after the consultants leave. Most strategy practices stop at the recommendation. The Dark Horse Advisory starts where strategy stops being
useful and execution becomes the actual job.
If you lead a team that produces good plans and inconsistent results, you do not need a better plan. You need to look at those three pieces of architecture and ask, honestly, which one is missing.
Usually it is one. Sometimes it is all three. Either way, the work of fixing it is real, learnable, and not the same as having a smarter strategy.
That is what we build here.
To my capstone team, thank you for being the kind of team I would build a company around. You are the case study I will reference for years.
To the Idaho Military Museum, thank you for trusting us with work that matters to your mission.
More to come.
Comments