Our leadership team carries deep baggage from a botched software migration last year, and executives are now cynical and shooting down new initiatives. How do we clear this past resentment and rebuild operational trust?

Question

Tyler Smith · Accepted Answer

When a major operational failure occurs and is never fully resolved, it creates relational debt. Your leadership team stops trusting each other's competence and motives. Cynicism takes root, and artificial harmony replaces honest debate because no one wants to risk another disaster.

You cannot fix this with team-building exercises or pep talks. You fix it by confronting the failure head-on in your next offsite or extended Level 10 Meeting™.

Dedicate two full hours to a structured post-mortem. Put the failed project on the board as the primary issue for IDS®. Set ground rules: this is not about assigning personal guilt, but about uncovering the systemic truths of why it failed. Address three explicit questions:
- What operational assumptions did we make that were demonstrably false?
- Where did communication and accountability break down across seats?
- What commitments were made that were not kept?

Force every executive to state their perspective candidly. As the owner or Integrator, you must model vulnerability first. Acknowledge where your own leadership or oversight failed during that rollout. When leaders see the head of the company take ownership of mistakes without defensiveness, the defensive walls in the room begin to drop.

Once the brutal facts are out, define the concrete lessons learned and agree that the post-mortem is officially closed. You cannot run a high-growth company while driving with your eyes in the rearview mirror. Build the guardrails into your current V/TO® and quarterly Rocks, and require every leader to commit fully to forward execution.