L2 Flashcards
What does problem space mean and why is it important?
Problem space involves understanding the overall purpose and users’ needs before starting to develop the details.
Starting with technical details (“nuts and bolts”) can lead to overlooking usability and experience goals, resulting in a product that does not address the identified needs.
A team working together to analyze the problem space can avoid incorrect assumptions and better identify user goals. By making underlying assumptions and claims explicit, one can ensure the solution addresses the real problems.
Example:
A software company discovered that many users had switched to another browser. Assumptions included that their browser had deficiencies and that competitors’ products were better. After observing and talking to users, they realized the bookmarking feature was not used because it was time-consuming and cumbersome. They decided to investigate how to improve the saving and retrieval of web pages. This led to the development of simpler functions that better met the users’ needs
What is an assumption?
Taking something for granted when it needs further investigation
Example:
People want to watch TV while driving
What is a claim?
Stating something to be true when it is still open to question (a multimodal style of interaction for controlling GPS - one that involves speaking while driving - is safe)
From problem to design space (3 steps)
Problem space —> Conceptual space —> Design space
What is a conceptual model?
It is not a description of the user interface but a structural outline of the core concepts of the design and the relationships between them
It is an abstract model
Why a conceptual model?
Helps the design to:
Not become narrowly focused early on
Establish a set of common terms they all understand and agree upon
Reduce the chance of misunderstandings
Provides undisputed guidance
What does conceptual model describe?
Metaphors and analogies
The concepts that users are exposed to through the product
The relationships between the concepts
The mapping between the concepts and the user experience the product is designed to support
First steps in formulating a conceptual model?
What will the users be doing when carrying out there tasks?
How will the system support these?
What kind of interface metaphor, if any, will be appropriate?
What kinds is interaction types to use?
Metaphors
The transference of the relation between one set of objects to another set for the purpose is brief explanation
Metaphora = to carry over, transfer
Interface metaphors
Conceptualising what we are doing, ex surfing the web
Metaphor - key points
Help borrow behaviours from systems familiar to users
- makes learning new systems easier
- helps users understand the underlying conceptual model
Isn’t always necessary
Interaction types
Instructing
Issuing commands using keyboard and function keys and selecting options via menus, ex vending machines
Conversing
Interacting with the system as if having a conversation, ex Siri, IKEA bot
Manipulating
Interacting with objects in a virtual or physical sis d by manipulating them, ex using drag and stop, physical controllers
Exploring
Moving through a digital, information space, or a physical space, ex in a game Minecraft or descending folders
Responding
The system is taking the initiative to alert or show the user something that it “thinks” is of interest or relevance to the context the user presently in, ex fitness tracker
