This talk was given at Interaction 16 in Helsinki, Finland.

1. 10Team Goals
for Effective Design
Specifications
Jack Moffett
Manager Apps Development – GUI
Inmedius, a Boeing Company
@jackmoffett | jackmoffett@mac.com
designaday.tumblr.com

2. Poor documentation is
a source of
unmet expectations
misunderstood requirements
incorrect implementation
unexpected complications
blown estimates
The cup that can only be half-full. by vrogy

3. ARGUMENTS
Buttin’ heads by shellac

4. CONSISTENCY
Repeating Lines - Project 50/50 (Week 23) by Jason Mrachina

5. CONSISTENCY

6. CONSISTENCY

7. We are all different by Paolo Braiuca
A foolish consistency is the hobgoblin of little minds.
Ralph Waldo Emerson

8. Flexible Flamingo by Jeff S. PhotoArt at HDCanvas.ca
Flexibility

9. Flexible Flamingo by Jeff S. PhotoArt at HDCanvas.ca
Flexibility

10. Flexible Flamingo by Jeff S. PhotoArt at HDCanvas.ca
Flexibility

11. Flexible Flamingo by Jeff S. PhotoArt at HDCanvas.ca
Flexibility

12. Flexible Flamingo by Jeff S. PhotoArt at HDCanvas.ca
Flexibility

13. Flexible Flamingo by Jeff S. PhotoArt at HDCanvas.ca
Flexibility

14. Thoroughness
nested un-whole cube in red oak by Jared Tarbell

15. Thoroughness
nested un-whole cube in red oak by Jared Tarbell

16. Thoroughness
nested un-whole cube in red oak by Jared Tarbell

17. Thoroughness
nested un-whole cube in red oak by Jared Tarbell

18. Unintelligent Design by Pete Ashton
Correctness

19. Unintelligent Design by Pete Ashton
Correctness

20. Unintelligent Design by Pete Ashton
Correctness

21. Unintelligent Design by Pete Ashton
Correctness

22. Unintelligent Design by Pete Ashton
Correctness

23. Unintelligent Design by Pete Ashton
Correctness

24. Conciseness Thou Art Verbose in Thy Praise by Jason Rinka

25. Conciseness Thou Art Verbose in Thy Praise by Jason Rinka

26. Clarity

27. Clarity
• Proofread (or have someone else do it).
• Develop a common vocabulary.
• Refer to specific UI elements by name.
• When using names, give them
consistent typographic treatment.
• Use images.
• Use the language of your readers.

28. Clarity
• Proofread (or have someone else do it).
• Develop a common vocabulary.
• Refer to specific UI elements by name.
• When using names, give them
consistent typographic treatment.
• Use images.
• Use the language of your readers.
Design your document!

29. Clarity
• Proofread (or have someone else do it).
• Develop a common vocabulary.
• Refer to specific UI elements by name.
• When using names, give them
consistent typographic treatment.
• Use images.
• Use the language of your readers.
Design your document!

30. The Eye by Augusto Serna
Visuality

31. The Eye by Augusto Serna
Visuality
the quality or state of being visual or visible

32. The Eye by Augusto Serna
Visuality
the quality or state of being visual or visible

33. Organization
Looking for by ilConte

34. Organization
Looking for by ilConte

35. Organization
Looking for by ilConte

36. Organization
Looking for by ilConte

37. Organization
Looking for by ilConte

38. Organization
Looking for by ilConte

39. Shareability
Macro of two white straws by Horia Varlan

40. Shareability
Macro of two white straws by Horia Varlan

41. Locked Out by Chris Yarzab
inclusiveness

42. Locked Out by Chris Yarzab
inclusiveness
Developers
Testers
Product Management
Sales & Marketing
Customers
Users

43. ConclusionYou aren’t creating documentation for its own sake.
There are problems your documentation is solving.
There are needs being fulfilled.

44. ConclusionInstitute a process that ensures
correctness prior to implementation,
during testing, and beyond.
Iteratively evaluate and improve.

45. ConclusionResponsibly reduce your documentation.
The more you can show, the less you
have to describe.
Design documentation for its target
audience.

46. QuestionsConsistency
Flexibility
Thoroughness
Correctness
Conciseness
Clarity
Visuality
Organization
Shareability
Inclusiveness
Jack Moffett
Manager Apps Development – GUI
Inmedius, a Boeing Company
@jackmoffett | jackmoffett@mac.com
designaday.tumblr.com

47. More