Daniel Westheide and Fabian Walther describe how product teams can respond with the Agentic Trio. On the new website agentictrio.org, they set out 12 theses on how roles and responsibilities are changing and where the freed capacity is best invested. The goal is better outcomes for users and organisations, not more generated code.
From Product Trio to Agentic Trio
Teresa Torres' Product Trio brings product management, UX and engineering together in discovery. A small unit works out together which problems users really have and which solutions are worth pursuing. Each role brings its own perspective. Delivery has so far been handled by the rest of the product team. Because coding agents now take over large parts of the implementation, the same three roles in the Agentic Trio share responsibility for both discovery and delivery. There are no delivery-only roles anymore.
Why More Output Isn’t Enough
The obvious move would be to put the freed capacity into more output. What that can lead to is shown in the AI Engineering Report 2026 by Faros AI. Across more than 4,000 teams, it compares periods of low and high AI adoption. With high adoption, epics per developer rise by 66%, median time in review by 441% and bugs per developer by 54%. That is why the Agentic Trio invests the capacity in better discovery instead. Teams that check whether a problem is real before they build anything build less that isn’t needed and take pressure off review and the pipeline.
Every hour we invest in discovery instead of more output pays off three times over: it relieves the review bottleneck on our senior engineers, which in turn stabilises the system, and code that never gets written never has to be maintained.
Daniel WestheideSenior Consultant at INNOQ
Who Is This For?
- Product managers and UX designers who use coding agents to build solutions themselves and need to judge what generated code can and can’t do.
- Developers, for whom taking part in discovery becomes a must and harness expertise becomes a key qualification.
- Leaders and those responsible for team organisation who decide how teams are structured, where freed capacity goes and how juniors learn.
More on agentictrio.org
Each of the 12 theses has its own page on agentictrio.org with a detailed rationale. The website is available in English and German, and a glossary explains the key terms. The design is by Sebastian Eberstaller. For a deeper dive, read Daniel Westheide’s in-depth article “The Agentic Trio” on the INNOQ blog.
Questions and experiences from your own teams are very welcome. Just drop us a line at [email protected].