Courage, C. and Baxter, K. (2005): Understanding Your Users: A Practical Guide to User Requirements. London: Morgan Kaufmann Publishers.
Synopsis
The focus of this book is on the ‘user requirements gathering’ stage of product development, in terms of data collection techniques and data analysis.
The authors define requirements as the “…features./attributes the product should have or how it should perform.” Requirements for a variety of sources including the user (i.e. stakeholders) should be taken into account (e.g. marketing, purchase-decision makers, product development)
User Requirements Definition
- “…the features/attributes your product should have or how it should perform from the users’ perspective” (p3)
User-Centred Design (UCD) Description
- Definition – “…product development approach that focuses on the end users of a product” (p3)
“…the product should suit the user, rather than making the user suit the product” (p3) - Principals of UCD (Gould and Lewis 1985) – Note date and how they are still being considered today
- Early focus on users and tasks:
- Structured and systematic collection of data relating to user requirements.
· “To maximise the usability of a product, the user should be involved from the product’s conception” (p4)
· “The earlier the user is involved, the less repair work needs to be done at the final stages of the lifecycle” (p4) – In other words after a usability test.
· “By collecting user requirements, you can gain an understanding of such things as what your users really want and need, how they currently work or how they would like to work, and their mental models or mental representations of their domain. This information is invaluable when creating a superior product” (p4) - Empirical measurement of product usage
· A measurement on product usage based on experience rather than theory.
· Usually involves testing of a prototype or final product on the user by asking them to perform a number of tasks and by identifying the issues that arise. - Iterative Design
· In other words the repeated design, testing and modification of requirements.
· “…you continue to iterate and fine-tune with each cycle until you get it right” (p5)
· “No one gets all the information the first time, no matter how expertly you execute each usability activity” (p5)
Variety of Requirement
- “…many product teams now realise the importance of understanding their users and the consequences that result when users are unable to utilize products with maximum case” (p8)
- However, many companies only perform a usability test as opposed to user requirements.
- “There is a clear difference between usability testing and user requirements gathering. Usability testing determines whether a given solution is usable. Requirements gathering provides insight into the many possible solutions and allows a person to select and investigate the best solution from the users’ perspective. The difference between a good designer and the outstanding designer is the latter’s vision of solutions. Without requirements gathering, your vision is seriously limited” (p9)
- Usability testing is still very important but it only plays a part
Importance of Getting the Correct Information Concerning User requirements
- “…before and the product is sold, you want to make sure that end users can actually use it and that it contains the features they need” (p13)
- “…you may think you understand what the end users want and need because other sources have told you on their behalf. This is the number one mistake that product teams make” (p13)
- USEFUL DIAGRAM OF MISCOMMUNICATION OF PRODUCT RESEARCH / USER REQUIREMENTS ON PAGE 14
- “…you must talk to the actual users, the people who will use the product at the end of the day, to gain an understanding of their perspective and needs” (p14)
Benefits of Correct User Requirement Information
- Customer satisfaction and increased ease of use = increased sales and market share
- Decreased training and support calls that often occur as a result of a mismatch in the users’ mental model (conceptual model)
- Decreased development time and cost as the product only contains the “necessary functionality” (p14)
Learn About Your Product
- "It is key for you to ascertain as much as possible about the existing product in terms of its functionality, competitors, customers etc. In addition, you need to assess what is currently understood about the users and begin to create user profiles" (p29)
- "Before you even begin working with a single user, you need to understand the domain you are working in" (p29)
- It is important know your product intrinsically - functions (available or planned), competitors, issues, perceived users etc.
- "...the best way to learn about a product is to use it" (p31)
- Networking - Find out from people in your domain
- Log files - Web server log files can be very useful in finding out about usability data. They indicate such aspects as files requested, times and dates of requests, content type and length, error messages, users browser etc. However, you would need a specific programme to be able to do this.
- Surrogate products - These are products which may not directly compete within your market segment but have similar features. Analysing these types of product can also provide very useful.
Competitors
- "A competitive analysis can be an effective way to gain an advantage over your competitors" (p37)
- "It is beneficial to conduct a competitive analysis when you are creating an entirely new product or simply entering a new product domain" (p37)
- This can also be useful if you are struggling with your product but your competitors are thriving. That way you can analyse what it is that is making them succeed.
Learn About Your Users
- "If you do not understand who your users (or potential users) are, your product is doomed to fail" (p41)
- "The single most critical activity to developing a quality product is understanding who your users are and what they need" (p41)
- This can be done by developing a user profile (a detailed description of user attributes - e.g. experience, level of education, age etc.) personas (examples of your end user) and scenarios (a day-in-the-life of your end user). SEE TABLES ON PAGE 42 FOR A COMPARISON OF THESE THREE ASPECTS.
User Profile
- Understanding this characteristics of your users help you create a better picture of who you are building your product for. Possible areas to consider are:-
1. Demographic Characteristics – age, gender, location, socio-economic status
2. Occupation Experience – current job, length of experience, responsibilities, previous employment
3. Computer Experience – skill set, skill level, experience
4. Education – degree, subject area etc.
5. Tasks – primary and secondary.
6. Domain Knowledge – user’s level of understanding of product area.
7. Technology Available – hardware, software, other tools.
8. Attitudes and Values – product preferences, fear of technology etc.
9. Learning Style – visual learner, audio learner etc.
10. Criticality of Errors – possible consequences of user error. - Once this information has been established you can then group each attribute into the following categories:
1. Age (child, young adult, adult or older)
2. Experience (noive, expert)
3. Attitudes (first adopters or technophobes)
4. Primary Tasks (e.g. buyer, seller)
This will be incredibly useful to include in the assignment section on how to establish your users.
Scenarios
- "Scenarios help you test your system and to build functionality into your product that users will actually want to use" (p41)
Personas
- A fictitious method for establishing a 'typical' user of your product
- "Personas are designed to help keep specific users in focus during design discussions" (p41)
- There are a number of benefits for using personas when attempting to understand your users:
1. "...personas give your users life and help team members feel connected to them" (p48)
2. "Trying to build a porject for a generic "user" is like trying to hit a moving target. Without a specific target to focus on "the user" can change from the expert to the noive to your grandmother all in the midst of a single conversation" (p49) - There are also a number of things to be aware of when using personas:
1. Numbers are an important aspect to consider. Too many examples of personas and you may end up being to vague and non-specific. At the same time, "By limiting your vision to one persona, you may end up filtering out valuable data from end users who do not match that one profile" (p49)
2. "Personas should never replace conducting usability activities with your end users. Personas should be based on the data from usability activities" (p50) - Creating personas can be done by including the following informaiton:-
1. Identity - first name/sirname, demographic information (age, gender etc.)
2. Status - primary, secondary user?
3. Goals - user's goals
4. Skill set - background, education level, expertise, training, specialist skills (does not have to relate to product)
No comments:
Post a Comment