Web of data — third of five IA Summit 2007 themes

(Here’s the third post on the 2007 IA Summit. You can find the first one that introduces the series and describes the first theme ‘tangible’ here and the second one on ‘social’ here.)

Typically, IAs have concerned themselves with the design of web sites. The metaphor most suited and used for the web so far has been space. Even the term ‘information architecture’ points to this. Nowadays, besides having to tackle the social dimension (as per the previous trend mentioned) IAs are forced to rethink the spatial metaphor in favour of a new one: the web as platform. This means designing for a web of data, where sites become data sources and tools to view and manipulate that data. This is a far cry from the old hierarchical model. Like design for social software, IAs are still exploring this new territory.

There was an excellent panel on this subject (notes and audio at The Chicken Test), with amongst others Tom Coates and Matt Biddulph (both previously employed by the BBC). Coates’ presentations (Native to a Web of Data and Greater than the sum of its parts) are essential resources. He gave a super short overview of what designing for the web of data is all about. Matt went beyond screen based media into the realm of physical computing (see the first trend) showing some cool examples of Arduino prototypes feeding into Second Life.

Jared Spool talked about the usability challenges of web 2.0 and focussed on (among many things) the shortcomings of RSS and the dangers of mash-ups. RSS as a technology is pretty cool, but no normal user intuitively understands its application. This is a technology still looking for a killer app. Mash-ups are typically made by enthusiastic amateurs looking to combine available data sources or interfaces. This means we’ll see a wave of sites with serious usability issues. I’m not sure that’s a bad thing per se, but still something to look out for.

Social — second of five IA Summit 2007 themes

(Here’s the second post on the 2007 IA Summit. You can find the first one that introduces the series and describes the first theme ‘tangible’ here.)

The recent web revival, that I will not name, pushed one trend to the forefront – social software. The most challenging aspect of designing social sites and applications is that you’re not ‘just’ designing for single users, but also for groups as a whole. The IA community is still in the beginning phases of creating a body of knowledge about how to best go about this.

Andrew Hinton gave one of the best talks of the event, first describing the unique properties of network-like communities of practice and how to design for them. From there he made the point that IA itself is a community of practice, not a formal discipline, which means it should try to stay open and flexible.

Bonus: Gene Smith took a stab at the building blocks of social information architectures and came up with this nice model.

Tangible — first of five IA Summit 2007 themes

I’ll be posting a top 5 of the themes I noticed during the past 2007 IA Summit in Las Vegas. It’s a little late maybe, but hopefully still offers some value. Here are the 5 themes. My thoughts on the first one (tangible) are below the list:

  1. Tangible (this post)
  2. Social
  3. Web of data
  4. Strategy
  5. Interface design

1. Tangible

The IA community is making a strange dance around the topic of design for physical spaces and objects. On the one hand IAs seem reluctant to move away from the web, on the other hand they seem very curious about what value they can bring to the table when designing buildings, appliances, etc.

The opening keynote was delivered by Joshua Prince-Ramus, of REX (notes by Rob Fay and Jennifer Keach). He made some interesting points about how ‘real’ architects are struggling with including informational concerns in their practice. Michele Tepper, a designer at Frog talked us through the creation of a specialized communications device for day traders where industrial design, interaction design and information architecture went hand in hand.

More to come!

UX designers should get into everyware

I’ve been reading Adam Greenfield’s Everyware on and off and one of the things that it has me wondering the most lately is: are UX professionals making the move to design for ubiquitous computing?

There’re several places in the book where he explicitly mentions UX in relation to everyware. Let’s have a look at the ones I managed to retrieve using the book’s trusty index…

On page 14 Greenfield writes that with the emergence of ubicomp at the dawn of the new millennium, the user experience community took up the challenge with “varying degrees of enthusiasm, scepticism and critical distance”, trying to find a “language of interaction suited to a world where information processing would be everywhere in the human environment.”

So of course the UX community has already started considering what it means to design for ubicomp. This stuff is quite different to internet appliances and web sites though, as Greenfield points out in thesis 09 (pp.37-39):

“Consistently eliciting good user experiences means accounting for the physical design of the human interface, the flow of interaction between user and device, and the larger context in which that interaction is embedded. In not a single one of these dimensions is the experience of everyware anything like that of personal computing.” (p.37)

That’s a clear statement, on which he elaborates further on, mentioning that traditional interactions are usually of a “call-and-response rhythm: user actions followed by system events.” Whereas everyware interactions “can’t meaningfully be constructed as ‘task-driven.’ Nor does anything in the interplay between user and system […] correspond with […] information seeking.” (p.38)

So, UX designers moving into everyware have their work cut out for them. This is virgin territory:

“[…] it is […] a radically new situation that will require the development over time of a doctrine and a body of standards and conventions […]” (p.39)

Now, UX in traditional projects has been prone to what Greenfield calls ‘value engineering’. Commercial projects can only be two of these three things: fast, good and cheap. UX would support the second, but sadly it is often sacrificed for the sake of the other two. Not always though, but this is usually dependent on who is involved with the project:

“[…] it often takes an unusually dedicated, persistent, and powerful advocate […] to see a high-quality design project through to completion with everything that makes it excellent intact. […] the painstakingly detailed work of ensuring a good user experience is frequently hard to justify on a short-term ROI basis, and this is why it is often one of the first things to get value-engineered out of an extended development process. […] we’ve seen that getting everyware right will be orders of magnitude more complicated than achieving acceptable quality in a Web site, […] This is not the place for value engineers,” (p.166)

So if traditional projects need UX advocates on board with considerable influence, comparable to Steve Jobs’s role at Apple, to ensure a descent user experience will it even be possible to create ubiquitous experiences that are enjoyable to use? If these projects are so complex, can they be even gotten ‘right’ in a commercial context? I’m sorry to say I think not…

Designers (used broadly) will be at the forefront of deciding what everyware looks like. If you don’t think they will, at least I’m sure they should. They’re not the only ones to determine its shape though, Greenfield points out that both regulators and markets have important parts to play too (pp.172-173):

“[…] the interlocking influences of designer, regulator, and market will be most likely to result in beneficial outcomes if these parties all treat everyware as a present reality, and if the decision makers concerned act accordingly.” (p.173)

Now there’s an interesting notion. Having just come back from a premier venue for the UX community to talk about this topic, the IA Summit, I’m afraid to say that I didn’t get the impression IAs are taking everyware seriously (yet.) There were no talks really concerned with tangible, pervasive, ubiquitous or ambient technologies. Some basic fare on mobile web stuff, that’s all. Worrying, because as Greenfield points out:

“[UX designers] will best be able to intervene effectively if they develop appropriate insights, tools, and methodologies ahead of the actual deployment of ubiquitous systems.” (pp.173-174)

This stuff is real, and it is here. Greenfield points to the existence of systems such as Octopus in Hong Kong and E-ZPass in the US. Honestly, if you think beyond the tools and methods we’ve been using to communicate our designs, IxDs and IAs are well-equipped to handle everyware. No, you won’t be required to draw wireframes or sitemaps; but you’ll damn well need to put in a lot of the thinking designers do. And you’ll still need to be able to communicate those designs. It’s time to get our hands dirty:

“What fully operational systems such as Octopus and E-ZPass tell us is that privacy concerns, social implications, ethical questions, and practical details of the user experience are no longer matters for conjecture or supposition. With ubiquitous systems available for empirical enquiry, these things we need to focus on today.” (p.217)

So, to reiterate the question I started with: are there any UX designers out there that have made the switch from web-work to ubicomp? Anyone considering it? I’d love to hear about your experiences.

IA Summit 2007 — Leaving Las Vegas

I’m sitting in the North West Airlines World Club in Detroit using my eleven hour (!) lay-over to work away all the email and RSS feeds that have been piling up during the past days of being (mostly) off-line.

I had a great time at the IA Summit. It was definitely worth the trip. Attended lots of thought-provoking talks and met a whole bunch of inspiring people. It’s interesting to now be able to put the European IA scene in context of the ‘international’ one.

I’m single-quoting international, because to be honest, I think the IA Summit is a North American event. Of course there were quite a few visitors and even speakers from outside the US & Canada, but I can’t help but feel that the majority of attendees really are not very aware of the truly international character of the IA community.

That’s a shame.

One example is something I really should have fixed during 5 minute madness: the announcement of the European IA Summit. Apart from mentioning the event’s name and URL, people weren’t exactly persuaded to come over. It wasn’t even mentioned that this is in the beautiful city of Barcelona!

Anyway, I’ll just use this opportunity to invite all my American colleagues to make the trip and get a taste of how we do things in Europe. Seriously, I’m sure people will enjoy learning about the unique issues we’re dealing with (I did the other way around). Like Jesse James Garrett said: “embrace ambiguity”.

On a different note, I’ll probably be doing a series of posts over the coming weeks like I did for the last Euro IA Summit, once I get my notes ordered and filtered. Stay tuned.

Packing for the IA Summit

Just firing off a quick post while packing for the IA Summit. Tomorrow morning I’m taking off on my flight to Vegas. For anyone curious about my doings while in the states, your best bet is Jaiku1. SMS-ing the occasional update should be affordable and won’t take too much time. No live blogging I’m afraid, I will be taking plenty of notes2 and promise to do a proper write-up when back.

1. Although all the crazy Americans are hooked on Twitter like an addict on crack, so to keep up with what’s going on there I’ll need to switch between two presence apps. Grumble.

2. A fresh squared Moleskine pocket notebook is ready for action.

IA Summit 2007 — one week to go

IA Summit 2007 logo

While we’re on the topic of attending events: I’m lucky enough to attend this year’s IA Summit. It’s all the way in Las Vegas (a long flight from my humble country) so there’ll be plenty of jet lag to cope with. Also it’s just the conference for me, no time to attend the pre-conference workshops (which is a shame really, because there’s plenty of interesting stuff). Regardless, I’m looking forward to experiencing the mothership conference after two years of being at the Euro IA Summit and meeting lots of new interesting people. Perhaps I’ll see you there?

Spatial metaphors in IA and game design

Looking at dominant metaphors in different design disciplines I’m in some way involved in, it’s obvious to me that most are spatial (no surprises there). Here’s some thoughts on how I think this is (or should be) changing. Information architecture tends to approach sites as information spaces (although the web 2.0 hype has brought us a few ‘new’ ones, on which more later.) I do a lot of IA work. I have done quite a bit of game design (and am re-entering that field as a teacher now.) Some of the designers in that field I admire the most (such as Molyneux and Wright) approach games from a more or less spatial standpoint too (and not a narrative perspective, like the vast majority do). I think it was Molyneux who said games are a series of interesting choices. Wright tends to call games ‘possibility spaces’, where a player can explore a number of different solutions to a problem, more than one of which can be viable.

I don’t think I’m going anywhere in particular here, but when looking at IA again, as I just said, the field is currently coming to terms with new ways of looking at the web and web sites; the web as a network, web as platform, the web of data, and so on. Some of these might benefit from a more procedural, i.e. game design-like, stance. I seem to remember Jesse James Garrett giving quite some attention to what he calls ‘algorithmic architecture’ (using Amazon as an example) where the IA is actually creating something akin to a possibility space for the user to explore.

Perhaps when we see more cross-pollination between game design and information architecture and interaction design for the web, we’ll end up with more and more sites that are not only more like desktop applications (the promise of RIA’s) but also more like games. Wouldn’t that be fun and interesting?

Using concept models to design for the web of data

Flickr concept model by mApplogic

I’m lucky enough to be doing some concepting and interaction design work for a social web site. This presented me with the opportunity to integrate some stuff I found while reading on social software, and the web as platform/network. Here’s how I’ve been integrating some of it.

I was inspired by the concept model of the Flickr ecosystem I saw in Luke Wroblewski’s presentation on social interaction design (which was done by Bryce Glass) to try and create one myself. Coincidentally there’s a whole chapter in Dan Brown’s book (which Peter was smart enough to purchase and was lying around the office) on creating concept models.

One of the things I wanted to do is make the site play nice with the web of data. To that end, I decided to apply Tom Coates’ 3 basic page types to the design of the site. So what I did was first create a concept model (of course following some research of the site’s business and user goals) and then look at the nouns and verbs in the model. For each noun I created a single object view page and a list view page. For each verb I created a manipulation interface page. Of course, all list type pages would get RSS feeds in the eventual site.

For instance if you have a model that states ‘Reviewer rates Book’ then you’d end up with a page for each reviewer and book, a page to list reviewers, a page to list books and a manipulation interface for rating a book.

Doing this resulted in a nice list of pages that I could then analyse for completeness and/or redundancy. Of course this only works if your concept model accurately reflects what the site should achieve. If your model sucks, your list of pages will too.

Another caveat lies in the fact that a concept model tends to be very effective for mapping the functional aspects of a site, but not very suitable for creating an overview of its content (which is often more push oriented). If the kind of site you’re creating involves more information architecture than interaction design you might want to do some additional content inventory work and fold that into the page list.

One last challenge would be organizing these pages in a coherent whole (beyond coupling lists to single items to interfaces). I can imagine I’d attempt some card sorting to achieve that.

Finally, for creating the concept model I used the specialized (and free) tool CmapTools which is pretty nice in that it goes beyond visually modelling the concepts but actually tracking the statements you implicitly make when linking concepts to each other.

Anyone else have experience with trying to integrate some of the stuff Coates was talking about in their design of a site?

Accessibility (a Euro IA theme)

It’s been a while, but here’s my final post on the Euro IA Summit. Usability has been a design value long championed by HCI professionals from which IA has partly developed. Naturally, they’ve often been responsible for ensuring usability in projects. There have been developments that force IAs to take a broader view and see usability as one of many values that go into a successful user experience on the web. Morville realised this quite a while ago and reminded us in his keynote of his user experience honeycomb.

Accessibility is one of those other values, and quite a few talks discussed it in some way.

For instance Fredy Oré’s talk on the project he did for Digital UK (the independent, non-profit organisation leading the UK’s move to digital television) contained quite a few examples of how he as an IA was faced with accessibility problems. From figuring out how to create a site structure that would support both English as well as Welsh to working around the limitations of a legacy CMS, there were many accessibility-related decisions to make.

Bogo Vatovec summarized the results from a test he did with several content adaptation solutions (mobile web browsing applications). The state of affairs in this area appeared to be quite sordid. Opera’s mobile web browser came out as the best option currently available. However, smart software will never be the silver bullet to solve all mobile web-browsing woes. We’ll need to build sites to be accessible for a broad range of devices. I feel we need to go even one step further and create alternative architectures specifically tailored for the mobile context.

Finally Steven Pemberton flexed his W3C muscles and overwhelmed the poor non-techy IAs with a deluge of information on new web standards such as XHTML 2 and XForms. The key takeaways for me were that the W3C is still pushing for a true Semantic Web (yes, uppercase). Example: Pemberton said XHTML 2 is “microformats done right”. Also, XForms promise to be a real alternative for other RIA technology, with the main benefit that it won’t need third party technology to be installed on the client.

So again, I expect IAs to be involved in more and more accessibility-related discussions. Accessibility is one of many design values that go in a user experience. These values should be prioritised for each project. Some might even put accessibility above usability. IAs could do worse than educate themselves on some accessibility basics.

This is the fifth and final post on themes spotted during the Euro IA Summit 2006. The first post was on strategy, the second on social search, the third on process & deliverables and the fourth on involving the client. My first post-summit post can be found here.