A PM can build a working flow. A designer can work directly in code. An engineer can explore several approaches in the time it once took to implement one.
I’ve been living this change. It’s a large part of why I started Super IC: expertise can travel further when AI helps you do work that previously sat outside your role.
But what happens when these people need to build something together?
As I wrote in Individual Speed Is Not Team Speed, the gains don’t automatically add up. A feature generated in an afternoon can still spend days waiting for review. A working prototype can conceal product decisions nobody has made. More output also means more things for someone to inspect, question and take responsibility for.
This is where end-to-end AI-driven development gets interesting. The team has to change how it works.
Product intent, design decisions and technical constraints need to be available to everyone and their agents. Work needs to be small enough to review and revise. Ownership needs to remain clear even as people contribute across disciplines. And we need to protect the human judgement that all this faster generation depends on.
My next free lightning lesson, Super IC Teams: What End-to-End AI Development Really Takes, brings these threads together. We’ll examine how PMs, designers and engineers can take a feature from intent to release, and the agreements that make that collaboration work.
This is the question I keep returning to in my work and in this newsletter: how do we turn expanded individual capability into a team that builds better products?
Join me on 11 November, 3–4 PM PST. Register on Maven →