Agentic Trio: 12 theses on digital product development
Coding agents make building software cheap, and the bottleneck shifts to discovery. The Agentic Trio extends Teresa Torres’ Product Trio: product management, UX and engineering share responsibility not only for discovery, but also for delivery. This is possible because agents take over large parts of the implementation. The goal is better outcomes for users and organizations, not more generated code.
Read more
The freed capacity is a strategic choice.
Many open questions can be answered before building
More output destabilises the system
The product trio in pre-agentic times
The Agentic Trio has no delivery-only roles
The skills of PM, UX and developer converge
Discovery participation is both a duty and an opportunity for developers
The developer is an agent harness engineer
The harness must come before production work
Harness expertise becomes a key qualification
Junior developers: rotation instead of writing code
Background
The term Agentic Trio was coined by Daniel Westheide and Fabian Walther at INNOQ. The theses describe how roles, responsibility and team size change when coding agents make building software cheap, and why the freed-up capacity should go into discovery.
We describe the approach in more detail in the article The Agentic Trio on the INNOQ website.
Wondering what the Agentic Trio means for your teams? Get in touch. We are just as interested in disagreement and in experiences from your own teams.