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.
Related Insights
Cascading OKRs through multiple layers (company to department to team to individual) often results in "OKR theater" where the connection to business impact is lost. Instead, an individual product manager's goals should be no more than one link away from a core business objective that leadership cares about.
When different departments push their own projects onto the sales team, reps get overloaded. To solve this, enablement leaders must shift the focus of every initiative away from departmental priorities and toward a shared customer outcome. This unified goal minimizes internal friction and clarifies what's truly important.
Innovation leaders struggle to secure resources. A powerful tactic is to have VPs align on their long-term strategic goals, identify overlaps, and then dedicate cross-functional teams to these shared priorities. This creates executive buy-in and carves out protected capacity for innovation.
To get buy-in for developer experience initiatives, don't use generic metrics. First, identify leadership's primary concerns—be it market share, profit margin, or velocity. Then, frame your measurements and impact using that specific language to ensure your work resonates.
Product leaders often feel pressure to keep executive discussions confidential. However, effective leaders break this norm by immediately sharing and translating high-level business goals for their teams. This transparency empowers individual PMs to connect their daily work to what truly matters for the company's success.
To solve misalignment, the company cascaded OKRs from the CEO down. Critically, regional leaders were made 'champions' of key pillars like user acquisition. This gave them ownership and a direct voice in shaping product solutions, turning potentially adversarial relationships into collaborative partnerships.
Most business struggles stem from a misaligned or forgotten North Star Metric (NSM). A successful framework aligns the entire company by ensuring all OKRs ladder up to a single, durable NSM, with KPIs serving as health checks for those OKRs. This creates a clear hierarchy for decision-making and resource allocation, preventing strategic drift.
To avoid "set it and forget it" goal setting, Atlassian teams use a monthly ritual. They score progress on their OKRs and write a public, tweet-sized update. This lightweight, consistent practice ensures accountability, maintains visibility across the company, and prompts regular re-evaluation.
Shift your team's language from tracking output (e.g., 'deployed XYZ API') to tracking outcomes. Reframe milestones to focus on the business capability you have 'unlocked' for other teams. This small linguistic change reorients the team toward business impact and clarifies your contribution to metrics like NPS.
Don't build a feature roadmap and then write OKRs to justify it. Instead, start with the outcome you want to achieve (e.g., "move metric X to Y"). This frames all features as experiments designed to hit that goal, empowering teams to kill features that don't deliver value.
