Communicating Design

Here are some great points made by Keith Robinson, of Blue Flavor, in his talk on design process and deliverables.

1. Documenting your design decisions is important, but it’s not the document, it’s the communication that matters. Involve stakeholders and communicate.

*

2. The Design Process you use depends on the projects needs. Here are some design deliverables and guidelines for when to use them:

*

3. Don’t use deliverables to build consensus. Designers should make the design decisions! Weak design consensus results in weak design. The designer should present the decisions 1^st and then create high quality deliverables. Great designers show stakeholders that their issues are understood, have a history of great work and can tie designs back to goals and use user research results.

*

4. Use a project brief. Focus on problems, not features. Clearly set goals and make sure all team members have reviewed the brief.

*

5. Create personas with all stakeholders and use the personas in scenarios.

*

6. Screen Description Diagrams are a great way to describe in detail (using real data) what you want to include on the screen. You should prioritize each screen element and describe how each element reflects the user’s goals. Leave out the visuals here to give the visual and interaction designers more control later.

*

7. Use wireframes to communicate interaction and layout. Be as detailed as possible. Annotate thoroughly to describe interaction. Also, remember to “move on” after a set number of iterations-> the goal is to create an app, not a perfect wireframe.

*

8. Keep your style guide short and up to date. Kevin uses 37 Signals whiteboard for his style guides.