Thesis 7

The skills of PM, UX and developer converge

The Agentic Trio requires a T-shaped profile from all three roles: each role keeps its depth in its own focus area, but the crossbar, the shared breadth, grows considerably.

When it comes to delivery, all three roles use coding agents to implement solutions. PM and UX become active authors and producers. The developer remains the deep technical expert, but prompting and working with coding agents become a core skill for all three roles.

On the discovery side, all three members of the trio need to be skilled in user interviews, opportunity mapping, and assumption testing, and they take part equally in these activities as well as in solution ideation. In the ideal Product Trio this was already the case, but the developer often lacked the capacity to take part sufficiently.

Convergence is not uniformity. PM and UX need to understand what generated code can do, where architecture decisions are product decisions, and where technical debt constrains strategy. The developer needs to take the user’s perspective, grasp opportunities before moving to the solution level, and apply discovery methods. Each role understands more of the others’ specialties than before, but the focus areas remain distinct.

Posts

There are no posts on this thesis yet.

Background

The Agentic Trio is an approach by Daniel Westheide and Fabian Walther at INNOQ. More background or get in touch.