When the internet arrived, it didn't just add a channel – it redrew roles, teams, and entire org charts. AI is doing the same, faster. The "product engineer" – one person who ships product, not just code – is showing up everywhere, and some teams are now audiences of one. For CTOs and CIOs the question isn't whether this is real; it is what to do about your org. In this workshop we look back at how the internet reshaped technology organizations, then work forward: what roles emerge, which ones compress, and how the org chart should respond. Participants apply my ownership-organizational model to their own company and leave with a concrete set of role and structural changes to test.

We cover the new roles showing up in AI-era engineering organizations (product engineer, agent operator, platform owner, and others), walk through the ownership-organizational model as a tool for deciding who owns what when teams shrink and tools amplify, redesign one team or function from a participant's own org, and end with peer pressure-testing. Everyone should leave with a clear answer to the question: do I still need PMs, TPMs, and engineering managers the way I did in 2023?

For CTOs, CIOs, VPs of Engineering, and heads of product who are actively reshaping their organizations and hiring plans in response to AI.