What does it mean that agent collaboration patterns?

Common patterns like pipeline fan-out and consensus for coordinating multiple agents.

Example: You are writing a research report. One approach: you research, outline, draft, edit, and fact-check — sequentially, alone. Another approach: you research while a colleague outlines based on prior notes, a third person drafts a section in parallel, and all three review each other's output before merging. Same report. The second version uses three distinct collaboration patterns — pipeline (research feeds outline feeds draft), fan-out (parallel drafting of independent sections), and consensus (group review before merge). You use these patterns constantly in team settings. The question is whether you use them deliberately, with names, or accidentally, without the ability to diagnose why coordination breaks down.

Try this: Identify a multi-step project you are currently working on — a content pipeline, a product launch, a home renovation, a course of study. Map the actual collaboration pattern in use. For each handoff between people or between your own cognitive agents, label it: is this a pipeline (sequential dependency), a fan-out (parallel independent work), a fan-in (aggregation of parallel results), or a consensus step (group evaluation before proceeding)? Draw the flow. Then identify one point where the pattern is mismatched to the task — a sequential bottleneck that could be parallelized, or a parallel step that actually has a hidden dependency. Redesign that single point.