@poteto: deleting the product it's funny how you can sometimes tell if a team culture is dysfunctional just by looking at how th…
Summary
A commentary on how dysfunctional team culture shows up in product design, arguing that OKR-driven incentives lead teams to ship org-chart bloat rather than build great products—especially in the agentic era when adding features is cheap. Fix culture before fixing the product.
View Cached Full Text
Cached at: 10/03/26, 06:52 AM
deleting the product it’s funny how you can sometimes tell if a team culture is dysfunctional just by looking at how their app is laid out. behind every feature, or tab in a sidebar likely lies a PM or someone responsible for an OKR.
the problem is when individual performance is measured by these metrics. it becomes the singular focus of the responsible person to make those numbers look good, since it determines whether they get rewarded or axed, even if it comes at the detriment of the overall quality of the product. this is why you mostly see features get added, but rarely removed. if you own a feature, then it being removed feels like an aura loss.
this is even worse in the agentic era when the cost to add features has become so low. you can simply will a new feature into existence overnight and add another tab. but users will notice that you ship your org chart.
teams that make people play silly games under the guise of performance management rarely build great products.
to build a great product you need to first fix your culture
Can provide more context on this? @poteto E.g. culture is hard to fix or create in a short time :(
To go fast, go deep first. This is the @poteto way
Similar Articles
@lennysan: .@OpenAI's Codex app lead: "A lot of companies are getting rid of the product role, and saying everybody's just going t…
OpenAI's Codex app lead Andrew Ambrosino argues that companies abandoning dedicated product roles in favor of everyone being a 'builder' is a terrible idea, emphasizing the value of product discipline and best practices.
@GergelyOrosz: From a friend who joined a fast-growth, later-stage startup: "I was wondering why no one is doing PRDs here. Then I rea…
A tweet shares an anecdote about a fast-growth startup where young product managers lack the attention span to read PRDs, reflecting on changing product management practices.
@kentcdodds: Stop tracking what your product has. Obsess over what it does for your user. All that matters is how it fits in and cha…
Kent C. Dodds advises product teams to focus on user outcomes rather than features, citing Grok Bot's effective announcement strategy as an example.
@poteto: https://x.com/poteto/status/2069824386283319343
The article draws parallels between managing engineering teams and managing AI agents, using Andy Grove's management principles to build reliable agent loops, illustrated through a performance debugging case study at Cursor.
@addyosmani: If you're building a software factory, code good enough to ship still needs human taste and ownership. You'll likely ne…
The article discusses the importance of human taste and ownership in automated software development, emphasizing the need for human oversight in design and quality checks while balancing automation with manual review.