Particularly within tech, design and development are notorious for collaboration gaps. While there are plenty of resources available that advocate for catalyzing collaboration between the teams, what we see far less are stories of that process in application. We'll cover how Atlassian’s HipChat team worked to adjust its culture to one fine-tuned for collaboration between design and development, and will provide actionable takeaways to adapt to your team's needs. Products covered: HipChat, Confluence, JIRA Software

1. BRANTLEY ESSARY • DEVELOPER • ATLASSIAN
Practiced Curiosity
Building Collaboration between
Development and Design

3. CAUSES
PROBLEMS
SOLUTIONS
Agenda

4. Our Problems

5. Roadmaps not
in sync

6. Lack of clarity
between
teams

7. Developers
designing,
without
design review

8. What causes this?

9. • Big cool statistic
• 2,56
9
• Add-Ons in Marketplace
No formal processes for
collaboration

10. • Big cool statistic
• 2,56
9
• Add-Ons in Marketplace
…maybe developers don’t
100% understand what UX is

11. • Big cool statistic
• 2,56
9
• Add-Ons in Marketplace
Designers not regarded as
major stakeholders

12. • Big cool statistic
• 2,56
9
• Add-Ons in Marketplace
Designers not regarded as
major stakeholders

13. Story time:
A Lack of Curiosity

14. What we can do to fix this

15. Have ALL
stakeholders
in planning
meetings

16. Have ALL
stakeholders
in planning
meetings
Product Management
Design
Engineering

17. Share your plan

18. Design
Reviews!

19. It’s about building products
that truly matter

20. To Summarize

21. Plan with all
stakeholders
Product Management, Design, Engineering

22. Share your team’s plan

23. Review work with
designers

24. Thank you!
BRANTLEY ESSARY • DEVELOPER • ATLASSIAN