Dialogue Driven Development
summary
Pcta Bank's platform team replaces a single legacy Kubernetes cluster by building a new platform, adds GitOps/CD and a cluster operator, and migrates ~200 products while supporting ~500 developers with a team of 4–5. They run dialogue-driven development: weekly user insights, surveys (~50 responses) and onboarding sessions, which shifts prioritization to users and lifts satisfaction across measured metrics. The effort scales to ~1,000 production clusters, reduces friction, and proves the approach works in practice.
AI-written summary · about
chapters (9)
- 0:00Dialogue Driven Development intro
- 3:42Kubernetes platform decline
- 8:19Platform failed user needs
- 10:04User research on failures
- 12:34Dialogue space creation
- 14:40Prioritizing features
- 16:27Measuring success
- 18:55Results and adoption
- 19:40Three key lessons
related talks
56mSmarter, Not Harder: Scaling without burning out in an always more landscape
28mRefactoring Your Team For Fun and Profit
23mThe Day 2 Hangover: What To Do After the Platform Party Ends - Cat Morris & Nitish Malhotra
58mKeynote: Seven Habits of a (Mostly) Successful Team
39mThis Is Not Your House!
40mPanel Debate Led by
32mSolving the Dev/IT Cultural Divide with Operational Agile
29mTDD - how to break the siloes between Dev and Ops teams