The lawn is telling you the path is wrong
Somewhere on every campus there is a paved path, and beside it a strip of dead grass worn into a track that goes where people actually want to go. The usual response is a sign: KEEP OFF THE GRASS. And that sign is one of the purest examples in the world of solving the wrong problem — because the grass is not the problem. The grass is the report.
Symptom, or cause?
A worn track across a lawn is data. It is thousands of independent people, none of whom coordinated, all reaching the same conclusion about where the path should have been. It is, if you like, a very large survey with a perfect response rate.
There are two readings.
The grass is the problem. Response: a sign, a fence, a hedge, a chain. Cost: money, permanently, and an ugly fence, and people walking round the fence to make a new track.
The path is the problem. Response: pave the track. Cost: once. Result: nobody walks on the grass again, because the path now goes where people go.
Same evidence. Two frames. One of them fights the users forever and one of them ends the problem — and the difference is not intelligence, it is which thing you decided was broken. That decision happens in about two seconds, usually unconsciously, and it determines everything afterwards.
That is problem identification, and it is why the bulletin names it separately.
When many people fail, it is not many people's fault
A useful rule with a sharp edge: if one person cannot work something out, it might be them. If everybody cannot, it is the thing.
Everybody pulls the door that should be pushed. Everybody presses the wrong switch. Everybody walks on the grass. At that point user error has stopped being an explanation and become an excuse, because a failure rate that high is a property of the design, not of the population.
This matters because the tempting answer in these questions is almost always the one that corrects the people: educate them, sign it, train them, remind them. It sounds responsible. It is the KEEP OFF THE GRASS answer wearing better clothes.
The design answer changes the thing instead. And it is worth noticing that this is genuinely uncomfortable — it means accepting that people will not read your sign, will not learn your system, and will keep cutting the corner forever. Designing for people as they are rather than as they should be is the actual skill, and the questions in this area are frequently probing whether you have it.
The problem is usually one level up
A working habit: when you have identified a problem, ask what that problem is a symptom of, once. Just once — going further gets you to world peace and helps nobody.
The corridor is congested. One level up: the two rooms that generate the traffic are at opposite ends. The congestion is a symptom; the plan is the cause. Widening the corridor treats the symptom, and treating a symptom means the problem returns in a different shape.
The room is too hot. One level up: it faces west with unshaded glass. Air conditioning is a symptom-level answer that works and costs forever; a shade is a cause-level answer that works and costs once. Notice that the symptom answer is not wrong — it is just paying rent on a problem you could have bought outright.
That is generally the tell in these questions. The symptom-level option usually works, which is why it is tempting. It just costs forever, or fights the user forever, or moves the problem somewhere else. The cause-level option is often cheaper, quieter, and looks almost like doing nothing — and it is nearly always the answer.
The rules behind this
Sourced to the official brochure rather than restated here, so there is one place to correct when the Council revises it.
Part B examines six named areas: Visual Reasoning, Logical Derivation, General Knowledge/Architecture and Design, Language Interpretation, Design Sensitivity and Thinking, and Numerical Ability.
Visual Reasoning — understanding and reconstructing 2D and 3D composition. Logical Derivation — decoding a situation or context and drawing conclusions. General Knowledge, Architecture and Design — current issues, important buildings, historical progression, innovation in materials and construction. Language Interpretation — meaning of words and sentences, English grammar. Design Sensitivity and Thinking — observing and analysing people, space, product, environment; semantics, metaphor, problem identification. Numerical Ability — basic mathematics and its association with creative thinking; unfolding space using geometry.
Source · verified 2026-07-16
What almost everyone believes
“People walking on the grass are the problem, so the answer is a sign or a fence.”
The worn track is a report, not a fault. Thousands of people independently reached the same conclusion about where the path should be, and they are right.
This is the single most reliable trap in the area because the symptom answer genuinely works and feels responsible — a sign is active, visible, and cheap today. It just fights the users forever, and they walk round the fence to make a new track. If one person fails, it might be them; if everybody fails, it is the thing. Designing for people as they are rather than as they should be is uncomfortable, which is precisely why it is the skill being tested.
Depending on how long you have
Foundation
Understand the skill. Months out, or starting from zero.
Collect desire paths. Photograph every worn track you find and ask what it is reporting. It is a small habit that teaches the largest idea in this module — that people's behaviour is evidence rather than misbehaviour — and once you believe that, half the questions in this area answer themselves.
Drill
The practice protocol. What to repeat, how often, how to score it.
For every problem in a question, ask once: what is this a symptom of? Then check the options — which fix the symptom and which fix the cause? Track how often you were drawn to the symptom answer. For most people it is most of the time, because symptom answers are active and visible and feel like doing something.
Exam-Day
What to actually do under the constraint — 108 seconds, no instruments, one pass.
Distrust any option that corrects the people — educate, sign, train, remind. That is the KEEP OFF THE GRASS answer in better clothes. Prefer the option that changes the thing, and prefer the quiet answer that looks almost like doing nothing. It is usually the cause-level one.
Try it
Twenty minutes outside. Bring a phone and your eyes.
- 01Find a desire path — a worn track people made where no path was drawn. Every campus, park and bus stop has one.
- 02Stand at its start and ask: where were people going, and why did the designed route not take them there?
- 03Look for the sign or fence, if there is one. Ask what it cost, and whether it worked.
- 04Now find any rule posted anywhere — a notice telling people not to do something. Ask what design failure that notice is compensating for.
- 05Last: pick one annoyance in your own home and ask once what it is a symptom of. Only once. The answer is usually one level up and slightly embarrassing.
The short version
A desire path is a report, not misbehaviour — thousands of people independently agreeing where the path should have been. Two readings of the same evidence: the grass is broken (sign, fence, fight the users forever) or the path is broken (pave it once, done). If one person fails it might be them; if everybody fails it is the thing. Ask once what a problem is a symptom of, and distrust the option that corrects the people — it works, and it costs forever.
Next: people and space — reading a room by watching who stands where.
Questions people actually ask
- What is a desire path?
- A track worn by people walking where no path was designed — across a lawn, round a corner, through a gap. It is evidence rather than misbehaviour: thousands of people, none of whom coordinated, independently reaching the same conclusion about where the route should have been. The usual response, a KEEP OFF THE GRASS sign, is a textbook case of solving the wrong problem.
- How do I identify the real problem rather than the symptom?
- Ask once what the problem is a symptom of — only once, since going further gets you to world peace. A congested corridor is a symptom; the two rooms generating the traffic sitting at opposite ends is the cause. Widening the corridor works and the problem returns in another shape.
- Why is the tempting answer usually wrong in these questions?
- Because the symptom-level answer genuinely works, which is what makes it tempting. It just costs forever, or fights the user forever, or moves the problem elsewhere. The cause-level answer is often cheaper and quieter and looks almost like doing nothing. Distrust any option that corrects the people rather than the thing.