There are lots ways to elicit UCD requirements so I don’t intend on listing them all here, what I will note are some of the effective ways that I utilise. They can be described as structured, unstructured or a mixture of the two, but importantly the methods produce differing depth of requirements dependant not only on the method but on the skill of the facilitator and the characteristics of physical location used. In effect the method used is limited by the capability of the facilitator.
People focused Requirements Capturing requirements is subject to other peoples availability, this remains one of the most painful parts of the process as few participants seem to understand just how important their experience is to the project. Often a participant can shape the final output without realising they have done so, I include a Show
United States of America The American National Standard Institute (NSSN, http://www.nssn.org ) provides a national resource for national and international standards. ANSI/HFES-200 is focused on design requirements and recommendations to increase effective usability of software interfaces. Human Factors and Ergonomics Society (HFES) – http://www.hfes.org American National Standards Institute (ANSI) – http://web.ansi.org International International Standards Organisation
International projects should be constructed in consideration of the most stringent standards this is expected to be those pertaining to the USA, but also to include ISO9241 guidelines; Australia Australian Human Rights and Equal Opportunities Commission – http://www.hreoc.gov.au/ The Act provides key legal standards which inform their Disability Discrimination Act 1992 (http://www.austlii.edu.au/au/legis/cth/consol_act/dda1992264). Their disability standards
I have worked with a number of banks and financial services companies mainly in user experience and team management, I have also been involved in the development of new business models. I keep being asked to provide structure information for various clients so feel it simpler to make the enclosed structural diagram available here as
It is an understood factor in travel that if the journey starts even half a degree wrong then the final destination will be considerably different from where the person intended to be, this is for many why there is a make do culture when working with technology requirements. Unfortunately bad requirements gathering can seriously derail a project before it really begins.
User centered design (UCD) is a project approach that puts the intended users (audience) of a product or piece of technology at the centre of its research, design and development. It does this by talking directly to the user at key points in the project to make sure the product or piece of technology will
The following is the first page of a Web Governance document I created and have used with a number of institutions, it’s here to layout one way to tackle this really complex type of project. 1.0 Introduction 1.1 …Background This document is intended to support the decision making process to re-establish xxxxxxxxx Web Presence
Security and trust are vital principals in building interpersonal and business relationships. These same principles should be employed to both directly and indirectly communicate with users. The following post shows how the construction of password reset challenge questions tell a narrative story of capability and intention as much as supporting text and brand values of the system and service that is secured by them.
Getting into user experience, what you need to know? What will a person need to be able to do to get into user experience; 1. Can you think? Not the most subtle way to ask, but can you be creative? Thinking at the beginning of a project can save a huge amount of money and time
While any kind of user testing is better than none, usability testing out of context is like testing a car on water, it gives some basic information and not a lot more. If performance and use are important at all, then testing should take place in an environment standard to the expected users.
The following is a paper I wrote in 2005. From WWW/Internet 2005 Proceedings Converting browsers to buyers: exploring what drives consumer choice in internet e-commerce Why do internet users behave as they do, are their activities solely determined by website design? Or do they create their own pathways as a response to designated systems. For many, internet
There seems to be a huge level of confusion around user experience (UX) but one of the key things is that user interface UI is not the user experience UX Simple digital systems are constructed with several interlinked components; User Interface – what the user sees Interface Logic – what the user can do Logical
Philosophy of UX User experience is about making people’s lives better not just changed A persons experience is based in their mind and their emotions and can be established by both actual interaction and reflective (biographical experience) inputs. In UX we define inputs in digital or real world frameworks which enable the creation of solutions