When AI Gets a Login: Managing Digital Labor

Todd Curzon

[calm] Welcome to the show. Daniel, I want to begin with an uncomfortable premise: if your operating model still assumes every worker is human, your workforce plan is already out of date. Not next year, not in some speculative future... already. [short pause] In large firms right now, AI agents are being given logins, assigned tasks, and, in a few cases, treated as if they sit somewhere in the reporting structure, even if nobody has quite had the courage to draw them neatly onto the org chart.

Daniel Carter

[questioning tone] The word that gets me there is logins. Not “pilot,” not “experiment” -- logins. That means access, permissions, audit trails. It stops being a clever chatbot and starts looking a lot more like labor you have to supervise.

Todd Curzon

Precisely. And once something has access, a queue, and an expected output, the old framing of “AI as a tool” becomes too small. This is not just about whether an employee writes an email faster. It is a labor design question: who gets the work, who approves the work, who has decision rights over the work, and when something goes wrong, who is accountable for the consequence.

Daniel Carter

[warmly] And for a newly promoted VP or Director, that last word -- accountable -- is the one that matters. Because nobody gets to walk into the QBR and say, “Well, the agent did it.” [short pause] That is not, and will never be, a serious management sentence.

Todd Curzon

[chuckles] No, it is not. Managers are going to become, in a very literal sense, agent bosses. Which sounds faintly absurd until you realize the mechanics are quite ordinary. Somebody has to define the scope, set tolerances, monitor performance, and decide when human review is required. In other words, management. Only now the team may include digital workers that do not tire, do not complain, and can still create a remarkable amount of operational risk if left unsupervised.

Daniel Carter

Let me try to explain it back. So this is less like buying better spreadsheet software and more like quietly hiring a new class of worker that nobody interviewed, nobody onboarded in the traditional sense, but everybody is suddenly expected to manage?

Todd Curzon

[reflective] Almost. The missing piece is that these workers are not merely helping individuals; they are beginning to sit inside workflows. That changes the unit of analysis. Instead of asking, “Which employee uses AI?” the better question is, “Which parts of the business should be performed by humans, which by agents, and where do we place the handoff?” That is a far more strategic conversation.

Daniel Carter

And it’s a more political one too. Because the moment you ask where the handoff sits, you’re really asking who owns the process. Sales ops? Rev ops? Finance? Product? The friction is not technical first. It’s territorial.

Todd Curzon

Yes -- ownership is what people actually associate with leadership. If an agent triages inbound customer issues, drafts resolutions, and routes edge cases, then somebody must own that system end to end. Not just the software budget. The outcome. The escalation path. The standard of judgment.

Daniel Carter

[skeptical] Which is why I get nervous when leaders talk about AI purely in productivity language. “We’ll save time.” Fine. Save whose time? On what process? Under whose authority? If you can’t answer those three questions, you don’t have an AI strategy. You have an expensive demo.

Todd Curzon

[matter-of-fact] Exactly. And for listeners sitting in that newly expanded seat -- Director, VP, first real enterprise span of control -- the shift is simple to say and difficult to live: your workforce is no longer just headcount. It is headcount plus digital labor, arranged inside a system that still requires very human clarity.

Daniel Carter

[curious] The framework I keep coming back to is that progression from assistant to colleague to process owner. Because it explains why so many leaders feel, honestly, a little disoriented. We started with AI as a helper -- summarize the meeting, draft the memo, clean up the slide. That’s familiar. But now the model is shifting toward a digital colleague that can take a stream of work, and then beyond that, toward agents that can run chunks of a business process with periodic human checks.

Todd Curzon

And that progression matters because each stage changes the managerial burden. An assistant improves individual output. A colleague changes team design. A process owner changes the operating model. That is an entirely different order of consequence. One recent executive survey found 81% expect agents to be integrated into their company’s AI strategy within the next 12 to 18 months. Twelve to 18 months is not a distant horizon; it is, in enterprise terms, tomorrow morning.

Daniel Carter

Eighty-one percent is the number I can’t shake. Because if four out of five leaders expect integration inside 18 months, then waiting for “clarity” is basically choosing to be late. And there’s another number in the mix: 24% have already deployed AI organization-wide. Not in a lab. Organization-wide.

Todd Curzon

[calm] Quite. Which is why you’re hearing new vocabulary emerge so quickly -- work charts, human-agent ratios, agent bosses. The language sounds novel, but it points to an old truth: organizations need a way to describe who does what. If some of the “who” is now nonhuman, the chart must evolve.

Daniel Carter

[laughs softly] Work charts is such a revealing phrase. It’s like the org chart admitted it was incomplete. But here’s where I want to push a little. Leaders are talking about 2025 as a pivotal year, and that may be true, but employees today are still getting destroyed by interruption. Meetings, Slack, Teams, email, random pings at 4:47 p.m. If AI becomes one more thing to check, one more dashboard, one more bot sending updates... congratulations, you’ve automated additional annoyance.

Todd Curzon

[responds quickly] I think that is exactly the right pushback. AI only matters if it removes real drag. If your people remain trapped in fragmented days -- ten minutes of strategy, seven minutes of interruption, twelve minutes of status theater -- then adding an agent is cosmetic. The promise is not novelty. The promise is reducing cognitive burden.

Daniel Carter

And the best enterprise case for that, to me, is when the agent doesn’t just answer questions; it clears the runway. It gathers context before the meeting, drafts the follow-up after the meeting, updates the ticket, routes the exception, maybe flags the two items that actually need executive judgment. That’s not magic. That’s removing friction.

Todd Curzon

[reflective] Yes. And the enterprise adoption data is beginning to reflect that seriousness. OpenAI has reported broad usage across large organizations, and in controlled workplace studies the productivity gains are material enough that executives are no longer treating this as side-of-desk experimentation. But again, the sensible interpretation is not “replace everyone.” It is “reassign work with discipline.”

Daniel Carter

Let me sharpen that. If an agent can handle the first 60% of a recurring process, the value is not merely lower effort. The value is that your best people stop spending Wednesday afternoon doing work a machine can do at 2 a.m. [pauses] That is a management question before it is a technology question.

Todd Curzon

And once you see it that way, the frontier firm idea stops sounding futuristic. It sounds administrative, which is precisely why it matters. The frontier is not sci-fi. It is who owns the queue, who reviews the output, and how often a human needs to step back in.

Todd Curzon

[serious] The strategic mistake, I think, is treating AI adoption as a software rollout. Software rollouts are about licenses, training modules, maybe a launch calendar. This is different. This is a redesign of roles, escalation paths, approval thresholds, and accountability. If you automate a process without clarifying decision rights, you do not get leverage. You get confusion at machine speed.

Daniel Carter

Machine speed confusion is exactly right. [short pause] Because the bad version of this shows up fast. An agent drafts responses, another agent routes requests, nobody knows who has final say, and suddenly a customer issue or pricing exception bounces around the system like a pinball. The problem wasn’t that the model was incompetent. The problem was that management never defined the handoffs.

Todd Curzon

Which is why some firms are already contemplating new management roles around this. Roughly 28% are considering AI workforce managers, and 32% are planning for AI agent specialists. Those numbers are fascinating because they indicate leaders understand, perhaps dimly but genuinely, that digital labor requires oversight structures of its own.

Daniel Carter

Twenty-eight and 32 are not fringe numbers. That’s not two innovation teams in hoodies. That’s a real share of the market saying, “We may need people whose job is to manage the machine workforce.” And I think newly promoted leaders need to hear this clearly: if you’re responsible for headcount planning, you are now also responsible for task architecture.

Todd Curzon

[warmly] Beautifully put. Headcount planning used to be a fairly stable exercise in budget, spans, layers, and capability gaps. Now it must include process ownership. Which tasks require judgment? Which require consistency? Which can be delegated to an agent under supervision? Which demand human escalation every single time? Those are design choices, not technical footnotes.

Daniel Carter

And managers have to learn a new rhythm: when to trust, when to verify, and when to intervene. That sounds simple, but it’s a genuine craft. Trust too early and you create hidden risk. Verify everything and you erase the productivity benefit. Intervene too late and the error has already propagated into finance, customers, or compliance.

Todd Curzon

[calm] Yes. Discipline is what earns trust, and judgment is what earns promotions. I suspect that will become even more true in hybrid human-agent organizations. The strongest leaders will not be those who merely adopt AI quickly. They will be the ones who define clear reporting structures, clear review loops, and clear accountability when digital work touches consequential decisions.

Daniel Carter

There’s also a people leadership piece here that I don’t want us to skip. Teams are going to look to their VP or Director and ask, very quietly, “What happens to my job? What am I still expected to own?” If you don’t answer that with specificity, people fill in the blanks with fear. You need to tell them what gets automated, what gets elevated, and what judgment still belongs to a human being.

Todd Curzon

[softly] And that is where the winners will separate themselves. Not by having the most licenses. Not by announcing the flashiest partnership. But by turning digital labor into a disciplined operating model -- one in which agents have defined scope, humans retain meaningful authority, and the system as a whole becomes calmer, faster, and more coherent.

Daniel Carter

[reflective] So maybe that’s the question to leave hanging: when your next org review comes around, are you still defending boxes on a chart... or are you actually designing a workforce that knows, with precision, what only a human should decide?