~/talk

Function and Form: The Case for UI/UX Design as a Platform Engineering Superpower

links:none on file
links:none on file
slides:none on file

Argues that adding UX to platform engineering raises adoption by 25% adoption increase, cuts onboarding and speeds delivery by applying empathize → define → ideate → prototype → test, and catches costly mistakes early where $1 on design saves $10 in dev and $100 post-release. Recommends small scoped IDP work, naming the platform, building a cross-team council, using component systems (Rancher + Storybook) or Backstage on Kubernetes, and favoring extensible buy-or-contribute approaches.

AI-written summary · about

  1. 0:00UI/UX in platform engineering
  2. 1:48Design core to platform engineering
  3. 3:15Platform engineering challenges
  4. 4:59Who benefits from UX design
  5. 6:04Evidence for design in platforms
  6. 7:48Design process for platforms
  7. 10:17Overcoming engineer bias
  8. 12:45Platforms must be user-centric
  9. 14:30Iterative design benefits
  10. 15:34Closing assumption gaps
  11. 17:17Collaborating with designers
  12. 18:47Design accelerates adoption
  13. 19:27Early design cost savings
  14. 21:11First steps for design
  15. 22:57Building platform team
  16. 24:45Build vs buy platforms
  17. 25:46Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.