My favorite book on science…
“It is a natural human impulse to think of evolution as a long chain of improvements, of a never-ending advance towards largeness and complexity - in a word, towards us. We flatter ourselves.”
My favorite book on science…
“It is a natural human impulse to think of evolution as a long chain of improvements, of a never-ending advance towards largeness and complexity - in a word, towards us. We flatter ourselves.”
Interesting article from business week on the importance of analytics. The article discusses the growing demand for data analysts as the amount and availability of data increases and decision-making becomes more performance-based.
They don’t mention the other benefits, which are that user experience researchers and designers working in an agile environment can conduct more focused, speedy, and motivated work when they have data to base their early decisions on. In addition, relying on management intuition is often difficult. Regardless of whether decisions are right or wrong, different people will always have different opinions. The presence of data backing up each decision made is much more likely to bring everyone into the same focus, and avoid in-fighting or subversion.
It’s been a while since I posted here, but what better time to start posting again than the new year. I have a good feeling about 2010…
One of the biggest challenges in my work as a researcher right now is communication of findings to the rest of the organization, so I was happy to find the beautifully presented content on this Service Design Tools site.
Happy New Year!
“I don’t know what I want but I know how to get it”
- Sex Pistols
Jeff Patton uses this quote to describe a common occurance in agile teams - teams focus on defining what they want to build and then creating it incrementally using agile methods. The weakness of this approach is the inherent inability of such teams to cope with inevitable change or new knowledge. During the interview Jeff offers three strategies for product owners that can help agile teams focus on creating the right software, in addition to creating software in the right way…
Strategy 1: Focus on goals or outcomes rather than software solutions. For example, instead of saying “we want to create these features by this time,” focus on a single goal “we want to increase our market share by diversifying our product offering.” Agile is not about defining what you want to build and building it a chunk at a time. Instead, it is about being clear about the outcome you want to achieve, and constantly adjusting your actions to best reach that outcome given the current circumstances.
Strategy 2: Delay decisions as long as possible. Defer decisions about what to do and exactly how to build it to the last minute possible. Define the specific solution late, when you know more about the problem, constraints and economics. The result will be the most suitable and economically advantageous solution.
Strategy 3: Build up quality. Focus on creating the simplest thing possible. Build up necessities first, then add sophistication later. This may mean that a feature is is not complete the first time around. Early development efforts may build an example of a solution that simply allows you to discover if this feature will help you solve your business problem.
The consequence of following these strategies is that you must give up the myth of being able to accurately estimate or predict what you want, what you will do, and when you will do it by. Looking critically at these strategies, they are all pretty difficult to do in most organizational environments. But hey, who ever said that software development was easy :-).
Jeff also has some interesting insight into user experience, the role of user experience in agile development (part of the product owner team), and the skills needed to fill the user experience role.
Watch it!
Short and sweet. Kimberly Krause Berg writes a refreshing and to-the-point article on how to improve site usability and conversion rates.
An example of what I would love to see happen over the internet. Except…instead of clips being pulled together by a single person, many individuals can work together to collaborate, create, and riff on each other to pull together music and stories as variations on a theme.
John Pettengill explores possibilities of the mobile web. The mobile web should be more than a watered down version of the internet. Instead, it should take advantage of context and appreciate the different states that users are in as they are out and about in the world (vs. sitting at their computer).
In his closing plenary to the IA Summit 2009, Jesse James Garrett stepped out on a limb and suggested the use of the umbrella term ‘User experience designer’ rather than the outwardly confusing terms ‘Information architect’ or ‘Interaction designer.’ See also: the UX tribe, It’s just UX - petition in support of UxD.
Garrett also has some interesting things to say about the state of our profession…
“Name the five best-known information architects. Now: name a work of information architecture created by one of these people. Is that a sign of a mature profession? “
…and on our role in society…
“We must acknowledge that as user experience designers we have a broader place in the world than simply delivering value to businesses. We must embrace our role as a cultural force. “
Recommended reading for any infomration architect, ux designer/analyst/research, interaction designer, usability specialist, …
When I think of the women in technology who have inspired me, the people that come to mind are the practitioners and thought leaders in the field of agile user experience: Angela Martin, Marilyn Mantei-Tremaine, Leah Buley, Kate Rutter, Helen Sharp, Lyn Miller… While I do not talk to these women on a regular basis (or at all, in some cases) they are women that inspire me to develop my own practice and push forward in my field.