1. Emphasize a set of tactics that support a single concept - A conceptual brainstorm with the design team may result in a "shopping list" of potential tactics to support a single theme. Quantity of output is important, but only to provide enough valuable, tactical choices to choose from. Force the team to prioritize only 2-3 tactics to include in the design comp. Don't try to incorporate everything, or the design will quickly become a "patchwork quilt" of content modules. If this happens, the design will lose clarity.
2. Exaggerate focus and prioritization on supporting design elements - Visual Designers often find it aesthetically offensive to mock-up large interface elements (text, buttons, tabs, widgets, etc.). However, in the case of visualizing a concept, it may be necessary to exaggerate the page elements that underscore the idea. The conceptual comp is a visual aid for a presentation. The strategic concept must be recognizable in 2-3 seconds. Don't make the client read paragraphs of text, or work too hard, to "get it." The point of the exercise to is to bring an idea forward, not to hide it in a forest.
3. Don't get caught up in the UX details (aka - "the weeds") - The Information Architects on the design team, myself included, will likely get caught up in tactical details related to "way-finding," "affordance," and "design consistency." These are all extremely important objectives for "market-ready design," but not for the purpose of painting broad strokes around a concept. The important details can be worked out later.
Measure the success of conceptual design with client feedback that indicates complete understanding of the concept and general acceptance of it.
No comments:
Post a Comment