January 5th. The leadership team books a room for two days. Strategy gets debated. OKRs get drafted. By Friday, the quarter has a plan.
The plan commits to one approach per objective. One pipeline strategy. One retention play. One product bet. The team walks out aligned.
By the second week of March, the leading metrics on at least one of those bets are flat. By the time you have data clean enough to be sure, the quarter is essentially done. You start the next planning cycle reading a postmortem on a strategy you committed to before you had any of the information that would have told you whether it was the right one.
What’s the smarter OKR strategy for an uncertain quarter? Run a portfolio, not a single bet. Pick one outcome. Identify two or three candidate initiatives that could plausibly produce it. Resource them lightly at the start, watch the leading indicators, and reallocate hard at week five toward whichever initiative is actually moving the number. Most VPs treat OKRs as a commitment to one path. The smarter teams treat them as a frame for running multiple bets in parallel.
This isn’t an argument for setting more objectives. Three focused objectives still beats six that get shrugged at. The portfolio lives in the initiatives layer, not the objective layer.
The Hidden Bet in Your OKR Strategy
Read your current OKR set carefully. Underneath every objective, there’s an implicit assumption about how you’re going to hit it.
“Increase qualified pipeline by 60%” comes with an assumed strategy. Maybe it’s an outbound push. Maybe it’s a paid acquisition test. Maybe it’s a partner program. Whatever it is, you wrote one. You committed to it. The quarter rides on that approach being right.
That’s a bet. Most VPs don’t realize they’re making it.
The bet was made in the conditions where bets are worst. Early in the cycle. Before you have signal. With every meeting biased toward consensus and conviction. By week three, you’re executing on an unfalsified hypothesis. By week eight, the data starts coming in. By week twelve, you’re writing the postmortem on a strategy that, in hindsight, you didn’t actually have evidence to commit to in January.
The portfolio approach to OKR strategy acknowledges what’s actually true. You don’t know which path will work until you’ve put some capital down on a few of them and watched.
Run OKRs Like a Portfolio: One Outcome, Multiple Paths
The structure changes at the initiative layer, not the objective layer.
The objective stays singular. “Build a qualified pipeline that funds Q4 hiring.” One outcome. Clear, specific, action-oriented. Same as any well-written OKR.
The key results stay outcome-focused. Two or three measurable targets that define what success looks like. “Lift qualified pipeline value from $1.2M to $2.4M by quarter end.” “Hold pipeline-to-close conversion at 22% or above through Q3.” These are the goalposts. They don’t change.
The initiatives become a portfolio. Two or three candidate paths to the same outcome, each with a leading indicator that tells you, week to week, whether that path is actually producing.
For the pipeline objective above, that might look like an outbound SDR push (meetings booked per week as the leading indicator), a webinar-driven funnel (post-attendance demo requests as the leading indicator), and a partner referral program (signed partners and submitted referrals as the leading indicator).
Each initiative gets resourced lightly upfront. The plan, from day one, is to reallocate.
What Mid-Cycle Reallocation Actually Looks Like
By week five, the leading indicators have data. Not enough to fully prove anything. Enough to tell you which bet is in the running.
The check-in conversation changes. Instead of “are we on track,” the question becomes “which initiative is showing the most leverage, and what do we move to it?”
Some initiatives will be clearly winning. Outbound is producing meetings, and the meetings are converting to qualified pipeline at three times the rate of the partner program. Some will be clearly losing. Webinar attendance is high, but post-webinar demo requests are anemic. Some will be inconclusive at week five and need another two weeks before you can call them.
You kill the losers. You move the resources that were funding them to the winner. Not by 10%. By a meaningful share of the team’s capacity.
This is what a real OKR check-in produces. Not status. Capital reallocation. The cycle becomes a sequence of decisions about where to put effort, informed by leading indicators you set up specifically to make those decisions possible. The check-in we wrote about in the difference between OKR reporting and progress tracking is the meeting where this conversation happens.
When the Portfolio OKR Strategy Doesn’t Work
Honest answer. Three situations where a single-bet OKR is genuinely the right call.
The outcome is binary. Some objectives ship or they don’t. SOC 2 readiness, a regulatory deadline, a critical contract close. There’s one path because the outcome itself is structural.
You only have one team. A portfolio assumes you can split focus across multiple initiatives. A six-person team running three parallel bets isn’t running a portfolio. They’re running zero of them well. Below a certain scale, single-bet commitment beats portfolio dispersion.
The strategy is genuinely well-tested. Some objectives have so much prior signal that the path isn’t a hypothesis anymore. If your last four quarters of pipeline came from outbound, putting all your Q3 chips on outbound isn’t an unproven bet. It’s a continuation of a known-working strategy.
Outside those cases, the portfolio approach is more honest about what you actually know in January.
How to Pitch This OKR Strategy to Your Leadership Team
The objection you’ll hear is “we’ll lose focus.” It’s a real concern. The pitch is two sentences.
We’re not running more objectives. We’re running multiple initiatives under one objective. The focus stays at the outcome level. The optionality lives at the path level.
That’s the frame that wins the room. It respects the brand truth that focused execution beats sprawling priorities. It also respects what’s actually true about strategy under uncertainty. As John Doerr makes clear in Measure What Matters, OKRs are a system for setting and pursuing ambitious outcomes. They aren’t a system for predicting which approach will produce them.
The companies that compound across multiple quarters are the ones that build the muscle of testing fast and reallocating hard. HBR’s research on strategic agility consistently lands on the same finding. Portfolio thinking under deliberate uncertainty outperforms single-bet conviction across long enough time horizons.
You’re Not Running a Quarter. You’re Running an Experiment With a Deadline.
The OKRs you set in January are not a forecast. They’re a framework for the decisions you’ll make later in the cycle. The decision in week one is “what are we testing.” The decision in week five is “what’s working.” The decision in week eight is “where are we doubling down.”
Most quarterly cycles skip the week-five and week-eight decisions, and end up with a quarter that was effectively decided in January. That’s the cycle worth changing.
Book a Demo to see how OKR Leader makes initiative-level tracking and mid-cycle reallocation part of the standard check-in flow.
FAQs: Running OKRs as a Portfolio
What does it mean to run an OKR strategy like a portfolio?
It means picking one clear outcome (the objective), defining the measurable targets that prove you’ve achieved it (the key results), and identifying two or three candidate initiatives that could plausibly hit those targets. Each initiative is resourced lightly at the start of the cycle and tracked by its own leading indicator. Mid-cycle, you reallocate resources from underperforming initiatives to the ones generating signal.
How is this different from setting multiple OKRs?
It isn’t a structure for running more objectives. The portfolio is at the initiative or project layer beneath the OKR. You still hold to a small number of objectives per cycle. Two or three is the OKR Leader recommendation, not five or six. The optionality lives in how you’re going to hit each objective, not in how many objectives you’re running.
Doesn’t running multiple initiatives split focus?
It can, if you over-commit. The discipline is in resourcing each initiative lightly upfront and being willing to actually kill losers at the mid-cycle review. Teams that resource three initiatives at full intensity from week one aren’t running a portfolio. They’re running three parallel quarters at half effort. The portfolio model only works if reallocation is a real decision.
When does mid-cycle reallocation happen?
Around week four or five of a thirteen-week cycle, with a smaller second look around week eight or nine. By week four, the leading indicators on each initiative usually have enough data to separate signal from noise. The reallocation conversation belongs in your standard weekly OKR check-in, not in a separate strategy meeting.
What types of objectives benefit most from this OKR strategy?
Objectives where the outcome is meaningful but the path to it is genuinely uncertain. Pipeline growth, retention improvement, activation lifts, market expansion, new product adoption. Anywhere the outcome is clear but there are multiple credible strategies to get there. Binary outcomes (compliance milestones, contract closures) and well-tested strategies (where the path isn’t a hypothesis anymore) don’t benefit from this structure.
TL;DR
The OKRs you set in January aren’t a forecast. They’re a framework for the decisions you’ll make later in the cycle. Most teams treat them as a commitment to a single strategy, then discover in March that the strategy didn’t work. The portfolio approach to OKR strategy keeps the objective and key results singular and runs two or three candidate initiatives underneath, each with leading indicators. By week five, the data tells you which path is winning. You reallocate hard. The quarter ends on a strategy that was selected by evidence, not the strategy you guessed at in January.
