Five steps, and they must not blur together
Each step needs a different capacity; run them together and they contaminate each other.
延伸阅读
Splitting one thing into five of different kinds
Most people treat solving a problem as one activity, and so use the same head at the start and at the end. The book cuts it into five, collectively the five steps. The list itself is not novel and comes in many versions; what does the work in the argument is that it supplies five different tests — the goal step asks what you want, the diagnosis step asks why, the design step asks how. Split apart, each step gets a completion standard of its own.
Blurring contaminates in a fixed direction
The harder requirement is not 'go through five steps' but 'do not run them together', and the damage has a fixed direction: think about feasibility while setting goals and the goal gets trimmed back to what you can already do; think about solutions while diagnosing and the diagnosis stops at the layer you happen to know how to fix. The reason the second step is called not tolerating problems is the same: it is only meant to put problems on the table, and the moment 'can this be solved' joins in, the unsolvable ones vanish before they are recorded.
Why blurring necessarily lowers the output
What is being reconstructed is the thought behind 'keep the steps apart', and the condition it depends on.
A goal-setting meeting that never sets one
Cracks in this reading
Turning 'separated beats blurred' into a testable specification
The claim under test: setting goals and assessing feasibility in two separate rounds yields wider goals than doing both at once, without worse plans.