Freud asked, “What does a user really want?” Ten-plus years into web development, we still don’t know. One of the biggest problems in creating and delivering a site is how to decide, specify, and communicate exactly what we’re building and why. Use cases can help answer these questions by providing a simple, fast means to decide and describe the purpose of your project. In this quick-reading article, Messieurs Carr and Meehan introduce use cases and their, uh, uses.
More from A List Apart
Business communications benefit from better, tighter delivery—a technique we learned from fairy tales, Anne Gibson reminds us.
The same typefaces crop up everywhere on the web. But why? Jeremiah Shoaf thinks the answer might lie in cognitive biases.
User testing is a necessary part of the design process, not a luxury.
Tim Baxter encourages us to move beyond the “measles of markup” to write rich, semantic HTML and CSS. Only habit is stopping us.
Before you plan the trip, make sure you know who’s coming. Sophia Voychehovski tells us why action-first design is risky business.
Seeing clients as clueless or “difficult” is a red flag—for us. How to turn client confusion into better experiences.
Translate analytics into product paths with narrative structures. New excerpt from Donna Lichaw’s The User’s Journey.
In an excerpt from Design for Real Life, Eric A. Meyer and Sara Wachter-Boettcher discuss designing for stress cases.