When a product improvement is meant to benefit another department (e.g., reduce support tickets), don't just ship it and hope for the best. Create a joint, aligned goal with that department's leader. This ensures they are accountable for accruing the benefit (e.g., reallocating saved capacity) and solidifies your impact.

Friction between teams often arises from deeply misaligned values, not just personality clashes. A "move fast" team measured by DAUs will inevitably conflict with a "reliability" team measured by uptime SLAs. True alignment requires shared goals, not just shared projects.

Simply stating a goal, like "increase sales by 15%," is insufficient for autonomous teams. Leaders must also articulate the "anti-vision"—the negative outcomes to avoid, such as eroding customer experience. This rich context provides clearer guardrails and a more nuanced understanding of the mission.

Decades before OKRs became popular, W. Edwards Deming identified their core flaw. He argued that 'management by numerical goal' is a substitute for leadership and a way to manage without understanding the system of work. It encourages short-term thinking and gaming metrics, the precise issues plaguing modern companies.

A team hitting all its targets is not an endpoint for celebration, but the starting point for an investigation. This counter-intuitive approach prompts leaders to ask critical questions, such as what unintended negative consequences this success could be creating for other departments months from now.

Setting rigid targets incentivizes employees to present favorable numbers, even subconsciously. This "performance theater" discourages them from investigating negative results, which are often the source of valuable learning. The muscle for detective work atrophies, and real problems remain hidden beneath good-looking metrics.

The culture around OKRs often treats the framework as gospel. When teams struggle, the default response is "you're doing them wrong," labeling critics as heretics. This prevents genuine discussion about whether the system is fundamentally flawed, trapping organizations in a cycle of failed implementation.

When problems like missed forecasts or high churn recur quarterly, the issue isn't an underperforming team (e.g., sales or CS). It's a systemic problem. Finger-pointing at individual departments masks deeper issues in cross-functional alignment, ICP definition, or process handoffs that require a holistic diagnosis.

When teams are singularly focused on hitting a number (e.g., engagement, account openings), they may rationalize unethical methods, as seen with Facebook's platform issues and Wells Fargo's fraudulent accounts. The relentless pursuit of a metric can justify evil outcomes.