Create organizational alignment by using a two-tiered outcome system. At the executive level, define success with financial outcomes (e.g., revenue). For product teams, define success via the specific user behavior changes that will produce those financial results, connecting daily work to the bottom line.

Tekmetric's marketing team uses OKRs for creating new capabilities needed for future growth (e.g., founder-led content). KPIs are used for monitoring ongoing operational health (e.g., paid media performance). This distinction clarifies strategic versus tactical work.

Directly trying to change a North Star metric like MAU is ineffective. Instead, product leaders must identify and focus on 'driver metrics'—the specific, controllable inputs like organic traffic sources or keyword performance—that collectively influence the ultimate KPI.

Varonis's CMO sets simple, easy-to-remember leading indicators as goals. For example, the executive briefing team's primary goal is the number of C-level guests hosted, not the resulting ARR. This focuses the team on activities they can directly control.

A common OKR failure is assigning teams high-level business metrics (like ARR) which they can only contribute to, not directly influence. Success requires focusing on influenceable customer behaviors while demonstrating how they correlate to the company's broader contribution-level goals.

To align teams with strategy, compensate them for performing specific activities you hypothesize will lead to success (e.g., discovery calls), not just the final outcome (e.g., revenue). If the activities don't work, it's a leadership failure, not an employee one.

Revenue is a lagging indicator and is too slow for validating major strategic shifts. To get an early signal, establish checkpoints using leading indicators. For a decision aimed at acquiring more customers, track metrics like sales team win rates on a monthly basis to see if the hypothesis is proving correct before revenue numbers reflect the change.

Focus on what customers value (e.g., delivery speed, order accuracy) rather than internal business metrics like ARR or user growth. This approach naturally leads to a better product roadmap and a more defensible business by solving real user problems.

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.