#Things to consider

  1. We determine a wireframe’s effectiveness by the conversations it creates.
  2. The primary benefit of wireframes to software organizations isn’t their ability to represent a user interface but their ability to visualize and facilitate the transformation from idea to code—in the same way that a napkin sketch can instantly cause one person to understand what another is talking about. The understanding is the output.
  3. A good wireframe should be designed from the user’s point-of-view and present solutions that work for its intended user.
  4. Wireframing is more than just creating artifacts; it’s a process of collaborative design.
  5. At a minimum, ask for feedback at two points in your design process: once when you’re about thirty percent done, and once at around ninety percent.