- Another PM Day
- Posts
- Team Topology: The Secret Sauce to Product Success!
Team Topology: The Secret Sauce to Product Success!
Master Product Topology

Today at a glance
My favorite weekly finds
🛠️ Tools
Agentforce just got an upgrade—meet AgentExchange. A marketplace packed with AI agent components so you can automate your workflows in minutes.
Use Brainnote as an AI thought organizer to summarize your ideas in seconds
You.com is taking on Perplexity. It’s an AI search engine that lets you toggle between GPT-4.5, Claude 3.7, and more—all in one place.
olmOCR turns messy PDFs into clean, structured text while preserving tables, equations, and even handwriting.
OLMoE brings AI2’s OLMo 2 and Tülu 3 straight to your iPhone 15 Pro. Run models locally, no cloud, no data leaks.
PublicView makes SEC filings searchable, analyzable, and chat-friendly. No more digging through PDFs.
📰 Intelligent Insights
Big brains talking AGI—watch this 1-hour convo on artificial general intelligence (aka AI that can do everything a human can) and the geopolitical chaos that might follow.
A new survey of AI researchers just dropped: Most don’t buy the idea that cranking up today’s neural networks will magically lead to AGI. Turns out, size isn’t everything.
The internet’s about to get way weirder. Here’s why we probably need verified video before deepfakes run wild.
Hugging Face’s Thomas Wolf makes a sharp point: AI is turning into a bunch of “yes-men on servers,” too polite (or dull?) to drive real scientific breakthroughs.
OpenAI chairman Bret Taylor is betting big—says AI agents will run most brands’ digital experiences in 5-10 years. So, your next customer service rep? Probably a chatbot in a suit.
👀 ICYMI
Fail Smarter, Winning Through Mistakes (Learn more)
Stop Building 'Faster Horses' (learn more)
Help Your Company Speak ‘Strategy’ (learn more)
Team Topology: The Secret Sauce to Product Success!
Why should I care?
Last week, I spilled the beans on my wild ride trying to set up a growing product team at Slack.
I figured that a killer team culture would fix any overlapping responsibilities.
Boy, was I wrong! Without clear ownership, even top-notch teams get stuck in endless debates rather than making moves.
I felt it firsthand—my focus on strategy got buried under minute details from every PM.
We needed defined responsibilities, pronto.
The kicker?
Our whole crew was working on Slack’s search ranking system, so splitting up the work felt as awkward as slicing a pizza into uneven pieces.
Some splits work better than others, trust me.
I had already shared three key ideas: substance, independence, and balance.
There’s no magic formula—just a series of trade-offs that fit your current strategy. The real trick?
Base your team structure on your strategic pillars, not on arbitrary engineering constraints.
Ready for some real talk?
Let’s break down what works, what flops, and how to steer clear of those pesky team structure blunders.
User Personas
Imagine each PM as the superhero for a specific user type—they own the whole experience from start to finish.
In a marketplace, one PM champions buyers, while another looks after sellers.
This method is gold when different user groups have separate, non-conflicting needs.
Customer Journey Phases
Here, you split ownership by stages of the customer journey.
Picture an e-commerce site:
One PM handles onboarding,
Another nails product discovery, and
A third masters checkout. This works best for mature products with rich, detailed user flows.
Goals-Based Ownership
Every PM takes charge of specific goals and can tweak any feature to hit them—just like Growth PMs pushing for more sign-ups or better retention.
This style is perfect for mature products with clear problems or for those temporary, fire-fighting task forces. Plus, you can layer it on top of any other method.
Do this for your product: a clear path saves time and money while steering every move toward your big goal.
Reply