Revision as of 19:13, 15 May 2007 edit Rjwilmsi (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 933,649 edits m Typo & format fix, Typos fixed: completly → completely, using AWB ← Previous edit		Revision as of 13:24, 7 November 2007 edit undo Mild Bill Hiccup (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 175,657 edits m "get buy in" --> "get buy-in" Next edit →
Line 1: {{Orphan\|date=October 2006}} When applied to building a website or similar work product, a '''Visual Guide''' can be an intermediate step toward the end goal of a complete website. By creating a visual guide along the way, the designer or developer can get buy -in from the other people involved in the website such as the customer, their manager and other members of the team. A visual guide could be a [[Website wireframe\|wireframe]], creative composition or information architecture. A device that will enable collaboration will save time, decreasing the chance of work having to be completely redone. A manager could create a visual guide for the team to complete the build -out. Paper prototype could be an excellent way to develop Visual Guides. ==External links== Some links about this topic are:

Visual guide: Difference between revisions