Out of My Head · Lesson 23 of 33
Workflow steps should be atomic
The video for this lesson is being recorded. The whole lesson is written out below.
Read the lesson0% complete
Hand it over: a team that acts without asking you
Workflow steps should be atomic
Jay WestOut of My Head · 2 min read
By the end: That workflow split into steps a competent stranger could complete without asking you a question.
The idea
Each step in a workflow should be small enough to complete without ambiguity.
An example
A content team has a publishing workflow with a step labeled "Prepare the article for publication." Three different editors interpret this differently: one checks grammar only, another also reformats images, the third also writes the social media blurb. When articles go live with broken formatting or missing social copy, no one knows where the process failed because the step was too large to diagnose. They replace the single step with five atomic steps — copyedit prose, resize and compress images, write meta description, draft social excerpt, preview in staging — and the errors become immediately locatable because each step either happened or it did not.
Where it goes wrong
Going too fine. Atomicity is not an instruction to decompose every action into its smallest conceivable components. If your morning workflow includes a step that says "pick up the toothbrush with your dominant hand," you have passed the useful threshold and entered bureaucratic overhead territory. The right granularity is the level at which a step can be completed without ambiguity but also without condescension — where each step represents a single meaningful action that could independently succeed or fail. The failure mode is not insufficient decomposition. It is decomposition that generates more cognitive load than it eliminates.
Make it stick
You now know how to decompose workflows into atomic steps — units that can independently succeed or fail without ambiguity. The next structural question is ordering: which of these atomic steps must happen in sequence, and which can happen simultaneously? Before moving on, review your decomposed workflow from the exercise and mark each step with a tentative label: does this step depend on the output of the previous step, or could it run independently?
Do this now
Take one recurring workflow from your life — morning routine, weekly review, project kickoff, content publishing, anything you do repeatedly. Write out every step as you currently understand it. Then, for each step, apply the ambiguity test: if you handed this step to a competent stranger with no additional context, could they complete it without asking a single clarifying question? Any step that fails this test is not yet atomic. Decompose it until every sub-step passes. Notice how many hidden assumptions your original steps contained — assumptions that work fine when you are alert and experienced, but that become failure points when you are tired, distracted, or handing the workflow to someone else.
This step is drawn from one lesson of the full curriculum. Read the full lesson on howtothink.ai (L-0804)
Lesson 23 of 33
Next: lesson 24 →