Before you launch Hub, some testing can help uncover issues to fix or questions to anticipate and address in your change management plan. As with other Dayforce changes, we recommend that you test on a pre-production environment so that your employees don’t see a hub before you are ready for them to adopt it. Note that hubs follow role-based authorizations in Dayforce, so you need to make sure that your testers have the right permissions to see any features or hubs you have set up.
Ask for volunteers from your first audience to sit down with you in a short testing session. Usually, 3-5 is enough to identify any major issues. For more information see, (NN/g: How Many Test Users in a Usability Study?). A simple way of testing is to ask test users to complete the last task they did in Dayforce, or to answer goal-based questions derived from the task chart you made when determining audiences. Watch your volunteers as they perform the tasks, then note where they stumble. Bear in mind that you should avoid tasks that could reveal personal information to which you may not otherwise have access. Alternatively, you could ask test users to describe their process without you watching their inputs.
As your volunteers work through their tasks, it is ok to ask for clarification or details on their thought process. However, try not to guide them through the activity or to ask leading questions. This data is richer than a survey and requires less prep from your volunteers.
Be wary of asking for preferences. People often have a disconnect between what they like and what they do, may have various levels of tolerance for change, or otherwise alter what they say to fit social norms.
There are numerous online resources on conducting usability tests that can help you refine your technique and improve the quality of the feedback you receive, such as NN/g: Usability Testing 101. This step is also where your internal user experience experts, if you have them, may be able to help. In the end, getting feedback through a method that is achievable with your resources is better than getting no feedback at all. So, start simple, while striving for good quality feedback.