Update usability-testing.md

content/en/design/user-experience-research/usability-testing/usability-testing.md

@@ -4,4 +4,66 @@ linkTitle: "Usability Testing"
 weight: 3
 description: >
   Usability testing is the practice of testing how easy or difficult a design solution is to use by observing how users interact with it. 
----
+---
+
+These are one on one sessions that can be done in person where the facilitator observes the user directly, or remotely where the facilitator shares their screen and asks the user what they would do next and acts as their proxy.
+
+## Planning
+
+
+
+1. Prepare your design prototypes to test
+2. Identify your test goals and objectives
+3. Develop your test script, tasks and scoring criteria
+4. Establish timelines and resources required:
+    1. Recording equipment (record the user and their interactions with the prototype when possible)
+    2. Personnel
+    3. Location or connectivity if remote
+    4. Testing devices or device with screen sharing capabilities if remote
+
+
+
+Here is a [sample usability test](https://docs.google.com/document/d/1su4B0SZLZl32DvcFxlKP7mHHLa_mTZ4C_vwW1OJ7O5Y/edit#heading=h.ekb2g8hgnfts)
+
+
+## Recruiting
+
+Test with 6-8 users based on the relevant persona the prototype is designed for, considering:
+
+
+
+* Engagement (active vs inactive users)
+* Technical literacy 
+* Age
+* Role
+* Location
+* Experience with the CHT 
+
+
+## Executing
+
+
+
+1. If the usability test is being run in person, make sure the user is physically comfortable with the testing setup
+2. If the test is being run remotely, ensure a proper connection and that the user can hear you properly
+3. Ensure users know what is going to happen in the session; most times CHT users don’t have experience with usability testing
+4.  Make it clear that the moderator is testing the designs and not them and that there are no wrong answers
+5. Ask permission to record the session and start the recording
+6. Begin the session and run through the scenarios and tasks until all are completed
+7. Thank the user for their participation, ask them if they have any questions and let them know their feedback is important in improving the CHT 
+
+
+#### Tips:
+
+
+
+* Watch for verbal cues and body language. Some users won’t explicitly say they are confused but could sigh in frustration
+* Don’t speak too much to avoid interfering with the users’ thought – ask them to say what they are thinking out loud as they are performing each task
+* Keep an even tone, don’t agree or disagree with the user to avoid influencing their answers
+* If a user is confused, probe to find out why instead of guiding them to the correct answer
+* Whether the user passes or fails the task, do not give an indication of either and simply thank them for completing the task
+
+
+## Synthesizing
+
+The scoring of each task in the test guide should indicate the pass/fail rate of the designs tested and the average ease of use score to highlight areas of improvement for the prototypes.