We recently automated our client-facing deliverables using generative AI, creating a new seat for AI Prompt Optimization and Output Quality Control. This seat is highly technical yet requires deep customer context, and none of our department heads want to absorb it into their current seats. How do we assign accountability for this critical modern seat?

Question

Tyler Smith · Accepted Answer

This is a common challenge when modernizing operations. A new, specialized seat is created, but because it carries unfamiliar technical requirements and potential liabilities, team members try to pass the buck. On an EOS Accountability Chart, every seat must have one name, and every major operational task must roll up to a seat on the leadership team. You cannot leave this seat unassigned. To resolve this, you must first define the five core roles for this new seat, such as prompt library maintenance, output quality assurance, and model latency tracking. Once the roles are clear, look at your current structure and determine where this output ultimately impacts the customer experience. Because it directly affects client deliverables, this seat most naturally rolls up under your primary operations or delivery seat, even if the work is technical. The Operations Director does not need to do the daily work, but they must be accountable for the outcome. They can hire a technical specialist or delegate the tasks to a direct report who has the GWC for it. If the technical demand is too high for operations to manage, then your technology seat must own the technical maintenance while operations owns the quality sign off. Use the IDS process with your leadership team to decide which department head is ultimately accountable for the numbers on the Scorecard.