In a nutshell I think that the User Experience requirements gathering process is a very valuable and necessary process. However it is often a challenge in educating the client on this value and in some ways seems to annoy the client to the point where they say "Alright Already.... just show me a semi working site and I will tell you what I like and don't like. Heck I could almost do this on my own on my Myspace account!"
As an Interactive Producer / Project Manager here are a few of my questions when it comes to delivering value to my clients in driving a project through the User Experience phase.
What is the perceived value and benefit of User eXperience (UX) analysis relative to the size/cost of a project and the size/market cap of the companies involved with the project?
At what point is documentation crossing over a point at which the cost of producing it is more that its return on investment to the client or the perceived success of the project?
When are too many requirements documents too much?
What is the minimum amount of UX documentation needed to complete a project most effectively?
What is the most agile way of developing UX documentation?
When is live prototyping worth the most with the least abount of risk?
Perceived Value of UX questions and requirements documentation.
By bkenyon - Posted on January 3rd, 2008