The Two Documents That Never Met
How PMOs Can Connect Strategy, OKRs, and the Project Portfolio
It is Tuesday. You have two browser tabs open.
One is the annual strategy deck: bold verbs, a nice gradient, and phrases like “become the market leader in customer trust.”
The other is your live project list: forty-two rows, some of them named things like “Phoenix Migration Phase 2” and “CRM Cleanup (Dave).”
Here is the uncomfortable part:
Nobody in the building can draw a clean line from the first tab to the second.
The strategy sounds important. The project list sounds busy. Somewhere between them, a lot of money, time, and effort is quietly going toward work that may not move the strategy one inch.
This is the gap that OKRs and portfolio management are supposed to close.
OKRs define the outcomes the organization wants to achieve. Portfolio management determines which investments receive funding, people, and time to help achieve them.
One without the other leaves a gap.
---
What an OKR Is, and What It Is Not
Let us define the terms before leaning on them, because the word objective gets used for everything from a mission statement to a task on somebody’s to-do list.
An objective is a short, plain description of a meaningful change you want to see. It is directional and should feel ambitious without becoming vague.
A key result is how you will know that change occurred. It is a measurable outcome, not a task.
Task: Launch the loyalty program.
Key result: Increase the repeat purchase rate from 22 percent to 30 percent.
That distinction matters.
> Objectives describe the change. Key results prove whether it happened. Projects are the work you fund to get there.
A project is not a key result. Completing the work does not automatically mean the desired outcome happened.
You can launch the loyalty program on time, stay within budget, and still fail to improve customer retention.
That is why a project should not be considered successful simply because it reached the finish line. The portfolio should continue tracking whether the expected business result actually occurred.
A quick warning: OKRs are not free.
They take real discussion to write well. They require leadership agreement, meaningful measures, and regular review. They also tend to rot quickly when nobody revisits them.
Treat OKRs as a living agreement about outcomes, not a poster for the break room.
---
The Honest Bridge Between Strategy and Projects
Once objectives and key results exist, every project in the portfolio should be able to answer a basic question:
What outcome, obligation, capability, or dependency justifies this investment?
For directly strategic work, the next question is:
Which key result does this project support, and what contribution do we expect it to make?
Some projects will point directly to a key result. Others will not, and that does not automatically mean they should be canceled.
A healthy portfolio usually contains several kinds of work.
Strategic Initiatives
Projects intended to move a measurable business outcome.
Mandatory Work
Regulatory, legal, security, contractual, or compliance investments that the organization must complete.
Operational Work
Maintenance, support, upgrades, and other keep-the-lights-on activities required to operate the business.
Risk Reduction and Technical Debt
Work that may not create an immediate business result but reduces exposure, improves stability, or protects future delivery.
Enabling Investments
Projects that do not directly move a key result but create a capability or remove a dependency for projects that do.
Experiments and Strategic Options
Small investments designed to test an idea, reduce uncertainty, or prepare the organization for a future opportunity.
The point is not to force every project into an OKR.
The point is to make the reason for every investment visible.
When a project has no measurable outcome, no mandatory requirement, no enabling purpose, and no credible strategic hypothesis, it may simply be a habit nobody has questioned in two years.
That is valuable information.
---
Alignment Should Be a Hypothesis, Not a Promise
Portfolio plans often pretend to be more certain than they really are.
A team may believe a project will increase retention by five percentage points, reduce processing time by 20 percent, or generate $2 million in new revenue.
Those estimates may be reasonable, but they are still assumptions.
A strong project-to-key-result link should include more than a checkbox.
It should capture:
- The primary key result the project is expected to support
- Any legitimate secondary key results
- The project’s expected contribution
- The evidence supporting that estimate
- A confidence level
- The person who owns the expected benefit
- The date when the result will be measured
This changes the conversation from:
> “This project supports customer retention.”
to:
> “We believe this project could improve repeat purchases by five to seven percentage points, with medium confidence, assuming customer adoption reaches the forecasted level.”
That is a much more honest portfolio conversation.
---
A Worked Example
Imagine you run the PMO for a mid-sized retailer.
Leadership establishes the following objective for the next six months:
Objective: Make Returning Customers Feel Like the Business Remembers Them
Two key results sit beneath it:
- KR1: Increase the repeat purchase rate from 22 percent to 30 percent.
- KR2: Reduce customer support response time from 14 hours to under 4 hours.
Now the PMO maps proposed investments against those results.
Loyalty Program Rebuild
The loyalty program rebuild primarily supports KR1.
The team estimates it could contribute between five and seven percentage points to the repeat purchase rate, with medium confidence. That estimate assumes customers adopt the program at the expected rate.
This is a strong strategic link, but it is still a hypothesis that must be measured after launch.
Support Chat Overhaul
The support chat overhaul directly supports KR2.
The team believes it can reduce average response time to under four hours, assuming the planned staffing model remains in place.
Again, the project does not control the outcome by itself. Staffing levels, customer volume, adoption, and operating processes will also affect the result.
Warehouse Robotics Pilot
The warehouse robotics pilot is exciting, expensive, and potentially valuable.
It also does not support either of the current key results.
That does not necessarily mean the pilot is a bad investment. It may support another strategic objective, reduce long-term labor risk, or represent an innovation experiment.
Leadership now has three honest choices:
- Align it to another approved strategic objective.
- Fund it through a clearly defined innovation or experimentation allocation.
- Defer it until capacity and funding become available.
What leadership should not do is pretend it supports customer retention simply because that is the objective currently receiving attention.
CRM Cleanup (Dave)
At first glance, CRM Cleanup (Dave) appears to be ordinary technical work.
Once the portfolio team looks more closely, it becomes clear that both the loyalty program and the support overhaul require accurate customer records.
The cleanup project does not directly move either key result. It is an enabling dependency that both strategic projects need.
That distinction matters.
A project does not need to create value independently if it clearly enables another investment to create value.
It does, however, need to be labeled honestly.
---
Where the Real Tradeoff Appears
The loyalty rebuild and the support overhaul both require the organization’s only senior integration engineer.
Same person. Same six weeks.
This is not an OKR problem.
It is a capacity and sequencing problem.
OKRs will not create another engineer. They will not eliminate dependencies or resolve scheduling conflicts.
What they do is frame the tradeoff honestly.
Leadership is no longer choosing between two vaguely important projects called loyalty and support.
Leadership is choosing which measurable outcome receives the scarce resource first:
- The 30 percent repeat purchase target
- The four-hour support response target
Leadership chooses KR2 first because slow support is actively losing the customers the loyalty program hopes to retain.
The support overhaul receives the engineer first. The loyalty rebuild begins three weeks later. Dave’s CRM cleanup runs in parallel because it enables both.
Notice what happened.
The conversation moved from “everything is important” to a sequence people can understand and execute.
That is the value of connecting strategy to the portfolio.
---
Prioritization Is Not Enough
Many organizations believe they have solved portfolio planning because every project has a priority score.
Unfortunately, priority scores do not account for time.
You can assign three projects the labels high, critical, and executive priority and still discover that all three need the same engineer on the same Monday.
A ranked list tells you what matters more.
A sequence tells people what should happen next.
That is why a portfolio plan needs to consider:
- Strategic contribution
- Mandatory deadlines
- Expected benefits
- Risk
- Dependencies
- Available capacity
- Scarce skills
- Funding
- Timing
- Confidence
The PMO’s job is not merely to produce a list of important work.
It is to help leadership create a realistic investment sequence that the organization can actually deliver.
---
Where a PPM Tool Helps
You can perform this exercise in a shared spreadsheet.
Create columns for:
- Objective
- Key result
- Project
- Investment category
- Expected contribution
- Confidence
- Benefit owner
- Dependencies
- Required skills
- Planned timing
Honestly, a well-maintained spreadsheet is more valuable than an expensive platform nobody trusts.
The challenge begins when the portfolio grows and conditions change.
A project slips. A regulation creates mandatory work. A scarce employee becomes unavailable. A key result falls behind. Leadership introduces a new objective. A dependency changes. Funding is reduced.
Now the organization must understand how each change affects the rest of the portfolio.
That is where a PPM platform becomes useful.
A portfolio tool should preserve traceability across:
> Strategy → Objectives → Key Results → Investments → Projects → Capacity → Delivered Outcomes
Perspective helps organizations connect projects to strategic objectives, categorize investments, map dependencies, and sequence work against shared capacity.
This allows leaders and PMOs to answer questions such as:
- What percentage of our capacity is supporting strategic objectives?
- Which key results are underfunded?
- Which projects are mandatory, operational, or enabling?
- Where are the same scarce people overcommitted?
- Which dependencies are putting strategic outcomes at risk?
- Are completed projects producing the benefits we expected?
- Which investments should be delayed, reshaped, or stopped?
The software does not create the discipline.
It makes the discipline easier to maintain when the portfolio changes.
If the OKRs are vague, the capacity data is fictional, or project-to-result links are based on wishful thinking, no tool will save the portfolio.
Write the honest links first. Automate them second.
---
How to Start This Week
You do not need a reorganization.
You need a few focused hours, leadership attention, and a willingness to hear uncomfortable answers.
1. Choose One Real Objective
Select one objective leadership genuinely cares about this quarter.
Do not start with the entire corporate strategy. Start with one outcome that matters now.
Write two or three measurable key results beneath it.
2. Map the Relevant Portfolio
List every active or proposed project that claims to support the objective.
Assign one primary key result to each strategic project. Add secondary relationships only when they are meaningful.
For projects without a direct strategic link, identify whether they are:
- Mandatory
- Operational
- Risk reduction
- Enabling
- Experimental
- Unjustified
Do not force the connection.
3. Record the Expected Contribution
Estimate how much each project is expected to contribute to its key result.
Capture the supporting evidence and confidence level.
The estimate will not be perfect. That is acceptable.
An imperfect, visible assumption can be tested. An invisible assumption cannot.
4. Find the Real Constraints
Identify the specific people, skills, vendors, environments, approvals, and dependencies each project requires.
Look for the same names and capabilities appearing more than once.
That is where your real portfolio conflicts usually live.
5. Sequence the Work
Do not stop after ranking projects.
Decide what begins first, what follows, what runs in parallel, and what must wait.
Base the sequence on:
- Which outcome is most urgent
- Which work unlocks other work
- Which deadlines cannot move
- Which resources are genuinely available
- Which assumptions carry the greatest risk
6. Review the Map With Delivery Teams
Share the portfolio map with the people who own and perform the work.
Ask them where the plan is wrong.
It will be wrong somewhere.
A hidden capacity issue, missing dependency, unrealistic estimate, or unsupported benefit assumption will surface.
That is not a failure of the exercise.
That is the exercise working.
7. Revisit It Regularly
Strategy alignment is not a one-time intake activity.
Review the portfolio regularly and ask:
- Are the key results moving?
- Are the projects still expected to contribute?
- Have capacity or dependencies changed?
- Are the original assumptions still credible?
- Should any investment be accelerated, delayed, reshaped, or stopped?
- Did completed projects deliver the benefits they promised?
The portfolio should change when the evidence changes.
---
The Final Test
Someone’s favorite project may land in the parking area.
A highly visible initiative may turn out to have a weak link to strategy.
A small technical project with an unfortunate name may prove essential to multiple business outcomes.
People will have opinions.
That is not a failure of the method.
That is the method working out loud.
Strategy is not what the organization wrote on a slide.
Strategy is what receives funding.
It is what receives scarce capacity.
It is what your calendar, your roadmap, and your one overbooked integration engineer actually do next week.