Lucasarts material

People interested in the history of video-games and in the material behind production may be intrigued by "Rogue Leaders: The Story of LucasArts" (Rob Smith)

I received my copy the other day and focused my attention on all this curious prototypes and documentation of game design. Maniac Mansion or Secret of Monkey Island meant a lot to me and it's refreshing to stay the history behind. The book is a thorough survey of a video game company with lots of concept art, character sketches, storyboards and timelines.

All these impressive maps and graphs were really an important component of game/level design at the time. Simply, because the game itself was really close to these elements; whereas today game levels are far different from the maze depicted above. It does not remove the value of this documentation and I am pretty sure there are lessons to draw from these.

Why do I blog this? an interesting book about Lucasarts game design practices, surely some insights to draw for my own research.

20 years of the WWW afterthoughts

The other day at CERN, one of the thing that intrigued me most was the discussion around the first webpage. Tim Berners-Lee showed us the HyperMedia Browser/Editor, represented above. What's important there is the notion of a read/write piece of software, which reminds us that the "write" (i.e. "participate in the creation of content") component was there right from the beginning of the WWW.

As a person interested in how things age, I quite enjoy the crappy sticker on the first webserver ("This machine is a server, do not power it down")

Paleo-future textures

The city of the future was supposed to have a certain kind of texture and rugosity. Seen last week in Paris, in the Front-de-Seine neighborhood, where I encountered an intriguing set of paleo-futurist buildings.

Why do I blog this? ... this material goes straight to my set of futurist architecture.

Battlestar Galactica and UN

A curious article in the NYT about the presence of Battlestar Galactica's creator at a United Nation meeting:

"Representatives from the Sci Fi Channel approached the United Nations early this year. “They came to us and explained that there were themes common to both the show and the U.N.,” Mr. Brandt said, “and that those themes could be discussed here in a serious manner.” (...) “The show has been a sort of laboratory for the choices and issues real people in governments are making every day,” "

Why do I blog this? curious hint about the importance of fiction and politics.

20 years of the first paper about the World Wide Web

Yesterday I attended "World Wide Web@20" at CERN in Geneva where Web founders celebrated the 20 years of the "Original proposal for a global hypertext project at CERN" (1989). Tim Berners-Lee, Ben Segal, Jean-Francois Groff, Robert Cailliau and others gave a set of talks about the history and the future of the Web.

The afternoon was quite dense inside the CERN globe and I won't summarize every talks. I only wanted to write down the set of insights I collected there.

First about the history:

• The main point of Berners-Lee was that "people just need to agree on a few simple things", which was quite a challenged in the context of emergence of his invention: CERN. At the time, computers and IT in general was a zoo. There were many companies(OS), network standards were different (each company had at least one, CERN had its own... TCP/IP just began to appear form the research environment but were opposed by European PTTs and industry).
• What was interesting in the presentation was the context of CERN itself: computing was really one of the last important thing in terms of political order (after physics and accelerators). Desktops, clusters and networking were also perceived as less important as big mainframes. And of course, TCP/IP was considered "special" and illegal until 1989! To some extent, there was an intriguing paradox: the Web was created at CERN but from its weakest part and using "underground" resources
• The Web wasn't understood at first. This paradigm shift was not understood, people did not get why they should put their data on this new database because they did not understand what it would lead to The key invention was the url, something you can write on a piece of paper and give to people
• Berners-Lee also pointed out the importance of the Lake Geneva area ("looking at the Mont Blanc this morning I realized how much you take it for granted when you live here") and how the environment was fruitful and important in terms of diversity (researchers coming from all around the World).
• The basic set of things people should agree on was quite simple:
  • URIs
  • HTML was used for linking but it ended up being the documentation language of choice
  • Universality was the rule and it worked, an important step was having CERN not charging royalties
• It was also interesting to see how the innovation per se was more about integrating ideas and technologies than starting something from scratch. As shown during the demo of the first webserver and by the comments on the first research papers about the Web, it was all a matter of hyperlinks, using an existing infrastructure (the internet), URI and of course the absence of royalties from CERN. People just needed to agree on a few simple things as TBL repeated.

The future part was very targeted at W3C thinking about the web future. As Berners-Lee mentioned "the Web is just the tip of the iceberg, new changes are gonna rock the boat even more, there are all kinds of things we've never imagined, we still have an agenda (as the W3C)". The first point he mentioned was the importance for governments and public bodies to release public data on the web and let people have common initiative such as collaborative data (a la open street map). His second point here was about the complexity of the Web today:

"the web is now different from back then, it's very large and complicated, big scale free system that emerged. You need a psychologist to know why people make links, there are different motivations we need people who can study the use of the web. We call it Web Science, it's not just science and engineering, the goal is to understand the web and the role of web engineering"

And eventually, the last part was about the Semantic Web, the main direction Tim Berners-Lee (he and the team of colleagues he invited in a panel) wanted to focus on for the end of the afternoon. From a foresight researchers standpoint, it was quite intriguing to see that the discussion about the future of the Web was, above all, about this direction. Berners-Lee repeated that the Semantic Web will happen eventually: "when you put an exponential graph on an axis, it can continue during a lot of time, depending on the scale... you never know the tipping point but it will happen". The "Web of data" as they called it was in the plan from the start ("if you want to understand what will happen, go read the first documents, it's not mystical tracks, it's full of clever ideas"): we now have the link between documents and the link between documents and people or between people themselves is currently addressed. Following this, a series of presentation about different initiatives dealt with:

• grassroots effort to extent the web with data commons by publishing open license datasets as linked data
• the upcoming webpresence of specific items (BBC programs)
• machine-readable webpages about document
• machine-readable data about ourselves as what Google (social graph API), Yahoo, Russia (yandex) are doing: putting big database of these stuff once you have this, you can ask questions you did not have previously. FOAF is an attempt into this direction too.

The last part of the day was about the threats and limits:

• Threats are more at the infrastructure level (net neutrality)than the Web level, governments and institution which want to snoop, intercept the web traffic
• A challenge is to lower the barrier to develop, deploy and access services for those devices, which should also be accessible for low literacy rates, in local languages (most of which are not on the web).
• One of the aim is to help people finding content and services even in developing countries. It's also a way to empower people.
• The dreamed endpoint would be the "move form a search engine to an answer engine : not docs but answers" and definitely not a Web "to fly through data in 3D".

Why do I blog this? The whole afternoon was quite refreshing as it's always curious to see a bunch of old friends explaining and arguing about the history of what they created. It somewhat reminded me how the beginning of the Web as really shaped by:

1. a certain vision of collaboration (facilitating content sharing between researchers), which can be traced back to Vannevar Bush's Memex, Ted Nelson's Xanadu, the promises of the Arpanet/Internet in the 70s (Licklider).
2. the importance of openness: one can compare the difference between the Web's evolution and other systems (Nelson's work or Gopher). What would have happened if we had a Gopher Web?
3. a bunch of people interested in applying existing mechanisms such as hypertext, document formating techniques (mark up languages)

What is perhaps even more intriguing was that I felt to what extent how their vision of the future was still grounded and shaped by their early vision and by their aims. Their objective, as twenty years ago, is still to "help people finding content, documents and services", the early utopia of Memex/Arpanet/Internet/Xanadu/the Web. The fact that most of the discussion revolved around the Semantic Web indicates how much of these three elements had an important weight for the future. Or, how the past frames the discussants' vision of the future.

Curiously enough the discussion did not deal with the OTHER paths and usage the Web has taken. Of course they talked briefly about Web2.0 because this meme is a new instantiation of their early vision but they did not comment on other issues. An interesting symptom of this was their difficulty in going beyond the "access paradigm" as if the important thing was to allow "access", "answers" and linkage between documents (or people). This is not necessarily a critique, it's just that I was impressed by how their original ideas were so persistent that they still shape their vision of the future.

Manhole covers from the 21st century?

Street "traps" or elevators are definitely an interesting feature of cities that I am noticing lately (Paris and Lyon above, Geneva below).

These devices definitely remind me of the pipes in Mario Bros, sort of tubes that allow people to be transferred to some underground secret world:

Beyond this aesthetic concern, they do exemplify the 3D nature of cities. More importantly, this hidden stairs/elevators are important as they reveal the underlying infrastructure of the city as well as the need to access this infrastructure (sewage, electrical station, etc.) to fix things. It's the sort of modern version of manhole covers in a more technological fashion.

Social practices around mobile gaming

This picture of kids I encountered in Japan in 2004 playing with a game-boy exemplify one of the most intriguing feature I observe in gaming: a situation where only one person has a game device and the others are participating without it, in their own way. This is a common situation in gaming, one can also observe it on game consoles (where one person plays with the pad and the other helps in a less formal way).

In their paper presented at CHI 2008 "Renegade Gaming: Practices Surrounding Social Use of the Nintendo DS Handheld Gaming System", Christine Szentgyorgyi, Michael Terry & Edward Lank describes an interesting exploration of the social practices related with a mobile game platform. Unlike my picture above, they investigated players who had their own mobile consoles. Based on a qualitative study, the authors studied how players engage in multiplayer games via ad-hoc, wireless networking and how it affects the social gaming practices.

In their results, they identify three themes related to the multiplayer gaming practices of the Nintendo DS:

" renegade gaming, or the notion that users reappropriate contexts traditionally hostile to game play; pragmatic and social barriers to the formation of ad-hoc pick-up games, despite a clear desire for multiplayer, collocated gaming; and private gaming spheres, or the observation that the handheld device’s form factor creates individual, privatized gaming contexts within larger social contexts."

The paper provides informative elements about these themes and also tackles their design implications:

"we focus on two particularly salient design implications suggested by the data, namely better support for ad-hoc, pick-up gaming, and mechanisms to expand the social gaming experience (...) Mechanisms that allow one to more easily locate other local DS gamers, invite a player to a multiplayer game via the DS itself, join preexisting games, and gracefully exit games would all help address the desire for pick-up games. The implementation of these suggestions is certainly technically feasible for a system such as the DS (...) To help create a broader social context, the system could provide provisions to externally display game state on a shared display so non-players could observe game action. "

Why do I blog this? gathering material for a potential project about social gaming practices for a client. This is quite an exciting topic and I am try to collect some material about it in the context of mobile games. I am quite sure that lessons can be learned from the Nintendo DS and that it would be possible to transfer them into a cell-phone context.

How to define a "failure"

An interesting reaction to my talk at Lift09 last week is the one by Tim Leberecht from Frog Design:

"He presented a nonchalant history of product flops (from the picture phone to the smart fridge to location-based services), which were in his judgment all hampered by "over-optimism," "lack of knowledge," and "blind faith in the Zeitgeist." Yet I found his definition of product success flawed as it was obviously based on the principle of mass adoption – a questionable proposition in times of increasingly fragmented audiences and micro-markets. Which new product – besides maybe the iPod and the iPhone – has really gone mainstream in the past ten years? Many of the products and technologies Nova stigmatized as "failures" have found their audience in some form and created significant value both for their inventors and consumers. Yet we simply fail to recognize their success since it occurs in market niches and communities."

His main comment stems from my definition of "failures" that is flawed (or perhaps my absence of definition) because I too much relied on "mass adoption" as an indicator of success, according to what he perceived. Unfortunately, this was not my point. Some comments:

• I fully acknowledge the importance of niches, as attested by my slide about the non-existence of the "average human". This part was about the importance of targeting products and services (as opposed to designing to a non-existing average person extracted from the masses.
• I do agree I should have added a slide to define what is a "failure" and what I meant here. Or perhaps I should have discussed the common misconception that failures. While, the failure lies in how a certain vision (a "smart fridge") is turned into a certain product (a certain model of smart fridge), I did not meant that the vision failed. It's indeed true that lots of failed products have resurfaced in other contexts, with new and original usages (videophone vs skype).
• Although video-communication is a bit used (to convey sign language for example) OR in certain cultures, it's above all a failure in lots of markets.
• Perhaps my selection of "failures" (videophone, smart fridge, multi-user LBS) was a bit limited and lead him to find it "nonchalant" but I wanted to point out examples (as opposed to showing matrixes and statistics of examples).
• Besides, unlike my speech (that I wanted more synthetic than academic), I can also use the academic trick of quoting references. That said, I was a bit reluctant to quote this sort of material (hence the nonchalant attitude?) because (1) it would take lots of time to discuss the epistemological basis of research papers, (2) it would sound patronizing in this kind of setting. The literature about failures (and successes) is quite abundant in domains such as management of innovation, marketing or foresight. See for instance Van der Panne, G., C.P. van Beers & A. Kleinknecht: 'Success and failure of innovation: A literature review' which provides an interesting overview of success factors and also points to other papers about this topic. For example, in Asplund, M. & Sandin, R. (1999) The survival of new products, the authors describes that "only one out of every five projects ever initiated proves viable". The literature about foresight is also consistent; Steven Schnaar's "Megamistakes: Forecasting and the Myths of Rapid Technological Change" discusses how forecasts are only 20% to 25% correct. In this case, what is interesting is that it's the vision that is described as a failure (not products)
• A mistake I made (not pointed by Leberecht but I do think about it anyway) is that my perspective was certainly too occidental and that cultural variations matter. For instance, some smart fridges in Japan and Korea have succeeded.

Regarding the final comment:

"Both Nova and Gyger heralded a more pragmatic model of future-oriented thinking. But I'm not sure if I share their skepticism towards grand visions. What if the future has arrived, however – to paraphrase William Gibson – it is so widely distributed (that is, buried in fragmented micro-markets) that we don't notice it? "

I actually used the same quote from Gibson to indicate that "product failures" are interesting hints for the future. Which refers to the example I mentioned: personal communication with video has been more successfully adopted on laptops/computers compared to videophones and mobile phones. Why do I blog this? simply because critiques like Leberecht's are important as it allows to refine and precise my points. Will try to get back to my pen-and-paper thinking about come up with a deeper definition of "failure".

Avoiding interface confusion

User inscriptions to go beyond interface confusion.

User research data analysis

Two quick links that I still have to digest, think about, mix and adapt about user research and design by Steve Baty: First, Deconstructing Analysis Techniques: different sorts of analysis to apply to user research.

• "Deconstruction: breaking observations down into component pieces. This is the classical definition of analysis.
• Manipulation: re-sorting, rearranging and otherwise moving your research data, without fundamentally changing it. This is used both as a preparatory technique - i.e. as a precursor to some other activity - or as a means of exploring the data as an analytic tool in its own right.
• Transformation: Processing the data to arrive at some new representation of the observations. Unlike manipulation, transformation has the effect of changing the data.
• Summarization: collating similar observations together and treating them collectively. This is a standard technique in many quantitative analysis methods.
• Aggregation: closely related to summarization, this technique draws together data from multiple sources. Such collections typically represent a “higher-level” view made up from the underlying individual data sets. Aggregate data is used frequently in quantitative analysis.
• Generalization: taking specific data from our observations and creating general statements or rules.
• Abstraction: the process of stripping out the particulars - information that relates to a specific example - so that more general characteristics come to the fore.
• Synthesis: The process of drawing together concepts, ideas, objects and other qualitative data in new configurations, or to create something entirely new."

Second: Patterns in UX Research: different types of patterns one can find in user research that can be turned into actionable insights:

• "trends: a trend is the gradual, general progression of data up or down.
• repetitions: a repetition is a series of values that repeat themselves
• cycles: a cycle is a regularly recurring series of data.
• feedback systems: a feedback system is a cycle that gets progressively bigger or smaller because of some influence.
• clusters: a cluster is a concentration of data or objects in one small area.
• gaps: a gap is an area in which there is an absence of data.
• pathways: a pathway is a sequential pattern of data.
• exponential growth: in exponential growth, there is a rapidly increasing rate of growth.
• diminishing returns: when there are diminishing returns, there is a gradually decreasing rate of growth.
• long tails: the Long Tail is a pattern that rises steeply at the start, falls sharply, then levels off over a large range of low values."

Why do I blog this? material to rethink my methodologies. It's too rare to encounter hints, ideas, recommendations about the "analysis" part of user research.

Design/Futures/Design

It's been a while that "On Futures and Design" by Alex Soojung-Kim Pang was stuck in my RSS reader. Finally got some time to read it. In this article, Alex examines the role of design in futures research and how both field can be beneficial to each others. (Crafted piece of the future at LDM, EPFL in Lausanne)

In the first part of the paper, he shows how research techniques developed by designers (especially those about human/device interactions, i.e. user research) is of interest for technology forecasting. The main issue in forecasting is that people have the tendency to base forecasts exclusively on technology trends. This determinism makes futurists stating that "mobile technologies will turn us into postmodern nomads, wanderers as disconnected from place as we are wired into the electronic hive mind". This connects to what I described last week in my Lift talk about the fact that forecasting is framed into a certain mindset, a "zeitgeist" that only see certain aspects shaping the future (yesterday nuclear power, today the power of networks for instance). Alex's point is that "the relationship between technology-- especially information technology-- and people is considerably more complicated". And if one wants to highlights possibles futures path, it's important to "go below broad trends in order to understand how technologies and people interact". What does it mean more concretely? Simply that it's important to look at "how technologies are used, how they're integrated (or not) into products, and what prior concepts or mental models users bring to new devices or products". This is where designers come into play: their approach to deal with these issues is fundamental and can be transferred to futures researchers.

The second part of the paper deals with the contribution futures research can make to design. The authors takes the example of how "we can create devices that make the long-term consequences of day-to-day actions visible to users".

And finally, in the last section, Alex points out how "the ability to create devices that give users a feel for the future, for the cumulative long-term impact of small changes, and for the collective impact billions of such choices could have on the world, is the most important and exciting development for futurists since the invention of oracle bone". He shows that beyond white papers and dense powerpoint slides there is a need to change the way futures researchers work and communicate their thinking. Learning to talk about the future through things is a new and exciting direction. This does not mean that futurists should become designers, it's instead a call to renew the tools, methods and collaboration by benefiting from a neighboring field.

Why do I blog this? this short article features an exciting agenda for futures research. What is perhaps controversial in this pieces is the fact that futurists can learn from ethnography/user research. This is something new I agree with. There is therefore some methodologies to rethink about this issue, related with what Jason Tester defined in his blogpost called "the case for human-future interaction.

Besides, I would be interested in how designers can think and write about it, perhaps to exemplify how, as designers, they would expand on how futures research can benefit to them.

On a different note, I am still looking for papers and references about how futures research can be described as a specific form of "long-term design" (a topic that Bill Cockayne addressed in his Lift08 speech last year).

Clive Grinyer at Mobile Monday Zürich

Quick trip to Zürich yesterday for Mobile Monday where I was invited to participate as a workshop moderator. The keynote speaker was Clive Grinyer who recently moved to Cisco as a customer experience director (after a position at Orange/France Telecom). His presentation was called "I've never used that: adoption and accessibility in mobile technology" and it addressed the disconnect between technology, and what users actually want and need. Here are my quick notes:

"I hear a lot this "i've never used that" and I worry about it, especially after 5 years working at FT

mobility is everywhere, cheap, and cool how can we help clients using it? what i love about mobility is that customer who are driving usages when it works for them: voice, sms text... but people reject it when it's wrong: overselling of WAP as the mobile internet, low (3%) uptake of 3G video calling, slow uptake of mobile music, complex user interfaces, menus and terminology. 90% of users access only 10% of functionalities. Customers differ widely in their use of mobile, from teenagers, old users, etc.

after 5 years of mobile internet, 18% of US and european accessed the internet once a month after 1 month 98% of users did the same! they must have done something good! and now there's lots of internet phones, and normal people buy them (fully screen touch interface 3g and wifi enabled devices specifically designed for the internet) now we even have usable applications that make money, which is a first

iphones, clones change game this is purely because of usability and design

services finally work, since 2003, consumers have rated LBS a their favorite technology feature but usage was zero until nokia, google and apple make it work and a gathering of new tech is about to happen: NFC, new LBS

Grinyer's law: "it takes 5 years before a new mobile tech becomes usable enough that people will actually use it" it can work but it takes more time to be adopted

something's wrong, how to improve?

• open system makes it easier to make applications but not be integrated and designed around the user; co-creation tells you what people think they want but they not what they don't know they want!; wisdom of crowds is nice but what if great ideas remain inaccessible?
• we have to design our future: mobile experiences have to be better coordinated; we have to move to leaderships position and not jut experts; we have to make our colleagues aware they designing the experience with EVERY decision
• creating a vision of how things will be at the beginning (what about writing the user guide at the beginning?)
• find out what's really going on, what do people do? you know what is going on when you go to the toilet of life!
• make it simple, co-create with users and prototypes, close user-testing and this should be part of design, not a different unit
• understand the future: use probes such as whirlpool's washing machine (plants that grows in sort of washing machine) to try things, get feedbacks, have a dialogue with the future
• make it for everyone, people-centric
• put in love, even if you have usability. e-books generally have no love in them, they are horrible pieces of technology.
• hold your vision, management process where people give their opinions can lead to a total mess

Across all industries, usability unlocks adoption and finds great leaders (jonathan ive, bill buxton): we should not stay at usability departments, we need to make others know that it's just a nice to have"

Exploring failed futures at Lift09

At Lift09 the other day, I gave a modified version of my earlier talk about failed products/futures. I tried to take into account the remarks I received from various attendants of Design Engaged and came up with the following script: Smart fridges, flying cars and visiophones are common examples of innovations designed by technological companies and envisioned by science-fiction writers. Devices you always see in beautiful ads and that you never buy or you stop using almost immediately after acquiring them. You often see them in pulp novels from the 20s and glossy ads from the 60s. To some extent, they can be perceived as futures that refuse to arrive; some sorts of suspended endpoints that keep luring us again and again.

(Visual representation of my talk by Martin Kuipers)   Most of the time, they are not isolated examples: there is not just one model of intelligent fridge, nor one type of flying car. Failures are often repeated; they are recurring till the happy end where a convenient instantiation of the future can be found. This is what happened with visiophones. For forty years, plenty of phone boxes with videos and pictures have been designed and have always failed. Personal communication with pictures finally works out with desktop PCs and laptops using software such as Skype. The idea was correct, the instantiations were wrong as explained by Chris Heathcote in a blogpost commenting my talk at Design Engaged.   Personally, failed products fascinate me. My work is to carry out studies of how people use technologies to help designers refine their products. From this point of view, I cannot help being mesmerized by artifacts, which are not appropriated. Is it useful? I do think it is. First, failures often result in more detailed critiques than successes. The documentation of inadequate products offers a rich material to help learn from mistakes. Second, as the example above has shown, failures are simply good ideas that came before their time. As William Gibson, the science-fiction author, says “the future is already here. It's just not very evenly distributed". Spotting failures is therefore a good way to understand possible avenues for the future. Finally, understanding why something failed is a good input for design, perhaps even a “design strategy” where mistakes from the past are just seen as iterations towards a success.   What are the reasons for failed products? In general, there are three issues:

1. Innovation is not just technical: a technological breakthrough is not enough to design a product. A product must fulfill a need and fit with people’s habits. For example, it’s nice to have a fridge that can scan your food and display the time limit. However, you need RFID tags or barcodes on every food item to work this out. It’s tough to ask people to tag their own food for so little benefit. A good understanding of future users is important and often missing. It simply means that a product should not be designed for the “average human” but for a target with specific needs and behavior.
2. The big picture is often ignored: the technology is fine but the world is not ready to accept it. Think about flying cars, even if technology was ready, it would be tremendously difficult to have new regulations and signposts adapted to 3D navigation!
3. The way we perceive change is flawed: we often think change is linear and that the future will be based on the past. But it is not the case, big changes occur: the arrival of digital cameras was quite a surprise for companies such as Kodak. Moreover, we tend to over-estimate the speed of short-term adoption and under-estimate the dissemination of technology as pointed out by futurist Roy Amara.

Traffic light in staircases

Lift09 is over and I only have enough energy to post this intriguing light sign we encountered when visiting the cathedral in Geneva. It's supposed to indicate to visitors when they can go down the stairs (to avoid traffic congestion in the narrow staircases). An interesting example of signage.

Design flop reasons

Cris sent me this highly interesting paper that is spot on my Lift presentation: Why the overwhelming numbers of design flops? by Alice Rawsthorn. The article tries to list the reasons why design goes wrong and misses the point (besides reasons such as budget issues, deadline pressure and lack of talent). The list consists in:

1. "Designing for other designers (...) ignoring entire consumer categories
2. Change for change's sake
3. They made us do it (...) one reason why cellphones are so infuriatingly difficult to use. The market is dominated by the cellular networks, which are understandably anxious to ensure that new phones are compatible with their technology. Unless the manufacturer complies, they refuse to sell the phone.
4. Innovation for innovation's sake: why invent a new version of something that doesn't need to be improved?
5. As long as it's green: sustainability is often used to excuse other deficiencies in desig
6. Design by committee: The more ambitious - and expensive - the project, the more vulnerable its orchestrators seem to feel. That's why such projects end up being subjected to so many people's opinions, that they become as bland as a Hollywood blockbuster with a plot determined by repeated test screenings.
7. Up, up and away: As corporate life expectancy shortens, ambitious executives have so little time to make their mark in particular roles that they meddle unnecessarily.
8. But it worked for them/me-tooism, or copy the competition"

Why do I blog this? This is great material as it uncovers an interesting typology of failures with some underlying reasons.

Clive Grinyer on customer experience design

In this insightful blogpost Clive Grinyer, formerly designer a Orange, now at CISCO, reflects on his experience of customer experience design in the mobile industry. Some excerpts I enjoyed:

"In the conventional industrial product development process at that time, my design specification was handed to a mechanical engineer, with specialisms in a greater level of detail of material and process. It was a shock to then realise that the design was treated as merely a guide, where the engineer would take hold of the reigns and steer the object in whatever route made the production easier and more robust. (...) It is only in exceptional circumstances, such as at Apple, where their leadership, investment and strategy embraces those values, that you see the full impact. (...) In the mobile world I saw this repeated through a culture dominated by technology and decisions and assumptions made at every level that impacted badly on the end experience of the user. The situation was worse, in that I was not in the right order of process and "design" had already happened by the time I or my team had anything to do with it. This leads to technology developed without any thought of how it would be used, or 3rd party application providers incapable of customising or improving usability. (...) For the last months I have also struggled to understand what to say about the mobile. It seems so exciting that millions of people can be walking round with so much technology in their pocket but find so little use for it apart from speaking and texting. Open platforms, the promise of Android, ever more capable devices failed to unlock my cynicism in the ability of the mobile to deliver useful applications to normal people. And then the iPhone 3G did it."

His conclusion about "what to do" is basic: Talk about people (look at what people do), Discover the customer journey, Tell stories of how it could be, which are relevant aims in technological companies, and as he points out generally a surprise ("Hardly rocket science but revealing to most people still").

Why do I blog this?some good hints here to be re-used in my user experience course. The "talk about people" is a familiar trope to me. I often face the same situation, delivering a speech to technology people in a certain company (e.g. video-game industry, mobile software organization, design students) and I see the fascination towards the material I show them. Most of the time, documenting people's life is of great value to them as they smile and see how things work (or don't work) in a concrete way. However, it's then important to show them how this is valuable for the time being, for what they're achieving. Which is why what Grinyer describes about telling "stories of how it could be" is important. Perhaps I would add as a preliminary step "showing problem, issues, pain points and dreams", as a sort of material to inspire design.

Clothe pegs hack

Along with duct tape, clothe pegs are perhaps one the most intriguing tool to modify the purpose of things in order to meet new objectives. The example above, encountered this afternoon in a french bathroom shows a striking example of a thoughtless act: how wooden clips can keep a tube of toothpaste properly squeezed.

Why do I blog this? documenting thoughtless acts is always a pleasure at Pasta and Vinegar.

Bluetooth in your life?

Overemphasis on technology? Seen last week in Geneva.

Pervasive computing to the maximum.

About space and 'plek'

The distinction between "space" and "place" is commonly discussed in recent academic work in ubiquitous computing/HCI by researchers such as Paul Dourish. In a seminal paper form 1996, Harrison and Dourish express that "space is the opportunity; place is the understood reality." They raised the social construction of space by exploring how human actions are structured by the spatial organization of our environment. Unfortunately, as Dourish pointed out in his 2006 paper, this discussion lead to a misunderstanding: some people tended to exaggerate the distinction between spatial and social components. Interestingly enough, reading Assia Kraan's paper "To Act in Public through Geo-Annotation shared location", I ran across this interesting paragraph:

" It is important to make a distinction between space and plek. Anglo-Saxon theoreticians talk about space and place. The Dutch word plek (plural plekken) will be used here because the alternative ‘place’ does not express its meaning adequately. ‘Place’ is used, for instance, to refer to the physical space of a settlement, while plek refers to the meaning that a physical space has for somebody. A plek can be described as a complex ensemble of physical characteristics, cultural experiences, history and personal logic. Geographers target the navigational characteristics of plekken, but the computer scientists Paul Dourish and Steve Harrison emphasize an aesthetic quality. They recognize the function of plekken in a creative appropriation of the world and describe plekken as ‘developed sets of behaviour, rooted in our capacity to creatively appropriate aspects of the world, to organize them, and to use them for our own purposes’"

Why do I blog this? ruminating about different words and their cultural meaning is relevant here as it can express underlying dimensions.

Subway poetry

A short poem written on a post-it stuck in the subway in Paris. A basic form of location-based annotation.