Every senior leader has, at some point, sat in a room and heard a version of the same complaint. The team isn’t committed. They won’t hold each other accountable. Conflict turns personal instead of productive.
The instinct is to treat each of those as its own problem, with its own fix. A commitment problem gets a goal-setting exercise. An accountability problem gets a new scorecard. A conflict problem gets a mediator.
None of it holds because none of it is actually the problem. It’s a symptom of the same missing foundation showing up in three different rooms.
The Blind Spot Between Intention and Impact
Desiree Petrich has spent years inside teams stuck in exactly this pattern, and she starts in the same place every time: trust.
Not the surface version of showing up on time, doing what you said you’d do. The deeper version: a team member’s willingness to admit a mistake, ask for help, or say “I don’t know” out loud without wondering if it will be used against them later.
Here’s what makes that layer so easy to miss.
Most leaders believe their intentions are good, and most of the time they’re right. But a team doesn’t experience intentions. It experiences impact.
When the two don’t match — when a leader means to be supportive but the team experiences pressure, or means to be direct but the team experiences dismissal — a gap opens that nobody names out loud. That is exactly where a lack of trust actually lives. Not in bad intent. In an unexamined blind spot between what a leader means and what a team feels.
The distinction matters because it changes where you look for the fix. You don’t fix a blind spot by trying harder at the thing you’re already doing. You fix it by building the kind of environment where someone will actually tell you it’s there.
The Question That Diagnoses Itself
When Desiree works with a smaller, intact team, she starts with a survey. Buried inside it is one question she calls the most self-diagnosing of the set:
Out of a list of trust behaviors, which ones do this team most need in order to build trust?
The answers tend to sort into two very different categories, and which category a team lands in tells a leader almost everything.
One category is corrective — stop gossiping, admit mistakes without fear, let go of grudges. These are signs a team hasn’t reached a trust baseline yet. There’s active toxicity to clear before anything constructive can be built on top of it.
The other category is additive — understand each other’s working styles, spend more time together, learn about each other’s lives outside of work. These are teams that have already cleared the baseline and are looking to deepen something that already works.
Both are useful information. But leaders are frequently surprised by which category their own team falls into because from the front of the room, a team that’s quietly below the line on trust can still look calm, professional, and functional.
That’s exactly what makes trust the layer organizations skip. It doesn’t look broken until you ask the right question.
Breaking the Fourth Wall
If the diagnosis stopped there, it would just be a more articulate way of staying stuck. Desiree’s answer to “now what” comes down to a behavior she calls breaking the fourth wall.
The idea: a leader who never lets a team see effort, uncertainty, or a modification to the plan is performing leadership rather than practicing it. Breaking the fourth wall means dropping that performance — telling a team the truth about what’s actually happening, even when it’s a mid-course correction, even when it means admitting a limit.
It sounds small. It isn’t. A leader who is willing to say “I don’t know” or “here’s what I’m adjusting and why” in front of the group is doing the single most repeatable trust-building act available to them. It costs nothing to implement and nothing to scale. It simply requires a leader willing to stop protecting an image of having it all figured out.
Why Consistency Beats Another Workshop
The most common way this work fails isn’t resistance. It’s momentum loss. A team has a strong session, has the hard conversation that needed to happen, and then a few weeks later the person responsible for keeping the effort alive quietly lets it slide. Not out of bad faith. Because something more urgent showed up, and rebuilding trust doesn’t send a calendar reminder the way a production deadline does.
Consistency is the variable that actually separates teams that change from teams that felt good for a month. Not a bigger initiative. Not a better workshop. A leader who keeps showing up to the work after the workshop ends — reading fifteen minutes with the door open so the team sees it happening, revisiting the hard conversation instead of letting it fade, choosing the uncomfortable check-in over the comfortable silence, week after week.
Trust isn’t built in a day. It’s not lost in a day either; in most cases it erodes the same way it’s built: through the accumulation of small, repeated choices nobody is keeping score on except the subconscious of the team living inside them.
From Compliance to Commitment
There’s a version of this that works without any of the above. A leader with enough authority can demand compliance, and for a while, they’ll get it. People will do what they’re told because the alternative is worse.
What that leader will never get is commitment — the kind of engagement where a team pushes for a result because they’ve bought into it, not because they were assigned to it. And the two produce dramatically different teams under pressure. A compliant team executes the plan exactly as written and stops the moment the plan runs into something it didn’t anticipate. A committed team adapts because they understand the goal underneath the instructions.
The uncomfortable finding underneath the compliance-versus-commitment divide is that trust obligates people in a way authority never does. A team that has been given real trust tends to feel a pull to return it — with effort, with engagement, with the benefit of the doubt during a hard stretch. A team that has only been given orders feels no such pull. Compliance has to be re-extracted every single day. Commitment compounds.
Scaling Trust Beyond One Room
All of this is straightforward to picture in a single team of eight or ten people. It gets harder to picture across a cohort of fifty or a hundred frontline supervisors spread across shifts, sites, and departments — which is the actual scale most senior operations leaders are working at.
The mechanism doesn’t change with scale. It just has to be deliberately handed down a level. A senior leader who empowers frontline supervisors to be part of real decisions, who treats them as advocates for their people rather than enforcers of a directive, is teaching those supervisors the exact behavior they need to replicate with their own teams. Influence scales through example far more reliably than it scales through policy. The leadership style a new supervisor was shown on the way up is, more often than not, the leadership style they hand back down — for better or worse.
That’s the actual leverage point for a senior leader who wants trust to exist at scale. Not a single all-hands workshop. A visible standard, modeled consistently at the top, that gives every layer below it something worth copying.
Where to Start
Naming the gap is diagnosis. This is the part where diagnosis turns into action. And only action creates outcomes.
Start with The Leader’s Preflight Checklist at operationlead.com/checklist — a free tool built to help a leader show up with the kind of daily consistency that actually builds trust instead of just discussing it.
If you’re ready to have a facilitator do this work inside your team directly, Desiree Petrich and Intentional Action specialize in exactly that — you can learn more at desireepetrich.com or intentionalaction.net.
And if you’re a senior leader who needs this built as infrastructure across an entire organization — not a single session, but a system that holds after everyone leaves the room — you can learn about our system and process at operationlead.com.
The diagnosis was never the hard part. The rebuild is. And it starts with a leader willing to break the fourth wall first.
Let’s Lead,
Craig
