So, my post outlining my thoughts on the Euro IA generated some interest.
Kars Alrink an attendee at Euro IA and author of Leapfrogblog seemed to think that I was ‘Euro IA Bashing’, getting on my pedestal and berating my European colleagues for being 3 years behind the US equivalent.
yes, I think that the content on offer at 2006s Euro IA conference was a little safe for my liking, and debate wasn’t particularly rife during sessions, but I’m not sitting here looking down on people, far from it.
I’ve been working with the Web since 1993 and my educational background is in Product Design, I don’t consider my self an IA. I consider it part of my role, but not how I’d describe it.
In the teams which I work at within LBi, we believe in a philosophy called Experience Design. It’s fundamental basis is that brands are built through experience and that developing digital experience is a composite effort between Experience Architects and Designers and where possible (not all our clients buy build work from us) Interface Developers.
In essence THREE are three layers to realising a brand in a digital capacity:
• Visual Principles - This describes the presentation layer, the personalities illustrated, typographic hierarchy, photographic style etc and it is the domain of the ‘Designer’.
• Architectural Principles - This describes the fundamental engineering oif the site, how it works, where pages/states live within a system and where modules or interactive touch-points live with pages/views. Essentially the underlying core usability and ease of use is the domain of the Experience Architect.
We’ll come to the third in a minute.
This is where a lot of our competitors stop. They have Information Architects working through a information classification and hierarchy, which is them expressed in wireframe format, with sitemaps, process flows etc and is then handed to a Designer to ‘brand’.
FUNDAMENTAL ERROR.
Branding is about experience. Branding 101. Anyone who thinks that the person responsible for the functional integrity of a system isn’t a brand engineer, then they may as well go home now.
In Experience Design we have a third layer that sits between the visual and the architectural. Its called the Behavioural and its where differentiators are realised and branding comes to life.
• Behavioural Principles - This describes the attitude of the site, and is where through tight collaboration across EA and Design, we can contrive the behaviour to be appropriate to the brand we are working for. it’s the layer where its possible to realise brand attributes such as FRIENDLY, TRUSTWORTHY, HONEST, DYNAMIC, STRAIGHTFORWARD etc etc.
To illustrate my example I’ll use the design of a mobile phone application.
Imagine you are in the middle of writing a text message to your wife or girlfriend and during composition she calls you.
This is what I’d call an ‘interrupt’ and can be handled in many ways, but some more appropriate to the brand than others.
OPTION ONE
- In text composition mode, call displayed
- Call answered by clicking soft-key ‘Answer’
- Message saved to drafts
- Call taken
- Call terminated
Makes sense right. Feels okay?
You could even return the user to what they were doing when the call came in eh?
Sure, but either way as our user has spoken to the person that they are sending a text to, they now want to delete the text and will have to:
- click menu
- click messages
- click drafts
- select message
- delete
Right, now if one of the brand values or principles of the brand is to fundamentally make things easier and to be effort free, maybe this works better.
OPTION TWO
- In text composition mode, call displayed
- Call answered by clicking soft-key ‘Answer’
- Call taken
- Call terminated
- User shown option screen offering:
- Continue writing text message
- Delete text message
- Save to drafts folder
Both options are usable and schematically okay, but one is fundamentally about attitude and behaviour. It’s a subtle brand inflexion realised within the bounds of interactive space. It’s an example of something that ‘just works’.
When you have Designers and EAs overlapping their respective disciplines in the way I described above you will realise a better product.
There will be a natural tension that exists in the product development that should exist in all great product be they physical or virtual.
So, briefly coming back to the IA Vs EA thing, sure it’s a label but its also a philosophy and outlook. I believe being an EA is about saying ‘Hey, I’m responsible for brand too’.
I propose that the IA discipline will always be there, but its as a subset of a wider more strategic approach. This was mentioned at Euro IA when Olly Clark started to talk about the ‘Strategic IA’ - someone who gets further into the business to influence design, brand and product strategy.
Yes! Yes! Yes!
I just prefer the idea of Experience Architecture as it’s provides remit for holistic user experience design across a range of platforms and services. My my language is wrong and the idea of Strategic IA is easier to swallow than Experience Architect?