Discovery Template – User Research
On this page
Method
Our researchers will consult with a range of users during the Discovery to explore their context, needs, emotions, and behaviours.
Qualitative research
The following qualitative research methods will be used:
- One-to-one interviews with user representatives (users and administrators).
- User needs workshops.
- Field visit observations.
- Open text comments from online surveys.
Quantitative research
The following quantitative research methods will be used:
- User feedback survey.
- Online user needs survey.
- Review published and unpublished Health Education statistics.
Note: Due care should be given to ensuring there is no bias towards users with higher digital literacy. At least some interactions should be face-to-face.
Service User Roles
Primary Roles -
Primary user 1:
- Describe what they do
- Describe how they do it
Primary user 2:
- Describe what they do
- Describe how they do it
Primary user N:
- Describe what they do
- Describe how they do it
Secondary Roles -
Secondary user 1:
- Describe what they do
- Describe how they do it
Secondary user 2:
- Describe what they do
- Describe how they do it
Secondary user N:
- Describe what they do
- Describe how they do it
Key Findings
The key findings from the user research were:
-
-
User Needs -
User 1's needs:
- [Insert need]
- [Insert need]
User 2's needs:
- [Insert need]
- [Insert need]
User N's needs:
- [Insert need]
- [Insert need]
Context of Service
Do all users understand the importance of the service?
Current Process
What are the positives and the negatives of the current process?
Improvement Opportunities
What are the improvement opportunities?
Validating the User Needs
We will conduct a validation exercise of the user needs discovered; establishing MoSCoW labels for each need for future backlog prioritisation.
Categorise user needs. Something like: Automate, Capture, Collaborate, Communicate, Complete, Process, Publish, Store [amend as necessary].
Create a survey asking survey participants to prioritise categories and then each need within those categoies. Summarise the findings here. Full results in appendix.
Prioritising the Backlog
The evidence from surveys and other methods of user research were used by the IT Recruitment Marketplace and PSIT teams to prioritise and order the backlog.
[Consider applying MoSCoW]
The MoSCoW method is a prioritisation technique used to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement.
The term MoSCoW itself is an acronym derived from the first letter of each of four prioritisation categories (Must have, Should have, Could have, and Won't have)