The Qonto Tech and Product Operating system
summary
Company scales to ~500 product+tech people and 450k customers while insisting features work right first time; process tools include a Figma single source of truth for screens and specs, colored backend flow diagrams, and a supermarket capacity board that limits teams to two concurrent pipelines. Continuous improvement shows up as 423 PDCAs in 2023 and 50+ Kaizens (CI build time cut from ~10 to ~3 minutes). Outcome: no QA team, ~91 logged bugs across the org, and under two QER returns per cycle for 80% of features.
AI-written summary · about
chapters (14)
- 0:00Introduction to Qonto's OS
- 3:24Lean framework foundations
- 5:45Value stream mapping
- 8:04Visual management practices
- 10:34Managing rework and waste
- 13:03Continuous improvement methods
- 15:32Advanced problem solving
- 19:43Ensuring one-piece flow
- 23:48Product feature delivery
- 28:34Single source of truth
- 36:45Scaling technical documentation
- 40:25Delivery and quality control
- 44:26Conclusion and core takeaways
- 48:21Q&A session
related talks
30mA framework for ambitious companies
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
22mOptimizing Product Development: Balancing Speed, Quality, and Process
53mWhat Happens When Everyone is QA? And I Mean Everyone!
24mScaling a Product Vision Through World-Class Team and Culture
36mHow programmers & testers can be productive
45mFrom 5 to 100 in Product Development team in just 5 years
44mExceeding Expectations, Inspiring Quality