Beginners Guide to TikTok for Search - Rachel Pearson - We are Tilt __ Bright...
10 Team Goals for Effective Design Specifications
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
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!
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.