Chapter 3: The New Leadership Pact

In most organizations IT and business leaders operate as stakeholders with dependencies to move work from ideation to scope to launch. This model assumes work is linear and decomposable. In an agentic enterprise, work is continuous, interdependent, and adaptive, which means integration itself becomes the primary leadership responsibility. Business leaders define their needs and requirements and IT builds systems, workflows, or apps to deliver on those needs. However, in an intelligent agentic era, the work is no longer linear or driven by cause and effect. 

To get digital workers out of the lab and into the P&L, business leaders will need to stop acting as passive customers of IT and start operating as partners in a unified workforce model: IT manages the infrastructure, security, governance, while the business defines the context, knowledge, and training. This partnership isn’t about alignment meetings or faster handoffs. It’s about jointly owning where integration lives in the system and ensuring it doesn’t fall back onto human cognition. Here’s the framework to bridge the gap. 

The New Division of Labor: Who Leads What?

To ensure digital labor delivers a measurable ROI, leaders need to start owning their specific halves of digital workers’ outcomes. Clear ownership prevents the performance decay that turns a productive digital worker into a sunk cost, ensuring that integration moves the needle instead of creating more manual work for your team.

The IT Lead: The Infrastructure Architect

IT is responsible for the infrastructure that makes digital labor possible. Their mandate is to ensure integration can execute safely and repeatedly without requiring human intervention, giving every digital worker the right access, ingredients, and guardrails to operate reliably.

• Systems & Permissions: Ensure digital workers have the write permissions and licensing for the right systems, including your ATS, CRM, and internal databases.
• Data & Contextual Knowledge: Ensure that the data, knowledge, and context are clean, real-time, and accessible for your digital workers to read and process.
• The Trust Layer: Manage security and compliance to ensure candidate Personally Identifiable Information (PII) is protected and that your digital worker operates within Global Data Protection Regulation (GDPR) and other legal frameworks.

The Business Lead: Your Digital Worker Manager

The business unit lead is the direct manager. If your digital worker fails, it’s a management problem, rather than a technical failure. If humans are forced to reconcile outputs, re-check decisions, or advance work manually, the integration layer has failed by design.

• Jobs to be Done: Define the specific tasks, inputs, and expected outputs. If your business hasn’t documented a process, your digital worker can’t improve it.
• Motivation: Define the behavioral frameworks of how your digital worker communicates, collaborates, problem solves, and its emotional intelligence.
• Success Metrics: Define how your digital worker’s performance will be measured (e.g., lead-to-meeting conversion rates or accuracy scores).
• Continuous Coaching: Provide the nuanced best practices, brand voice, and industry-specific context that your digital worker needs to stay on par with the human team.

The Digital Labor Discovery Template

To move from a vague idea to a productive worker, Asymbl utilizes a rigorous discovery template. This framework ensures that before a single line of configuration is written, the job is fully understood.

The Joint Front: Orchestration and Oversight

While roles are distinct, there is a shared orchestration center where IT and the Business Lead must act as one. This is the control plane where integration is designed, monitored, and improved as a system capability rather than absorbed as human effort.

1. Integrated Workflow: Jointly decide where your digital worker lives, whether that’s in Slack, Salesforce, or within a specific system of record.
2. The Escalation Path: Define exactly when your digital worker should hand off a task to a human. This prevents your digital worker from guessing when it hits a complex scenario.
3. ROI Transparency: IT provides the unit cost of technology, while a Business Lead provides the value created (e.g., hours reclaimed or revenue generated). Together, they present a unified ROI to the organization. ROI only becomes visible when repeated human coordination is removed from the workflow and replaced with reusable system behavior.

‍

‍‍

The Pact in the Field: Engineering QA & Velocity

When IT and business leaders sign this pact, the too many cooks problem disappears because decision rights are clear and the workflow is designed end to end. Chaos fades when everyone knows what they own, what they don’t, and what done means. Take an engineering quality assurance (QA) digital worker as an example.

In this scenario, the IT Lead ensures the environment is secure, compliant, and reliable. They supply their digital worker with encrypted access to the code repository and establish guardrails so that proprietary code never leaves the environment. They manage identity, access, and infrastructure so work can happen safely and at scale.

Meanwhile, your Business Lead defines the work itself. They aren’t concerned with server uptime or access controls; they’re focused on outcomes. They specify the exact test cases their digital worker must execute and the Correct Action Rate (CAR) required before code is passed to a human developer for final creative review.

Because the roles are explicit, your business isn’t blocked waiting on IT approval to move forward, and IT isn’t pulled into remediating unclear or broken workflows. Integration no longer depends on escalation. It executes by design. Both sides operate as a unified system, moving code from build to production in days rather than months.

The too many cooks problem is solved when everyone knows who’s prepping the ingredients and who’s plating the dish. To see AI on the P&L statement, you have to stop managing the tech and start managing the partnership. Because leadership now determines whether integration is a reusable system capability or an invisible human tax.