From Friction to Adoption: Hacking Human Psychology for Platform Success
summary
Tells why slow platform adoption comes from mismatched expectations and usability not tech: platform often solves bootstrapping but not middle-stage production needs, so users hit missing alerts, confusing APIs (Scala foldable example) and bad defaults. Recommends concrete fixes: mark components "experimental", treat early adopters as design partners and be available, require a visible serve‑to‑production flow that enables alerts, run a user test where an average developer onboards from zero, ship concrete code examples and docs, and offer 3–4 preset reliability configs (low‑latency, safety‑critical, etc.).
AI-written summary · about
chapters (7)
- 0:00Introduction and personal story
- 2:11Why organizations build platforms
- 3:57Managing user expectations
- 7:29Dirty details of early infrastructure
- 10:04Overcoming the curse of knowledge
- 11:07Default settings and paradox of choice
- 13:40Key takeaways for platform success
related talks
35mPushing through Friction
57mEthical Design: Is it possible?
29mBuild with a Beginner Mindset
26mSolving the problems in front of you
36mPsychological Safety for Your Platform Engineering
22mFumbling Forward: Embracing Mistakes in Agile Teams
28mChange Management for Humans
11mTechnology As If People Mattered