From the source
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.






