Working with developers

A presentation at Batony #5 in October 2019 in Łódź, Poland by Łukasz Przywarty

Slide 1

Slide 1

Batony #5 – October 2, 2019 WORKING WITH DEVELOPERS Łukasz Przywarty

Slide 2

Slide 2

Łukasz Przywarty Head of Design, Infermedica

Slide 3

Slide 3

Once upon a time, there was a designer… @LukaszPrzywarty

Slide 4

Slide 4

Incorrect animations 1 Expectations vs reality vs 2 3 Missing elements Wrong colors

Slide 5

Slide 5

This is not what I’ve designed. Developers don’t care about design. There was too much to do and too little time. I can’t talk to developers. It’s not my fault. ! @LukaszPrzywarty

Slide 6

Slide 6

1 PREPARE

Slide 7

Slide 7

Become a design advocate

Slide 8

Slide 8

First, explain the basics What is the job of a designer? What is the business value of design? What are the examples of great product design? @LukaszPrzywarty

Slide 9

Slide 9

Next steps Host design workshops Show off your work (e.g. “demo days”) Invite developers to research sessions, etc. @LukaszPrzywarty

Slide 10

Slide 10

“ I saw Łukasz designing this. Paweł, Infermedica

Slide 11

Slide 11

Get to know your developers

Slide 12

Slide 12

How? Grab a coffee and… talk! Learn how do developers work (process, tools) Find out how do they like to communicate @LukaszPrzywarty

Slide 13

Slide 13

2 DESIGN

Slide 14

Slide 14

Include developers in your design process

Slide 15

Slide 15

“ The ultimate goal is to feel included. Jake Archibald, Developer at Google @LukaszPrzywarty

Slide 16

Slide 16

How? Remote work is not an excuse Collaborate from the start Brainstorm, research, design together Leverage the knowledge of engineers

Slide 17

Slide 17

Share your work early and often

Slide 18

Slide 18

How? Share prototypes (InVision, etc.) Share user research findings Ask for feedback

Slide 19

Slide 19

Justify your decisions

Slide 20

Slide 20

How? Show the path that led you to the current design Discuss the pros and cons of different solutions Use data

Slide 21

Slide 21

Answer “Why?”

Slide 22

Slide 22

Think like an engineer

Slide 23

Slide 23

How? Find out how things work (read the docs, use developer tools, etc.) Learn a few technical terms (API, cache, requests, etc.) Consider learning to code

Slide 24

Slide 24

What if there’s no picture? Edge cases What happens when errors occur? What happens when there’s no Internet access? What happens if the element is empty? @LukaszPrzywarty

Slide 25

Slide 25

Hand off your designs

Slide 26

Slide 26

“ The best hand-off is no hand-off Bjørn Rostad, Product Designer at Dropbox @LukaszPrzywarty

Slide 27

Slide 27

How? Find out what the developers need from you Provide as much information as you can Don’t made developers guess Unless you want to test their creativity! @LukaszPrzywarty

Slide 28

Slide 28

Use hand-off tools

Slide 29

Slide 29

Create a style guide

Slide 30

Slide 30

Design all possible flows

Slide 31

Slide 31

Prototype in code

Slide 32

Slide 32

Use real data (InVision Craft, populate.design, tinyfac.es, etc.) Remember about language differences

Slide 33

Slide 33

3 DEVELOP

Slide 34

Slide 34

Regularly check progress

Slide 35

Slide 35

How? Set up the design review process Make use of developers’ meetings Prioritize design tweaks @LukaszPrzywarty

Slide 36

Slide 36

Share your comments

Slide 37

Slide 37

4 FOLLOW UP

Slide 38

Slide 38

Developers are not your enemies @LukaszPrzywarty

Slide 39

Slide 39

“ How can we honestly build empathy for our users if we can’t empathize with each other, or those outside of our towers? Mustafa Kurtuldu, Design Advocate at Google @LukaszPrzywarty

Slide 40

Slide 40

Get to a solution together @LukaszPrzywarty

Slide 41

Slide 41

Sources • • • • • • A mindful design process Creating a collaborative environment Everyone is a designer. Get over it How designers work with developers How to work effectively with engineers The beauty of imperfection in interface design • The nine states of design • The power of experience mapping • When design feels like an uphill battle • Who is responsible for design? @LukaszPrzywarty

Slide 42

Slide 42

THANK YOU! @LukaszPrzywarty on Twitter lukasz@przywarty.com