The Theory
The idea that you should get it right the first time is one of the most counterproductive myths in thinking. Iterative refinement works differently: you produce something rough and incomplete on purpose, then improve it through successive cycles. Writers draft and revise. Designers prototype and test. Software developers ship, get feedback, and iterate. The first version is not a failure — it is a probe, a way of learning what the problem actually looks like once you engage with it. Each iteration teaches you something the previous one could not.
What the Research Found
Flower and Hayes modeled writing as a recursive draft-revise process, showing that skilled writers do not plan everything in advance — they discover their argument through the act of writing and revising. Norman demonstrated that iterative design consistently produces better products than waterfall approaches because each cycle incorporates new learning. Stokes showed that constraints, rather than limiting creativity, actually enhance it by forcing novel solutions within bounded spaces — each iteration under constraint refines the solution.
How We Use It
Question B1 option (c) — "I put it into practice in rough form, then refine it: first attempt, then improve" — maps to iterative-refinement strategy (dimension value 2.3). B4(c) — stripping a failing project to basics and trying again — captures the iterative recovery pattern. B7(a) — "constraints help me, I think better within boundaries" — connects to Stokes's findings about constraint-driven iteration. If your instinct is to produce rough drafts and improve through cycles rather than plan for perfection, your strategy is iterative.
Related Articles
References (3)
- Flower, L. & Hayes, J. R. (1981). A cognitive process theory of writing. DOI
- Norman, D. A. (1988). The Design of Everyday Things.
- Stokes, P. D. (2005). Creativity from Constraints: The Psychology of Breakthrough.