On creating wireframes

This week for our course module we were to sketch out wireframes for the Lunch Money Buddy application. I created several low-fidelity wireframes to showcase a simulated workflow in using the application. After sketching them out we were to submit them for peer review for our peer members to comment and provide feedback on.

I was able to get some really good feedback from my peer group members. After we gave feedback the next step was to create a digital version of our sketches. I used Moqups to create my wireframes. The process was pretty simple and I was able to replicate most of my designs directly from the sketches using the templates provided by Moqups.

I struggled with providing the rationale in my designs. I haven’t figured out why I design something in the way I did. Because this is only a seven week course we started with the research and assumptions already completed for us. So, as we sketched out the wireframes and began to create our digital designs we were to design on our own volition. I wanted to create designs that are sound and logical for the end user. I designed in a why that I thought would be the most efficient for our personas and the application requirements. Is there some sort of article or book to read that would give relevant examples of why a wireframe or an interaction would be designed in a specific way?

Like what you read? Give Ken Jackson a round of applause.

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