XIV · Anti-PatternsAnti-pattern✕

Multi-Agent on Sequential Workloads

also known as Multi-Agent Over-Engineering, Pointless Chain Decomposition

Anti-pattern: split a fundamentally sequential workload across multiple agents, degrading accuracy by 39–70% with no parallelization benefit.

Context

A team has a workflow that is sequential by nature (each step depends on the previous step's output). Pressured by 'multi-agent is the modern way' rhetoric, the team decomposes the workflow into multiple agents with handoffs. The German t3n 2026 quantified analysis: multi-agent only pays when single-agent success >45% AND ≥45% of the workflow is parallelizable.

Problem

Each agent loses context the previous one had, must re-establish state from handoff messages, and adds a round-trip of latency and cost. Sequential workflows degrade by 39–70% in accuracy under multi-agent decomposition vs single-agent. Cost rises proportionally to handoff count. The decomposition serves neither parallelism nor specialization.

Forces

  • Multi-agent is the prestige architecture in 2026; reviewers ask why a team uses 'only' one agent.
  • Sequential workflows look like 'pipelines' which intuitively map to chains-of-agents.
  • Per-agent specialization sounds appealing even when context loss costs more than specialization gains.

Example

A team decomposes a 'classify-then-extract-then-summarize' single-agent workflow into 3 specialized agents. Single-agent baseline: 88% end-to-end accuracy. Multi-agent: 52%. Each agent loses the context the previous one had. The 'specialization' did not exceed the context-loss cost. Reverted to single-agent.

Diagram

Solution

Therefore:

Measure single-agent baseline before considering multi-agent. Apply the 45/45 gate: only decompose if both parallelizability and single-agent accuracy clear the threshold. When decomposition is required for non-accuracy reasons (governance, specialization), preserve full context in the handoff message and measure the accuracy delta explicitly. Pair with demo-production-cliff-multiagent awareness.

What this pattern forbids. No useful constraint; the missing constraint is the 45/45 gate before multi-agent decomposition.

And the patterns that stand alongside it, or against it —

  • complementsDemo-Production Cliff (Multi-Agent)✕— Anti-pattern: multi-agent pilot benchmarks at 95% accuracy / 2s latency on a curated demo set, then degrades to ~80% / 40s under realistic 10k-RPD load.
  • complementsAutomating a Broken Process✕— Anti-pattern: deploy agents on top of a workflow that is already dysfunctional, so the dysfunction is amplified at machine speed instead of resolved.
  • alternative-toParallelization★★— Run independent LLM calls concurrently and combine results.
  • alternative-toAugmented LLM★★— Build the foundational agent block as an LLM augmented with retrieval, tools, and memory that the model actively chooses to use, rather than a bare-model call.
  • complementsHero Agent✕— Anti-pattern: stuff every capability into one agent with one giant prompt.
  • complementsOne Tool, One Agent★— Design agent systems as a team of narrow single-purpose agents, each owning one tool or one capability, rather than a single super-agent that handles every tool — the agent analogue of microservices over monolith.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

References

Provenance