Your Team Doesn't Have a Performance Problem. It Has a Missing Operating System.
The agreements that govern how decisions get made, how conflict gets handled, and how work comes back to you were never written down. So every person on your team is running their own version.
It shows up two ways.
You gave them autonomy.
And they stopped bringing things back. Deadlines slip quietly. Decisions you should have seen get made without you. You find out about problems when they're already expensive.
You kept the reins.
And now every decision routes through you. Your calendar is the bottleneck. Your team waits on you, and you wonder why capable people stopped acting like it.
They feel like opposite problems. They're the same one: nobody ever agreed what comes back to you, when, and in what form.
In a recent session with a room full of CEOs, not one had written operating agreements in place.
Four questions every high-performing team can answer. Most teams can't answer one.
Do I know you beyond your role?
Trust starts with seeing a person, not a job title. Teams that skip this stay polite and shallow, and polite teams sit on what they know.
Do I know how you work?
You process, decide, and handle pressure differently than the person next to you. Different isn't wrong. Unspoken different is daily friction, and friction compounds.
Have we agreed on how we operate?
How decisions get made. How conflict gets handled. What comes back to the leader, and when. Or is every person on the team running their own operating system?
Do we know where we fit?
How your team connects to the teams around it. Synergy with the rest of the organization, or clash that creates work for everyone and burns your team's credibility.
The progression runs from the individual to the system. Performance lives at the end of it.
Your team writes it. That's why it holds.
Over 60 to 90 days, your team builds and commits to its Core Constants: the small set of operating agreements that stay stable no matter what the quarter throws at them. Not values on a wall. Working rules your team authored, tested, and signed.
Discover
Build
Hold
A documented set of Core Constants your team wrote, committed to, and knows how to use. The operating system stays when projects, deadlines, and even people change.
Why people say things here they don't say in meetings.
The working sessions run on LEGO® Serious Play®, a facilitation method built on one rule: everyone builds, everyone shares.
People put their thinking into a physical model before they speak, so the hardest things get said about the model, not at a person. That's the difference between a team that performs the meeting and a team that actually talks.
The agreements that come out of these rooms hold because they were built on what people really think, not on what they were willing to say out loud last quarter.
"In one session, my team was able to visibly see why we were finding progress so slow on a project. The models we built clearly showed we were each solving a different problem."
A team that executes without you in every decision.
That's the destination. The operating system is how you get there. Start with a conversation about which of the four questions your team can't answer yet.