Sunday, August 23, 2009

The level of detail in your mock-ups should reflect the level of confidence in your design

Mock-ups are prepared as a way of exploring a particular design problem, and in order to communicate your thoughts on a solution to important stakeholders (i.e. users, clients or developers).
In the early stages of design, mock-ups should communicate broad concepts and groupings of information or functions.  Keeping the details scant at these early stages allows you to progress through iterations quickly and keeps your stakeholders from throwing the baby out with the bath-water by quibbling over colours and button placement.
As you progress towards a final design, mock-ups should be rendered in increasingly higher fidelity so that the full detail of your approach is exposed.


  1. I think of this as "level of confidence in the design" rather than "completeness". The more confident I am, the higher fidelity I will go to.

  2. @simplerisbetter Hmm. This is an interesting perspective. I think you may be right here. Completeness implies implies that you are at a known point on a path toward a point of finality in your design... but as we know, designs are never finished, they just reach a point where the developers start (or finish!) coding it and you have to stop. Changing to confidence. Thanks!

  3. You're right. It's hard to really pinpoint whether a plan will work, but a detailed one does show more confidence.


Note: Only a member of this blog may post a comment.