WIG vs OKR: how 4DX differs from OKRs (and when each is the right fit)

WIG (4DX)

A Wildly Important Goal is a single, specifically phrased outcome a team commits to achieving in a defined timeframe. "From X to Y by when" is the canonical format. A team focuses on one WIG, two at most. Discipline 1 of 4DX is the discipline of saying no to everything else that could plausibly also be wildly important.

The WIG is paired with 1–2 lead measures (Discipline 2), a scoreboard showing both lead and lag (Discipline 3), and a weekly cadence of accountability with kept-promise tracking (Discipline 4). The book presents the four as one system; adopting only the goal-setting part leaves out the weekly mechanism that makes it work.

OKR

Objectives and Key Results grew out of Andy Grove's management practice at Intel and were brought to Google by John Doerr in 1999, who later described them in Measure What Matters (2018). An Objective states a qualitative direction; three to five Key Results make progress measurable. OKRs often run at several levels with quarterly cycles, and "stretch" OKRs are set knowing some will be missed.

OKRs are a goal-setting and alignment framework more than an execution discipline. How a Key Result moves week to week is left to the team, so the weekly cadence is much lighter than in 4DX unless the team adds one.

Number of goals

A team running 4DX has one WIG, two at most. A team running OKRs typically has one Objective with three to five Key Results — and the Objective tier above them, and possibly individual OKRs as well. The cognitive load and weekly attention demands are very different.

The 4DX bet is that one focus produces faster progress than five distributed efforts, particularly for behavioral or cultural change. The OKR bet is that ambitious goals cascaded across multiple priorities produce alignment and stretch. Both bets win in different contexts.

Cadence

4DX requires a weekly WIG Session — same day, same time, same agenda, every week, for the life of the cycle. The cadence is non-negotiable; if anything cancels, it's the regular team meeting. This is Discipline 4 and it's the operational mechanism that turns the WIG into kept commitments.

OKRs usually run on a quarterly cycle. Doerr recommends frequent check-ins, but the framework doesn't prescribe a fixed weekly meeting with a set agenda. Some OKR teams build a weekly rhythm; many don't, and OKRs become quarterly review events with little effect in between.

Lead vs lag emphasis

4DX's distinctive contribution is the lead measure discipline. Identify behaviors the team controls that predict the outcome; track them weekly; commit to them weekly. The methodology is built around making lead measures operationally central.

OKR Key Results are typically outcome-focused (lag-equivalent). Some OKR-running organizations bolt on activity tracking; the framework itself doesn't natively distinguish lead from lag. The result is goal-setting that may be ambitious but doesn't structurally drive weekly behavior change.

Cascade and alignment

OKRs are designed for organizational cascade. Corporate OKRs inform department OKRs which inform team OKRs; the framework's primary advantage is alignment across levels. This is structural and explicit.

4DX supports cascade (organizational WIGs cascading to department WIGs to team WIGs) but the methodology's center of gravity is the single team running its WIG well. The framework can be enterprise-deployed but is most often successfully run at the team level first.

Choose 4DX when

• The work is behavioral or cultural change rather than bounded project delivery — improving safety culture, sustaining infection prevention practice, building new clinical protocols into the daily flow.
• Weekly accountability is what's missing — the team has goals, the goals aren't getting executed, and the gap is between intention and weekly behavior change.
• The WIG can be stated as "from X to Y by Z" with hard numbers — outcomes the organization measures lag-style with periodic data.
• A stable team with consistent membership is available for the cycle duration — 4DX's cadence requires social accountability among the same people week to week.
• Leadership is willing to protect the WIG from additions — the discipline of saying no to other priorities for the cycle is a precondition.

Choose OKRs when

• The need is for cross-level alignment across an organization — corporate priorities cascading into team work that all moves in the same direction.
• Multiple priorities genuinely need parallel attention — different teams working on different objectives that ladder to the same broader goals.
• Quarterly review cadence is the operational rhythm — strategic check-ins rather than weekly behavior-shaping.
• Stretch goals and ambitious targets are wanted — the OKR framework's tolerance for missing is a feature, not a bug.
• The team has its own execution mechanism — daily standups, sprint reviews, or another weekly cadence that sits beneath the OKR framework.

Combining the two

Some organizations use both in layers. OKRs operate at the organizational and department level for alignment and quarterly stretch; 4DX operates at the team level for weekly execution discipline on the highest-priority outcome each team is owning. This works when the WIGs at the team level are derived from the team's OKRs — making the team's weekly behavioral target the operational mechanism for the OKR's top Key Result.

The combination requires care. Trying to run team-level OKRs and team-level WIGs simultaneously fragments attention. Pick which framework runs the team's weekly cadence and don't double-stack.