08 / Task Scenario Testing
I conducted Task Scenario testing with 5 participants, asking 5 questions each:
Feedback was positive, but they struggled with the PDV question
I realized the design was overly complicated
There were edge cases I needed to account for
I simplified the question from:
“Would you like to add additional PDV codes for a non-PDV visit?” to “Was this visit scheduled as a PDV?”
Skills
✔️ Test Planning
✔️ Applying Feedback
09 / User Needs Met
The user feedback proved to be successful in meeting their needs:
“Good, the Scribe doesn’t need to memorize codes”
“Easier and faster”
“Intuitive”
“No hesitations”
Skills
✔️ User Empathy
✔️ User Advocacy
Real feedback from task scenario testing
10 / Combatting Edge-Cases
In combination of the lo-fi phase + user testing, I identified several edge cases:
Appointment type may change, requiring updates for new additions
Users need manual code search
Incorrect code generation; users need a way to enter the correct one
Handle scenarios where a patient leaves early and isn’t billed
Users should be able to remove one code and add another
Skills
✔️ Critical Thinking
✔️ Thoroughness
AFTER testing designs - making updates to account for edgecases
Design BEFORE testing