On February 5th, Hong Kong had the chance of having Martin Fowler speak about Agile Methodology. I have to admit that I was actually dragged to the talk by my developer colleagues… I did not really feel like going to a very technical presentation where I would be totally lost. I was really wrong not to want to go. After I actually understood that XP did not mean Windows XP, but eXtreme Programming (he he… embarrassed smile) I really enjoyed the talk.

There are two main points that made me think about how Agile methodology could have an impact on my work: user experience / user research.

1. How can we make research more agile?

The Agile concept is to break down every project in small fully functional modules that can be delivered in a very short period of time (could be 2 weeks for a development project). This helps focusing on the core features of the project, while leaving the rest for later. This also helps starting the design even without knowing all the business requirements and actually supports better defining business requirements along the way as the client sees the system build itself from scratch.

In this post, I will just focus on the research part of user experience. Indeed, the interaction design part can be incorporated quite easily in an Agile methodology, but the preliminary research appears more tricky to me. Indeed, when we start a project we first want to know what the customers or users want. We have an array of tools to address this from quantitative ones like surveys to qualitative ones like usability testing or ethnographic research. Studies like this can actually last for quite a long time and from the client’s point of view it is hard to visualize what they will get out of it. What if we could break down any research into small items that would last maybe under a week and deliver clear conclusions at the end of each week. Being new to Agile stuff, I still need to think about that some more… the first problem I see is how to perform a relevant study (in terms of sample size for example) in such a short time… But with this in mind, making research more iterative helps design a better research in the end by fine-tuning the study objectives bit-by-bit.

2. Should I work towards not having a job?

From Martin’s point of view and following Agile concepts, the developer and the client should be in direct contact. This makes the role of the Business Analyst on such projects redundant. Of course he mentioned that on most projects Business Analyst are actually key in creating a bond between the different parties, but that made me think… Are researchers like business analysts?… In an ideal case, if my client (I mean, the operational teams) could talk directly to his or her customers, everything should be better. What if instead of designing punctual studies, researchers should all strive to design systems that allow their clients to stay in touch with their customers on a continuous basis, making our role as researchers redundant.

That’s pretty much the concept of customer experience. Stay in touch with your customers on a continuous basis so that you can better design your products and services depending on their changing needs. Still maybe more could be done to integrate advanced qualitative methods into the operations of a company. We see more and more ethnographic research within companies… but my feeling is that more is possible.

Just some unfinished thoughts…