You can test anything with anybody. Identify what problems you are trying to solve. What are the enhancements or improvements you are trying to build? Be honest about your goals and share with everyone in the group. Their insights will amaze you and should help shape your path. Your users really want to help. It ultimately helps them.
Build a list of skill-diverse participants that are real users. A manageable number for small teams to be effective interviewing within a week is around 20.
Reach out and speak to them. Email details of your request, goals, proposed meeting times. Get friendly. They need to let their guard down and feel comfortable in order to provide honest feedback. Make a spreadsheet, keep a schedule, send meeting invites. You want to interview them from their own environment using their own technology.
You'll need a document for your script, a spreadsheet to track your users, email and meeting scheduling software, a phone, a voice recording mobile app, and software to make nice artifacts based on your research.
Call your users, record the sessions, take notes, and ask many questions.
Brainstorm every session day. Take that feedback and run with it.
In addition to gathering insight about the usage of our software, we want to know about the people, their processes, their daily routine.
Some of what we learned:
Having a pre-determind set of deliverables is a good start and can inform your data collection process. After your data is consumed, a variety of artifacts can then be devloped from your research. A few we like are:
A user persona, in human centered design, is created to represent a user type that might use technology, applications, websites, brands, or products in a similar way.
User journeys are a series of steps which represent a scenario for how a user might interact with the software we are designing.
Nice things in the works.