We have split our operations department into two specialized seats, Delivery and Quality Control, but they share the same administrative assistants. Now both managers are fighting over who gets priority on support tasks. How do we draw this shared resource on the Accountability Chart without creating dual reporting?

Question

Tyler Smith · Accepted Answer

Splitting an operational department into Delivery and Quality Control seats is an excellent way to scale, but sharing administrative resources can quickly lead to operational gridlock. If both managers are fighting over the same assistants, you have a structural flaw in your Accountability Chart.

In the EOS® framework, every seat must have a single supervisor. You cannot have one administrative assistant reporting to two different managers with equal authority. This violates the rule of single ownership and creates a stressful work environment for the assistant.

To resolve this, you must choose one of two structural options.

Option one is to assign the administrative assistant seat to report directly to one of the managers, while establishing a clear service-level agreement for how they support the other department. The manager who owns the seat is responsible for their GWC™, reviews, and overall workload.

Option two is to place the administrative assistant in a shared service pool that reports directly to the Integrator or an Operations Director. The Integrator then manages the prioritization of their tasks and resolves any resource conflicts.

Draw this clearly on your Accountability Chart. Whichever option you choose, ensure the assistant has only one manager's name in the box above theirs. This eliminates reporting confusion and keeps your operations running smoothly as you scale.