User testing 101 - Suzie Jabergsuziejaberg.com/img/portfolio/testing_presentation.pdf · Complex Data Manipulation Tweak Parameterization & Variables Business Rules Context Browser
Post on 23-Aug-2020
0 Views
Preview:
Transcript
User testing 101
Best Practices Basics
• Let personas guide task-writing
• Use common language, avoid technical jargon
• Don’t use words that are leading, (eg. “drag a step”)
• Design test cases ranging in various levels of difficulty
• Clearly identify the expected goal and steps to the tester
• Pre-test with colleagues to weed out assumptions and missing details
Personas
Developer
Title: Solutions Architect
Name:John Rice
Goals: Motivate team to improve and innovate
Matches DT persona:Dave C# Developer
BDM
Title: HR Manager
Name:Sheila Turner
Goals: Find simpler way to onboard new employ-ees and streamline paperwork
Matches DT persona:Betsey, Business Admin
ITDM
Title: IT Director
Name:Seth O’Malley
Goals: Improving innovationwithin the business
Matches DT persona:None
Power User
Title: Sharepoint Admin
Name:Ian Yang
Goals: Expanding skillset beyond SharePoint
Matches persona:IkeIT Manager
Personas
Developer
Title: Solutions Architect
Name:John Rice
Goals: Motivate team to improve and innovate
Matches DT persona:Dave C# Developer
BDM
Title: HR Manager
Name:Sheila Turner
Goals: Find simpler way to onboard new employ-ees and streamline paperwork
Matches persona:Betsey, Business Admin
ITDM
Title: IT Director
Name:Seth O’Malley
Goals: Improving innovationwithin the business
Matches DT persona:None
Power User
Title: Sharepoint Admin
Name:Ian Yang
Goals: Expanding skillset beyond SharePoint
Matches DT persona:IkeIT Manager
Elements
Core Experiences
Process Triggers
Recipient Groups
References
Context Browser
Inline Composter
Rules Designer
Canvas
No Code
DeployBuild from Scratch
TweakComplex Data Manipulation
Parameterization & VariablesBusiness Rules
Basic Value Props
User Tasks Task One: new WF screen / dragging steps / drawing lines
Task Two: email step / recipients / smartfields.
Task Three: manipulating dates / task expiration
Task Four:References / Recipient Groups / Process Triggers
Task Five:To do
easiest
most difficult
Objectives: new WF screen / dragging steps / drawing lines
1. Open WF designer
2. Create a new WF
3. Design a basic workflow that starts sends an email and ends
Task One
Basic Value PropsNo Code Core Experiences
Process Triggers
Recipient Groups
References
CanvasDeployBuild from Scratch
TweakComplex Data Manipulation
Parameterization & VariablesBusiness Rules
Context Browser
Inline Composer
Rules Designer
Task Two
No Code Core Experiences
Process Triggers
Recipient Groups
References
CanvasDeployBuild from Scratch
TweakComplex Data Manipulation
Parameterization & VariablesBusiness Rules
Context Browser
Inline Composer
Rules Designer
Objectives: email step / recipients / smartfields.
1. Send the leave request to Codi for HR approval
2. Send confirmation to user via email that request has been recieved.
3. Send to requester’s manager for secondary approval
4. Send approved / declined email to requester. Email should read “Hi Lewis” where Lewis is the requester’s name.
Basic Value Props
Task Three
Core Experiences
Process Triggers
Recipient Groups
References
CanvasDeployBuild from Scratch
TweakComplex Data Manipulation
Parameterization & VariablesBusiness Rules
Context Browser
Inline Composer
Rules Designer
Objectives: manipulating dates / task expiration
1. Create a process to send a task to a user
2. In the task email, specify: “you have 30 days to do this task.”Set the task to expire on xx/ xx/ xxxx.
3. Set the task to expire in 30 days.
No Code Basic Value Props
Task Four
Core Experiences
Process Triggers
Recipient Groups
References
CanvasDeployBuild from Scratch
TweakComplex Data Manipulation
Parameterization & VariablesBusiness Rules
Context Browser
Inline Composer
Rules Designer
Objectives: References / Recipient Groups / Process Triggers
1. Start a process when an item is added to a list in sharepoint
2. Send an email to the HR team telling them who created the item and other details about the item. (eg. The title and description)
No Code Basic Value Props
Task Five
Core Experiences
Process Triggers
Recipient Groups
References
CanvasDeployBuild from Scratch
TweakComplex Data Manipulation
Parameterization & VariablesBusiness Rules
Context Browser
Inline Composer
Rules Designer
To Do
No Code Basic Value Props
To Do 1. Setup for each task: What we won’t be asking the user to do? (eg. Create SharePoint list)
2. Scenario Background: (eg. You are an HR manager trying to make people aware of new ideas)
3. Re-order stories for Devs so that user study tasks are ready.
top related