The teams that ship fastest are usually the ones with the most automated safety underneath them. This day was about the practices that make quick releases boring rather than risky.
At a glance
1 day
five sessions
90
product and engineering leads
3
live incident walkthroughs
The agenda
Sessions ran back to back with a break between each block.
09:30 · Opening
Why "move fast" and "do not break things" are the same investment.
10:30 · Release engineering
Trunk-based development, feature flags and rollbacks that actually get used.
12:00 · Incident practice
Three real incidents walked through end to end, including what was missed.
14:00 · Product instrumentation
Deciding what to measure before building, not after launch.
15:30 · Panel
Balancing roadmap pressure against paying down the things that slow you down.
What people took away
- A rollback nobody has rehearsed is not a rollback
- Feature flags need an expiry date or they become permanent branching
- Instrument the question you will be asked, not the event that is easy to log
- Blameless post-mortems only work if the actions get scheduled
The incident walkthroughs drew the most questions — largely because everyone recognised their own systems in them.
See what we do
Practical questions
Product and engineering leads at companies past their first few customers, where reliability has started to matter as much as pace.
These are free, and deliberately small. Places are limited to keep the discussion useful.
Want to hear about the next one?
We run these two or three times a year. Tell us what you would want covered.
