Human Experience Testing
At the core, human experience design is about problem solving. We start with assumptions about what we think our customers need. Those assumptions are based upon our experience, our critical thinking, our business goals and our humanity. These assumptions help us create a starting point; from there, we test.
This process begins with testing our assumptions. I have found that breaking our assumptions down into general, and sometimes vague, concepts gives us a set of questions we can ask real people. An example could be a onboading process for an application. Our assumption could be that a person would not like to go through more that three steps to complete the process. Our question could then be constructed as "How many steps would you be willing to go through to start using an app you like, need, or want?" As we synthisize the responses we get a clearer picture of the expected process and potential pain points for the user.
As we begin to design + refine it is good practice to check in with people who may use your app to see if you are on the right track. To accomplish this we create usability plans. These plans require us to constantly consider our flows. By defining Scope, Purpose, Time Frames, Equipment, Scenarios, and roles, we can test and collect metrics and responses to our designs and solutions. In conjunction with rapid prototyping we can clarify our directions quickly and make corrections early.