Opening: what we learned from 800 product teams
The state of building software in 2027, from our survey of last year’s attendees.
Star the sessions you want and they’ll be saved on this device. Turn on “My schedule” to see just your day. Times are Lisbon time (WEST).
The state of building software in 2027, from our survey of last year’s attendees.
Moving a payments core to an event log, one table at a time, with zero downtime.
Patterns for showing confidence, sources and undo when the machine might be wrong.
Documentation, governance and the three meetings that kept forty teams aligned.
How to run a week of customer interviews when the roadmap is already due.
Bring a laptop. Instrument a real service and find the slow query before the coffee break.
Work-sample interviews that are fairer, faster and better at predicting the job.
Three dashboards that looked great while the business quietly got worse.
Treat it like page weight: measured on every pull request, never traded away.
Why the most innovative teams pick the dullest tools they can.
Every experiment, including the ones that went badly, with the numbers.
How one team merged nineteen services into three and shipped twice as often.
Turn twenty interview transcripts into decisions in ninety minutes.
Docs, decisions and the art of the one-page proposal.
What to do, what to stop doing, and how to know it’s working.
Feature flags, canaries and the kill switch that saved our launch day.
Where models actually helped our users, and where they made things worse.
Four speakers, no slides, your questions.
Nothing here yet. Star a few sessions, or switch day or track.