1912 - Alpha Trial run with TEC
Project | Voluntarily - teacher flow usability testing dry run |
Testing Date/s | December 2019 |
Success Metrics |
|
Process
Stage | Prompts | Results / Notes |
Intro & Qualifiers |
|
|
Begin Test |
| Access email and sign up | Time: Create account | Time: Complete school profile | Time: Find an ITF activity to run | Time: Create an ITF event with a date and location | Time: Accept a volunteer | Time: Close activity | Time: Provide feedback | Time:
Need a way to fake volunteer applications for test on beta |
Key Takeaways
A lot of form fields are either too generic or should be hidden based on path taken to get to the form (ie: a school first time setup should be different to a corporate org setup or asking for CSR justifications from teachers)
Flash of text / broken action cards cause confusion for users ie: create your profile page currently goes to a blank profile page, and not the editable page, or clicking edit / create new page causes the page to flash with a blank activity
Need to signify that in their current state, tags are merely informational - no functionality when you click them atm and need stronger comms around why are they exist / how they bring volunteers in
Copying the information over to a blank opdetailpage caused a lot of confusion for the user - perhaps quick win would be to cull fields during activity instantiation process, and do a proper stepped wizard later?
User did not know that we send out the opportunity to volunteers after the activity is created - should probably communicate this as a completed activity creation state or just show next steps as a checklist
User expected next steps after the template was created
Fears around volunteers not selecting the opportunity - how do we deal with nonperforming ops? User wants to choose volunteers from a list