Archive
Design philosophy

Screwdrivers

Congress shall pass no law limiting the rights of persons to manipulate, operate, or otherwise utilize as they see fit any of their possessions or effects, nor the sale or trade of tools to be used for such purposes.

From Artraze commenting on this Slashdot story about the levels of DRM in Windows 7.

I think it maybe needs some qualification about not using your things to cause harm to other people, but it’s an interesting idea. See also Mister Jalopy’s Maker’s Bill of Rights from Make magazine a couple of years ago.

Read More

West London from Richmond Park - Trellick Tower in the centre

How much of designing an environment is consciously about influencing how people use it? And how much of that influence is down to users learning what the environment affords them, and acting accordingly?

The first question’s central what this blog’s been about over the last four years (with ‘products’, ‘systems’, ‘interfaces’ and so on variously standing in for ‘environment’), but many of the examples I’ve used, from anti-sit features to bathrooms and cafés designed to speed up user throughput, only reveal the architect’s (presumed) behaviour-influencing intent in hindsight, i.e. by reviewing them and trying to understand, if it isn’t obvious, what the motivation is behind a particular design feature. While there are examples where the intent is explicitly acknowledged, such as crime prevention through environmental design, and traffic management, it can still cause surprise when a behaviour-influencing agenda is revealed.

Investigating what environmental and ecological psychology have to say about this, a few months ago I came across The Organization of Spatial Stimuli, an article by Raymond G. Studer, published in 1970 [1] – it’s one of the few explicit calls for a theory of designing environments to influence user behaviour, and it raises some interesting issues:

“The nature of the environmental designer’s problem is this: A behavioral system has been specified (within the constraints imposed by the particular human participants and by the goals of the organization of which they are members.) The participants are not presently emitting the specified behaviors, otherwise there would be no problem. It is necessary that they do emit these behaviors if their individual and collective goals are to be realized. The problem then is to bring about the acquisition or modification of behaviors towards the specified states (without in any way jeopardizing their general well-being in the process). Such a change in state we call learning. Designed environments are basically learning systems, arranged to bring about and maintain specified behavioral topologies. Viewed as such, stimulus organization becomes a more clearly directed task. The question then becomes not how can stimuli be arranged to stimulate, but how can stimuli be arranged to bring about a requisite state of behavioral affairs.

[E]vents which have traditionally been regarded as the ends in the design process, e.g. pleasant, exciting, stimulating, comfortable, the participant’s likes and dislikes, should be reclassified. They are not ends at all, but valuable means which should be skilfully ordered to direct a more appropriate over-all behavioral texture. They are members of a class of (designed environmental) reinforcers. These aspects must be identified before behavioral effects of the designed environment can be fully understood.”

Now, I think it’s probably rare nowadays for architects or designers to talk of design features as ‘stimuli’, even if they are intended to influence behaviour. Operant conditioning and B.F. Skinner’s behaviourism are less fashionable than they once were. But the “designed environments are learning systems” point Studer makes can well be applied beyond simply ‘reinforcing’ particular behaviours.

Think how powerful social norms and even framing can be at influencing our behaviour in environments – the sober environment of a law court gives (most of) us a different range of perceived affordances to our own living room (social norms, mediated by architecture) – and that’s surely something we learn. Frank Lloyd Wright intentionally designed dark, narrow corridors leading to large, bright open rooms (e.g. in the Yamamura House) so that the contrast – and people’s experience – was heightened (framing, of a sort) – but this effect would probably be lessened by repeated exposure. It still influenced user behaviour though, even if only the first few times, but the memory of the effect that such a room had those first few times probably lasted a lifetime. Clearly, the process of forming a mental model about how to use a product, or how to behave in an environment, or how to behave socially, is about learning, and the design of the systems around us does educate us, in one way or another.

Stewart Brand’s classic How Buildings Learn (watch the series too) perhaps suggests (among other insights) an extension of the concept: if, when we learn what our environment affords us, this no longer suits our needs, the best architecture may be that which we can adapt, rather than being constrained by the behavioural assumptions designed into our environments by history.

I’m not an architect, though, or a planner, and – as I’ve mentioned a few times on the blog – it would be very interesting to know, from people who are: to what extent are notions of influencing behaviour taught as part of architectural training? This series of discussion board posts suggests that the issue is definitely there for architecture students, but is it framed as a conscious, positive process (e.g. “funnel pedestrians past the shops”), a reactionary one (e.g. “use pebbled paving to make it painful for hippies to congregate“), one of educating users through architectural features (as in Studer’s suggestion), or as something else entirely?

[1] Studer, R.G. ‘The Organization of Spatial Stimuli.’ In Pastalan, L.A. and Carson, D.H. (eds.), Spatial Behavior of Older People. Ann Arbor: University of Michigan, 1970.

Dan Lockton

Read More

Thermostat with friendCentral heating systems have interfaces, and many of us interact with them every day, even if only by experiencing their effects.

But there’s a lot of room for improvement. They’re systems where (unlike, say, a car) we don’t generally get instantaneous feedback on the changes we make to settings or the interactions we have with the interface. It’s a slow feedback loop. We don’t necessarily have correct mental models of how they work, yet the systems cost us (a lot of) money. How effectively do we use them? Around 60% of UK domestic energy use goes on space heating, and 24% on water heating. (See this Building Research Establishment report [PDF] for more detailed breakdowns.) That 84% cost me and my girlfriend £430 last year. It’s worth thinking about from a financial point of view, regardless of the environmental aspects.

Frankie Roberto and colleagues at Rattle Research have carried out a brilliant exercise in exploratory design thinking about central heating*:

Heating systems are something we all interact with, especially in the depths of winter where we depend on them, and yet there seems to have been very little evolution in the design of their interfaces. What’s more, with an ever increasing focus on energy efficiency, both from an environmental and economic standpoint, there’s a need for heating systems and their interfaces to be smarter, more efficient and transparent.


Design Monday #1 – Central Heating (short version) from Rattle on Vimeo.

Read the full post.

The Rattle team think through existing systems and consider a number of possible revisions to improve the way that information is presented to users, and the level of control that it might be useful for users to have. This is a great piece of work, impressive and very thorough, and it’s interesting to see how their thinking evolved: I get the impression that (as service designers) they’re a lot more focused on users’ needs than the designers of many heating systems are. It’s also an exciting thing for a design company to be able to take time to address problems outside their immediate sphere, since they’re bringing a whole new level of domain expertise to it.

The ‘I’m working’ indicator is a really good idea – it reminds me of some higher-end car tyre air pumps at petrol stations where you can just set the pressure you want to achieve, and the pump cuts out (and alerts you) when it reaches it. But the idea of doing away with the ‘desired temperature’ setting and just having warmer/colder is also interesting – “forc[ing] people to always make decisions based upon how they’re feeling right now”.

Equally the ‘shift to service’ approach of having an API and making clever use of it has a big potential to help in energy saving (and cost saving for the user), especially if the usage data were (anonymised or otherwise) available for analysis. Just being able to tell users “it’s costing you £X more to heat your home than it does for a similar family in a similar house down the road – if you insulated better you could save £X every month” would be an interesting mechanism for persuasion. As with so many things, it relies on having that API or other interface available in the first place…

Folk theory of thermostats

The ‘folk theory of thermostats’ which Frankie mentions, popularised in Don Norman’s The Psychology / Design of Everday Things, has long intrigued me:

There are two commonly held folk theories about thermostats: the timer theory and the valve theory. The timer theory proposes that the thermostat simply controls the relative proportion of time that the device stays on. Set the thermostat midway, and the device is on about half the time; set it all the way up and the device is on all the time. Hence, to heat or cool something most quickly, set the thermostat so that the device is on all the time. The valve theory proposes that the thermostat controls how much heat (or cold) comes out of the device. Turn the thermostat all the way up, and you get the maximum heating or cooling. The correct story is that the thermostat is just an on-off switch. Setting the thermostat at one extreme cannot affect how long it takes to reach the desired temperature.

People’s mental models of heating systems are often stereotyped or played with (as we’ve discussed before here), but as Willett Kempton found out in a classic study, there are some nuanced versions of the theories, which, in practice, are perhaps not as silly as Norman suggests. People satisfice.

Say you come in from outdoors, and are cold. Because of the delay in your exposed skin warming up to room temperature, it surely does warm you more quickly if you stand near something that’s hotter than you actually want to be, e.g. a log fire / stove. So the heuristic of ‘turning up the heat to more than you need, in order to feel warmer more quickly’ is pretty understandable, especially when the temperature controlling the thermostat is the temperature of the thermocouple/probe/whatever and not actually the body temperature of the users themselves. (That would be a good innovation in itself, of course!) Am I wrong?

Given that a lot of people do try to control heating systems as if they worked on the valve model, would it be sensible to develop one which did? Do they already exist?

*Rattle’s second ‘Design Monday’ session, on ‘Lunch’, is also well worth a look.

Read More

Angled StepsIt’s a simple question, really, to any readers with experience in urban planning and specifying architectural features: what is the reasoning behind positioning steps at an angle such as this set (left and below) leading down to the Queen’s Walk near London Bridge station?

Obviously one reason is to connect two walkways that are offset slightly where there is no space to have a perpendicular set of steps, but are they ever used strategically? They’re much more difficult to run down or up than conventionally perpendicular steps, which would seem like it might help constrain escaping thieves, or make it less likely that people will be able to run from one walkway to another without slowing down and watching their step.

Like the configuration of spiral staircases in mediaeval castles to favour a defender running down the steps anticlockwise, holding a sword in his right hand, over the attacker running up to meet him (e.g. as described here), the way that town marketplaces were often built with pinch points at each end to make it more difficult for animals (or thieves) to escape, or even the ‘enforced reverence’ effect of the very steep steps at Ta Keo in Cambodia, are angled steps and staircases ever specified deliberately with this intent?

Angled Steps

The first time I thought of this was confronting these steps (below) leading from the shopping centre next to Waverley Station in Edinburgh a couple of years ago: they seemed purpose-built to slow fleeing shoplifters, but I did consider that it might just be my tendency to see everything with a ‘Design with Intent’ bias – a kind of conspiracy bias, ascribing to design intent that which is perhaps more likely to be due to situational factors (a kind of fundamental attribution error for design), or inferring the intention behind a design by looking at its results!

What’s your angle on the steps?

Angled Steps

Read More

Most things are unnecessary. Most products, most consumption, most politics, most writing, most research, most jobs, most beliefs even, just aren’t useful, for some scope of ‘useful’.

I’m sure I’m not the first person to point this out, but most of our civilisation seems to rely on the idea that “someone else will sort it out”, whether that’s providing us with food or energy or money or justice or a sense of pride or a world for our grandchildren to live in. We pay the politicians who are best at lying to us because we don’t want to have to think about problems. We bail out banks in one enormous spasm of cognitive dissonance. We pay ‘those scientists’ to solve things for us and them hate them when they tell us we need to change what we’re doing. We pay for new things because we can’t fix the old ones and then our children pay for the waste.

Economically, ecologically, ethically, we have mortgaged the planet. We’ve mortgaged our future in order to get what we have now, but the debt doesn’t die with us. On this model, the future is one vast pyramid scheme stretching out of sight. We’ve outsourced functions we don’t even realise we don’t need to people and organisations of whom we have no understanding. Worse, we’ve outsourced the functions we do need too, and we can’t tell the difference.

Maybe that’s just being human. But so is learning and tool-making. We must be able to do better than we are. John R. Ehrenfeld’s Sustainability by Design, which I’m reading at present, explores the idea that reducing unsustainability will not create sustainability, which ought to be pretty fundamental to how we think about these issues: going more slowly towards the cliff edge does not mean changing direction.

I’m especially inspired by Tim O’Reilly’s “Work on stuff that matters” advice. If we go back to the ‘most things are unnecessary’ idea, the plan must be to work on things that are really useful, that will really advance things. There is little excuse for not trying to do something useful. It sounds ruthless, and it does have the risk of immediately putting us on the defensive (“I am doing something that matters…”).

The idea I can’t get out of my head is that if we took more responsibility for things (i.e. progressively stopped outsourcing everything to others as in paragraphs 2 and 3 above, and actively learned how to do them ourselves), this would make a massive difference in the long run. We’d be independent from those future generations we’re currently recruiting into our pyramid scheme before they even know about it. We’d all of us be empowered to understand and participate and create and make and generate a world where we have perspicacity, where we can perceive the affordances that different options will give us in future and make useful decisions based on an appreciation of the longer term impacts.

An large part of it is being able to understand consequences and implications of our actions and how we are affected, and in turn affect, the situations we’re in – people around us, the environment, the wider world. Where does this water I’m wasting come from? Where does it go? How much does Google know about me? Why? How does a bank make its money? How can I influence a new law? What do all those civil servants do? How was my food produced? Why is public transport so expensive? Would I be able to survive if X or Y happened? Why not? What things that I do everyday are wasteful of my time and money? How much is the purchase of item Z going to cost me over the next year? What will happen when it breaks? Can I fix it? Why not? And so on.

You might think we need more transparency of the power structures and infrastructures around us – and we do – but I prefer to think of the solution as being tooling us up in parallel: we need to have the ability to understand what we can see inside, and focus on what’s actually useful/necessary and what isn’t. Our attention is valuable and we mustn’t waste it.

How can all that be taught?

I remember writing down as a teenager, in some lesson or other, “What we need is a school subject called How and why things are, and how they operate.” Now, that’s broad enough that probably all existing academic subjects would lay claim to part of it. So maybe I’m really calling for a higher overall standard of education.

But the devices and systems we encounter in everyday life, the structures around us, can also help, by being designed to show us (and each other) what they’re doing, whether that’s ‘good’ or ‘bad’ (or perhaps ‘useful’ or not), and what we can do to improve their performance. And by influencing the way we use them, whether nudging, persuading or preventing us getting it wrong in the first place, we can learn as we use. Everyday life can be a constructionist learning process.

This all feeds into the idea of ‘Design for Independence’:

Reducing society’s resource dependence
Reducing vulnerable users’ dependence on other people
Reducing users’ dependence on ‘experts’ to understand and modify the technology they own.

One day I’ll develop this further as an idea – it’s along the lines of Victor Papanek and Buckminster Fuller – but there’s a lot of other work to do first. I hope it’s stuff that matters.

Dan Lockton

Read More

Staggered crossing in Bath

I’ve mentioned a few times, perhaps more often in presentations than on the blog, the fact that guidelines for the design of pedestrian crossings in the UK [PDF] recommend that where a crossing is staggered, pedestrians should be routed so that they have to face traffic, thus increasing the likelihood of noticing oncoming cars, and indeed of oncoming drivers noticing the pedestrians:

5.2.5 Staggered crossings on two-way roads should have a left handed stagger so that pedestrians on the central refuge are guided to face the approaching traffic stream.

When I gave this example of Design with Intent at Lancaster, the discussion – led, I think, by Lucy Suchman and Patricia Clough – turned to how this arrangement inevitably formalised and reinforced the embedded hegemony of the motor car in society, and so on: that the motorist is privileged over the pedestrian and the pedestrian must submit by watching out for cars, rather than the other way around.

Now, all that is arguably true – I had seen this example as merely a clever, sensible way to use design to influence user behaviour for safety, for everyone’s benefit (both pedestrians and drivers) without it costing any more than, say, a crossing staggered the opposite way round – but this is, maybe, the nature of this whole field of Design with Intent: lots of disciplines potentially have perspectives on it and what it means. What a traffic engineer or an ergonomist or a mistake-proofer sees as a safety measure, a sociologist may see as a designed-in power relation. What Microsoft saw as a tool for helping users was seen as patronising and annoying (at least by the most vociferous users). It’s all interesting, because it all broadens the number of interpretations and considerations applied to everything, and – if I’m honest – force me to think on more levels about every example.

Multiple lenses are helpful to designers otherwise stuck at whatever focal length the client’s prescribed.

Back to the crossings, though: the above crossing in Bath is a bit unusual in how it’s arranged with so many control panels for pedestrians. But in general, with simple Pelican and Puffin crossings in the UK, there is a design feature even more obvious, which only struck me* the same day I photographed the above crossing in Bath: the pedestrian signal control panel is usually also to the right of where pedestrians stand waiting to cross, i.e. (with UK driving on the left), in order to press the button, pedestrians have to turn to face the oncoming traffic.

The guidelines actually mention this as helping people with poor vision, but it would seem that it really assists all users, even if only slightly. It means you can watch the traffic as you decide whether or not you actually need to press the button, and will be more likely to be standing in a position where you can see the oncoming traffic at the point when you walk out into the road.

5.1.7 To assist blind and partially sighted pedestrians, as they approach the crossing, the primary push button/indicator panel should normally be located on the right hand side. The alignment should encourage them to face oncoming vehicles. The centre of the push button should be between 1.0 and 1.1 metres above the footway level.

This is the sort of ‘hidden’ intentional, strategic design detailing which fascinates me. It is obvious, it is quotidian, but it’s also thoughtful.

Staggered crossing in Bath

*Looking back through my notebooks, I see that someone actually mentioned this to me at a seminar at Sheffield Hallam in September 2007 but I forgot about it: many thanks to whoever it was, and I should be better at reading through my notes next time!

Read More

@danlockton

Error: Twitter did not respond. Please wait a few minutes and refresh this page.

Upcoming talks & events

I'm speaking or running workshops at:

Some of my previous presentations

Comments & trackbacks

Blog 2005-date