What does it mean that micro-chains for complex tasks?

Break complex tasks into short chains of three to five behaviors.

Example: A software engineer named Tomás has two tasks on his afternoon list. Task one is fixing a bug — a well-defined problem with a clear starting point. He opens the file, reads the error, and starts debugging without hesitation. Task two is writing the architecture document for a new system — an ambiguous, cognitively demanding project with no obvious first sentence. He stares at the blank document for twenty-two minutes, checks Slack, refills his coffee, reads two articles tangentially related to the project, and by 3:40 PM has written nothing. The next day, he installs a micro-chain: open the document, re-read the last section he outlined, write one rough sentence describing the next component, and continue from there. Four links. Under ninety seconds to reach the first unit of output. The architecture document, which had been stalled for a week, is drafted in three days — not because the work got easier, but because the starting problem disappeared.

Try this: Identify the one task you have been avoiding or delaying most consistently over the past week — the task where you know what to do but cannot seem to begin. Write down the exact sequence of physical actions that would take you from not doing the task to actively doing it. Start with the most trivially easy action (open the app, pick up the pen, navigate to the file) and end with the first unit of real output (one sentence written, one function coded, one sketch drawn). The sequence should be three to five links and completable in under two minutes. Write the micro-chain on a sticky note and place it where you will see it when the task is due. Execute the micro-chain once today, even if you stop after the first unit of output. Tomorrow, execute it again. Track how many seconds elapse between initiating link one and producing the first output. By day three, the starting problem should be noticeably weaker.