Please enable JavaScript.
Coggle requires JavaScript to display documents.
Intentional Prototyping (What are prototypes (Anticipate challenge, Engage…
Intentional Prototyping
-
-
-
Rapid prototyping
-
-
-
-
Do
Work collaboratively with users, business and IT stakeholders while rapid prototyping.
Avoid “prototype creep” by setting expectations for the process, including ones affecting the purpose, fidelity, scope and duration.
When creating interactive high-fidelity prototypes and simulations, build in realistic delays , so that users do not expect instant response times from the final product.
For computer-based prototyping, saving reusable templates, stencils, patterns and widgets for future projects.
Begin every prototype review session with the disclaimer that this is just a prototype, a mock-up, not the actual solution.
Don‘t
Don’t prototype features or functionality that cannot be implemented—often an issue with software package implementations.
-
-
-
-
Sensemaking
-
Sensemaking is a social activity in that plausible stories are preserved, retained or shared
-
Sensemaking is ongoing, so Individuals simultaneously shape and react to the environments they face.
People extract cues from the context to help them decide on what information is relevant and what explanations are acceptable
-
-
Cognitive Walkthrough
Disadvantages
Tends to yield a relatively superficial and narrow analysis that focuses on the words and graphics used on the screen.
-
-
-
-
Advantages
Unlike some usability inspection methods, takes explicit account of the user's task.
-
-
-
-
Procedure
-
-
-
Bring all the analysts together to develop a shared understanding of the identified strengths and weaknesses.
-
-
-
-
Pluralistic Walkthrough
Procedure
-
Tasks
Once everyone has written down their actions independently, the participants discuss the actions that they suggested for that task.
After the users have finished, the usability experts present their findings to the group.
-
The walkthrough facilitator presents the correct answer if the discussion is off course and clarifies any unclear situations.
a product expert (usually a product developer) gives a brief overview of key product concepts and interface features.
After each task, the participants are given a brief questionnaire regarding the usability of the interface they have just evaluated.
-
-
Characteristics
Participants are all asked to assume the role of the user for whatever user population is being tested.
The participants write down the action they would take in pursuing the designated task online, before any further discussion is made.
-
It is only after all participants have written the actions they would take that discussion would begin.
The main modification, with respect to usability walkthroughs, was to include three types of participants: representative users, product developers, and human factors (usability) professionals.
Limitations
-
Only a limited number of scenarios (i.e. paths through the interface) can be explored due to time constraints.
-
-
A fairly large group of users, developers and usability experts has to be assembled at the same time.
-
Benefits
Synergistic redesign because of the group process involving users, developers and usability engineers.
Valuable quantitative and qualitative data is generated through users’ actions documented by written responses.
Strong focus on user centered design in task analysis, leading to more problems identified at an earlier point in development.
Product developers at the session gain appreciation for common user problems, frustrations or concerns regarding the product design.
Early systematic look at a new product, gaining early performance and satisfaction data from users about a product.
-
Verbal Protocol
retrospective protocol identified significantly more
usability problems, including more unique problems, than the concurrent protocol
-
-
-