Product development has changed. So we work differently.
Code used to be the slow, expensive part, and everything was organised around it. Now agents write it in hours. The rest has to change too.
The code shrank. The ends grew.
Where a product team's time goes.
What we do, and why.
01 Close to the people who use the product.
The more layers between users and builders, the more gets lost. We see firsthand where users struggle, and what they're actually trying to get done, not just what they ask for. What we learn turns directly into improvements.
02 People set the direction. Agents provide the capacity.
Agents handle most of the implementation. We decide which problems are worth solving, what to build, and what good looks like.
03 We build the system that builds the product.
We don't just tell agents what to build. We create the tools, workflows and environments that let them work independently. Every improvement to that system makes everything we build next easier.
04 Speed is a product strategy.
What matters is how quickly we turn what we learn into improvements, not how much we ship. When changes take hours instead of weeks, we can challenge earlier decisions instead of defending them. And when building is cheap, saying no matters more.
05 One team. End to end.
The same small team takes a product from problem to production and keeps improving it after launch. No handoffs between teams, no divided ownership.
06 Own the product, not just the work.
A closed ticket doesn't mean the problem is solved. We take responsibility for the outcome, not just the delivery. What matters is whether we've actually solved the problem.