Your constantly-updated definition of Contexts of Use and
collection of videos and articles
507shares
What are Contexts of Use?
One of the key focal points of user-centered design is the context in which the designs will be used. For technology products and services, contexts of use include a potentially broad array of factors—physical and social environments, human abilities and disabilities, cultural issues and similar.
ShowHide
video transcript
Transcript loading…
Contexts describe the actual circumstances of use. While not all of the aspects mentioned above apply in each case, it is important to consider what is and isn’t relevant. For example, almost all products and services operate within a legal context that requires them to be operable by people with disabilities. Other legal contexts govern the use of personal data – the GDPR in Europe, for instance—the ages for which certain content may be shown, along with strict laws in some locations around gambling and betting.
Environmental and physical contexts may not be particularly relevant to most websites, but this can change dramatically for systems used outside the typical home or office. Examples include external Automated Teller Machines (“cash machines” or “cash dispensers”), computing systems used in farming—some of which must be steam cleaned—and systems used for stock control in unheated warehouses or, more challenging still, cold stores.
How to Define Contexts of Use
User research and observation is essential to determine context of use. The goal of these processes, which include contextual interviews, user visits, etc., is to answer key questions such as the ones suggested by the leading UX consultancy Experience Dynamics:
Where do your users engage with your product or service? (physically, environmentally, device-specific)
What is happening to the user when they are using it? (social or emotional influences)
What is physically or socially preventing users from completing their tasks? (e.g., another party or person has to act first)
When does usage happen and what triggers it? (timing and coordination)
What expectations do users bring to the task? (mental model)
Why do users want to do this before that? (workflow, motivation, flow)
What makes sense to users and why does that differ from how you think about it? (content, labeling, problem-solving)
Contexts of Use in HCI
In user-centered and user experience design, one of our main concerns is usability. The international standard on the ergonomics of human-system interaction (see Learn More About Contexts of Use) defines usability as
“…the extent to which a system, product or service can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use.”
Notice that the very definition of usability depends on the context of use. This isn’t hard to understand outside of software systems. However, contexts are usually overlooked because contexts of use are outside of the normal considerations in most software development methods.
The standard goes on to describe the components:
“The context of use comprises a combination of users, goals, tasks, resources, and the technical, physical and social, cultural and organizational environments in which a system, product or service is used.”
This is a much broader definition of contexts than is used in practice, but it is complete. Less formal definitions tend to group users, goals, tasks and resources separately from the environments as described above. However, the benefit of grouping all of these elements together becomes obvious when considering how the standard describes achieving usability in design and development. The steps are:
1. Understand and specify the context of use.
2. Specify the user requirements, including usability considerations.
3. Produce design solutions making use of the above.
4. Evaluate the design solutions.
When referring to a complete system, the context of use would include all users along with their respective goals, tasks and the required resources as well as the environmental contexts across all of those factors. These include
Technical environment: Equipment and applications, including hardware, furniture; information (data the users have access to) relevant to the tasks; support services, either human- or system-based (such as assistive technology).
Physical environment: Where the system will be used and what the environmental factors would be (consider the warehouse, farm or cold storage examples earlier).
Social, cultural and organizational environment: Other people involved (such as stakeholders) and the relationships between them, the organizational structure, language, legislation, cultural norms and values, work practices, group working and privacy.
Contexts of Use in Mobile
The context of mobile use is very different from that of desktops. It will require a different approach, such as context awareness, mobile-first or task-oriented design. In this video, Frank Spillers, the founder of Experience Dynamics, shares practical tips on how to understand the context of use in mobile User Experience (UX) design.
ShowHide
video transcript
Transcript loading…
Researchers Savio and Braiterman introduced the “overlapping spheres of context” to a mobile user’s context that included:
Attention levels (complete or partial, intermittent or continuous).
Tasks (for example, make calls, send a video, or get directions).
Device constraints (including, among other things, software, sensors, battery and network).
Secondary activities (such as walking, eating, etc.).
Environment (sound, light, space, etc.).
Culture (economics, religion, law, etc.).
Mobile experiences that factor in the context of use will be more likely to be successful than designs that are made for a generic audience with a one-size-fits-all approach.
Learn More About Contexts of Use
Find here a research study into contexts of use and user experience.
Detailed article on the role of contexts of use in usability (PDF).
Interactions between products/designs/services on one side and humans on the other should be as intuitive as conversations between two humans—and yet many products and services fail to achieve this. So, what do you need to know so as to create an intuitive user experience? Human psychology? Human-centered design? Specialized design processes? The answer is, of course, all of the above, and this course will cover them all.
Human-Computer Interaction (HCI) will give you the skills to properly understand, and design, the relationship between the “humans”, on one side, and the “computers” (websites, apps, products, services, etc.), on the other side. With these skills, you will be able to build products that work more efficiently and therefore sell better. In fact, the Bureau of Labor Statistics predicts the IT and Design-related occupations will grow by 12% from 2014–2024, faster than the average for all occupations. This goes to show the immense demand in the market for professionals equipped with the right design skills.
Whether you are a newcomer to the subject of HCI or a professional, by the end of the course you will have learned how to implement user-centered design for the best possible results.
In the “Build Your Portfolio: Interaction Design Project”, you’ll find a series of practical exercises that will give you first-hand experience of the methods we’ll cover. If you want to complete these optional exercises, you’ll create a series of case studies for your portfolio which you can show your future employer or freelance customers.
This in-depth, video-based course is created with the amazing Alan Dix, the co-author of the internationally best-selling textbook Human-Computer Interaction and a superstar in the field of Human-Computer Interaction. Alan is currently professor and Director of the Computational Foundry at Swansea University.
A tablet computer switching the orientation of the screen, maps orienting themselves with the user’s current orientation
Book chapter
Open Access—Link to us!
We believe in Open Access and the democratization of knowledge. Unfortunately, world-class educational materials such as this page are normally hidden behind paywalls or in expensive textbooks.