Jared Spool’s Anatomy of a Design Decision argues that design decisions are be made on several levels. The decision level, a design is made on, reflects on the final product.
It’s not the purpose of this post to explain each level, however they do make sense for this post. The levels are:
- Unintentional design
- Self-design – design for me
- Genius design – we know what works from past experience
- Activity-focused design – design to support activities
- Experience-focused design – design for the experience – what happens in between activities
Jared Spool missed an important point.
The designer can progress from level to level in order to enable more abstract design decisions. In the latter levels, designers use user interface design patterns to add consistency to the user experience. A user experience is contextual to each design case, why Jared argues that design patterns only make sense when they are contextual to the specific design case.
So does that mean that design patterns of such that is based on UI-Patterns.com are built on false assumptions? No. Jared Spool missed an important point.
Design patterns work on multiple levels
Design patterns can be used on several levels. In broad terms, each level can be seen as helping describing implementation, flow, and context.
Design patterns aiding implementation
The lowest level is contextual to each design case. It defines that for a given site, the search box should be placed in the upper right, that form labels are to be placed directly above input fields, and that square thumbnails of images should have the dimensions of 100 × 100 pixels. When defining interface design patterns on this particular level, they can only be contextual to a specific design case; to one website.
This is the level Jared Spool refers to, and I don’t disagree with him. If you want to focus on delivering a consistent experience, design patterns on this level are needed. A service like Patternry will assist you in building your own private pattern library for your own projects.
Patterns of implementation are concerned purely with consistency across your pages. Defining and agreeing on how to implement specific features (a carousel or login box) help ensure consistency across every page.
Design patterns aiding flow
The middle level describes what building blocks of recurring solutions that solve common design problems we have available in our toolbox as designers. This level describes functionality and how it will affect flow.
Here designers choose between alternatives that solve the same problem, but will affect the flow and the composition of the experience as opposed to the consistency of experience discussed at the implementation level.
Contrasting patterns: registration
This is the level of design patterns that UI-Patterns.com focus on.
Where implementation patterns are tactical, flow patterns are strategic. Flow patterns help users experience a consistent flow throughout your site. They are abstract interpretations of several different implementations.
Design patterns aiding context
The highest level of user interface design patterns are the ones who define what context we are in. Are we building an artist, museum, automotive, magazine, or e-commerce site? Choosing to build an artist site, there are several things that are mandatory: an event calender, a biography, discography, and maybe a portfolio. Welie.com have a bunch these patterns in their library.
Design patterns save both you and your users time. You will save time by not reinventing the wheel. Users save time in learning new interface systems.
Design patterns are empirically proven solutions to common problems that were deemed so effective that more and more started using them until they became commonplace. They are your toolbox that will help you put together both creative, valuable, and effective solutions – as long as you know enough about them to choose the right one for the right job.