Designing for Success: UX Principles for Internal Developer Platforms
summary
Argues that weekly think-aloud studies (30–60 minutes) uncover real onboarding friction, shows how to map the onboarding journey and cut cognitive load with progressive disclosure, recommends adding Appcues overlays or GitHub Copilot–style contextual help, and audits logs/support tickets to prioritize the most frequent errors using a five-question error-message rubric. Demonstrates handling complexity (don’t kill advanced workflows) with examples like selecting from more than 150 steps and practical steps to boost IDP adoption.
AI-written summary · about
chapters (15)
- 0:00UX for internal platforms
- 1:05Why platforms fail adoption
- 2:54False consensus effect in design
- 4:23Lightweight user research
- 6:32Onboarding for real behavior
- 9:42User journey friction points
- 10:27Cognitive load with disclosure
- 11:31Contextual help in tooling
- 13:17Errors as user frustration
- 15:21Error messages for developers
- 16:27Documentation for technical tasks
- 18:14Ashby’s law for complexity
- 19:20Simplicity versus flexibility
- 20:45Platform adaptability needs
- 21:05Next steps for DX
related talks
40mInternal platforms in practice
35mBuilding Effective Developer Experience
57mEthical Design: Is it possible?
32mLessons Learned from 7 Years of Running Developer Platforms
26mBuilding Internal Platforms to Enhance Developer Experience
49mCo-creating with UX and Software
34mUser Onboarding for the Long Run
52mSpeeding Developer Onboarding: Practical Lessons