AI agents and asynchronous work: delegating without confusing supervision with management

Updated 6 September 2026. This article extends “Junyr Agents™: delegating AI without losing control” by distinguishing the supervision of software from the management of people.

• It concerns work assigned to an agent and reviewed later.
• It does not assume that every job follows this model or that asynchronous work is always preferable.
• It separates delegation skills, hierarchical authority and organisational accountability.

What asynchronous execution actually changes

An agent enables a work loop in which a person defines an expected outcome, lets the system perform several steps, then resumes control to review or decide, without that sequence automatically changing the person’s occupation or employment status.

• Delegation covers a task, data and tools that have been expressly authorised.
• Resumption occurs at a known deadline or control point.
• Decision-making remains human when the effects exceed the granted mandate.
• Formal roles change only when the organisation actually changes a person’s authority and responsibilities.

Microsoft describes a shift among advanced users towards intent, evaluation and ownership of outcomes, but its survey covers 20,000 knowledge workers who already use AI at work and cannot establish that every employee becomes a manager [1].

• 50% of respondents name quality control of AI output among the skills becoming more important.
• 46% name critical thinking.
• 86% say they treat AI output as a starting point and remain responsible for the thinking.
• These are self-reported responses from a selected population of AI users.

Choosing between synchronous, asynchronous and hybrid work

The useful distinction does not divide software into two absolute categories: it describes the autonomy granted, the delay before human review and whether the person can pursue other work during execution.

• Synchronous: the human interacts at every stage, as in a problem-solving conversation.
• Asynchronous: the agent receives a bounded work package and returns with an output or a request for a decision.
• Hybrid: the agent proceeds independently between planned approvals, which suits many business processes.

Asynchronous execution is useful when work divides cleanly and remains recoverable, whereas a tighter loop is better when ambiguity, urgency or risk requires continuous judgement.

• Good candidate: prepare a first draft report from approved sources, with review before circulation.
• Hybrid candidate: reconcile invoices, then request approval for discrepancies or payments.
• Poor candidate without safeguards: publish, pay, delete or contact a third party without prior review.

Delegation skills do not create hierarchical authority

Directing an agent’s work borrows clarity of mandate, monitoring and review from management, but the analogy ends there because software is neither an employee, a colleague nor the holder of employment rights and duties.

• Delegation skill: describe the outcome, constraints and acceptance criteria.
• Formal authority: allocate or assess other people’s work on behalf of the employer.
• Business accountability: accept an output and own the decision that uses it.
• System accountability: administer access, data, logs and the agent’s lifecycle.

NIST expressly recommends defining and differentiating roles and responsibilities in human–AI configurations, which supports naming several owners instead of assigning an undifferentiated “agent manager” role to every user [4].

• The sponsor authorises the objective and risk level.
• The process owner defines controls and exit criteria.
• The user reviews within their domain of competence.
• Technical and control functions manage access, security and incidents.

Parallel work without confusing activity with value

Deferred execution can reduce elapsed time when an agent works while the person handles something else, but the number of tasks started says nothing by itself about quality achieved or time actually saved.

• Measure end-to-end time, including the wait for review.
• Measure human attention, including framing, monitoring and corrections.
• Measure quality, through errors, rework and compliance with acceptance criteria.
• Measure full cost, including software, integration, operation and control.

In 2026, METR reported that working on unrelated tasks while waiting and using several agents concurrently made time per task difficult to interpret in its experiment with open-source developers, a measurement limitation that favours several indicators over one productivity rate [3].

• Its new study also suffered from selection and participation effects.
• The authors describe the data as an unreliable signal of the current effect of AI tools.
• This observation concerns software development and does not prove an identical effect in every occupation.

Four costs to anticipate before delegating

Useful delegation transfers part of the execution while creating framing, verification, exception handling and skills-maintenance work that belongs in the economic assessment.

• Framing: prepare data, instructions, examples and success criteria.
• Verification: apply more control when an error is costly, subtle or hard to correct.
• Exceptions: handle out-of-scope cases and stop the agent before a sensitive action.
• Skills: retain enough human practice to detect a plausible but false output.

The control point should precede the first effect that is difficult to reverse, because a final review cannot protect against something already published, paid, deleted or sent to a third party.

• Allow a draft to be prepared, then block circulation.
• Allow a proposal to be calculated, then block contractual commitment.
• Allow an incident to be detected, then reserve destructive remediation for an authorised person.

A simple discipline: plan, execute, verify

In Junyr practice, the Plan → Execute → Verify loop makes each delegation readable and reviewable, without claiming that an internal method alone guarantees quality, security or compliance.

• Plan: state the steps, authorised sources, success criteria and escalation cases.
• Execute: log actions, observe permissions and preserve the evidence needed for review.
• Verify: compare the output with the criteria, record discrepancies and obtain the planned approval.

On the internal Junyr Method™ scale, Orchestre qualitatively describes the coordination of several uses under shared rules, while Architecte describes processes redesigned more systematically around AI.

• This interpretation helps describe an operating model; it is neither an external standard nor a professional title.
• Moving from Artisan to Orchestre requires shared practices, rather than simply more agents.
• Progress should remain grounded in observable evidence for each process.

A minimum viable SME pilot

An SME can test asynchronous work on one low-risk flow, with a baseline and a named owner, before increasing autonomy or multiplying agents.

• Before: record volume, elapsed time, human time, rework rate, incidents and cost.
• Mandate: write the objective, inputs, tools, permissions, prohibitions, expected output and escalations.
• Control: place a human stop before any sensitive or irreversible consequence.
• After: compare the same indicators and collect effects on workload and skills.

The 2025 France Num survey reports that 26% of French microbusinesses and SMEs surveyed use AI solutions, while only 5% report task-automation solutions, reminding us that using an assistant and asynchronously delegating a process are different practices [5].

• The 26% figure covers declared use of at least one AI solution.
• Generative AI and assistants dominate the reported uses.
• The survey measures neither widespread autonomous-agent use nor a universal transformation of jobs.

Three questions for framing the first trial

Three questions can expose an ill-defined delegation before the organisation invests in a platform or grants more autonomy.

• What exact outcome should the agent deliver, from which sources and against which criteria?
• Who may authorise the mandate, who reviews the output and who decides when it falls short?
• Before which action must the agent stop, and how can the previous state be restored?

Conclusion: organising delegation without overclaiming

Asynchronous agents can shift part of the work from execution to framing and review, but that shift remains partial, depends on the process and requires an explicit allocation of authority, controls and accountability.

• Every employee need not become a manager or use agents.
• Supervisory skill can be taught without changing hierarchical authority.
• Value comes from a controlled outcome, rather than the number of active agents.
• Autonomy should increase only when evidence from the pilot supports it.

---

Going further

A free, no-commitment 30-minute video audit positions your company on the Junyr scale, identifies its main blocker and first sensible project, and provides a one-page follow-up.

• Book the AI maturity audit
• Understand the five levels of the Junyr Method™
• Discover Junyr Agents™

---

Sources verified on 6 September 2026

[1] Microsoft, 2026 Work Trend Index Annual Report, “Agents, human agency, and the opportunity for every organization”, 5 May 2026: report and methodology.

[2] Jiayi Geng and Graham Neubig, “Effective Strategies for Asynchronous Software Engineering Agents”, 23 March 2026: preprint and abstract.

[3] METR, “We are Changing our Developer Productivity Experiment Design”, 24 February 2026: methodological note.

[4] NIST, AI Risk Management Framework 1.0, Govern 3.2: official framework.

[5] French Directorate General for Enterprise / France Num, Baromètre France Num 2025: official findings.

---

Paul-Antoine Tual is an AI Transformation Leader and runs Croissance et Transitions (SAS), which operates the Junyr™ suite; he advises French mid-sized companies and SMEs on AI transformation.