
A seed stage founder asked how to coordinate 7 developers using AI agents - the answer reveals why org design matters more than ever
"How do I coordinate a team of 7 developers who are using AI agents on one thing without them stepping on each other?"
This was a real question I got last week from a seed stage founder I met at an event.
My answer? You probably can't. Not if they're working anywhere close to the way I work now, talking to multiple agents at a time or maybe even an orchestrator of agents.
A team of 7 working this way would act more like a team of 20-30 or more from a couple of years ago. And some are building faster than that.
You'll have to split them up to different work streams. Otherwise you'll get a lot less done with 7 than you would with 2 working on one focused area.
It's a strange place to be now where a team of 1 to 3 folks can dramatically out-ship what we used to think of as a fully staffed team.
Org design is going to be even more important than it already was for a lot of teams that started before ChatGPT.
Aligning platform teams and the product / value stream teams they support was a best practice before. Now, it's going to be a necessity even in smaller teams, not just those with 50-100+ engineers.
And if you want a guide who's been neck-deep in both org design and AI workflows, I run 2-4 week sprints to sort that out.
The instinct to push back against non-technical folks using AI agents is understandable, but drawing a hard line could cost your business when it needs innovation most
Scaling impact with AI comes from codifying senior judgment into skills and agent workflows—which also becomes the training material for the people still climbing the ladder.
Shipping fast means nothing if you're not shipping the right stuff - a lesson learned the hard way from a startup that built amazing software but couldn't find traction
Get More Like This
Follow along as I build and share what I learn
Found this helpful? Share it with your network!