Design documentation

A presentation at IXDA Port Harcourt in June 2020 in by Eriol Fox

Slide 1

Slide 1

Design documentation How documentation can level up your design processes. @erioldoesdesign @ixdaph #ixda

Slide 2

Slide 2

( Hi, I’m Eriol. Ehh-roll). I’m a humanitarian designer. I’m part of an Open Source Design movement. 10 years in digital product design and UX. @erioldoesdesign @ixdaph #ixda

Slide 3

Slide 3

Designers and people who work with designers: 1. What information best helps you to work together? E.g. It’s really helpful when I know the constraints that developers are aware of and how that affects design. @erioldoesdesign @ixdaph #ixda

Slide 4

Slide 4

Designers and people who work with designers: 2. What do you wish other teams members knew about your work and the way you work? E.g. How long it takes and what I do when I conduct user research/testing and the way I interpret the results into design. @erioldoesdesign @ixdaph #ixda

Slide 5

Slide 5

Designers and people who work with designers: 3. What method of communication works best for you? E.g. I find it easier to record a conversation and then transcribe the conversation with the key points and decisions picked out. @erioldoesdesign @ixdaph #ixda

Slide 6

Slide 6

Ideas on how you can use documentation to improve this: 1. As a designer, I can catalogue the existing core UI components in a dev framework and what might be missing for a product I’m designing. 2. As a designer, I can invite team members as active or silent participants into my process and/or I could explain as simply as possible how I came to a design decision. 3. I can share audio recordings or notes from conversations and share them with my team widely. I could also take the time to explain in new conversations what decisions were made and why. @erioldoesdesign @ixdaph #ixda

Slide 7

Slide 7

What springs to your mind when you think of the word ‘documentation’? Documentation is also know in the shortened form ‘docs’ @erioldoesdesign @ixdaph #ixda

Slide 8

Slide 8

(Too)Technical Specifications Manuals Guides Tech only Complex information Giving away my ideas Boring papers/ writing @erioldoesdesign @ixdaph #ixda

Slide 9

Slide 9

‘Official’ definitions: 1. Documentation is a set of documents provided on paper, or online, or on digital or analog media, such as audio tape or CDs. 1. Good documentation—including installation guides, user guides, white papers, FAQs, and more—provides users a roadmap to using software and hardware. Article via open source.com here @erioldoesdesign @ixdaph #ixda

Slide 10

Slide 10

What is open source? OSS can be a “tool”, a service or project that is made available under an ‘open license’ such as Creative Commons, APGL or MIT license. The source code and often all other vital components of the project live in a fully disclosed and open way on the web, typically on sites like GitHub or Gitlab. @erioldoesdesign @ixdaph #ixda

Slide 11

Slide 11

What is open source? Typically, OSS is being perceived as something that you can use for free and also adapt and change in ways that are useful to you and/or your organisation. And OSS often is a collaborative community effort, to build and improve a ‘technology’ or product, together. Contributing to OSS is part of many developers lives, and where they learn, share and mentor each other, and how they ‘give back’ to their community in a way. In case that reminds you of IxDA’s mission: Correct. Big similarities. @erioldoesdesign @ixdaph #ixda

Slide 12

Slide 12

How design fits in open source Design hasn’t got a well established place in open source software/projects. Largely due to the space being initiated by developers/coders and continuing to cater to these kind of skills/ backgrounds. This is changing and you can be on the ‘ground floor’ of this change. @erioldoesdesign @ixdaph #ixda

Slide 13

Slide 13

A good ‘playground’ for designers. @erioldoesdesign @ixdaph #ixda

Slide 14

Slide 14

Docs are key for open source design and how this helps all designers. @erioldoesdesign @ixdaph #ixda

Slide 15

Slide 15

Why we need more design documentation. @erioldoesdesign @ixdaph #ixda

Slide 16

Slide 16

‘The big reveal’ is harmful to current and future design practices. @erioldoesdesign @ixdaph #ixda

Slide 17

Slide 17

The best knowledge isn’t always from published authors or contained in books. @erioldoesdesign @ixdaph #ixda

Slide 18

Slide 18

Writing articles are important but are they ‘docs’? @erioldoesdesign @ixdaph #ixda

Slide 19

Slide 19

Examples: Design discovery and research @erioldoesdesign @ixdaph #ixda

Slide 20

Slide 20

@erioldoesdesign @ixdaph #ixda

Slide 21

Slide 21

@erioldoesdesign @ixdaph #ixda

Slide 22

Slide 22

@erioldoesdesign @ixdaph #ixda

Slide 23

Slide 23

@erioldoesdesign @ixdaph #ixda

Slide 24

Slide 24

@erioldoesdesign @ixdaph #ixda

Slide 25

Slide 25

@erioldoesdesign @ixdaph #ixda

Slide 26

Slide 26

Open Design’s five core design activities. @erioldoesdesign @ixdaph #ixda

Slide 27

Slide 27

Examples: Design decision and synthesis @erioldoesdesign @ixdaph #ixda

Slide 28

Slide 28

@erioldoesdesign @ixdaph #ixda

Slide 29

Slide 29

@erioldoesdesign @ixdaph #ixda

Slide 30

Slide 30

@erioldoesdesign @ixdaph #ixda

Slide 31

Slide 31

@erioldoesdesign @ixdaph #ixda

Slide 32

Slide 32

@erioldoesdesign @ixdaph #ixda

Slide 33

Slide 33

@erioldoesdesign @ixdaph #ixda

Slide 34

Slide 34

Examples: What you and your team call ‘good design’ @erioldoesdesign @ixdaph #ixda

Slide 35

Slide 35

@erioldoesdesign @ixdaph #ixda

Slide 36

Slide 36

Examples: Design ‘file’ docs @erioldoesdesign @ixdaph #ixda

Slide 37

Slide 37

@erioldoesdesign @ixdaph #ixda

Slide 38

Slide 38

@erioldoesdesign @ixdaph #ixda

Slide 39

Slide 39

@erioldoesdesign @ixdaph #ixda

Slide 40

Slide 40

Examples: How to get (designers) involved @erioldoesdesign @ixdaph #ixda

Slide 41

Slide 41

@erioldoesdesign @ixdaph #ixda

Slide 42

Slide 42

Good habits @erioldoesdesign @ixdaph #ixda

Slide 43

Slide 43

Getting familiar with an ‘open’ home for your design docs @erioldoesdesign @ixdaph #ixda

Slide 44

Slide 44

Summarising/explaining your design @erioldoesdesign @ixdaph #ixda

Slide 45

Slide 45

Careful! This does not mean ‘selling’ your ideas! @erioldoesdesign @ixdaph #ixda

Slide 46

Slide 46

Careful! This also does not simply mean ‘a how-to tutorial’. @erioldoesdesign @ixdaph #ixda

Slide 47

Slide 47

MVDD’s or Minimum viable design docs for software @erioldoesdesign @ixdaph #ixda

Slide 48

Slide 48

Check out projects with designers involved: http://opensourcedesign.net/ https://github.com/ushahidi/tenfour https://docs.ushahidi.com/platform-developer-documentation/design/designprocess https://github.com/Erioldoesdesign/opendesign https://github.com/foss-responders/fossresponders.com https://github.com/jcklpe/open-source-branding-toolkit https://github.com/kantord/LibreLingo @erioldoesdesign @ixdaph #ixda

Slide 49

Slide 49

Where to look for guidance & advice. https://opensource.com/article/20/4/documentation https://opensource.com/tags/documentation https://docusaurus.io/ https://github.com/hotosm/ux-review https://opensource.google/docs/ https://thegooddocsproject.dev/ https://www.writethedocs.org/ https://increment.com/documentation/documentation-as-a-gateway-to-open-source/ https://blog.teamtreehouse.com/contributing-open-source-documentation https://medium.com/capital-one-tech/art-of-open-source-documentation-5b8b3f5b0ab https://www.digitalocean.com/blog/documentation-as-an-open-source-practice/? @erioldoesdesign @ixdaph #ixda