Antipatterns I've seen in product teams running on the wrong incentives:
1. Engineers focused on delivery speed, not value
2. Product managers tracking success by feature count
3. Designers rewarded for aesthetics over functionality
Good goals don't compensate for bad incentive
Your product needs to evolve using real patterns of how customers use the product, not just the team's assumptions.
Build better feedback loops, not longer feature lists.
Traditional products measure TASK completion.
The new wave of AI-enabled products should measure if users are meeting their GOALS.
Is the shift between experiences led by commands (old) vs. intent (new).
@Eric_Neuman That's a good point. Yet, in most cases what I've seen is that that overhead is just about context information sharing, which is what AI can facilitate across the team.
Most PMs are delegating the wrong half to AI.
Give it the coordination overhead: status updates, handoff summaries, alignment pings.
Keep the judgment calls: what to build, what to cut, what the customer actually needs.
Delegate the overhead. Keep the judgment.
Your team needs a product context strategy.
When everyone shares the same context things move faster. Context removes unnecessary layers.
Shared context over hierarchy.
#ProductStrategy#Context
We built +60 years of software on predictability. AI products bring a new paradigm: asking user to trust a system that they can't fully predict.
That's a completely different design problem to solve.