Friday 23 April 2010

Something for the Weekend - Visual Onomatopoeia

I thought I'd share something related that I spotted on SVN. Keith Lang gave a talk called 'The Science of Aesthetics' at UXAustralia last year and in it he talks about (synaesthesia) what I suppose are deep-rooted, even instinctive, human behaviors and how an understanding of that can benefit application design. The images below give a great example of what he's talking about...

... when the shapes of objects all look the same (worst of all friendly and rounded) it's hard to understand at first glance that they have different consequences. Make the big decisions look significant (in this case, like clicking it too fast might cut your finger!) and it breaks the autopilot behavior. It's almost like a visual version of onomatopoeia, objects can look like what they are. It’s similar to using ‘red’ for cancel buttons or ‘x’ to close windows, just a bit more dramatic!

As the tools we develop increasingly get deployed globally the challenge of understanding a users common 'frame of references' increases dramatically. The considerations we apply today only touch the surface when you consider your user to be just about everyone. Hooking UI into deep-rooted human instinct means we anchor on at least a small part of everyone's frame of reference.

If you'd like to watch the full video
here's the link. Also check out the Kiki & Bouba effect if you're not familiar with it.

Thursday 15 April 2010

Something for the Weekend - Mystery Flavour

I spotted a great example of LEAN practices this week that I really wanted to share. You may remember before Christmas I wrote about the importance of establishing flow in processes with the article of the Empire State Building, this isn't quite as impressive as building the world's tallest building in a year but its good thinking all the same!

Dum Dums are a US lollipop and they started creating a 'Mystery Flavour' in 2001. Basically Mystery Flavour is a by product that the manufacturing process creates as it switched from one 'actual' flavour to another. So you might get a mix of Cherry Cola and Banana split… quite good fun but also a really good example thinking differently.

Two things are noteworthy with this example:

  • The downtime of shutting down production, cleaning and restarting would obviously cost more than the waste - so they've got the LEAN flow principles down correctly by leaving the machines running and increasing production.
  • Creating value from waste that can’t be removed is an interesting thought. Do we have unavoidable waste that could used to better effect?

Sources & Credits
Thanks to
Dum Dums and the Signal Vs Noise Blog reflections on programming by products

Friday 9 April 2010

Something for the Weekend....Andrew Kim's Eco Friendly Coke Bottles

There's not much in the packaging world that you can point to as inspirational. That is except for Andrew Kim's concept design for Eco Friendly Coke Bottles.

3 million bottles of Coke are sold worldwide each day - so savings, environmental or otherwise certainly add up. Whilst the current design keeps (albeit quite loosely) the iconic Coke Bottle design, it is cylindrical which means that lots of air is shipped in each box. Andrew's square, stackable and collapsible design means that an additional 3949 bottles could be squeezed in per shipping container (321,856,830 bottles of Coke shipped per year with a zero carbon footprint!). And when you've finished with it, you can squash it down, so you can make fewer trips to the recycling centre.

Even if you don't design packaging I think there are lessons here for us all the same. Probably more on the operational design side than technical but the crux is the acceptance that the decisions we take with process design can have long term operational cost and environmental impacts.

  • When improving processes removing as many physical items as possible (most likely paper / stationery in our world) will create savings - each item has a cost and a need for creation, processing, storage, transport & destruction.
  • Follow the 'life' of any physical items and remove 'waste' wherever possible.
  • Just because something is valuable (like the brand aspect of the Coke bottle shape) doesn't mean it’s the only way to do things - it's always worth the challenge!
  • Perhaps the most simple of all, remember that 'waste' is multiplied by volume. Even small improvements can make huge differences in our high volume processes.

You can read a little more on the coke bottle here. Lets see if Coke adopt it!!

Thursday 1 April 2010

Something for the Weekend - Technical Debt

Technical Debt is a metaphor developed by Ward Cunningham to raise awareness of some of the long term impacts of the decisions that we take to get project or technical change live. 
 Ward's metaphor refers more to 'debt' taken with ugly coding or patched together architecture but I think this concept expands well to design too.

We all take shortcuts in order to meet deadlines, restrict cost or work within other constraints. More often than not it’s the right commercial decision but the metaphor really helps to ground the decisions you need to take. 
So what is Technical Debt… imagine it as a bank account, if you take a shortcut with your project/design you go into debt and will, one day, need to repay that debt (correct your shortcut).

Also, just like an overdraft you incur interest... perhaps operational pain, perhaps defects in the code & most likely rework. The longer you live with the debt the more you pay. 
No ones saying you can't go into Technical Debt but there are rule…
  • Make decisions that are deliberate - inadvertent decisions are just bad design (or worse)!
  • Take the debt if its prudent to do so, if the commercial advantages outweigh the debt you're in the right place.
  • Have a plan to repay the debt - a follow up release, back out, etc. Compounding the problem will just make it un-repayable.

This virtual bank account isn't really measurable in £ - it's unquantifiable productivity cost and therefore needs subjective judgment but I really like the concept to articulate some of the decisions we take and live with. 
This cover the basics but if you want to read more check out the links below.

Sources and Credits
http://martinfowler.com/bliki/TechnicalDebt.html
http://senses.thirdi.com/posts/225-what-is-technical-debt/