The Digital Worker Is Not Remote. The Digital Worker Is Augmented.

The Wrong Definition Generates the Wrong Design Questions

When digital worker means remote worker, the design challenge is logistics: connectivity, equipment, schedule coordination. That problem is largely solved. When digital worker means augmented worker, the design challenge shifts entirely: which AI tools extend this person's capability, how are those tools integrated into their actual workflow, and how does the organisation measure the output of a human-AI pair rather than an individual contributor?

Most organisations do not have good answers to those questions because they have not asked them at the right level of specificity. The conversation has stayed at the adoption level, which tools are being deployed, which teams have access, what the rollout timeline looks like. That is a procurement conversation. The design conversation is different: for this specific role, in this specific context, with this specific mix of tasks, what does augmentation actually change about what this person produces and how they produce it?

The gap between the adoption conversation and the design conversation is where AI investment loses its return. Tools get deployed; work does not get redesigned. The augmented worker is left using new tools within an old role structure, which produces neither the efficiency of the old structure nor the amplification the new tools are capable of. Both the tool and the person are running below their potential because the configuration around them has not changed.

Measure One Augmented Role Against Its Pre-Tool Baseline This Quarter

For one role in your team that has received AI augmentation tools in the last 12 months: run a brief baseline comparison. What did this person produce per day before the tools were introduced? What do they produce now? And are the current performance metrics capturing the right signals given what the tools have changed about the work?

If the metrics have not been updated since the tools were introduced, you are measuring augmented workers using standards designed for unaugmented work. That produces two outcomes, both misleading. Underperforming augmented workers appear to be a person problem when they are often a configuration problem: the tool is not integrated into the workflow in a way that actually extends capability. Overperforming augmented workers appear to be outliers when they may be demonstrating what the role looks like when it is properly configured.

A salesperson augmented with AI-driven prospect intelligence and automated follow-up can cover more ground in a day than an unaugmented peer in a week. Measuring that person against the same daily call volume metric used before the tools were introduced tells you nothing useful. Fix the measurement before drawing conclusions about either the value of the tools or the performance of the people.

Access Versus Amplification Is the D5 Maturity Distinction That Matters

D5 frames the maturity distinction for augmented work as the difference between designing for access and designing for amplification. Designing for access means giving workers the tools. Designing for amplification means configuring the work system so the tools and the worker each do what they do best, at a level neither could reach independently. Most organisations are at the access stage. They have deployed the tools; they have not redesigned the work. The amplification stage requires the design discipline that access does not: clear decisions about role boundaries, human-AI handoff points, and performance metrics that reflect augmented rather than unaugmented output.

The question is not whether your team has AI tools. The question is whether the work is designed to let those tools produce the value they are capable of producing.