It’s been a long time since I last wrote an Instructable, but as I’ve resolved that 2009′s going to be a year where I start making things again (2008 involved a lot of sitting, reading and annotating, and in 2007 most of what I made was for clients, and thus confidential), I thought I’d write up a brief (10 minute) fun little bodgey project which has, very marginally, boosted everyday productivity: the One-Touch Keypad Masher.

Wasting valuable seconds typing in a code every time you need to open the door?

This little ‘device’ streamlines the process by pressing the right keys for you, and can be hidden in your palm so you simply mash your hand against the keypad and – apparently miraculously to anyone watching – unlock the door in one go.

Time to make: Less than 10 minutes
Time saved: About 30 seconds per day in my case; your mileage may vary.
Payback time: 20 days, in this case

(There’s a (weak) correlation with some of the Design with Intent topics, since it could be seen as a device which allows a user to interact with a “What you know” security measure using a “What you have” method. At some point in the near future I’ll be covering these on the blog as design patterns for influencing behaviour.

It’s also a kind of errorproofing device, a poka-yoke employing specialised affordances. If used, it prevents the user mistyping the code.)

The Instructable is also embedded below (Flash), but for whatever reason there are a few formatting oddities (including hyperlinks being ignored) so it’s easier to read in the original.

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.

Summary for mystified international readers: In the UK new houses/flats must, by law, have a number of light fittings which will ‘not accept incandescent filament bulbs’ (a ‘green’ idea). This has led to the development of a proprietary, arbitrary format of compact fluorescent bulb, the BC3, which costs a lot more than standard compact fluorescents, is difficult to obtain, and about which the public generally doesn’t know much (yet). If you’re so minded, it’s not hard to modify the fitting and save money.

A lot of visitors have found this blog recently via searching for information on the MEM BC3 3-pin bayonet compact fluorescent bulbs, where to get them, and why they’re so expensive. The main posts here discussing them, with background to what it’s all about, are A bright idea? and some more thoughts – and it’s readers’ comments which are the really interesting part of both posts.

There are so many stories of frustration there, of people trying to ‘do their bit’ for the environment, trying to fit better CFLs in their homes, and finding that instead of instead of the subsidised or even free standard 2-pin bayonet CFLs available all over the place in a variety of improved designs, styles and quality, they’re locked in to having to pay 10 or 15 times as much for a BC3 bulb, and order online, simply because the manufacturer has a monopoly, and does not seem to supply the bulbs to normal DIY or hardware stores.

Frankly, the system is appalling, an example of exactly how not to design for sustainable behaviour. It’s a great ‘format lock-in’ case study for my research, but a pretty pathetic attempt to ‘design out’ the ‘risk’ of the public retro-fitting incandescent bulbs in new homes. This is the heavy-handed side of the legislation-ecodesign nexus, and it’s clearly not the way forward. Trust the UK to have pushed ahead with it without any thought of user experience.

One of the most egregious aspects for me is the way that Eaton’s MEMLITE BC3 promotional material presents users with, effectively, a false dichotomy between the ‘energy saving BC3′ and the energy-hungry GLS incandescent filament tungsten bulbs, as if these are the only two options available. There is no mention at all of standard 2-pin bayonet CFLs which have all the advantages of the BC3 with none of the disadvantages. The adoption of CFLs has been, I would argue, in large part because they are widely available as drop-in replacements for standard 2-pin bayonet (or Edison screw) bulbs. If they’d all required special fittings, very few people would have bought them.

Anyway, if you don’t fancy swapping your BC3 fittings for standard 2-pin bayonet ones (which is cheap but would(?) presumably make your home non-compliant with part L of the building regulations – any knowledgeable readers able to clarify this?), it isn’t actually too difficult to get a 2-pin bulb to fit acceptably. You will need a pair of pliers, ideally thinner/longer-nosed than the ones in my photos. I should warn you to TURN OFF THE ELECTRICITY FIRST. Unless you’re absolutely sure that someone else won’t walk in and flip the light switch, don’t rely on just turning this off. Turn it all off at the main switch for the house.

Here (above) is a Philips Genie 11W 2-pin bayonet CFL. It fits properly into a 2-pin bayonet fitting. When you try to fit it into the BC3 fitting (below), one of the pins will go into one of the J-slots OK, but due to the offset of the other slots, the other pin won’t go in. Ignore the third slot.

But if you look carefully at how the non-fitting pin lines up with the slot (below), you can see that the bottom end of the slot, i.e. where the pin would sit if it could be got into the top of the J, is (just) to the left of the pin. (See the line I scratched on the fitting.) That is, if you could get it there, it would still sit in place without immediately falling out.

So, with the pliers (making sure the electricity really is off), bend the edge of the non-fitting slot (the inside edge of the J) inwards and fold it back on itself, squeezing it as tight as you can (below two photos):

Now try the 2-pin bayonet bulb again (below) – it should fit OK, with a bit of wobbling perhaps. One pin should fit under the bit you just bent; the other should butt up against the inside corner of the J on the other side. It’s not perfect, but the friction there is enough to hold the bulb in place OK.

Switch on the electricity again, and there you have it: any standard 2-pin bayonet bulb, working, in a BC3 fitting (below). Given the amount of free CFLs handed out by various organisations, you could probably replace all the BC3 bulbs in your house for zero cost, once they come to the end of their lives.

Disclaimer: I can’t accept any responsibility for injuries, non-compliance with building regs, incidental damage, etc. The above is just a proof of concept, etc. Have fun.

Italian railway operator Trenitalia has a simple way of locking the windows shut in some of its older carriages with (retro-fitted?) air-conditioning. This was on a train from Florence to Pisa; the sticker probably cost more than the screw. I like that.

It also allows passengers who really need some air to unscrew them – perhaps if the air-conditioning fails, or indeed otherwise – as a couple of people had done.

As longer-term readers may remember, back in 2005, I initially approached this whole subject from a very anti-control point of view. Products, systems, environments which seek to control or coerce the user into particular behaviours are, ultimately, not desirable, and the user mentality which seeks to avoid that control, or circumvent it, is something to be applauded, and very much necessary for the advance of society. Designing ‘for’ emergence is difficult; but emergent behaviour – at the very least, weak emergence – will emerge anyway.

Now, I still very much hold the anti-control belief – the proliferation of fundamentally anti-user artefacts in public space (as we see every couple of weeks on the blog) still astonishes me – but the major insight that led to taking on the PhD and the direction since the end of 2007, has been that, applied in a different context, some of the same techniques can actually help the user, improving efficiency and helping society at the same time. All design is persuasive, perhaps: any design technique can be used for ‘good’ or ‘evil’, just like any other tool. Guiding/persuasion/coercion may all be part of a continuum, depending on your point of view, but if something is (transparently) helping you to achieve something which benefits you, you’re less likely to try and find a way round it.

Rest assured, then, I will attempt to include recognition of this in the method that’s being developed, even if it’s a simple step that asks the designer to consider that the particular technique under consideration “has been shown to provoke user resistance/hostility/reaction” and hence maybe isn’t ideal. We’re all users, even designers: even supercilious councillors were kids once, and we mustn’t lose sight of that.

Heading north-east
I’m going to be away for a few days in Finland presenting at Persuasive 2008 (in fact, should be there already as this post appears on the blog), so the posts might get a bit slower/briefer for a while: apologies if I haven’t/don’t reply to your emails or comments (yet), but I hope to do so as soon as I can. It’d be great to do a bit of Jan Chipchase-style blogging while I’m experiencing these liminal spaces of departure lounges and interstitial connexions: I’ll see what I can do.

Bicycles can churn up the surface of footpaths…

…You can put up signs to tell cyclists not to do it…

…or you can put in gates (kissing gates as they’re known in the UK) to try to stop them (along with livestock)…

…but it doesn’t mean anyone will take any notice!

Interesting to see the BBC’s summary of the current iPhone update story: “Apple issues an update which damages iPhones that have been hacked by users”. I’m not sure that’s quite how Apple’s PR people would have put it, but it’s interesting to see that whoever writes those little summaries for the BBC website found it easiest to sum up the story in this way. This is being portrayed as Apple deliberately, strategically damaging the phones, rather than an update unintentionally causing problems with unlocked or modified phones.

Regardless of what the specific issue is here, and whether unmodified iPhones have also lost functionality because of some problem with the update, can’t we just strip out all this nonsense? How many people who wanted an iPhone also wanted to be locked in to AT&T or whatever the local carrier will be in each market? Anyone? Who wants to be locked in to anything? What a waste of technical effort, sweat and customer goodwill: it’s utterly pathetic.

This is exactly what Fred Reichheld‘s ‘Bad profits’ idea calls out so neatly:

Whenever a customer feels misled, mistreated, ignored, or coerced, then profits from that customer are bad. Bad profits come from unfair or misleading pricing. Bad profits arise when companies save money by delivering a lousy customer experience. Bad profits are about extracting value from customers, not creating value.

…

If bad profits are earned at the expense of customers, good profits are earned with customers’ enthusiastic cooperation. A company earns good profits when it so delights its customers that they willingly come back for more—and not only that, they tell their friends and colleagues to do business with the company.

…

What is the question that can tell good profits from bad? Simplicity itself: How likely is it that you would recommend this company to a friend or colleague?

If your iPhone’s just turned into the most stylish paperweight in the office, are you likely to recommend it to a colleague?

More to the point, if Apple had moved – in the first place – into offering telecom services to go with the hardware, with high levels of user experience and a transparent pricing system, how many iPhone users and Mac evangelists wouldn’t have at least considered changing?

The liquid detection stickers in mobile phones, which allow manufacturers and retailers to ascertain if a phone has got wet, and thus reject warranty claims (whether judiciously/appropriately or not), seem to be concerning a lot of people worldwide. Around a quarter of this site’s visitors are searching for information on this subject, and the comments on last October’s post on the subject contain a wealth of useful experience and advice.

This current thread on uk.legal.moderated goes into more depth on the issue, and how the burden of proof works in this case (at least in the UK). While informed opinion seems to be that the stickers will only change colour when actual liquid is present within the phone, rather than mere moisture or damp, this may well include condensation forming within the casing, as well as the more obvious dropping-of-phone-into-puddle and so on. The main point of contention seems to be that the sticker may change colour (perhaps gradually) and the phone continue working perfectly, but when an unrelated problem occurs and the phone is taken in for repairs under warranty, the presence of the ‘voided’ sticker may be used as a universal warranty get-out even if the actual problem is something different.

Tilt detection
Along these lines, one of the posts tells of a similarly interesting design tactic – tilt-detectors on larger hardware:

30 years in the IT industry and associated customer service tells me they are trying it on and most people buy it. In the olden days, hardware used to come with a similar red dot system indicating the kit had been tilted more than 45 degrees and the manufacturers claimed the kit could not be installed and had to be written off.

Of course, 99.9% of the time the kit was fine, but they had a get-out from a warranty claim or so they thought. When the buyers tried to claim on their insurance or against the transport companies insurers the loss adjusters got involved and invariably the kit was installed and worked fine for years rather than the insurers paying out.

In some cases, of course, tilt-detectors were (are still?) necessary in this role. A piece of equipment with multiple vertically cantilevered PCBs laden with heavy components – relays, for example – might well be damaged if the PCBs were tilted away from the vertical. Certainly some devices with small moving coil components would seem as though they may be damaged by being turned upside down, for example. (Do the ultra-fine damper wires on an aperture-grille CRT monitor such as a Trinitron need to be kept in a particular orientation when handling the monitor?)

This patent, published in 1984, from which the above images were extracted, describes an especially clever ‘interlock’ system using two liquid-based detectors arranged so that if the device/package is tilted and then tilted back again, the second detector will then be triggered:

…it is desirable that the tilt detectors not be resettable. In particular, it must be possible to combine a package with at least a pair of the tilt detectors such that attempting to reset one would cause the other to be tilted beyond its pre-determined maximum angle so that the total combination would always afford an indication that the tilt beyond that allowed had been effected.

This is something of a poka-yoke – but as with the phone liquid-detection stickers, it’s being used to detect undesirable customer/handler behaviour rather than actually to prevent it happening. Other than making a package too heavy to tilt, I am not sure exactly how we might design something which actually prevents the tilting problem, aside from rectifying the design problem which makes tilting a problem in the first place (even filling the airspace in the case with non-conductive, low-density foam might help here).

But there’s certainly a way the tilt-detector could be improved to help and inform the handler rather than simply ‘condemn’ the device. For example, it could let out an audible alarm if the package or device is tilted, say, 20 degrees, to allow the handler to rectify his or her mistake before reaching the damaging 45 degrees, whilst still permanently changing colour if 45 degrees is reached. In the long run, it would probably help educated users about how to handle the device rather than just ‘punishing’ them for an infraction. I’m sure that mercury-switch (or whatever the current non-toxic equivalent is) alarms have been used in this way (e.g. on a vending machine), but how often are they used to help the user rather than alert security?

The patent description goes on to mention using tamper-evident methods of attaching the detectors to the device or packaging – this is another interesting area, which I am sure we will cover at some point on the blog.

We’ve looked before at a number of technologies and products aimed at ‘preventing’ photography and image recording in some way, from censoring photographs of ‘copyrighted content’ and banknotes, to Georgia Tech’s CCD-flooding system.

Usually these systems are about locking out the public, or removing freedoms in some way (a lot of organisations seem to fear photography), but a few ‘fightback’ devices have been produced, aiming to empower the individual against others (e.g. Hewlett-Packard’s ‘paparazzi-proof’ camera) or against authority (e.g. the Backflash system intended to render a car number plate unreadable when photographed by a speed camera). The field of sousveillance – lots of interesting articles by Régine Debatty here – is also a ‘fightback’ in a parallel vein.

Taking the fightback idea further, into the realms of everyware, Miquel Mora’s IDentity Protection System, shown last month at the RCA’s Great Exhibition (many thanks to Katrin Svabo Bech for the tip-off), aims to offer the individual a way to control how his or her image is recorded – again, Régine from We Make Money Not Art:

With IDPS (IDentity Protection System), interaction designer Miquel Mora is proposing a new way to protect our visual identity from the invasion of ubiquitous surveillance cameras. He had a heap of green stickers that could stick to your jacket. Or anywhere else. The sticker blurred your image on the video screen.

“With the IDPS project I wanted to sparkle [sic.] debate about all the issues related to identity privacy,” explains Miquel. “Make people think about how our society has become a complete surveillance machine. Our identities have already been stored as data in many servers ready to be tracked. And our self image is our last resort. So we really need tools to protect our privacy. We need tools that can allow us to hide or reveal our visual image. We must have the control over it.”

“For example in one scenario a girl is wearing a tooth jewellery with IDPS technology embedded. So when she smiles she reveals it and it triggers the camera to protect her. With IDPS users can always feel comfortable, knowing that with a simple gesture like smiling, they are in control. The IDPS technology could be embedded in all kind of items, from simple badges to clothes or jewellery. For the working prototype I’m using Processing to track the stickers and pixelate the image around when it founds one.”

Image from Miquel Mora’s website

While the use of stickers or similar tags (why not RFID?) which can be embedded in items such as jewellery is a very neat idea aesthetically, I am not sure what economic/legal incentive would drive CCTV operators or manufacturers to include something such as IDPS in their systems and respect the wishes of users. CCTV operators generally do not want anyone to be able to exclude him or herself from being monitored and recorded, whether that’s by wearing a hoodie or a smart black hat with maroon ribbon. Or indeed a veil of some kind.

Something which actively fought back against unwanted CCTV or other surveillance intrusion, such as reversing the Georgia Tech system in some way (e.g. detecting the CCD of a digital security camera, and sending a laser to blind it temporarily, or perhaps some kind of UV strobe) would perhaps be more likely to ‘succeed’, although I’m not sure how legal it would be. Still, with RCA-quality interaction designers homing in on these kinds of issues, I think we’re going to see some very interesting concepts and solutions in the years ahead…

But its ViewFinder image gallery website* sadly falls into the trap of trying to restrict public engagement rather than make it easy. Yes, someone specified the old ‘right click disabled‘ policy:

Screenshots of this page, launched from this page.

Now, the image in question – here’s a direct link – which happens to be an engraving of the former Datchet bridge**, in 1840 according to this page (with a colour image) is, even taking English Heritage’s “1860-1922” suggested date range, surely out of copyright, so presumably there cannot be any ‘legal’ question over ‘letting’ people save a copy (which is easiest to do by right-clicking on the most common operating systems and browsers). Using Javascript to remove the browser toolbars and menus also hides the ability to print the image for most users, presumably also deliberately.

Yes, of course, many (most?) readers of this post will know how to get around the no-right-click architecture of control, but you’re reading a technology blog; think of whom the site is presumably aimed at. It is supposed to be a resource to encourage public engagement with history and heritage. Most users will be computer-literate enough to know how to search and probably familiar with right-clicking, but not to mess round with selectively disabling Javascript. Why should they have to? Incidentally, if you do disable Javascript entirely, you can’t even view an enlarged image at all:

What actual use to the public, other than for momentary on-screen interest, is a photo archive website where nothing can be ‘done’ with the images? What is a child doing a local history project supposed to do? Order a print at £18.80 for each photo and then scan it in? Does English Heritage really think that the ability for someone to save or print or e-mail a low-resolution 72 dpi image is going to devalue or compete with the organisation in some way?

It’s ridiculous: such a short-sighted, narrow-mindset policy removes a significant proportion of the usefulness of the site. I don’t know whether the site developer did this with or without English Heritage’s instruction or cognizance (and it was in 2002, so perhaps different thinking would apply today), but it seems that no-one bothered to think through what an actual user might want to get from interacting with the site.

In fact, regardless of the fact that this particular image (as with many others on the site) is in the public domain, even the images which are still under copyright (or “© English Heritage.NMR” as the site puts it, NMR being the National Monuments Record) should, of course, be freely downloadable, printable, and do-whatever-you-want-able. Their acquisition, preservation and cataloguing were paid for by the public, and they should all be available as widely, and easily, as possible. As it is, I would call the website a waste of public money, since it does not appear to offer what most intended users would expect and need.

Still, at least the site’s not one giant bundle of Flash. That would make it marginally more hassle to extract the images.

*Partially funded by the Big Lottery Fund, and thus not entirely directly taxpayer-funded, unless one regards the National Lottery as an extra tax on the hopeful and desperate, which some commentators would.
**Almost exactly the spot where I’ve been testing a prototype radio-controlled toy for a client this very afternoon, in fact, though the bridge is long gone.

L.J.K. Setright, the late motoring writer and commentator, self-taught mechanical engineer and all-round Renaissance Man, once wrote:

Fashion is a terrible fetter; convention, since it lasts longer, is even worse.

This was in an issue of Car, when it was still any good.

Setright wrote it in reference to car design, and the lack of progress thereof, but I think we can all see how applicable it is to many fields of endeavour, not just in technology but in society also. We should be very wary when fashions become conventions – or at least we should think them through before they become norms. And we should always leave ourselves a way out. (I’ve mentioned this in a few contexts before, perhaps with a little hyperbole.)

What almost became a norm – DRM’d music – is now apparently on the way out. DRM was a fashion, not a convention: still a fetter, but one which can ultimately be shaken off, as it should be.

The great thing about fashions, of course, is that they can be talked into existence, and talked out of existence too. Fashions are not architecture.

First, an apology for anyone who’s had problems with the RSS/Atom feeds over the last month or so. I think they’re fixed now (certainly Bloglines has started picking them up again) but please let me know if you don’t read this. Oops, that won’t work… anyway:

Some developments in – and commentary on – digital architectures of control to end 2006:

It’s inevitable that for every attempt to cajole or impose control on users, there will be some people who seek to avoid or circumvent it. As Crosbie Fitch put it in a recent comment, “humans are designed to explore the parameters of their environment and to adapt to them”.

Supermarket loyalty cards are an interesting example of this. Whilst not a rigid method of control – more a method of persuasion – their ubiquity and fairly clear agenda make them common target for intentional avoidance, or subversion. For every person who hasn’t signed up out of just-not-being-bothered, there is probably at least one who doesn’t trust what will happen to his or her data, even if it’s only a vague feeling of unease. And there is a small segment of customers who will (admirably) attempt to manipulate the system, either for their own gain, or simply out of an inquisitive or rebellious spirit.

Rob Cockerham’s ‘Ultimate Shopper’ is one of the most famous (and apparently successful) ‘white hat’ attempts to subvert a loyalty card system: Rob replicated the barcode (scanned by the cashier) from his Safeway Club card, and sent out dozens of copies of it to friends and readers of his website, with the aim of creating an ‘interesting’ customer profile on Safeway’s system: one who bought vast quantities of products each month, right across the country:

I want to take the credit for all of my shopping, and for your shopping too!

…

Anyone who does this will be lumping their shopping data together with mine. Together we might amass a profile of the single greatest shopper in the history of mankind.

You will still get club card savings, but you will miss out on the odd promotions they have from time to time. Actually, some promotions are awarded at the register, so you may continue to benefit from those, although the rewards will be utterly unpredictable.

Actually cloning the data on the magnetic strip, to create a more foolproof (and less detectable) set of cloned cards, would be another step. Depending on the structure of the supermarket’s loyalty scheme, there may well be thresholds above which the ‘rewards’ for customers increase substantially, and assuming the participants in the cloning scheme can work out a fair or acceptable way to share their rewards, this could mean greater benefits for all of them than actually using their cards individually.

An alternative scheme is Rob Carlson’s ‘Giant BonusCard Swap Meet‘ where card-holders from Giant (“a large supermarket chain in the Baltimore/DC area”) swap details with other card-holders in order to give themselves more privacy – from a 2003 article:

Carlson’s site works like this: You enter your Giant card number on a form. It puts this number into a pool of numbers gathered from participants. Drawing from this pool, it displays for each visitor a bar-code replica of someone else’s number, allowing the visitor to print it out and tape onto his or her own card. Should you actually take the time to do this and then visit the local Giant to use this card, you are, to Giant, someone else. If enough people do this, the argument goes, Giant’s shopper profiles are rendered muddied and ultimately useless.

A Wired article from 2003 on Rob Cockerham and Rob Carlson’s projects.

Are there other similar examples?

[An additional aspect of supermarket 'fight back' borders on actual theft but is surely extremely common: when supermarkets' self-service systems (e.g. for weighing loose fruit and vegetables) allow customers to print out an appropriate barcode label, there's also (inevitably) the possibility of the customer, er, adjusting the process in his or her favour. If I buy an organic apple that costs more per pound than a non-organic apple, and ostensibly looks the same, what's to stop me entering the details for the non-organic apple and thus paying just for that? There may be CCTV watching the self-weigh units, but is the resolution good enough to tell the difference between different types of apple? Will the checkout assistant be able to tell the difference?

Of course, where these self-print systems are used in conjunction with self-scan systems (where the customer uses the scanner), there's even more potential to 'get away' with things, whether that's just under-weighing your goods or just pressing the button for the cheapest item each time - often, in the UK, onions - no matter what you're weighing. There's also significant potential for legitimate mistakes here. Since the CCTV can't read at that resolution, and you have a barcode for each item, you'd probably get away with it. Please note, I'm not advocating this, just pointing out a particular weakness of this aspect of retailing technology.

Getting back to the point, if the above onion trick is combined with a loyalty card which tries to build a customer profile, we'd end up with a customer who buys an enormous amount of onions and no other loose fruit or vegetables. That might be suspicious in itself; if the customer has a loyalty card, he or she could be identified and investigated; otherwise there would be no way of tracing the mystery onion-buyer. Thanks to a friend for this observation]

Stick

If we define ‘stick’ as ‘punishing the user for attempted deviation from prescribed behaviour’, then many of the architectures of control we’ve examined on this site demonstrate the stick approach. They’re not explicitly ‘technologies of punishment’ in Foucault‘s phrase, but rather a form of structural punishment. The thinking seems to be (for example):

…and so on. There are numerous other examples from software and urban planning, especially.

The thing is, though, for each of those ‘sticks’, a large percentage of people will not be obedient in the face of the ‘punishment’. They’ll try to find a way round it: a way of achieving their original objective but avoiding the punishment. They’ll search for what others in similar situations have done (e.g. DeCSS in the DVD example) or ask among friends until they find someone with the required expertise or who knows about an alternative. They may even actively destroy the ‘stick’ that punishes them. In some cases they might not even understand that they’re being punished, simply seeing ‘the system’ as beyond their comprehension or stacked against them.

Equally, there isn’t always a rational strategy behind the ‘stick’ in the first place. The anti-homeless bench doesn’t ‘solve’ the ‘problem of homelessness’. It just punishes those who try to lie down on it without offering an alternative. It’s punishment with no attempt at resolving the problem.

If a stick does get people to change their behaviour in the intended way, it will be accompanied by resentment, anger and dissatisfaction. It may only be fear of the consequences which prevent actual rebellion. In short: using sticks to change people’s behaviour is not a good idea.

Image from image.frame

Carrot

A ‘carrot’ means offering users an incentive to change their behaviour. This moves away from actual control to something closer to some aspects of captology – making a persuasive case for behaviour change through demonstrating its benefits rather than punishing those who disobey.

To some extent, control and incentives may be incompatible. Taking away functionality from users then showing them how they can get it back (usually by paying something) might be a classic combined “carrot and stick” technique, but it’s also bordering on a protection racket, and it doesn’t fool many people.

However, can control be used in conjunction with genuine incentives to serve the agendas of both sides? Electric lights that turn off automatically if no-one’s in the room take some control away from the user, but also offer benefits to both the user (lower electricity bills) and society as a whole (less energy used). But if they turn off automatically, is there actually any incentive for the user to change his or her behaviour? If we’re always spoon-fed, will we ever learn?

Perhaps mistake-proofing measures or forcing functions which allow a user to increase his or her productivity or safety, in return for giving up some ‘control’ – which may not be highly valued anyway – fit the definition best. If I’m working in a factory painting coachlines on hand-built bicycles, a steady guide arm that damps my arm vibrations – but only if I also take care as well – takes some control away from me, but also prevents me making mistakes, allowing me to paint more coachlines per hour, more accurately. It also helps my employer.

But that’s a very weak degree of control. Unless anyone can come up with any counter-examples, I would suggest that providing real incentives for users to change their behaviour is fundamentally a very different approach to the ‘control mindset’ (unless you are trying to trick people by offering false incentives, or by understating what they could lose by changing their behaviour).

I’ll get round to speedometers in a future post, since this approach is worthy of a deeper treatment.

*The phrase “carrot and stick” seems now universally to imply “offering incentives with one hand and punishment with the other” (though not necessarily at the same time), rather than the “carrot dangling from a stick, just out of reach” meaning (i.e. “motivating people to perform with incentives which will never be fulfilled”) which I first assumed it to have when I heard the phrase as a kid (I’m not the only one with this issue). In this post, I’ll use “stick” to mean “punishment”.

News Sniffer‘s Revisionista monitors alterations to published news stories from a variety of sources by comparing RSS feeds, sometimes revealing subsequently redacted information or changes of opinion (e.g. note the removed phrase in the first paragraph of this story about Cuba). While many of the changes are simply re-wordings for clarity or to correct grammatical errors, there are certainly also some instances of more substantial revisions – see the ‘recommended’ list.

Perhaps more revealing is News Sniffer’s Watch Your Mouth, which shows the reactively moderated comments removed from the BBC’s ‘Have Your Say’ threads. I’ve been reading this for a while – in fact I think I might have been one of the first subscribers via Bloglines – and am still amazed by just how many comments are removed by the BBC’s moderators, often making points which, though maybe controversial, are very much the voice of the common man and woman. Some are offensive, yes; others are genuine expressions of frustration or even first-hand annotations to or clarifications of aspects of the story above. Many are critical of the BBC, including those criticising the moderators for censorship of the very comments under dicsussion.

For many people in the UK, the BBC’s ‘Have Your Say’ is a first exposure to the concept of social media: their first experience of having their views and opinions directly shown to other users and being able to repsond to others’ opinions. Having such censorship in place may ‘tidy up’ the appearance of the site from the BBC’s point of view, and prevent arguments developing in the comments, but I feel that laying itself open to such (accurate) accusations of censorship will not be in the BBC’s best interests in the longer term. The BBC’s reaction to News Sniffer largely glosses over the ‘Watch Your Mouth’ section, which is a shame.

(When I was a teenager, I used to spend a lot of time listening to Talk Radio, and its successor, talkSPORT, even if only in the background while working. I knew the callers’ and presenters’ views weren’t representative of the population as a whole, but there was something intensely interesting about really being in touch with what (some) people were saying around the kitchen table, or in the pub. The views weren’t always informed, but there was a lot of common sense and frank opinion which rarely came across in other media available at the time (pre-fast Internet access). To some extent I see Watch Your Mouth as a kind of successor to that: the opinions that slip down, or are forced down, the back of the sofa, brought out into the open once more, whether idiotic or incisive.)

Is this relevant to architectures of control? I think so, even if only tangentially. News Sniffer is a fightback device against a formalised system of censorship, using simple, open technology (RSS) to break the control imposed by censors.

My Epson Stylus Photo R1800′s been running low on ink in a couple of cartridges for a few days now. I’ve been putting off ordering them until this weekend. Now I find that when the printer believes a cartridge has reached 0%, it won’t print anything at all, even if it doesn’t need that colour. Users (i.e. me) are forced into buying new cartridges at a time when they don’t actually need them in a pathetic exercise of Epson’s control. Workflow is interrupted, plans out of the window.

So now, in order to print something important which needs to be done this afternoon, I am going to have to get on a train and go into a local town, wasting a couple of hours of my life and resulting in entirely unnecessary energy usage and carbon emissions. That’s relatively easy for me: I live next to a railway station. But in areas of the world where it isn’t convenient or possible, how can such thoughtless design be tolerated? Printers a few years ago allowed you to keep printing until the cartridges were actually empty. You knew when to stop because you could see.

Hey Epson: if you push your customers around, they’ll walk away. Forever. It’s as simple as that. People’s time is precious. Convenience is important. There’s no way I’ll ever buy another Epson product or recommend them to anyone else. And I’m a techy guy: occasionally, people do ask my opinion on products. (Of course I’m going to buy cheap refill cartridges; ultimately I may have to get a continuous ink supply system)

Yeah, it’s a rant; it’s also a pathetic piece of design embodying absolute contempt for the customer.

(Sadly the SSC Service Utility mentioned a few months ago doesn’t seem to allow the ink levels to this particular printer to be re-set, though it’s undoubtedly of great use on other models.)

In a recent post, I discussed a Spiked article by Josie Appleton which included the following quote:

“Police in Weston-super-Mare have been shining bright halogen lights from helicopters on to youths gathered in parks and other public places. The light temporarily blinds them, and is intended to ‘move them on’, in the words of one Weston police officer.”

A friend, reading this, simply uttered a single word: “Mirror”.

What’d happen then? Is the risk of a blinded pilot and a crashed helicopter really worth it?

Or perhaps it’s the state, and by extension Avon & Somerset Police (in this case), who are the real blind pilots, attempting to ‘guide’ society in this way? If not blind, they’re certainly short-sighted.

Maybe an OGG version will be available for the next in the series?

Update: OK, they’ve now added the mp3 link to the post! Good on them!

I’ve just come across a very interesting new blog, uninnovate.com, which focuses on the phenomenon of “engineering expensive features into a product for which there is no market demand in order to make the product do less.” The first few posts tackle ‘Three legends of uninnovation‘ (the iPod’s copy restrictions, Sony’s mp3-less Walkman, and Verizon’s rent-seeking on Bluetooth features), Microsoft’s priorities (patching DRM flaws vs. security flaws that actually damage users), Amazon’s absurd new Unbox ‘service’ and ‘Trusted’ computing for mobile phones. The perspective is refreshingly clear: no customer woke up wanting these ‘features’, yet companies direct vast efforts towards developing them.

In a sense the ‘uninnovation’ concept is a similar idea to a large proportion of the architectures of control in products I’ve been examining on this site over the last year, especially DRM and DRM-related lock-ins, though with a slightly different emphasis: I’ve chosen to look at it all from a ‘control’ point of view (features are being designed in – or out – with the express intention of manipulating and restricting users’ behaviour, usually for commercial ends, but also political or social).

Uninnovate looks to be a great blog to watch – not sure who’s behind it, but the analysis is spot-on and the examples lucidly explained.