Put On Your Product Hat When Championing an Internal Tool
summary
Argues that internal platform work must be treated as product management with five key actions: direct user research (one‑on‑one interviews and observation), build an MVP first that solves one clear workflow, recruit early adopters as partners, iterate from their feedback, and instrument usage. Gives concrete tools and metrics: measure with Grafana and Prometheus, track UI logins and clicks, run NPS‑style satisfaction surveys, avoid heavy initial feature sets and needless new URLs or configs.
AI-written summary · about
chapters (12)
- 0:00Icarus effect in internal platforms
- 1:06User perspective importance
- 2:30Product development paradigm
- 4:14Developers' trap
- 4:35Five key actions for adoption
- 6:22Field research and connections
- 6:45MVP importance
- 9:36User feedback and engagement
- 10:40Weekly user feedback
- 11:23Measurement and data analysis
- 12:27Satisfaction surveys
- 14:21Paradigm shift necessity
related talks
33mWhy You Should Treat Your Platform as a Product
44mPlatform Engineering is All About Product
36mApplying Product Thinking to internal infrastructure
40mInternal platforms in practice
43mEngineering Platforms Evolved
28mDesigning for Success: UX Principles for Internal Developer Platforms
24mWhat I've learned on Being a better Engineer from being a Product Manager
06mPlatform Engineering with a Product Management Mindset: 10x Your De...