Design Methods Section

Of Equipit.com Case Study

Note: If you want to go back to the main case study close this tab
and select tab to the left..

I created a task flow (Figure 9) to see how most users were progressing through the process of building a Loadout/Kit and to analyze it from a macro (2,000 feet above) point of view. This method allowed me to see if within the “moments in between” there was any breakdown in the user experience. I also discussed and collaborated with the front end developer so that I could get his perspective on this process.

I also created a flow chart (Figure 10) of the Loadout/Kit process to give me a different perspective of the process.

After completed both research and diagrams above I thought that I should start giving Equipit some UI solutions for their issues regarding building a Loadout/Kit. As you can see by Figures 11–18 that through the process of iteration and working close with the Front End Developer how the UI
has evolved. Through this collaboration we had as many as 7 iterations.

As you have seen in the figures above, that using both my research results and iteratively collaborating with the front end developer certain themes emerged. First, I suggested to the team (supported by the research) that users did not know that they had a process to go through to create a Loadout/Kit. So, I designed a UI to show that this is indeed a step by step process. This was illustrated in the wireframes by showing a “stepper interface” which reinforces this point. Moreover, the user receives feedback on what progress they have made, by visually indicating it in the user interface. Second, there is a title on this section of the website giving the user feedback on where they are in the process. (ie: Step 1, Step 2, etc…) Third, the user has control to either go forward or backward in the process as he/she desires. My hope is that when these elements are implemented this will improve the user experience as well as retention. Our team decided to implement these changes.

I also made suggestions regarding Equipit’s main page and started the process/dialog using a mood board. This document was created to give the team a chance to discuss the direction they would like to take for a theme in their hero image.

I presented to the team 14 different ideas that they could use to replace their hero image along with a new tagline. In Figure 20 below I just want to show the overall look of what I was trying to do but I do not want to show much detail. The reason behind this is that at the time of this case study, nothing has been decided and implemented.

I had the chance to do a separate project for Equipit that was done in the hopes to generate some business for the company. It involved creating some ideas for ads on another site. In Figure 21 you can see both ads I designed.

Illustrated in Figure 22 & 23 are placement of the ads on a wireframe of
their webpage.

Related posts:

There are tons of facts that will never change about your programming Life and career. it's important you know them. I shared my few researched thoughts here. Change is constant! Adaptation is the…

The recent pullback in zinc prices proved short-lived. As I told you earlier, zinc is one of my favorite investment ideas for 2017. July’s volume is well up from the bottom. But it is about 26,000…

By designing a system of economic incentives that will provide access to reliable information to anyone with an internet connection. Be it artistic expression, scientific discovery, cultural artifact…