At the wireframing phase of the design process, our ideas are young and unpolished. Wireframes, whether created on scraps of paper, a whiteboard, or in a software program, serve to establish relationships between elements in a project such as: navigation, imagery, and calls to action. But if we think of wireframing as a tool, it’s ultimate purpose is to create an ideal space for collaborative conversations about design solutions, while supporting iterations and driving rapid ideation.

So how do you know if your wireframes are effectively driving the design conversation? The best way to tell if wireframes are hitting the mark is to take a step back and ask this question: When I share my wireframes, are the conversations about the execution OR about the experience I’m creating?

If your creative brainstorms and discussions are getting stuck on “how your wireframes look”, you may be missing the mark. And usually, it boils down to one or more of these three problems:

• Your wireframes are executed poorly. See 10 best practices below for help.
• You failed to set clear expectations with the client about how you are using wireframes as a tool to drive the conversation about design solutions.
• Your wireframes are too polished and not solution-oriented.

Best Practices for your Wireframes

• 1) Don’t use color. If you do, use it intentionally.
• 2) Consistency is key
• 3) Use actual content
• 4) Never wire alone
• 5) Communicate functionalities and interactions statically
• 6) Set clear expectations
• 7) Avoid unnecessary barriers to success
• 8) Practice non-attachment
• 9) Be selective and keep it simple
• 10) Control the conversation