1) The document discusses different approaches to user testing, including moderated vs unmoderated testing, prototyping full apps vs prioritized stories, and personalized vs aggregated feedback. It suggests balancing these approaches to learn quickly.
2) It recommends prioritizing the riskiest assumptions and most important things to learn when deciding how much of a design to prototype.
3) For quick prototyping, it suggests focusing user stories into specific tasks that can then be tested through a personalized scenario walkthrough. This allows learning patterns across participants.
WSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital Transformation
Remote Usability - Indigo.Design
1. Tweet-and-you-shall-receive giveaway!
Get accessto theonlycomplete design-to-codesystem
HOWTO PARTICIPATE
Takeascreenshotofthis session, addyourcomment and
tweetus @Infragistics#indigodesign
One luckywinnerwill bedrawnatrandomtoreceive a1-yearsubscriptionofIndigo.Design
Enterprise!
2. User Testingin the New Normal
Building better apps,faster,with early behavioral insights
GEORGEABRAHAM, PhD.
Sr.Product Owner &UX principal
gabraham@infragistics.com
JASONBERES
Senior. VP, Developer Tools
jberes@Infragistics.com
18. Making Trade-offs to learn quickly.
Moderated
Vs.
Unmoderated
Prototype the app
Vs.
Prioritized stories
Personalized
Vs.
Aggregated
1 2 3
19. 1. Moderated vs. Unmoderated feedback
Scoring the two approaches. More “dots” are better.
MODERATED UNMODERATED
Understanding why
Observe participant
Moderator as a resource
Scalability
Task metrics
Time for setup + feedback
Extracting patterns
20. Making Trade-offs to learn quickly.
Moderated
Vs.
Unmoderated
Prototype the app
Vs.
Prioritized stories
Personalized
Vs.
Aggregated
1 2 3
22. 2. Design everything vs. Prioritized Stories
What’s your riskiest assumption? What would you like to learn?
23. Making trade-offs to learn quickly.
Moderated
Vs.
Unmoderated
Prototype the app
Vs.
Prioritized stories
Personalized
Vs.
Aggregated
1 2 3
24. USER STORY 1 of 5
As a biz-dev associate, I want to set limits for
business expenses so that I’m aware how
much is safe to spend this month.
3. Personalized experience vs.Aggregate
User story is focused, but broad for quick prototyping
25. USER STORY 1 of 5
As a biz-dev associate, I want to set limits for business expenses so
that I’m aware how much is safe to spend this month.
USABILITY TASK 1 of 5
Change budget for coffee to $65
User story Usability Task
3. Personalized experience vs.Aggregate
26. Change budget for coffee to $65
What does the user see?
What will they do?
What will they see next?
What will they do?
What will they see next?
What will they do?
$65
27. Take part in a user test
Set up a user test
Get actionableinsights from testing
DEMO
bit.ly/participate-sample1
28. Medium fidelity - High Experience
CONTRAST HIERARCHY SIGNIFIERS
WHITE-SPACE SCALE / SCOPE TASK FLOWTRANSITIONS
CONTENT
29. Making Trade-offs to learn quickly.
Moderated
Vs.
Unmoderated
Prototype the app
Vs.
Prioritized stories
Personalized
Vs.
Aggregated
1 2 3
How many of you see a difference between prototypes meant for users vs. teams vs. business?
Personally, prototypes I create for my team depends a lot on where we are in the design process, my prior experience with the team and so on. Early on the process, I can .
But for early bird prototypes, instead of having to choose amongst three kinds, it’s always better to design for validation with users. Why? It can also be used with teams and business stakeholders.
How many of you see a difference between prototypes meant for users vs. teams vs. business?
Personally, prototypes I create for my team depends a lot on where we are in the design process, my prior experience with the team and so on. Early on the process, I can .
But for early bird prototypes, instead of having to choose amongst three kinds, it’s always better to design for validation with users. Why? It can also be used with teams and business stakeholders.
Sounds good.
Prototyping is a way to explore solutions with users, with minimal set up and risk. This is also when fresh ideas happen.
Something may look well designed, but only when you start using it do you realize whether it’s indeed well designed.
You have a disciplined practice if you can design today and validate tomorrow. How many among you have this?
The sooner you can run through this cycle, lower the risk of getting it wrong. You also better your chances of taking risks and genuinely experiment.
Prototyping is a way to explore solutions with users, with minimal set up and risk. This is also when fresh ideas happen.
Something may look well designed, but only when you start using it do you realize whether it’s indeed well designed.
You have a disciplined practice if you can design today and validate tomorrow. How many among you have this?
The sooner you can run through this cycle, lower the risk of getting it wrong. You also better your chances of taking risks and genuinely experiment.
Prototyping is a way to explore solutions with users, with minimal set up and risk. This is also when fresh ideas happen.
Something may look well designed, but only when you start using it do you realize whether it’s indeed well designed.
You have a disciplined practice if you can design today and validate tomorrow. How many among you have this?
The sooner you can run through this cycle, lower the risk of getting it wrong. You also better your chances of taking risks and genuinely experiment.
Sounds good.
Sounds good.
How many of you see a difference between prototypes meant for users vs. teams vs. business?
Personally, prototypes I create for my team depends a lot on where we are in the design process, my prior experience with the team and so on. Early on the process, I can .
But for early bird prototypes, instead of having to choose amongst three kinds, it’s always better to design for validation with users. Why? It can also be used with teams and business stakeholders.
How many of you see a difference between prototypes meant for users vs. teams vs. business?
Personally, prototypes I create for my team depends a lot on where we are in the design process, my prior experience with the team and so on. Early on the process, I can .
But for early bird prototypes, instead of having to choose amongst three kinds, it’s always better to design for validation with users. Why? It can also be used with teams and business stakeholders.
How many of you see a difference between prototypes meant for users vs. teams vs. business?
Personally, prototypes I create for my team depends a lot on where we are in the design process, my prior experience with the team and so on. Early on the process, I can .
But for early bird prototypes, instead of having to choose amongst three kinds, it’s always better to design for validation with users. Why? It can also be used with teams and business stakeholders.
How many of you see a difference between prototypes meant for users vs. teams vs. business?
Personally, prototypes I create for my team depends a lot on where we are in the design process, my prior experience with the team and so on. Early on the process, I can .
But for early bird prototypes, instead of having to choose amongst three kinds, it’s always better to design for validation with users. Why? It can also be used with teams and business stakeholders.
Prototyping is a way to explore solutions with users, with minimal set up and risk. This is also when fresh ideas happen.
Something may look well designed, but only when you start using it do you realize whether it’s indeed well designed.
You have a disciplined practice if you can design today and validate tomorrow. How many among you have this?
The sooner you can run through this cycle, lower the risk of getting it wrong. You also better your chances of taking risks and genuinely experiment.
Sounds good.
How many of you see a difference between prototypes meant for users vs. teams vs. business?
Personally, prototypes I create for my team depends a lot on where we are in the design process, my prior experience with the team and so on. Early on the process, I can .
But for early bird prototypes, instead of having to choose amongst three kinds, it’s always better to design for validation with users. Why? It can also be used with teams and business stakeholders.
Sounds good.
How many of you see a difference between prototypes meant for users vs. teams vs. business?
Personally, prototypes I create for my team depends a lot on where we are in the design process, my prior experience with the team and so on. Early on the process, I can .
But for early bird prototypes, instead of having to choose amongst three kinds, it’s always better to design for validation with users. Why? It can also be used with teams and business stakeholders.
