December 7th, 2010
Deliverables are the bread-and-butter of the UX profession. We produce a ton of them. We’re constantly reading them. We send them to our clients and hope for their comments.
Our deliverables need good design. They perform a function, just like the work they’re describing. They either do their job well, or they miss the boat. Nobody wants to have their great ideas submerged into obscurity because the deliverables didn’t do their job.
In this week’s UIEtips, our good friend Dan Brown shares some wisdom about well-designed deliverables: they have to tell a story. Theme, journey, conflict, and characters — pieces that keep us riveted to that page turner — are all essential in great deliverables. I’m sure you’ll find several great ideas on how to make your own deliverables that much better.
Read the article, What Makes a Good Deliverable.
By the way, did you know we’ve teamed up with Dan’s company, EightShapes, to bring you a fabulous series of virtual seminars this winter. The first one, 5 Simple Principles to Improve Your Information Architecture, is next week and I’m really looking forward to it. Dan’s packed some great wisdom into it — stuff you shouldn’t miss. Read all the details.
How have you integrated story elements into your deliverables? We’d love to hear what’s worked and what hasn’t. Leave your thoughts below.Tweet