User testing at any stage of the process
Test paper prototypes with users and adjust as needed
Users are able to understand the flow of an app with paper representations of screens. It doesn't take long for problems to be identified. A tangible representation of the workflow and design makes it easy for users to spot the things that confuse or frustrate them. They are usually happy to explain what doesn't work for them and why. This early-stage feedback can be used to revise the designs before engineers start to work.
Once the needs and wishes of the users have been consulted it is important to get the engineers' feedback on the design on whether it is feasible and how long it will take to build.
Test the high-fidelity prototype with users and adjust as needed
The Office of IT UX Team has the tools and skills to create high-fidelity prototypes, which can and should be used for more user testing and for obtaining stakeholder approval. We use Figma prototyping software, which is interactive and demonstrates the flow of the application.
Release Testing
Testing with personas is critical to knowing if all user groups have their needs met. The Service Desk is a good resource for testing personas because they can anticipate the needs of their customers. Past testing has shown that the Service Desk employees are good representatives of all campus departments' needs. Though they are more tech-savvy than the average student, they make great alpha testers. Testing with real, average, random users is essential prior to release. It only takes 10 or 20 testers to find bugs and it is better to find those bugs before the release of your product than after. The UX Team is available to help with this testing.
Be prepared to test after release. It's a good idea to do a soft/quiet release at non-peak times so that a small group of testers can validate the site. Sometimes running two sites in parallel helps. In any case, go out quickly and talk to users across campus. 10 to 20 users will likely identify any pain points that could be fixed in the next release.