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

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

The divide between design and development can be vast. Designers lob something over the wall for development without knowledge or perspective of technical limitations, and developers are left to sort out requirements and edge cases. No one is satisfied when designers' visions aren't implemented or developers are expected to explain why something can't be built.

It doesn't have to be this way. I'll cover solutions you can implement on your team to bridge the divide and do your best work.

This version of the talk was presented at Geo Rodeo in Austin, May 2017.

3993dbd973f71e3f2a9dd155155accc4?s=128

Glynnis Ritchie

May 19, 2017
Tweet

Transcript

  1. 3.

    How to Bridge the Divide Between Development and Design Setting

    Fire to Silos @glynnisritchie @glynnisritchie
  2. 7.

    “ 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
  3. 8.

    “ 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
  4. 18.

    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
  5. 20.
  6. 21.
  7. 22.
  8. 23.

    “Without requirements or design, programming is the art of adding

    bugs to an empty text file.” –Louis Srygley @glynnisritchie
  9. 31.

    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
  10. 32.

    “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
  11. 37.

    “ 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
  12. 38.

    “ 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
  13. 43.
  14. 46.

    @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
  15. 50.

    @glynnisritchie DESIGN DEVELOPMENT user testing to validate revisions for scope

    review of design implementation recommended alternatives review of feasibility
  16. 51.

    @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.”
  17. 53.
  18. 54.

    The team and your company’s perception of them benefit from

    a common, visible goal. @glynnisritchie