Research to Usability- Go Coffee prototyping project 1

In my first attempt to create a prototype I learned an amazing amount of new knowledge or rather the application of known knowledge in a new way.
On my first attempt I found that I was most surprised by how much I overlooked as common user knowledge like the login, payment, back and forward buttons. I also got hung up on the user flow map. I kept having to amend my map to make the product more usable.

Research- this is the interview and observation step. Asking questions, watch and most important listen and wait for the answers and don’t lead.

Requirements- the nuts and bolts of what you need the deliverable to do/ solve for. The more requirements, the more narrow the scope of the project. It can drive the speed and toughness of the completed deliverable.

Flow — Understanding this step helps drive the usability and quality of the deliverable. The more precise, organized and thoughtful the easier it was to design the visual usability of the deliverable.

Prototyping — the visualization and culmination of the research, requirements, and flow that guides the user. The prototype is the tangible 1st level deliverable still in its infancy and changeable

User testing — The ultimate in feedback, did it work, did it work the way it was expected, did you accomplish the initial requirements and was the user able to figure it out. Again you ask, observe and question. Then you tweak the prototype to produce a more user-friendly deliverable. Then test again.
It’s easy to get caught up in one step of the process for me it was the flow. It doesn’t have to be perfect all stages of the process can be revisited and reorganized to continually improve the outcome. This to can become in itself a rabbit hole. Getting it as precise and complete as possible will drive the timely completion and usability.

Like what you read? Give Natalie Wiesehuegel a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.