The Layers of Design: the style layer
Designing for the Web, as I see it, is a multi-layered process. It’s a process in which each layer addresses specific design needs related to client aims, brand characteristics and site user habits and expectations. Sadly, the last of these layers to be applied in the process, the application of style, is an oft-maligned element of design. Style for its own sake or by itself is not design, certainly, but stylistic concerns are important to successful design.
Even so, any day of the week you can find designers in online forums criticizing web page graphic designs for having style. Prime targets for criticism these days include rounded corners, gradients, drop shadows, large buttons, fat icons or a worn look. Some designs garner criticism simply because the title font is Trebuchet MS.
Much of this criticism is explained, ostensibly, by relegating these graphic elements into the dreaded and cliche Web 2.0-look category of graphic design. It seems that once a cliche is defined, all of its characteristics must be persecuted without thought or consideration for context; at least by those who lack relevant understanding.
Now certainly these or other graphic elements can be ill-used and irrationally applied to design. But like all graphic elements, each of these has communicative value and contributes to the message conveyed by the page design. A designer must know what each of these and other graphic elements communicates and use them where and how it’s most appropriate. Indiscriminate use of stylistic elements in design does indeed amount to needless affectation or embellishment. Nevertheless, style is an important layer in the design process and must not be neglected.
Breaking the design process up into layers is a useful mechanism for ensuring that the effort is comprehensive and contextual. By starting with the most fundamental factors in the design and designing them to be contextually appropriate, you can build successive layers of the design on the right sort of foundation.
Once you’ve got a clear picture of the client aims and desires, brand considerations, site and specific page purposes, target user habits and expectations and the different pages’ contents you can begin with the most fundamental layer. Different designers might categorize the layers differently, but my basic suggestion for layering would be:
- Information architecture Start by deciding and/or planning for what information is available where, when, and under what conditions throughout the site.
- Interface behaviors Specific behaviors are sometimes required or advisable for certain interface elements. These often affect the design effort from both a functional and visual standpoint.
- Visual hierarchy of the content It’s often beneficial to provide clues to what’s most important on the page, next important, and so on.
- Layout The fundamental visual framework to support the previously mentioned elements.
- Style The look and feel of the page/site must support all of the above and tie things together neatly.
Each layer is important and, done well, contributes to the wholeness of the design. Leave out one layer and the design will fail to reach its potential. One could go so far as to say, as I have on a few occasions, that designs that ignore one of these layers are simply poor designs.
Elements of Style
The application of style to the design might be subtle or heavy-handed, according to the context, but no amount of stylistic application can be said to be too little or too much in and of itself. Context matters in every aspect of design and this is certainly true of stylistic concerns.
Let’s take a couple of those much-maligned interface cliches for example. Note that both Blogger and Sprint use rounded corners in their page designs. However, these sites don’t use the same sort of rounded corners, and for good reason. Each is chosen for specific effect. Do you know what that effect is? These sites’ designers did.
Both Blogger and WordPress are weblog software application websites. However, Blogger uses lots of gradients, drop shadows, fat icons and rounded text in its main page interface while WordPress does not. Know why? These sites’ designers do.
There’s no two ways about it; style matters. And style applied to a web page design is not always just style for its own sake. It’s often a vital supporting element in effective design. Competent designers understand this. The nattering nabobs and little design generals of the online forums do not. Which is why there’s a difference between getting paid and getting comments in a forum.
So don’t mistake the presence of style for a lack of substance. Don’t forget context when evaluating or applying design. And don’t work for comments by doing what’s popular – work for clients and get paid for doing what’s effective.
ABOUT THE AUTHOR(S)
Carrie Spates is an Associate VP of Design at Siteworx, an award-winning digital experience agency with deep roots in experience design, web content management, e-commerce, digital asset management, and systems integration. She leads interaction design teams across the country, creating world-class experiences that validate the value, design, and usability of customer experiences while ensuring coherence of services and digital strategy across all digital platforms. Carrie is a champion of design ideas and a dedicated mentor to creative teams, supporting a collaborative approach to cross disciplines.
Matt has over five years of IT experience with specialization in user experience and user interface design. His project/industry experience includes: financial services, telecom, retail, pharmaceutical, utilities, chemicals, healthcare, and government. He is experienced with system implementation projects with responsibilities including concept development through implementation, testing, and go-live. He has specific expertise conducting user research, creating innovative designs, and setting strong usability standards. Before coming to Siteworx, Matt worked for LexisNexis as a Senior Product Designer where he was responsible for promoting user experience within an overall structure of deliverables that integrated the recommendations of the project team regarding user experience.