# Amazon — Taxonomy of multi-agent design patterns, anti-patterns, and lessons from manufacturing

- Company: Amazon (amazon.com)
- Announced: 2026-11-16T21:53:46+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/taxonomy-of-multi-agent-design-patterns-anti-patterns-and-lessons-from-manufacturing/
- Record: https://forck.live/items/36922-taxonomy-of-multi-agent-design-patterns-anti-patterns-and-lessons-from
- Subject: Bedrock / Nova

Amazon's guide lays out a taxonomy of multi-agent design patterns and anti-patterns, arguing that failed enterprise implementations usually stem from coordination rather than the model. It splits coordination into two tiers: deterministic control flow, where developers define the path, and autonomous patterns, where the model chooses the path at runtime at higher cost in tokens, latency and debugging. The post cites roughly 88% of AI pilots never reaching production and a Stanford HAI result that two models can perform worse collaborating than either alone when coordination overhead exceeds the benefit. It illustrates compounding risk with a sequential chain: ten steps each 95 percent reliable yield 59.9 percent end-to-end reliability, and 20 steps yield 35.8 percent. Tier 1 covers sequential pipelines, conditional workflows, conditional routers and parallel workflows, while Tier 2 covers plan-based orchestration and handoff. The guidance is to start with Tier 1 and move a task to Tier 2 only when its subtasks emerge during the work, and it says manufacturing concerns such as takt time, safety boundaries, edge data and shift cycles shape the architecture.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/taxonomy-of-multi-agent-design-patterns-anti-patterns-and-lessons-from-manufacturing/:

> Enterprise teams are building multi-agent systems, and when early implementations fall short, the cause is rarely the model. Multi-agent coordination is a distributed systems problem, and many teams taking it on haven’t yet built distributed systems instincts.
> 
> The numbers are consistent across sources: ~88% of AI pilots never reach production . Stanford HAI demonstrated that two models can perform worse collaborating than either alone when coordination overhead exceeds the benefit. The pattern is clear: teams are adding complexity faster than they build understanding. Ten steps that are each 95 percent reliable deliver only 59.9 percent end-to-end reliability, and 20 steps deliver 35.8 percent. This illustrative model assumes a strictly sequential chain with no retries, but the direction holds: each dependent handoff multiplies risk.
> 
> In this post, you learn how to decide whether a use case needs multiple agents, choose a coordination pattern, and spot costly anti-patterns early. You also see how takt time, safety boundaries, edge data, and shift cycles shape the architecture.
> 
> Multi-agent coordination patterns

---

Record: https://forck.live/items/36922-taxonomy-of-multi-agent-design-patterns-anti-patterns-and-lessons-from
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
