Look at any made object within reach — a chair, a kettle, a phone case, the trainers by the door. It feels permanent, as if it had always been that exact shape. It wasn't. Each one started as a problem: someone couldn't do something easily, or safely, or comfortably — and a designer set out to fix it by making something new.
So Design Technology is not really about glue guns and neat pencil lines, though you'll use both. At its heart it is one thing: solving real problems for real people by making things. A beautiful object nobody needs is not strong design. A plain object that quietly solves a real problem is. Useful comes first; the craft is making it useful and a pleasure to hold.
That means a designer always begins with two questions: who is this for, and what do they need? The person you are designing for has a name in this subject — the user. Sometimes there is also a client — the person who asks for the work and sets the task. The client might not be the user at all: a school (client) might order chairs for its pupils (users).
design — from the Latin designare, "to mark out, to point to". A designer marks out a path from a need to a made answer. The drawing came later; the pointing-at-a-problem came first.
The humble shopping trolley took three goes to catch on. When Sylvan Goldman invented it in 1937, shoppers refused to use it — men thought it looked weak, women thought it looked like a pram. He had to hire actors to push trolleys around his shops, pretending to shop, before real customers copied them. A strong design still needs people to want it.
A designer does not leap from a problem straight to a finished answer. They follow a process — a set of stages, each one feeding the next. The stages are: identify the problem and the user, research, write a brief and specification, generate ideas, develop and prototype, make, then test and evaluate.
Here is the part most people miss. The stages are not a straight line with a finish. When you evaluate — when you test a thing and see what falls short — what you learn sends you back round again. This is the single most important picture in the subject, so take a moment with it.
James Dyson built 5,127 prototypes of his bagless vacuum cleaner before he was happy — fifteen years of going round the loop. He has said he learned more from each of the 5,126 that didn't work than from the one that did. The loop isn't a sign you went astray; it's how the work is done.
The first half of the loop is about getting certain before you build anything. It is tempting to skip it — to grab a pencil and draw the answer you already pictured. The careful designer slows down here, because the time spent now is repaid many times over later.
Research comes in two halves. First, the user: you find out how they actually live with the problem — what they struggle with, how big their hands are, where they'll use the thing. Some of this is measured. The study of human body sizes is anthropometrics; designing so a thing fits the body comfortably and works well in the hand is ergonomics. Second, existing products: you study what's already out there, what works about it, and where it falls short — so you improve on it rather than repeat it.
Then you write two things down. The design brief is a short, plain statement of what you'll make and who it's for. The specification is fussier and more useful: a list of measurable requirements. Not "it needs to be sturdy" but "it must hold 2 kg without bending". Not "it needs to be small" but "it must fit a school bag under 25 cm wide". The point of measurable criteria is plain — at the end, you can test against them and know exactly where you stand.
A brief is the aim in a sentence: "Design a lunch box for a Year 9 pupil who cycles to school." A specification turns that into things you can measure and check off: holds two compartments · seals so liquid can't leak · survives a 1-metre drop · costs under £8 · fits a 25 cm pannier.
Next comes the lovely part: generating ideas. Here the rule is the opposite of the careful research stage — you go wide. Sketch quickly, mind-map, throw out odd thoughts. The trap to avoid has a name: fixation — falling for your first idea and stopping there. The first idea is rarely the strongest; it is only the quickest. Designers draw many, then choose.
Tap each card — the words designers lean on:
The first computer mouse, built at Stanford in 1964, was a carved block of wood with one button and a cable out of the front — which is why it was named a "mouse". It was a prototype meant only to prove the idea worked. Nobody expected the rough wooden block; they expected to learn from it. That is what a prototype is for.
Here is the idea that makes a designer strong at the work. The process is iterative — from iterate, to repeat. It means you improve the design through repeated loops of the cycle. A first prototype is almost never the final answer. You make one, test it against the spec, find what's lacking, and go round again — research, ideas, develop, prototype, test — each lap a little closer.
This changes how a designer treats a test that goes badly. When a prototype falls short against the specification, that is not a disaster — it is information. It tells you exactly what to fix on the next lap. A failed test you learn from is a step forward, not a wasted afternoon. The whole subject rests quietly on that one reframing.
Let's walk one full lap with something real: a better lunch box for a Year 9 pupil who cycles to school. Watch how the last stage — evaluating — hands straight back to the first.
The squeezy, upside-down ketchup bottle — the one that stands on its cap so the last of the sauce is always ready — was years of looping to get right: the valve that stops drips, the cap that won't clog, the body you can squeeze with one hand. A tiny detail most people never notice is often a hundred quiet laps of the cycle.
A friend props their phone against a mug to watch things while they eat, and it keeps sliding over. That's a problem worth solving: a small phone stand for a desk or kitchen table. Write the design brief — a short, plain statement. Name the user, name the problem, and say what you'll make. Two or three sentences is plenty.
strong You named a real user and a real problem before you reached for the answer — someone who watches things while they cook, and their phone slides off the worktop. That order is the whole skill of a brief: the need comes first, the object second.
try this One line drifts into how it will look — a folded metal triangle. Save the shape for the ideas stage. A brief stays at the level of the aim, so it leaves you free to sketch eight different shapes next, rather than locking you into one.
to add One detail about where it lives would sharpen the aim — a kitchen worktop gets wet and greasy, a bedside table doesn't. Naming the setting now will quietly write half your specification for you on the next page.
Fresh one. Designing a thing so it fits the body comfortably and works well in the hand — the right grip, the right height, the right reach — is called what? (It begins with "ergo".)
Pick one made object within reach — a water bottle, your headphones, a pencil case, a kettle. Now do what a designer does at the evaluate stage. Say who it's for and what it's meant to do. Say one thing it does well, and one thing that falls short. Then — the designer's move — say what you'd change on the next lap, and why. Four or five sentences.
strong You judged the bottle against what it's for, not just whether you like it — it keeps water cold all day, which is the whole point. That's the difference between an opinion and an evaluation: you held it up against its purpose.
try this The shortcoming — the lid is hard to open — is real, but it stops there. The designer's move is the next half-sentence: what would you change? A wider grip? A different thread? Naming the change turns the flaw into information you can act on.
to add One measurable line would sharpen it for the next lap — "the new lid must open one-handed." That's you writing a fresh specification point from what the test told you, which is exactly how the loop keeps turning.
Sit down with Dad for any of these. They're about the same pull this lesson is about — looking at a problem and itching to make it better. Heavier titles flagged for a chat first.
You learned that design starts with a real problem and a real user. You learned the loop — identify, research, brief and spec, ideas, prototype, make, test, evaluate — and that it runs round, not in a line. And you learned the word that holds it all together: iterative. A failed test isn't an ending; it's the start of the next lap. Now go and look at the objects around you a little differently. Florence, this is design.
