What it notices
What people actually do, as opposed to what they report or what the plan assumes. Design thinking pays close attention to workarounds, because a workaround is a user telling you the design is wrong. It notices when the brief itself is the problem, and it treats a failed prototype as information.
What it cannot see
Structure that no single user experiences. Watching twelve students closely will not reveal the loop between the timetable and the departments guarding their hours, because no student sees the whole loop. Design thinking also struggles with the long delay. A prototype tested for a week says nothing about what happens in three years.
It can mistake the users in the room for everyone affected. The students in the trial volunteered. The ones who most needed the change probably did not.
What it asks of teachers and students
Comfort with making something rough and showing it to people before it is good. For students used to being marked on finished work this is hard, and for teachers used to planning thoroughly it can feel careless. The discipline is in the testing, which has to be honest enough to kill a prototype you liked.
Good work shows the reframe and the evidence for it. Weak work shows the final idea and a picture of the process.
Where the values sit
In the word "preferred". Simon’s definition of design turns existing situations into preferred ones, and says nothing about whose preference. Buchanan argued that design has no subject matter of its own, which means the values come from whoever sets the brief. A design process run with students but briefed by management has already decided whose preferences count.
How it gets hollowed out
The workshop version is five coloured stages, a morning of sticky notes and a solution chosen by the most senior person in the room. It keeps the stages and drops the two things that made the method work: sustained attention to real users, and the permission to rewrite the brief. What remains is brainstorming with better stationery.