The Tability Method
Map the bets

Map the bets: how to pick initiatives that move the needle

Objectives and key results describe what needs to change. Initiatives describe how you hope to make that change happen. Think of every initiative as a bet you are willing to test and, if evidence contradicts you, to swap out without regret.

From fixed projects to flexible initiatives

Classic roadmaps often pre‑commit teams to a long list of projects months ahead. As soon as reality shifts—new data, customer feedback, unforeseen blockers—those commitments turn into anchors. OKRs avoid this trap by decoupling goals from work. You frame objectives and key results for the quarter, then keep the work layer fluid.

Initiatives sit in a Now-Next-Later queue:

  • Now: the handful of initiatives currently in motion, each tied to a single key result.
  • Next: well‑shaped candidates ready to start once capacity opens.
  • Later: rough ideas that need more discovery before you can judge them.

Moving something from Next to Now is a conscious choice: the owner of the key result explains how the initiative should shift the metric and what evidence will confirm or refute the bet.

In this model, initiative and bet mean the same thing—you are staking time and effort on an assumption, not guaranteeing delivery of a feature list.

Treat initiatives like bets

Initiatives power your key results, but they are not goals in themselves. Think of each one as a bet you place with time and talent:

  • OKRs drive the results. The objective and its key results define success. An initiative's only job is to nudge a metric in the right direction.
  • Double down on what wins. If an initiative starts moving the needle, expand or refine it while momentum lasts.
  • Walk away from what fails. When two weekly check‑ins show no progress—or worse, negative movement—be ready to kill the initiative without regret and pick the next best bet available.

Zoom out every month: initiatives that reliably move key results become core parts of your product, GTM motion, and processes. The rest become learnings and clear the path for new bets.

How to identify high‑leverage initiatives

Great initiatives rarely drop from brainstorming sessions alone. They emerge from everyday signals:

  • Conversion data: Identify the steepest drop‑offs in your funnel and ask what would ease that step.
  • Customer feedback: Scan support tickets and interview notes for repeated friction. Friction equals opportunity.
  • Usage metrics: Spot features that attract curiosity but fail to retain engagement. A small tweak can unlock value.
  • Churn patterns: Cluster cancellations by reason. A targeted fix can lift retention fast.
  • Competitive gaps: When prospects name a rival's capability, explore a focused test to close that gap.

Record each idea directly under the key result it could influence. Housing ideas next to KRs keeps context intact and make it easier to plan for success.

Size initiatives quickly

Skip exhaustive estimates. Use rough scores in thirds:

  • Impact: Will the initiative move the metric a little, a fair bit, or a lot?
  • Effort: How many days or weeks until you can see a difference in signal?
  • Confidence: How much evidence supports the idea?

Sort candidates by high impact and low effort. Break ties with confidence. Even a low‑confidence initiative can be worth a shot if effort is tiny and time‑boxed.

Respect capacity

No owner should juggle more than three active initiatives at once (even then, that's a lot). Focus beats juggling.

Enforce strict planning rules:

  • No one should have more than 3 items in progress.
  • No initiative should sit in the same state for more than 4 weeks.

Don't hesitate to break down large initiatives into smaller, more observable pieces. The goal is to validate your bets quickly and it can be costly to go months without getting feedback.

Retire or replace initiatives fast

  • Win: The metric turns green 3 weeks in a row. Scale the initiative or design a follow‑up to compound the gain.
  • Stall: No measurable progress after 3 weeks. Shrink scope, tweak the hypothesis, or drop it.
  • Backfire: The metric moves the wrong way 3 weeks in a row. Run a lightweight root‑cause review and revert if needed.

Momentum beats loyalty to any single idea.

Keep the initiative list alive

The Monday OKR review should be focused on discussing the goals, but it's also a great time to review and discuss the status of the initiatives attached to critical key results.

But, this is not the time to plan everything. You should schedule a second meeting during the week to review the list of existing bets, archive anything completed, and promote new items as capacity allows.

The feedback loop between OKRs and initiatives is the heartbeat of the team. Keep things small, testable, and tightly tied to a key result, and your OKRs will remain a living conversation instead of a static report.

Table of contents

Related content