Application Envisioning idea
L4.

Thoughtfully applied branding and non-interactive imagery are often noticeably absent in computing tools for knowledge work. Product teams can envision how aesthetic treatments and added graphic elements could help build emotional connections with users, promoting brand recognition and appeal while at the same time improving individuals’ understandings of product functionality.

Examples from three knowledge work domains:
(Illustrated above) An architect enjoys the richly animated imagery that covers the log in screen of her building modeling application. Once she has logged into the tool, however, its interface becomes a quiet, cool, unobtrusive frame that does not distract from her focused attention on the building model that she is currently working on.
A scientist likes that some dialogs in her analysis application use complementary illustrations to explain certain ideas, instead of just presenting text. Even after she has learned the illustrated information, she still finds the colorful images to be
appealing, and they sometimes act as landmarks that help her find her way.
A financial trader finds the branded color scheme of his current trading application more appealing than the black and green mainframe screens that he used to use. There’s something about the new tool’s animations and useful, attention grabbing cues that really set it apart from other trading products. It is all very simple, and it does not get in his way.
Many contemporary products for knowledge work are aesthetically bland, unrefined, and undifferentiated from one another. While product teams frequently prioritize certain types of iconography and other conventionally “necessary” graphical elements in their applications, other visual treatments and non-interactive imagery may not carry the same weight in teams’ design priorities.
Specialized computing tools can have unique, recognizable visual characters. Using the term branding to mean more than just a logo or swatch of color, product teams can extensively brand knowledge work applications while enhancing product usefulness and usability (D4, F). When branding is addressed during early ideation of potential application concepts, teams can envision approaches that broadly embody brand in a holistic sense (A, K12). Definers and designers can also identify opportunities in their functionality concepts for informative, stimulating, and memorable imagery (F10). This content can appear as a part of introductory instruction (K2), infrequently accessed processes (K5, K6), tasks that involve waiting (D3), and other classes of potential user experience.
When product teams do not actively consider how they might incorporate supplementary imagery and direct branding into their application concepts, opportunities to drive useful, unified, and meaningful visual approaches can be lost. While some visual treatments and graphic elements can be added on an item by item basis during product implementation, an early, foundational emphasis may be necessary for teams to arrive at consistent, strategically differentiated, and industry leading design approaches (L5).
See also: K1, L, M

Application Envisioning questions:
How might your team’s application concepts be extensively and recognizably branded, while enhancing — not distracting from — onscreen clarity and utility? Where in your sketched functionality ideas could there be opportunities for useful, stimulating, and memorable supplementary graphic elements?
More specific questions for product teams to consider:
How could your team’s interpretation of branding expand to mean more than just
a logo or swatch of color?
What types of emotional connections between user and brand are central to your design strategy and application concepts?
What larger design trends could influence your team’s approach to of branding and complementary graphic elements in your sketched product?
How might your computing tool have a unique and recognizable visual character, even if that character may emerge from the sum of relatively small design details?
How could selected brand characteristics of your firm, product family, and envisioned offering be usefully and valuably applied to your sketched application frameworks and functional areas?
How might targeted individuals identify with and respond to certain branding approaches, given that your team is striving to create a highly functional tool for thinking work?
What parts of your application’s scope have attentional and onscreen constraints that might not be conducive to incorporating any sort of “additional” visual content?
What key ideas, processes, and options within your functionality concepts might be clearly communicated to targeted workers through graphic imagery?
Where might instructive content in your sketched screens benefit from illustrations?
Could the user experiences of starting your product, waiting during specific processes, or exiting the computing tool present opportunities for engaging visual communication?
What styles of illustration could be domain and brand appropriate? How might these styles reference or play against the aesthetic conventions of contemporary computing?
Do you have enough information to usefully answer these and other envisioning questions? What additional research, problem space models, and design concepting could valuably inform your team’s application envisioning efforts?
< PREVIOUS PAGE | NEXT PAGE >

Back to top | View Table of Contents
|