I talked about how – when I was running the intranet at the BBC back in 2005 – I was inspired by the transformation programme at London’s South Bank Centre. I found it a useful analogy for the work we were doing to transform our digital workspace.
Useful to a point, I find analogies can become most interesting at the points where they break.
It’s a tablet (think iPad, Galaxy) with a marsupial-style pouch for a mobile handset.
No longer will you suffer eye-strain trying to read those tiny words on the handset screen. Just pop it in to the tablet, and read them in large print on the tablet.
ASUS promises seamless data transfer between the devices.
We are reassured that they’ve been using Design Thinking to make the product (or is that products? I’m not sure)
Now… am I missing something here?
As the owner of a mobile (smartphone) handset as well as a tablet, the last thing I want is to have to surrender my handset so I can use my tablet.
I’ve already chosen to carry a phone and a tablet around with me.
I like having both, and choose to have both because they serve me in different ways.
Surely data transfer can be just as seamless by pairing my devices using Bluetooth (or its successors). Sure, every now and then, it would be useful to be able to tap a webpage on my phone screen and it offer me the chance to view it on my tablet.
But keep them separate physically, and I’ll choose how and when I use each one.
Today is World Usability Day. The theme this year is communication. I’ve chosen to write about something which I find helps teams I work with communicate and explore what we design and put on the web.
Back in 2005, Yahoo! Search announced a “vision statement”.
Enable people to find, use, share and expand all human knowledge.
Somewhat ambitious, sure. A little grand, perhaps. But what a great way to think, not only about search, but also about everything we make on the web.
And it happens to form a handy mnemonic in the shape of the acronym FUSE.
At the time I was working on learning technology and intranet projects at the BBC, and found it was a really useful way to think about everything we designed, built and put out there.
If we design this site, template or widget, if we publish this content, if we make this web app, will people be able to find it, use it (more recently I’ve started using ‘understand’ as well), share it and extend it (which I prefer to ‘expand’)? FUSE?
And on every project I’ve worked in the five years since, it has still come in useful. Whatever becomes of Yahoo!, I for one, have a lot to thank them for.
[For more on FUSE, see this blog post by Tom Coates, not a fan of the acronym! In 2006, the BBC came up with its own version of FUSE – in Find, Play Share (BBC press release, Guardian article) – as its approach to all audience-facing digital output. Both work, but I find FUSE really gets people thinking.]
I’ve been thinking a lot about traffic lights recently.
Why are there three lights? Why are they vertically arranged? And how can the answers help us understand inclusive information design?
We learn from an early age that red means stop and green means go. We also learn the convention is to have red at the top and green at the bottom.
According to a Stanford University research article, “Roughly 1 in 10 men are fully or partly colour blind.” Although colour-blindness affects men and women, men are 20 times more likely to be colour blind than women.
For people with the most common types of colour-blindness, it’s hard to distinguish between red, yellow and green.
At a road junction, someone with red-green colour-blindness can see whether the red or green light is lit because of the additional information provided by the vertical arrangement of the lights.
In the world of project management, a common usage of the traffic light metaphor is as a project reporting device, using red, amber and green (RAG) to denote the current status of a particular aspect of the project. Red usually means there’s a problem, while green is all systems go.
In project reporting it’s common to show a single spot of colour to denote a RAG status (See 1a below).
To someone with colour-blindness the information design has failed. Showing a single traffic light removes the contextual information required to determine whether it’s red or green (See 1b below). That’s quite a fundamental problem.
One option is to reintroduce the full traffic light, with the RAG-status colour lit. Having three lights arranged vertically means that you don’t have to distinguish between red and green to know what the current status is. You just have to remember that top means stop. This option (not illustrated) would require some reworking of the grid to accommodate readable traffic lights, and would not make efficient use of the space available.
So what other options are there?
Adding the initial letter of the RAG status to the symbol enables us to see the differences (2a).
However, the colour-blindness simulation (2b) shows it still requires some cognitive effort to read the letters.
Better still, use a different shape for each of the three RAG statuses, as well as the colour (3a and 3b).
It’s easier to scan for triangles than the letter “R”, for example, to quickly identify the Red items.
Whichever you choose, it’s important to include a key in the diagram as well.
There’s a massive drive on at the moment to make public data available, and to use graphic design techniques to make sense of it all. A popular example is to overlay crime statistics on to a map. As data visualisation becomes ever more possible and ever more popular across digital and print media, the principle of inclusive design has never been more essential.
In a nutshell: to ensure your information design is inclusive, don’t rely on colour alone to convey meaning.
Tools and references:
Vischeck – colour-blindness simulation tools for testing images and web-pages.[N.B. the simulations shown above were generated using Vishceck’s online simulator, using the Protanope colour vision setting, a form of red-green colour-blindness.]
That’s the question currently on the homepage of Ask Nature, a new web-based resource which catalogues the many ways we can learn from nature when we’re trying to solve problems. The project is run by the Biomimicry Institute.
The site was announced this morning at TED Global in Oxford.
Here’s an excerpt:
Anchors of bull kelp protect it from torque by being flexible.
“Kelp’s survival depends on flexibility and extensibility. Each alga can grow up to 20 to 45 m (22 to 49 yd) long and consists of a holdfast, stipe, float, and fronds. The holdfast uses a flexible network of root-like haptera or anchors to attach the kelp to the ocean floor. By being flexible, the haptera allow the kelp’s base to rotate slightly, thus providing some protection from the high torque created by waves.” (Biomimicry Guild unpublished report) [read Bull Kelp article]
A good reason not to move entirely to virtual money…
I thought the six coins could make up a shield by arranging the coins both horizontally, as with the landscape idea, as well as vertically, in a sort of jigsaw style. I liked the idea and symbolism of using the Royal Arms, where individually the coins could focus on specific elements and when placed together they reveal the complete Royal Arms.
I found the idea that members of the public could interact with the coins the most exciting aspect of this concept. It’s easy to imagine the coins pushed around a school classroom table or fumbled around with on a bar – being pieced together as a jigsaw and just having fun with them.
Globally local – locally global – Jane McConnell in France. Useful international and strategic perspectives. Annual global survey giving excellent insight and evidence if anyone needs to build a business case for an intranet.
InfoDesign: Understanding by design – digest of design-related posts and articles (including interaction design, user experience design and information architecture) compiled by Peter J. Bogaards.
Inside out – A relative newcomer to the intranet blogging scene and a must-read from Richard Dennison at BT.
Intranet Blog – Toby Ward in Canada. Has worked with numerous companies and seen a lot of intranets – useful case studies and advice on avoiding common pitfalls.
IBF Blog – Rotating bloggers on a monthly basis offering insight and analysis from research and evaluations of dozens of company intranets. [I wear an occasional Intranet Benchmarking Forum hat]
The Obvious? – Euan Semple, who started the BBC’s internal blogs, wikis, discussion forum, profile pages long before anyone was talking about Enterprise 2.0 or other such neologisms. Thought-provoking ideas and ruminations on social media, the internet, society and work.
Signal vs. Noise – The blog from 37 signals makers of Basecamp and other useful, usable and desirable web apps.