Tweet
Tweet

Slide 1

Slide 1 text

10Team Goals for Effective Design Specifications Jack Moffett Manager Apps Development – GUI Inmedius, a Boeing Company @jackmoffett | jackmoff[email protected] designaday.tumblr.com

Slide 2

Slide 2 text

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

Slide 3

Slide 3 text

ARGUMENTS Buttin’ heads by shellac

Slide 4

Slide 4 text

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

Slide 5

Slide 5 text

CONSISTENCY

Slide 6

Slide 6 text

CONSISTENCY

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

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

Slide 9

Slide 9 text

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

Slide 10

Slide 10 text

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

Slide 11

Slide 11 text

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

Slide 12

Slide 12 text

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

Slide 13

Slide 13 text

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

Slide 14

Slide 14 text

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

Slide 15

Slide 15 text

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

Slide 16

Slide 16 text

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

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

Unintelligent Design by Pete Ashton Correctness

Slide 19

Slide 19 text

Unintelligent Design by Pete Ashton Correctness

Slide 20

Slide 20 text

Unintelligent Design by Pete Ashton Correctness

Slide 21

Slide 21 text

Unintelligent Design by Pete Ashton Correctness

Slide 22

Slide 22 text

Unintelligent Design by Pete Ashton Correctness

Slide 23

Slide 23 text

Unintelligent Design by Pete Ashton Correctness

Slide 24

Slide 24 text

Conciseness Thou Art Verbose in Thy Praise by Jason Rinka

Slide 25

Slide 25 text

Conciseness Thou Art Verbose in Thy Praise by Jason Rinka

Slide 26

Slide 26 text

Clarity

Slide 27

Slide 27 text

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.

Slide 28

Slide 28 text

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!

Slide 29

Slide 29 text

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!

Slide 30

Slide 30 text

The Eye by Augusto Serna Visuality

Slide 31

Slide 31 text

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

Slide 32

Slide 32 text

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

Slide 33

Slide 33 text

Organization Looking for by ilConte

Slide 34

Slide 34 text

Organization Looking for by ilConte

Slide 35

Slide 35 text

Organization Looking for by ilConte

Slide 36

Slide 36 text

Organization Looking for by ilConte

Slide 37

Slide 37 text

Organization Looking for by ilConte

Slide 38

Slide 38 text

Organization Looking for by ilConte

Slide 39

Slide 39 text

Shareability Macro of two white straws by Horia Varlan

Slide 40

Slide 40 text

Shareability Macro of two white straws by Horia Varlan

Slide 41

Slide 41 text

Locked Out by Chris Yarzab inclusiveness

Slide 42

Slide 42 text

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

Slide 43

Slide 43 text

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

Slide 44

Slide 44 text

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

Slide 45

Slide 45 text

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

Slide 46

Slide 46 text

Questions Consistency Flexibility Thoroughness Correctness Conciseness Clarity Visuality Organization Shareability Inclusiveness Jack Moffett Manager Apps Development – GUI Inmedius, a Boeing Company @jackmoffett | jackmoff[email protected] designaday.tumblr.com

Slide 47

Slide 47 text

More