Storyboards excel when an interaction is difficult to communicate using an abstract deliverable like a sitemap or user flow.Ī storyboard’s visual and narrative approach gives an additional layer of context. Users in their context of use (home, office, and so on) and any interactions or emotional responses that take place off the Scenarios, if created in your research phase, make excellent starting points for illustrating user journeys. Storyboards let you add instructional detail to complex interactions. WireflowsĪre particularly effective when the behavior of the interface is unconventional and demands visual explanation. Like a user flow, a wireflow shows how a user moves through the site, but replaces labels with rough representations of the relevant interfaces. Your developers if your proposed solution involves tricky technical logic. Instead, pay attention to the high-level interactions. It’s easy to overwhelm userįlows with irrelevant minutiae. User flows are great at explaining complex logic, but don’t let them become swamped with detail. If only a few sections of your site are process-led, you can create a user flow in tandem with a sitemap simply cross-reference Of your site, such as creating a new account or adding an item to a shopping cart. User flows are particularly suitable for task-driven sections Rather than capturing a hierarchical information structure. This deliverable describes how a user moves through a process, Under these circumstances a user flow may be more suitable. The simple hierarchical nature of a sitemap can be too limiting on sites with complex navigation, large amounts of user-generatedĬontent, or process-heavy applications that branch according to user input. This user flow captures a sign-in/register process using Jesse James Garrett’s visual vocabulary. Start creating all those boxes and arrows. Tools like Microsoft Excel and the Omni Group’s OmniOutliner will help you shuffle pages around before you Since a sitemap is all about structure and hierarchy, starting with a text outline can be useful. We’ll talk more about feedback and critique in Chapter 5. Share with your team, so don’t be surprised if it sparks debate. Let a sitemap’s simplicity fool you: it will play an important role in the project. It’s not unusual to discover branches reaching farther thanĬreating a sitemap will help you understand not only scope but also how sections and pages should be arranged and labeled.īy the end of the exercise you should have a fair idea of how your site navigation will work, and what labels you should giveĭocumenting a sitemap is a relatively simple task, thanks to Jesse James Garrett’s visual vocabulary ( in which you’ll find a standardized set of shapes and connectors for use in your sitemaps and other deliverables. It’s worth starting this process as early as you can, so that you can fullyĪppreciate the components of the system and what work lies ahead. Use what you learned in your research (card sorts, interviews, and so on) to draft a structure that holds the site’sĬontent in a way that’s meaningful to your users. This sitemap uses a top-to-bottom hierarchy to show site structure.Ī sitemap is a familiar tool to every UX designer you’ll use one for most sites you design, particularly large, information-heavy
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |