I can't take credit for this tip. Robert Hoekman (rhjr.net) inspired me to really think about whether or not we are gaining truly valuable information by spending days, weeks, months studying "real users". Thinking about attempts at studying users I have done before made me realize that, most of the time, the assumptions we made without users were largely correct. And while it is valuable to have your assumptions validated, it isn't always necessary before starting development. Notice that I say "most" of the time. Well, the reality is, get ready... we don't always get it right, even when we do extensive user testing.
Why? Well when you are testing users, regardless of how "real world" you try to make it, the user always knows that they are being tested. Many people are self-conscious having someone (or two people usually) looking over their shoulder. There are many other reasons as well.
Now before all the UCD practicioners stand up and start disagreeing with me, let me make one last point that is important. In order for this approach to work you have to make realistic assumptions in which you are highly confident. So how do you make confident assumptions? That is part of Tip #2. Stay tuned.
If ignoring your users sounds like an approach you are interested in, check out http://rhjr.net/theblog/2007/06/06/why-we-should-ignore-users-the-podcast/
Monday, June 25, 2007
Saturday, June 23, 2007
On "Rich Internet Applications (RIAs)"
I should have clarified in my initial post that my main focus is in the design/development of RIAs. So most of what I will be talking about will be focusing on apps based on Flex, AIR, Silverlight or AJAX. This isn’t to say that traditional desktop apps won’t be discussed. They just aren’t my focus.
Also, since I have had the opportunity to build apps in both AJAX and Flex, I will share my thoughts on my experiences.
Thursday, June 21, 2007
Hi
As a professional User Interface Designer working on an Agile development, I have had the opportunity to learn a lot about how to create software that is easy and obvious to use without a lot of up front work. In speaking with my peers, I have also found that many designers are trying to fight the mismatch between a User Centered Design approach (big up front design phase) and Agile (barely any up front design). This blog is intended to share what I have learned and hopefully learn some lessons from all of you.
More to come.
More to come.
Subscribe to:
Posts (Atom)