Slide 1

Slide 1 text

How to Bridge the Divide Between Development and Design Setting Fire to Silos @glynnisritchie

Slide 2

Slide 2 text

Glynnis Ritchie UX Engineer, New Orleans @glynnisritchie

Slide 3

Slide 3 text

How to Bridge the Divide Between Development and Design Setting Fire to Silos @glynnisritchie @glynnisritchie

Slide 4

Slide 4 text

@glynnisritchie

Slide 5

Slide 5 text

@glynnisritchie

Slide 6

Slide 6 text

@glynnisritchie

Slide 7

Slide 7 text

“ Our current implementation of the phone system needs to be significantly improved through integration with our multiple customer relationship management systems. We also need improved search capabilities so that people answering the phones can more quickly assist customers. @glynnisritchie

Slide 8

Slide 8 text

“ Our current implementation of the phone system needs to be significantly improved through integration with our multiple customer relationship management systems. We also need improved search capabilities so that people answering the phones can more quickly assist customers. @glynnisritchie

Slide 9

Slide 9 text

Building Search (It’s easy, right?) @glynnisritchie

Slide 10

Slide 10 text

Zero to production in 4 months. @glynnisritchie

Slide 11

Slide 11 text

But what’s the secret? Yeah, yeah. That’s cool and all. @glynnisritchie

Slide 12

Slide 12 text

Let’s Talk about Silos @glynnisritchie

Slide 13

Slide 13 text

@glynnisritchie

Slide 14

Slide 14 text

@glynnisritchie

Slide 15

Slide 15 text

@glynnisritchie

Slide 16

Slide 16 text

@glynnisritchie

Slide 17

Slide 17 text

@glynnisritchie

Slide 18

Slide 18 text

When designers don't see their designs implemented the way they envisioned and developers must explain why it can’t be built, no one is happy. @glynnisritchie

Slide 19

Slide 19 text

No one enjoys working this way. @glynnisritchie

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

“Without requirements or design, programming is the art of adding bugs to an empty text file.” –Louis Srygley @glynnisritchie

Slide 24

Slide 24 text

@glynnisritchie @glynnisritchie

Slide 25

Slide 25 text

@glynnisritchie @glynnisritchie

Slide 26

Slide 26 text

BRIDGING THE DIVIDE @glynnisritchie Polish those soft skills!

Slide 27

Slide 27 text

Life outside the silo is scary. @glynnisritchie

Slide 28

Slide 28 text

“Yes, and…” @glynnisritchie

Slide 29

Slide 29 text

Establish a safe space. @glynnisritchie

Slide 30

Slide 30 text

unicorn @glynnisritchie

Slide 31

Slide 31 text

Interdisciplinarity: the combining of two or more disciplines into one activity; creating something new by crossing boundaries as new needs emerge. https:/ /en.wikipedia.org/wiki/Interdisciplinarity @glynnisritchie

Slide 32

Slide 32 text

“I have experienced first-hand what happens to a project when there is a front-end dev with a strong design sensibility and when there is one without it. In terms of the final design, the difference is as stark as night and day.” Agile UX in the Enterprise, UX Pin @glynnisritchie

Slide 33

Slide 33 text

Interdisciplinary skills and team members are key.

Slide 34

Slide 34 text

Don’t be afraid to ask the obvious questions.

Slide 35

Slide 35 text

Repeat things back to your team mates.

Slide 36

Slide 36 text

DEFINE the problem @glynnisritchie before you argue about the solution.

Slide 37

Slide 37 text

“ Our current implementation of the phone system needs to be significantly improved through integration with our multiple customer relationship management systems. We also need improved search capabilities so that people answering the phones can more quickly assist customers. @glynnisritchie

Slide 38

Slide 38 text

“ Our current implementation of the phone system needs to be significantly improved through integration with our multiple customer relationship management systems. We also need improved search capabilities so that people answering the phones can more quickly assist customers. @glynnisritchie

Slide 39

Slide 39 text

@glynnisritchie

Slide 40

Slide 40 text

collaboration FIRST @glynnisritchie Don’t let hand offs be the only time you talk to each other.

Slide 41

Slide 41 text

@glynnisritchie

Slide 42

Slide 42 text

@glynnisritchie

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

Share meetings. @glynnisritchie

Slide 45

Slide 45 text

@glynnisritchie

Slide 46

Slide 46 text

@glynnisritchie “Too little collaboration means information lost, and designs lack direction. Too much ‘heads- down time’ and the designers find themselves siloed from the rest of the process, handing off their work rather than building something better together.” https:/ /www.invisionapp.com/blog/tuning-design-process/ –Mel DeStefano

Slide 47

Slide 47 text

@glynnisritchie wocintechchat.com

Slide 48

Slide 48 text

@glynnisritchie wocintechchat.com

Slide 49

Slide 49 text

@glynnisritchie DESIGN DEVELOPMENT estimates of effort technical feasibility performance considerations high-level vision user flows visual check of requirements

Slide 50

Slide 50 text

@glynnisritchie DESIGN DEVELOPMENT user testing to validate revisions for scope review of design implementation recommended alternatives review of feasibility

Slide 51

Slide 51 text

@glynnisritchie http:/ /www.gv.com/sprint/ “The sprint gives you a superpower: You can fast- forward into the future to see your finished product and customer reactions, before making any expensive commitments.”

Slide 52

Slide 52 text

DESIGN FOR THE IDEAL STATE @glynnisritchie then scale back or define iterative releases.

Slide 53

Slide 53 text

No content

Slide 54

Slide 54 text

The team and your company’s perception of them benefit from a common, visible goal. @glynnisritchie

Slide 55

Slide 55 text

@glynnisritchie

Slide 56

Slide 56 text

Glynnis Ritchie UX Engineer, New Orleans @glynnisritchie