Our head of operations is highly resistant to adopting any AI tools because they fear it will compromise our quality control, while our head of sales wants to automate everything. How do we resolve this conflict using the EOS framework?

Question

Tyler Smith · Accepted Answer

This type of friction is natural when implementing disruptive technology, and it often stems from a mismatch in conative styles on your leadership team. Your sales leader likely has a high Quick Start instinct, driving them to experiment and innovate, while your operations leader may have a high Fact Finder or Follow Thru instinct, driving them to protect systems and maintain quality.

To resolve this, use the IDS® process during your next weekly meeting. First, define the issue clearly: the conflict is not about AI itself, but about establishing safe, measurable boundaries for its implementation.

Rather than letting both sides debate abstract concepts, assign a temporary, thirty-day Rock to design a small, low-risk pilot program. The operations leader should own this Rock. This gives them control over the quality parameters, ensuring that any AI tool tested must pass their strict verification steps before it touches a client.

By giving the skeptical leader ownership of the evaluation process, you respect their role on the Accountability Chart and leverage their natural instinct to protect the business. This structure allows your company to innovate safely without creating division on your leadership team or sacrificing your operational standards.