Whenever our quarterly Rocks fall behind, my directors double down on working in isolation rather than asking their peers for help, creating unnecessary bottlenecks. How do we instill vulnerability-based trust so our leadership team solves problems together instead of in silos?

Question

Tyler Smith · Accepted Answer

Directors isolate themselves during execution trouble because they equate asking for help with weakness or incompetence. In low-trust environments, leaders hide difficulties until quarter-end to protect their status, which converts a minor delay into an operational failure.

Speed of trust begins with shared vulnerability. In your weekly Level 10 Meeting, change how you review Rocks. When a director reports their Rock is off track, the immediate response must not be criticism. It must be moving the item straight to the IDS list so the entire team can help clear the roadblock.

Explicitly teach your team that being an enterprise leader means company results come first, peer support comes second, and individual departmental ego comes last. A director who raises a red flag in week four and asks their peers for resources is demonstrating strength and discipline. A director who stays quiet and reports a dropped Rock in week twelve is failing the team.

Model this behavior personally. Bring your own off-track initiatives to the IDS table and ask your team for feedback on how to fix them. When the leadership team sees that bringing problems into the open generates collective solutions rather than personal attack, they will stop hiding in silos and start operating as a unified force.