Our Integrator is completely overwhelmed with nine direct reports and wants to create an Assistant Integrator seat on the Accountability Chart to help manage the department heads. Is this a legitimate way to reduce span of control, or are we violating EOS® structural rules?

Question

Tyler Smith · Accepted Answer

Creating an Assistant Integrator seat is a structural error that will introduce massive confusion and dilute accountability. In EOS®, we do not create buffer seats or middle-management patches to fix a span-of-control issue. One person must own the Integrator seat, and adding a proxy between them and the department heads will only create communication bottlenecks and political silos.

Your Integrator's ideal span of control is three to seven direct reports. If they have nine, the solution is to restructure the Accountability Chart to group related functions under fewer leadership seats.

For example, if you have separate seats for Customer Service, Account Management, and Technical Support reporting to the Integrator, consolidate these functions into a single Operations Director or Client Experience Director seat. The managers of those sub-departments will then report to that director, not to the Integrator.

Similarly, ensure your Sales and Marketing seats are properly structured. If they are split, consider whether they can report to a single revenue lead, or if the Integrator needs to delegate other administrative seats, such as IT or HR, to a dedicated People or Operations seat.

Use your next leadership team meeting to IDS® this issue and redesign the chart to bring the Integrator's direct reports down to a manageable number. This preserves clean lines of communication and keeps accountability absolute.