Parallel block in a Workflow does exactly that: every step inside it runs concurrently, and the pipeline waits for all of them before moving on.
Two ways to fan out
| Shape | Use when |
|---|---|
Parallel step in a Workflow | The set of investigations is fixed and the pipeline is auditable |
| Broadcast Team | A lead should synthesize independent opinions on one question |
Sequence only what depends
The skill is dependency analysis, not maximum parallelism. Put a step inParallel only when it does not read another step’s output. Keep the genuine dependencies sequential.
| Step | Depends on | Runs |
|---|---|---|
| Market assessment | Nothing | First, alone |
| Fundamental analysis | Market context | In parallel with technical |
| Technical analysis | Market context | In parallel with fundamental |
| Risk assessment | Both analyses | After the parallel block |
Why this matters for deep research
Deep research is slow because it is thorough. Parallelism is what keeps thoroughness affordable in wall-clock time. A five-specialist review that runs the three independent specialists at once finishes in roughly the time of the longest one, not the sum of all five.Next steps
| Task | Guide |
|---|---|
| Choose the orchestration shape | Orchestration patterns |
| Ground each parallel specialist | Grounding research |
| Synthesize into one artifact | Structured deliverable |