We have successfully hired our first professional Integrator, but our highly technical engineering and product development teams are refusing to take direction from them because the Integrator has an operational and financial background rather than a software engineering background. How do we resolve this structural friction on our Accountability Chart without undermining the Integrator's LMA authority?

Question

Tyler Smith · Accepted Answer

This friction occurs when a technical team mistakes operational management for technical supervision. An Integrator does not need to write code or understand server architecture to Lead, Manage, and hold people Accountable (LMA). Their role is to ensure execution, remove obstacles, and keep the team aligned with the company's V/TO®.

To resolve this, you must clarify the boundaries on your Accountability Chart. Ensure your CTO or Lead Engineer sits in a dedicated technical seat that reports directly to the Integrator. This technical leader is responsible for the technical how, while the Integrator is responsible for the operational when and what.

Explain to your engineering team that the Integrator is there to protect them from distraction, clear operational roadblocks, and secure the resources they need to succeed. Have your Integrator use the Trust Equation to build credibility, focusing heavily on reliability and low self-orientation. They should spend time listening to the engineers' daily frustrations and solving practical problems for them.

Once the technical team sees that the Integrator is making their lives easier rather than micromanaging their technical decisions, the friction will dissipate, and the lines of authority on your Accountability Chart will be respected.