Architects of Experience: Creating Connections Beyond Code
summary
Argues that developers must go beyond lines of code to own outcomes, break organizational silos and design end-to-end journeys — using cross‑functional squad model teams to surface root causes (not symptoms), unify trapped dark data, and individualize customer flows like the staged “Anya” example. Recommends partnering with product, support and sales, shifting focus to system design as AI changes tooling, and cites concrete Twilio building blocks — messaging, voice, email, video, authentication, contact center — plus a $20 Twilio credit to experiment.
AI-written summary · about
chapters (15)
- 0:00Introduction and passion
- 1:19About the speaker
- 2:19Evolution of technology and roles
- 3:44Developers as experience creators
- 5:07Beyond code to systems design
- 6:08Crafting experiences not just code
- 7:09Silos and dark data challenge
- 8:13Cross-functional teamwork
- 9:56Removing friction in journeys
- 10:58Building internal tribes
- 12:21Tribal leadership and Spotify model
- 13:25Embracing architect role
- 14:30Empathy and collective capability
- 15:33You are the differentiator
- 16:34Call to action and closing
related talks
03mCareer Advice for Architects
59mHow to Think Like an Architect
40mBeyond Code: Skills For Impactful Development That Makes a Difference
31mThe Effective Developer - Work Smarter, Not Harder
19mYou Are Enough: Bringing your Whole Self To Your Career
05mFull Stack Isn't Enough - The Rise of the Full Product Developer
03mFrom puzzles to products
44mTeams That Propel People Forward