Making as thinking

The practical lesson says: build six rough pieces before you build fifty. This page explains why the act of making is itself part of the creative process rather than the execution phase that follows it.

"Programmes are made in the making"

Adair devotes a late chapter to what he calls working it out, and it is the closest thing in the classical literature to prototyping theory.

He begins by separating creative thinking (which leads to the new idea) from creativity (which includes actually bringing it into existence) — and then immediately denies that the separation holds in practice. In most instances, he says, the split is entirely arbitrary. In the process of working an idea out, the idea is developed, adapted or changed, and new ideas and materials are added to the melting pot. He borrows a line from the broadcaster Hugh Wheldon that a team could usefully adopt: programmes are made in the making.

This matters because it reframes what a prototype is for. It is not a test of a finished idea. It is a continuation of the thinking by other means — which is why the lesson insists you name the question the prototype must answer, and why finding your concept collapsing at the prototype stage is not failure but the work being done.

Adair also names the judgement call precisely: knowing when to stop thinking and start working an idea out is an important act of judgement. Move too early and you waste time chasing ideas that were not right. Wait too long once you have a working clue and you have wasted the clue.

He is honest about the emotional cost as well — even professional creative thinkers go through what he calls the dark night of despair, and his summary line is worth keeping: if you haven't worked on the edge of failure you haven't worked on the edge of real success.

Finally, and relevant to anyone working alone: he notes that you must develop the product yourself up to a point, but beyond that point it necessarily becomes a team effort — especially if you intend to take the idea to a market.

Prototypes as boundary objects

Goller and Bessant treat prototypes as more than tests. A prototype is a boundary object: something concrete enough that people from different backgrounds can gather around it and have a conversation they could not have about an abstract description. This is why showing six rough cards to ten people produces information that describing your concept to the same ten people does not.

Their treatment of design thinking, agile innovation and lean start-up, and creativity under extreme constraints all rest on the same underlying claim: in conditions of uncertainty, learning by building cheap versions beats planning carefully in advance. Nowak's recent work on creative prototyping sits in the same tradition, treating the prototype as a distinct creative practice rather than a stage of production.

Intelligent failure

Goller and Bessant give failure a fuller treatment than most textbooks, and it is worth taking seriously before your first prototypes get a lukewarm response. They identify three ways failure contributes:

• Failure points the way. Under uncertainty there is always a risk the direction was wrong — and finding that out is information you could not have obtained otherwise.
• Failure builds capability. Teams learn more from well-run post-project reviews of what went wrong than from success, which tends to be attributed to talent and therefore examined less carefully.
• Failure lets people learn from each other. Sharing failure stories transfers knowledge that success stories do not.

They describe the practice of fast intelligent failure — deliberately creating small, cheap, fast experiments so that being wrong is affordable and informative. The critical framing point they make is psychological: intelligent failure means treating the experiment, not the person, as what failed. The experiment generated useful information; nobody is a failure.

Griffiths reaches the same conclusion in his chapter on creative leadership, arguing that creativity thrives in a climate of adventure and experimentation fed by risk — and that if you are not failing occasionally, it is a sign you are not attempting anything very innovative.

Clapham and Meyer connect this to organisational form. Reviewing Quinn's comparison of small start-ups and large organisations, they note that what gives small teams their creative advantage is a cluster of behaviours: testing multiple approaches, speedy decision-making, early prototyping, persistence and flexibility. Large organisations that innovate successfully reproduce these deliberately — flat structures, small autonomous units, support for trying multiple approaches early, and rewards for experimentation. A small youth team is, structurally, exactly such a unit. That is an advantage worth using rather than an absence of resources to apologise for.

AI, authorship and the skill of prompting

You will make choices about AI tools this week, so it is worth knowing that this is now a research field rather than a matter of opinion.

Oppenlaender, Linder and Silvennoinen investigate prompt engineering as a creative skill in AI art — that is, they treat the ability to direct a generative system as something learnable and unevenly distributed rather than as a shortcut that removes skill from the process. El Saddik and colleagues survey generative AI and multimodal content creation more broadly. Pranandari and Aoyama examine AI competence and innovation in the creative industries and find individual creativity acting as a moderator — in other words, the effect of AI capability on innovative output depends on the creativity of the person using it.

Taken together, these support the position the lesson takes: an AI tool is neither a replacement for creative capability nor a neutral instrument. It amplifies what the person brings. Someone with a clear concept and good judgement gets more from it than someone without, which is exactly why the lesson requires that you be able to explain how everything you make came to exist.

Dawson's myth — that creative output is always good — is the necessary counterweight, and the reason the lesson asks you to write down what you will never use these tools for.