The Pattern
Modern product orgs accidentally create conflict
Modern product organizations accidentally create conflict by teaching different functions to optimize for different things. PMs are told to drive business results. Designers are told to protect the user experience. Engineers are told to optimize for speed and technical efficiency.
Individually, these goals make sense. Collectively, they break teams apart.
I have sat in countless conversations where trust between Product and Design slowly deteriorated because both sides felt like the other fundamentally did not understand what mattered.
Two Vantage Points
The same product, seen through two different lenses
From the PM
- Remove friction.
- Increase conversion.
- Simplify the funnel.
- Drive revenue.
From the designer
- What happens to trust?
- Does the experience become manipulative?
- Does the user leave feeling pressured instead of supported?
- Does the company win the metric while damaging the relationship?
Over time, both functions begin seeing themselves as protecting the product from the other. The PM starts viewing Design as unrealistic. The designer starts viewing Product as willing to compromise trust for growth.
I do not think either side is actually the problem. The problem is the incentive structure.
The Reframe
Separate the expertise, not the mission
If PMs are primarily rewarded for revenue, short-term monetization becomes the default. If designers are only rewarded for delight, business realities become easier to ignore. Both become incomplete versions of product leadership.
The best organizations work differently. They do not separate the mission. They separate the expertise. Everyone is accountable for the same ultimate outcome: creating meaningful customer value in a way that also creates sustainable business value.
Different expertise. Shared goals. That shift changes conversations dramatically.
Instead of, "How do we maximize revenue?" versus "How do we protect the experience?", the conversation becomes, "How do we grow the business without damaging trust?" That is a much healthier organizational question.
Performance and Talent
If a function can succeed alone while the product loses, the system is broken
Most organizations still evaluate functions in isolation. PMs are rewarded for growth. Designers are rewarded for craft. Engineers are rewarded for speed. But if every discipline can succeed independently while damaging the overall customer experience, the incentive system itself is flawed.
The goal is not to make every function identical. The goal is to ensure no function can succeed while weakening the overall system. That means performance evaluation should include both functional excellence and shared outcome accountability.
Product
Market understanding, prioritization, and business strategy.
→ Evaluate on
- Retention quality and repeat engagement
- Customer trust signals and complaint rates
- Churn patterns and long-term product health
- Revenue, alongside, not instead of, the above
Design
Clarity, trust, and human understanding.
→ Evaluate on
- Activation and reduction in confusion
- Engagement depth and long-term retention
- Trust signals that also benefit the business
- Craft quality as a floor, not the ceiling
Engineering
Scalability, technical leverage, and quality.
→ Evaluate on
- Product quality and reliability
- Speed of learning and iteration
- Scalability of the underlying system
- Cross-functional collaboration health
If conversion increases while trust collapses, that is not truly successful product leadership. It is short-term extraction. Design cannot operate as if economics are someone else's responsibility. Engineering cannot operate as if collaboration is someone else's problem.
Healthy organizations create overlap in success metrics intentionally. Overlap creates shared ownership. The best product teams are not collections of isolated specialists protecting their own metrics. They are coordinated systems solving shared problems together.
Why This Matters Now
In the AI era, alignment is the moat
AI is dramatically reducing the cost of production. Teams can now generate designs, code, prototypes, and experiments faster than ever before. Output is no longer the competitive advantage. Alignment is.
When incentives remain fragmented, AI simply accelerates organizational dysfunction. PMs optimize growth hacks. Designers optimize aesthetics. Engineers optimize velocity. Everyone moves faster, but not necessarily in the same direction.
The best product organizations of the next decade will not be the ones that ship the fastest. They will be the ones that learn, align, and adapt together the fastest.
Great product organizations are not collections of functions. They are coordinated decision-making systems.