How we set a technical direction that lasts(and stuck to it) at Suvoda
summary
Suvoda becomes a multi-tenant SaaS platform for complex clinical trials and commits to an ambitious North star with conservative increments that aligns tightly with product goals; architectural decisions live as published RFCs for architecture that anyone can comment on, and execution focuses on core systems, APIs and a no-code/low-code customization layer. Practical lessons include avoiding parallel rewrites (London Clearing House), fixing the real bottleneck (big data pipeline at LiveRamp), and the cost of unmanaged politics (Riot client), while delivering stable progress over two years.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:04Aligning with product goals
- 2:07North Star and conservative strategy
- 3:10Transparent communication
- 8:14Suvoda’s technical direction
- 16:22Anti-patterns in direction setting
- 24:21Key insights
- 25:24Q&A
related talks
41mA tech leader's playbook: Galvanising product & tech organisations to deliver repeated success
50mMove Fast, Think Big
25mCommon platform team mistakes and how to avoid them
07mIterative Enterprise SRE Transformation
59mTech leadership, one year after
24mBuilding a product in a tech scale up
31mSuccess at Scale: Building a Platform Organization through Rebranding and Realignment
27mHow to Create and Lead Transformational Change