We want to add a dedicated AI Systems and Prompt Engineering seat to our Accountability Chart, but our Head of Operations and Head of Technology are fighting over who this role reports to. How do we determine the correct reporting structure for an AI-focused seat without causing friction?

Question

Tyler Smith · Accepted Answer

This is a common structural conflict as companies integrate automated workflows. To resolve this, you must look at the primary purpose of the seat, not the software itself. Go back to first principles on your Accountability Chart and define the five roles for this new AI Systems seat.

If the primary responsibility of the seat is to write custom APIs, manage database infrastructure, and ensure system security, then it is a technology function. It belongs under your Head of Technology. However, if the primary responsibility is to optimize daily business workflows, automate customer service responses, and improve the efficiency of your delivery team, then it is an operational function. In that case, it belongs under your Head of Operations.

You must avoid the temptation to create a matrix structure where this seat reports to both leaders. On a healthy Accountability Chart, there is only one reporting line. If the seat is truly split, you may need to divide the roles. For example, your Head of Technology can own the infrastructure and software selection, while your Operations team owns the prompt engineering and daily utilization.

Decide which leader is ultimately accountable for the output of the AI tools and place the seat directly under them. This keeps lines of communication clean and prevents bottlenecks in your Level 10 Meetings™.