Trust wasn't the first thing this team could fix

Many leadership frameworks place trust at the beginning. Lencioni puts it at the base of his pyramid. Psychological safety models call it a foundation. Team health assessments measure it first.

That ordering makes sense when you're describing a healthy team. It becomes much less useful when you're standing inside a damaged one and asking what to do on Monday morning.

I watched a VP discover this with a struggling engineering organization.

The exercises landed on top of the real problem

The VP followed Lencioni's model seriously. The group ran the exercises, shared vulnerabilities, and had the difficult conversations the book recommends.

Three months later, people were still hoarding information and second-guessing decisions. The sessions had begun to feel performative.

A growth sprint had left a mismatch between several roles, the work those engineers now carried, and the support available to them. Colleagues checked and rechecked the output because it needed checking. Asking everyone to be more vulnerable did nothing to resolve that mismatch.

There was also a history nobody could workshop away. A year earlier, a team lead had been blamed publicly for a failed project and then quietly managed out. Everybody remembered what happened. They had learned that failure could cost somebody their job, however safe the new exercise said the room was.

The VP was trying to begin with trust. The team first needed reliable work and evidence that the rules had changed.

A pyramid can describe the destination

Lencioni's Five Dysfunctions of a Team describes the dependencies clearly. Trust supports productive conflict. Conflict makes commitment possible. Commitment supports accountability and results.

Hold that model against a team that already works and you can recognize the parts. Using it as a repair sequence is harder. The word at the bottom of the pyramid isn't necessarily the first action available to you.

For this team, the practical work was far less elegant:

• Be honest about whether people were equipped for their roles, then give them the support or role changes they needed.
• Make leadership's response to failure predictable.
• Give people decisions they could genuinely own.
• Keep doing those things long enough for the old lesson to lose some of its force.

Trust would be the team's reading of that evidence. It couldn't be one of the tasks on the VP's plan.

Courtesy is still useful on day one

Courtesy, positive intent, and room to act can all begin on day one. I wrote separately about what a manager can honestly promise a new hire. A damaged team needs something different: repeated evidence that reliable work receives support and that failure won't be punished unpredictably.

Frameworks work best after the basics do

I suspect this is one reason trust exercises often look better in successful companies. Those organizations have enough stability to spend time on off-sites and team development. Much of the necessary evidence may already exist: people can do their jobs, leaders behave consistently, and mistakes are survivable.

In that setting, an exercise can help people name and strengthen a relationship they already recognize.

Inside the engineering organization I watched, the exercise was being asked to compensate for unreliable work and a remembered punishment. No workshop could carry that weight.

The less satisfying work came first. Fix what was broken, behave consistently when failure arrived, and wait for people to notice the pattern. There was no announcement that could make the process happen faster.

If a team says it needs more trust, what evidence is currently telling people to hold back?