During our Accountability Chart session, our Vice President of Operations threatened to resign if we split field service from warehouse logistics, arguing that her unique background is the only reason the current setup works. How do we enforce the 'structure before people' rule when a key leader holds the company hostage over their customized seat?

Question

Tyler Smith · Accepted Answer

When an executive threatens to walk because you are separating distinct operational functions, they are attempting to negotiate your company's future around their personal comfort. You must never let individual personalities dictate the structural architecture of the business.

In EOS, we enforce structure first, people second. Field service delivery and warehouse logistics require completely different operational cadences, metrics, and skill sets. Field service manages mobile technicians, scheduling, and customer disputes. Logistics manages inventory accuracy, freight costs, and facility throughput. Merging them because one person happens to understand both creates a single point of failure and makes the business unscalable.

Call the issue out directly in your session. Take people's names off the chart entirely. Remind the leadership team of your shared V/TO and the three-year target. Ask the room: If we were designing this business from scratch today to hit our revenue and margin targets without knowing who worked here, would field service and warehouse logistics be one seat or two? The honest answer is almost always two.

Once the ideal structure is locked, address the person. Acknowledge the leader's immense contributions, but make it clear the structure will not bend. Offer them the seat where their GWC delivers the highest leverage.

If they choose to resign, accept it. An executive willing to hold the enterprise hostage over box boundaries is already a structural bottleneck. Losing a leader is painful, but warping your organization around an ego will cripple enterprise value.