UIEtips: Designs and deliverables are haikus, not epic poems

Jared Spool

January 29th, 2014

In today’s UIEtips, we’re publishing an excerpt from the UXmatters article “Developing UX Agility: Letting Go of Perfection” by Carissa Demetris, Chris Farnum, Joanna Markel, and Serena Rosenhan. In it, Chris Farnum talks about design deliverables and their role in an incremental approach to your design.

If you want to hear more about Chris’ thinking on design deliverables join us for our January 30 virtual seminar Choosing the Right Wireframe Strategy for Your Project.

Here’s an excerpt from the article:

Once you have a firm grasp of the goals for a project and the functionality you need to design, the next steps for many UX professionals are creating user stories, wireframes, and prototypes. To kick off design, we often brainstorm and sketch. Often, cutting edge Web sites and a desire to meet or exceed competitors fuel our ideas in part. While you are in brainstorm mode, it’s certainly a good idea to sketch out a full user experience, complete with all the latest bells and whistles that would delight users and impress stakeholders.

But when you begin to craft a user experience for the initial stories that you’ll deliver to your Development team for implementation, you’ll need to be a strict editor and include only the core user interface elements. Limiting scope in this way can be challenging when you are used to waterfall approach, in which you may have only one chance to document all of the user interface elements you think your design should include.

Read the article Designs and Deliverables are Haikus, Not Epic Poems.

How does your team limit project scope in the early design stages? Tell us about it below.

One Response to “UIEtips: Designs and deliverables are haikus, not epic poems”

  1. Marco Brambilla Says:

    Dear Jared,
    I fully agree with the thesis of the article you are mentioning.
    Keeping focused and simple is crucial. At the same time, I think it’s important to enable expansion to more and more complete experience without throwing away what you have done so far.
    In our experience, we obtained this through model-driven development: in large-scale Web projects, from scenarios and user stories we move to software models with agile and lean approach (namely, using our own tool and the OMG IFML notation (www.ifml.org).
    We found it optimal in terms of binding between requirements/scenarios and implementation (also thanks to automatic code generation), and at the same time it allows very quick feedback cycles and improvement / expansion /refinement.


Add a Comment