Portfolio | Process Section | Prototypes
Prototypes
In my experience, wireframes have a very limited purpose. That is, to show where the main navigation, UI elements, and content COULD reside in the application and/or web page. Unfortunately, stakeholders have a hard time envisioning what the Designer is thinking from two dimensional, colorless line drawings. What they really want to see are graphic rich mockups, even prototypes! But that's a bit of a cart before the horse thing.
The wireframes that I've found are most effective allow for some sense of the style to creep into the layout. I often say, ‘UI options are like spokes on a wheel; any of which could be just fine’. But Designer's can waste a lot of time going towards the 9 o'clock option, when the client really would have preferred the option at 4 o'clock.
I usually start by asking the client to show me a site or an application they really like. This gives me a sense of where to start. Unless you have a solid grasp on what must be on the page, I find it’s best to stay flexible. Odds are, it’s all going to change several times as the design matures.
MUG Prototype & Wireframes
Site Wireframe - MHS User Group
MDR Prototype Option 1
MDR Prototype Option 1