Map the Workflow: Known Subtasks or Unknown Terrain?
Place a task on the predictability and coupling matrix to choose a Claude Code workflow shape.
Known + loosely coupled Best fit for parallel workers doing independent checks like security, docs, or performance review. Known + tightly coupled Often best as one main thread or a very coordinated lead session because each step affects the next. Unknown + loosely coupled Start with an orchestrator that can discover lanes and split them once the terrain becomes clearer. Unknown + tightly coupled High need for orchestration and frequent ground-truth checkpoints because the task unfolds as evidence arrives. Task feels big Task shape is known Common trap Using complexity as the only reason to parallelize.
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in