Our Head of Operations and our Head of Technology are constantly arguing over who owns the deployment of our automated customer onboarding workflow. How do we use the Accountability Chart to clearly define who has the final decision-making authority?

Question

Tyler Smith · Accepted Answer

When your Head of Operations and Head of Technology are clashing over automated workflows, it is a clear sign of overlapping or poorly defined roles on your Accountability Chart. To resolve this standoff, you must clarify who owns the ultimate decision-making authority for each step of the process.

Defining Core Accountabilities

Start by looking at the core roles of each seat:

• Head of Operations: This seat is primarily accountable for customer delivery, retention, and service quality. Therefore, they must own the business requirements and the customer experience of the onboarding workflow. They define what the process must achieve. For insights on documenting these processes, see [what operational playbooks do we need to document](/qa/operational-playbooks-for-strategic-premium-multiples).

• Head of Technology: This seat is accountable for system architecture, software integration, and data security. Therefore, they own the technical execution and the choice of tools used to build the automation. They define how the process is built and maintained. To explore structuring this, you might consider if you need an [AI Operations seat](/qa/ai-operations-seat-accountability-chart) or how to [integrate AI safely](/qa/safe-ai-customer-support-workflow).

Resolving the Impasse

To resolve the impasse, use the IDS® process in your next [Level 10 Meeting™](/qa/should-integrator-facilitate-level-10-meetings).

1. Have both leaders present their concerns openly.
2. Then, clearly assign accountability based on their core functions.

• The Operations leader has final sign-off on the workflow's performance and its impact on the customer experience.
• The Technology leader has final sign-off on the systems used, their implementation, and their maintenance.

Clarifying these boundaries on your Accountability Chart prevents political friction and keeps your automation projects moving forward. This approach helps avoid common issues like [leadership team turf wars](/qa/resolving-leadership-turf-wars-accountability-chart) and ensures clear decision-making.

Related questions

• [How do the Visionary and Integrator handle a disagreement when they are completely deadlocked on a major strategic decision?](/qa/visionary-integrator-deadlock-resolution)
• [How do we use the Kolbe A Index to diagnose why our Sales and Operations heads are constantly in conflict over project handoffs?](/qa/kolbe-sales-operations-conflict-handoffs)
• [When an issue is dropped to IDS, my leadership team immediately starts pointing fingers at other departments rather than taking ownership. How do we use the Accountability Chart to stop the blame game during meetings?](/qa/using-accountability-chart-to-stop-blame-in-ids)
• [How do we design a specialist seat on our Accountability Chart for a legacy leader who has hit their management ceiling, so we retain their expertise without stalling our growth?](/qa/restructuring-seat-for-legacy-leader-hitting-ceiling)
• [Our company is expanding rapidly, and I need to split our massive Operations seat into two distinct roles. How do I execute this structural change on the leadership team without causing a turf war?](/qa/splitting-operations-seat-on-accountability-chart)