Setting the scene for user experience to work
I have over the last few months had several rants about people claiming to be involved in user experience who are not regardless of their job titles.
I came across a great blog post by Whitney Hess (I don’t want to steal her traffic so here is just a link) about what shows your not a user experience person, but I though maybe I should point to what does show your are one to get some balance here.
Training clients what to expect
Does your client know what they want, this sounds obvious, but user experience is unlike a purely functional activity (asking developers to make sign in work), most clients just want better, but don’t know how to quantify better. This is not the time to set KPI’s except in the broadest terms, but clients do need to know where they ARE in a quantifiable way, ‘things are bad now and we want better‘ is not a good starting point.
What things, set against what standards or targets based upon what business or research rules (who wrote them and why) are BAD and what level of better is better, just to get a transaction, getting a reuse or becoming friend for life type of BETTER?
If you don’t set your clients expectations in a realistic manner they will come up with unrealistic expectations that you will never be able to meet. But to do that you’ll need a starting point, mid point and end point, that uses your clients own language and the only way to establish these things is through research.
Does your client understand that user experience involves thinking as well as making things?
User experience is not a headless chicken activity, involving lots of running around, thousands of meetings about meetings, it requires complex thought and strategy. I like many other user experience people find going for a walk while thinking about the complex interactive and logic of use in the initial part of a project very useful, either that or people can watch my head explode.
User experience is not a production exercise;
- User experience leads
- User experience finds out
- User experience tests
- User experience communicates
so trying to cost plan it or manage it in the same way as development does not work very well.
Does your client understand that there is a set of formal methods that will make the user experience work?
For some reason everyone focuses on wireframes. Wireframes are of the least importance in user experience and are the culmination (after a lot of versions) of the user experience research. Wireframes are low quality pictures for the most part (or should be, prototypes are something else) and should be as sketchy as possible to allow stakeholders to focus on signing off the interactions rather than focusing on pixel level graphics and colour.
I have previously mentioned about the avoidance of research by clients on the bases that they cannot see its value in the final deliverable. This stems from clients being misinformed by business journals (I have read some great howlers by highly reputable journals) and sales people not understanding that the user experience research is the deliverable and that wireframes or functional specifications are the communication tool.
- Getting into User Experience Part 2
- Getting UX done the engagement process
- User Experience as a process
2338total visits,2visits today
Karl Smith, Experience Consultant by Karl Smith is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Based on a work at http://karlsmith.info/.