Implementing the testing stage with a client
I almost fell into the trap of ignoring the testing stage.
We wanted to figure out the order and returns flow for the E-commerce site we were working on while working with a large client. We were attempting to improve the user experience while also meeting the client's logistical requirements.
It was a convoluted process. From logistics to money, there were numerous moving elements required just to commence a return, and don't even get me started on what was required to complete the remainder of the process.
We had spent weeks analyzing the requirements, coming up with ideas, and iterating the design while sitting alongside stakeholders, designers, and engineers. We were continually bouncing ideas back and forth, attempting to determine which option was the best. It was then that I knew we were missing something crucial.
Testing our ideas.
We were so focused on building the solution that we didn't even ask the user what they felt about it. We were so focused on the business demands that we forgot to consider the needs of the users. We had been assuming that the user would have a positive experience with our present design solution up to that point.
I pressed the pause button and informed the client that we needed to test this flow with real users in order to validate our ideas. As designers, we sometimes get so caught up in the details that we overlook important details. Perhaps by putting our ideas to the test, we'll get tangible input that will help us steer the design in the right way.
We went away and set up the testing environment after the client agreed. We produced high-fidelity prototypes to give the appearance that the customer was dealing with a live website because we were dealing with a significant client. The setup required some time, but the end product was well worth it.
Thankfully, the users in our testing environment were able to follow the flow. We had a few setbacks along the way, but these simply served to emphasize the necessity for us to iterate a few concepts. We came away from the meeting with a few concrete tasks to assist improve the solution. We could have saved weeks of wasted iterations if we had applied this method of thinking earlier in the project.
Testing doesn't need to be complex
It doesn't have to be so difficult to test your prototype. You don't have to have a high-fidelity prototype available to test all of the time. To validate an idea, even a wireframe scribbled on a piece of tissue will suffice.
Figma (to help us construct the high-fidelity prototype and flows) and Maze (to help us set up the testing ground and record important metrics on how the user interacted with the prototype) were the technologies we used in our situation and with the client we were working with. We were able to build up a remote testing environment with just those two apps, and we were able to gain a lot of useful information.
I hope I've shed some light on the importance of putting your ideas to the test. We designers aren't only making things lovely; we're also coming up with new ways to solve problems. As a result, using a process like design thinking to ensure the success of your digital ideas is a terrific idea.
What matters is that you test your concepts with real people, and that you do it early and often. Getting direct input from genuine users has a lot of value. It can save you time and money, as well as indicate when it's time to pivot away from that notion.