Press Space to continue
Team Size Changes Depend on Decision Cost and Blast Radius
Press Space to continue
Everyone is asking how much smaller teams get. @mshcheglov1's answer is that it depends entirely on what the team owns, and the split is sharper than I expected. He sorts domains by blast radius. Monetization, search, ranking, ML. Places where one tweak moves conversion dramatically. For those, he says essentially nothing has changed. Dedicated owner, same as before. For customer facing domains, one PM now runs three or four at once across multiple platforms without adding people. The…
Aakash Gupta@aakashguptaAug 29
Agents are building most of the features at OLX Uzbekistan. Mikhail Shcheglov (@mshcheglov1) is the CPO there, and over the last 5 months he built an entire company operating system on top of OpenClaw and Hermes. He doesn't read his email anymore. The agent does, and pings him only when something's urgent. It also screens stakeholder feature requests before they reach a PM, and it updates the Figma design system on its own. Then he open sourced the repo. We discuss: 🔶 The knowledge graph his whole company runs on 🔶 Why summarizing transcripts cost him 25% recall 🔶 The agent that kills bad feature requests 🔶 The "board skill" that pokes holes in your deck 🔶 Why the CPO should own this, not an AI ops hire 🔶 The one question that spots AI-native PMs Watch the full episode 👇 https://youtu.be/zocznD8Z-6k
View