We are debating how to assess the Capacity factor of GWC for our customer service leads now that we are deploying AI agents. The physical time requirement has dropped, but the cognitive demand for handling complex escalations has spiked. How do we redefine Capacity for these highly evolved seats?

Question

Tyler Smith · Accepted Answer

As you automate manual processes with AI, the nature of work shifts from transactional to analytical. Capacity is no longer just about having enough hours in the day to click buttons. In an automated environment, Capacity means having the mental, intellectual, and emotional bandwidth to manage exceptions, audit automated workflows, and handle complex escalations.

This shift impacts how you evaluate your team, especially for critical roles like customer service leads. The physical time requirement might decrease, but the cognitive demand for handling complex issues spikes.

Redefining Capacity Expectations

To redefine Capacity for your newly evolved seats, you must update the expectations on your Accountability Chart. Consider these critical criteria:

• Intellectual Capability: Does the person possess the critical thinking skills to analyze data trends and spot anomalies in the automated outputs? This goes beyond basic understanding; it requires a deep analytical mindset to troubleshoot and improve automated processes, much like how AI can be used to [simplify EOS process components](/qa/simplify-eos-process-component-with-ai).
• Emotional Resilience: Can they handle the higher stress of dealing exclusively with complex customer problems, since the simple ones are now automated? This demands robust interpersonal skills and the ability to de-escalate difficult situations without the buffer of routine tasks.
• Technical Adaptability: Do they have the aptitude to learn, update, and manage the automated systems themselves? The role now requires a degree of technical proficiency to interact with and optimize AI tools, similar to the skills needed to [use AI to draft customer support responses](/qa/safe-ai-customer-support-workflow).

Evaluating GWC for Evolved Seats

When evaluating GWC (Gets It, Wants It, Has the Capacity) for these high-velocity seats, you must look past a team member's historic output. Instead, assess their ability to operate in this new, cognitively demanding environment.

It's crucial to understand that a decrease in physical workload does not automatically equate to having the Capacity for the seat. If a team member lacks the capability to audit the automation and make real-time, high-stakes decisions, they do not have the Capacity for the seat, even if their workload has physically decreased. This is a common challenge that requires careful consideration when [restructuring a seat for a legacy leader hitting their management ceiling](/qa/restructuring-seat-for-legacy-leader-hitting-ceiling). Such changes often require a re-evaluation of not just GWC, but also underlying conative profiles, as seen when considering [Kolbe scores for leadership roles](/qa/head-customer-success-low-follow-thru-kolbe).

Related questions

• [Should we create a dedicated AI Operations seat on our Accountability Chart, or integrate AI into existing seats?](/qa/ai-operations-seat-accountability-chart)
• [How can AI enhance the effectiveness of the EOS People Component during growth phases?](/qa/how-can-ai-enhance-the-effectiveness-of-the-eos-people-component-during-growth-phases)
• [How do we handle a key department head who refuses to participate in offsite vulnerability or team-building exercises, claiming it is a waste of time?](/qa/handling-leader-resisting-offsite-vulnerability)
• [Our Head of Customer Success is a great culture fit and passes the gets it and wants it tests, but her Kolbe score shows she has a very low Follow Thru and high Quick Start. She keeps starting new client retention initiatives but never completes them. Is this a GWC capacity issue, or can we solve this by restructuring her seat?](/qa/head-customer-success-low-follow-thru-kolbe)