August 31st, 2010
The Vulcans had something good with that mind-meld thing. Just put your fingertips on someone else’s forehead and your two minds become one. I wonder if Vulcan designers used that technique to ensure everyone knew how to come up with a coherent, integrated design, even though they all worked on different pieces?
Without the mind-meld thing, we have to resort to more primitive approaches to get everyone on the same page. In the past, we’ve tried templates, guidelines, and style guides. However, these have not proven to be very effective and end up frustrating teams more than helping the design process.
A few years back, we started seeing the emergence of pattern libraries as a solution to this problem. However, recently our research has shown us that pattern libraries only get you so far. For the rest of the solution, a component library can fill the gaps.
We’re revisiting an article that Nathan Curtis wrote for us in January 2009. Nathan does a great job outlining what patterns and components are and how they’re related. I think you’ll find this article quite beneficial and a good refresher if you’re already working with patterns and components.
Read the article, Components Versus Patterns.
If you’re thinking a pattern or component library can help your team be more efficient and create better designs, then you’ll want to check out Nathan’s full-day workshop: Standards, Reuse, Consistency, & Libraries. Nathan received rave reviews on a similar workshop he presented at the Web App Summit in 2009. Get more details on his workshop and the other 7 at http://uiconf.com.
Nathan is presenting at this year’s UI15 conference. Explore his workshop and the other full-day workshops. Planning on attending? Register by 9/9/10 for the lowest rate.Tweet