UX + Engineering

Designers and engineers are often seen as complete opposites. Designers are portrayed to be sensitive creatives, and engineers as cold logisticians. But this doesn’t have to be the case. Join us (a designer and UI developer) as we show you how to collaborate together better and make amazing products.

You can teach better communication and empathy skills for everyone on your team, and we will show you how. You’ll leave this talk with a deeper understanding of how to bridge the gap between designers and developers through practical tips and tools we use for developing empathy on our teams.

Host: NDC Minnesota - Minneapolis, MN
Link: https://ndcminnesota.com/talk/ux-engineering-a-tale-of-two-cities

Transcript

1. UX
 +
 Engineering Technical Lead: @JoeKarlsson1 UX Architect: @EddieEcker
2. 2 Joe Karlsson @JoeKarlsson1 My Name is @JoeKarlsson /in/JoeKarlsson joekarlsson.com
3. 3 Edward Ecker @eddieecker My Name is /in/edwardecker
4. 4 What is this talk about?
5. 5 PART 1: Setting The Table
6. 6 Improving Team Morale And 
 Engagement J
7. 7 Driving Innovation E
8. 8 Getting “Lean” E
9. 9 Better Products Faster J
10. 10 What this talk isn’t about… E
11. 11 E Trying to make “Perfect” comps. E
12. E Hoarding designs until
 they are “ready”. E
13. 13 J Over Engineering. J
14. J
15. 15 Common Problems The Modern Evolution of a new Feature. Product Planning Dev Handoff Dev Sprint Feature Timeline UX
 Handoff E
16. 16 UX + Product Planning Dev Handoff Dev Sprint Feature Timeline Or, maybe it’s more like… E
17. 17 Feature Timeline Product / UX / Dev Ideation > Sprint > Production Ideally! E
18. 18 So, let’s talk! E
19. 19 PART 2: Dev DESIGN THINKING
20. How does it feel to walk in our customer’s shoes, today? EMPATHIZE E
21. What’s the worst problem the customer experiences that we control? Define E
22. How can we solve this problem today? Ideate J
23. 23 Good ideas can come from anywhere! Remember J
24. J Weigh in early in on potential solutions based on complexity. Review J
25. What could this new experience be once it’s fully fleshed out? Prototype E
26. J Move your favorite ideas to into user testing to vet their legitimacy. TEST E
27. J Micro Hackathons
28. 28 Sprint to the finish. PART 3: Sprint to the finish
29. 29 Sprint Handoff J J
30. 30 Design Dev Workshop! J
31. 31 • Keep it lean. Review tickets before you code. DDW Things to consider • Plan to checkin at least once more before sending things to QA. • Dev’s initiate! • Stop assuming! If you’re unsure, have a conversation. J • Lean on your Pattern Library!
32. 32 Designers, share what you know! E
33. 33 Engineers, share what you know! J
34. 34 PART 4: People > Process E
35. 35 Silos Suck. E
36. 36 Sit in close Proximity To your team. J
37. Checkout Ludo.team E
38. The MOST important slide J
39. COMMUNICATE! J
40. J
41. 41 • Get Engineers involved early and often! • Establish a clear vision as a team! • Share your knowledge! • Strive for innovation! • Collaborate! • Be a cool human!
42. 42 Questions & Answers
44. 44 Joe Karlsson @JoeKarlsson1 Let’s stay in touch @JoeKarlsson /in/JoeKarlsson joekarlsson.com
45. 45 Edward Ecker @eddieecker Let’s stay in touch /in/edwardecker
46. 46 yes, we are