A business may add another AI role because a workflow looks complicated. Before approving that change, ask the team to show a real piece of work crossing the proposed boundary. The useful question is what the recipient will know after the transfer.
Anthropic’s October 22, 2026 engineering guidance recommends considering whether some routing, planning and domain subagents belong inside a main agent using skills and tools. It retains reasons for separation, including verification, parallel work and permissions. This is vendor guidance, not proof that one architecture wins every task.
Make the proposed transfer tangible
Our practical recommendation starts with an invoice exception. Imagine a fictional accounts team receiving an invoice whose total differs from its purchase order. An assistant extracts the figures, another prepares an explanation and an authorized employee decides what happens next. This example illustrates a proposed office process, not a tested product capability.
Ask the designer to show the actual item the second assistant would receive. Does it include both document versions, the disputed amount, the currency and the relevant purchasing note? Or does it contain only a sentence saying that the invoice needs attention?
The second version forces someone to repeat the investigation. Naming that recipient a specialist would not supply the missing evidence. A discussion about roles becomes more useful when everyone can examine the proposed transfer record.
Write one complete exception record
For this fictional process, we would ask for a record containing the document references, figures extracted from each source, the precise discrepancy and the unresolved question. Include a link to the original material and identify anything the assistant could not read. Keep the record inside the organization’s approved information environment.
Use deliberately awkward examples when reviewing the proposal. One invoice might have a credit note attached; another might use a different currency; a third might contain a scan that is difficult to read. The purpose is to discover whether the transfer preserves the specific complication, rather than turning it into an ordinary mismatch.
Ask a colleague unfamiliar with the exercise to explain the case from that record. If they have to guess which total is disputed, improve the record. Their questions provide a concrete list of missing information before the organization introduces another automated participant.
Decide what the next person may conclude
The explanation should distinguish an observed discrepancy from a suspected cause. A difference between two totals does not establish which document is wrong. An assistant might identify a possible tax or shipping difference while leaving that explanation unconfirmed.
Our suggested review note would say what was compared, what differed and what evidence is still needed. It would leave payment approval with the existing authorized employee. A neatly written explanation should not acquire decision-making authority merely because it arrived at the end of an automated sequence.
Ask what the proposed role actually adds
Now return to the additional role. Have its owner describe the specific contribution to this exception record. If it supplies a useful analysis, show that analysis. If it only rewrites the first assistant’s note, explain why that rewrite helps the employee handling the case.
Keep the discussion grounded in the documents people will use tomorrow morning. The proposed design should make the discrepancy easier to understand and the unanswered question easier to resolve. Preserve established independent checks and access boundaries while reviewing that change.
A workflow diagram can begin the conversation. A clear, usable transfer record makes the decision more concrete: the team can see what the new role contributes, what it needs and which human decision remains open.
AI-generated conceptual editorial image; not an actual Anthropic system, product interface or benchmark.