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

3993dbd973f71e3f2a9dd155155accc4?s=47 Glynnis Ritchie
February 24, 2018

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. This talk will introduce solutions you can implement on your team to bridge the divide and do your best work. Using an internal project at Rackspace as a case study, Glynnis will talk about why upfront planning, identifying the problem before agreeing on a solution, and cross-disciplinary collaboration are crucial to successful projects.

This version of the talk was presented at Activate Conf in Baton Rouge, February 2018.

3993dbd973f71e3f2a9dd155155accc4?s=128

Glynnis Ritchie

February 24, 2018
Tweet

Transcript

  1. 1.

    Setting Fire to Silos How to Bridge the Divide Between

    Development and Design 
 Glynnis Ritchie
  2. 4.

    How to Bridge the Divide Between Development and Design Setting

    Fire to Silos @glynnisritchie @glynnisritchie
  3. 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
  4. 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 “
  5. 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
  6. 20.
  7. 21.
  8. 22.
  9. 23.

    Without requirements or design, programming is the art of adding

    bugs to an empty text file. –Louis Srygley @glynnisritchie “
  10. 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
  11. 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 “
  12. 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 “
  13. 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 “
  14. 42.
  15. 45.

    @glynnisritchie DESIGN DEVELOPMENT PLANNING 1 month 3 months 2 weeks

    Unsuccessful Project Timeline: Design as a Band-aid
  16. 46.

    @glynnisritchie FIXING DESIGN/UX ISSUES DEVELOPMENT DESIGN 2 months 3 months

    2 months Unsuccessful Project Timeline: Silos & Rework
  17. 47.

    @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 “
  18. 48.

    @glynnisritchie ITERATIVE DEVELOPMENT & DESIGN VISION & NORTH STAR DESIGN

    2 weeks 3 months Successful Project Timeline: Agile Cross-Disciplinary Collaboration DESIGN DEV DESIGN DEV DESIGN DEV
  19. 50.

    @glynnisritchie DESIGN DEVELOPMENT user testing to validate revisions for scope

    review of design implementation recommended alternatives review of feasibility
  20. 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. “
  21. 54.

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

    a common, visible goal. @glynnisritchie
  22. 60.

    If everyone starts with the same information, they can make

    better decisions on behalf of the team. @glynnisritchie
  23. 70.

    Developers would much rather leave design decisions to designers. They

    may not even know when they’re making a design decision. @glynnisritchie
  24. 72.

    As a product manager, being involved in design and development

    can help you keep your team focused. @glynnisritchie
  25. 73.

    You can’t accomplish any of this (especially shipping an ambitious

    project quickly) if you aren’t in the room. @glynnisritchie