Strategic alignment is the degree to which the work an organization actually funds and staffs matches the strategy it claims to be pursuing. In a project portfolio it is not a mood or a slogan on a slide. It is a measurable property: write the strategic objectives down, score every project against them, and look at where the money and the people are really going. Most portfolios turn out to be less aligned than their leadership believes, and the gap shows up in the budget long before it shows up in any status report.
Key takeaways
- Alignment is measured in dollars and headcount, not in intentions. The honest metric is the share of portfolio spend flowing to each stated objective.
- Portfolios drift out of alignment by default. Nothing in the normal machinery of a company stops a project that has quietly stopped mattering.
- The mechanism that produces alignment is a cascade: strategic objectives, then explicit alignment criteria, then a score for every project, then a decision that some of them stop.
- The Henderson and Venkatraman Strategic Alignment Model (1993) is what most searches for "strategic alignment model" surface. It is a business and IT alignment framework, useful for vocabulary, and it is not a portfolio scoring method.
- The real test: name the project you stopped last quarter because it did not support an objective. If you cannot, your portfolio is annotated with strategy, not aligned to it.
What is strategic alignment?
Strategic alignment means that the decisions an organization makes about where to put its scarce resources, money, people, and management attention, follow from its strategy rather than from habit, politics, or whoever asked most persistently. At the portfolio level, it answers one question: if the strategy says growth in the mid market matters most, is the mid market where most of the budget and the best engineers went?
The word gets used at three different altitudes, and conflating them is why the conversation so often goes nowhere.
| Altitude | What alignment means there | Who owns it |
|---|---|---|
| Organizational | Functions, structure, and incentives support the strategy rather than fight it | The executive team |
| Portfolio | The projects that get funded and staffed are the ones that advance the objectives | The portfolio board, supported by the PMO |
| Project | The scope being delivered still serves the benefit that justified the project | The sponsor |
This article is about the middle row, which is the one a PMO can actually influence. You cannot fix a broken strategy from the portfolio, and you cannot fix a badly scoped project from the portfolio either. What you can do is make sure the set of things being funded corresponds to the set of things the company said it cared about, and make the mismatch visible when it does not.
Why portfolios drift out of alignment
Drift is the default state, and it is worth understanding the mechanism rather than blaming anyone. Four forces push a portfolio away from its strategy, and all four operate quietly.
Strategy changes faster than the portfolio does. A three year project was approved under the strategy of three years ago. The strategy has since been rewritten twice. The project has a team, a plan, and a sponsor who still believes in it, and nothing in the calendar forces anyone to ask whether it still fits. So it finishes, and it delivers something the company no longer needs.
Nothing kills a project. Approving work is a well defined process with forms and committees. Stopping work is an act of individual courage, usually taken by someone who will be blamed for the sunk cost. Given that asymmetry, the rational move for every sponsor is to keep going, and the portfolio slowly fills with the living dead.
Run the business eats change the business. Maintenance, compliance, keeping the lights on: this work is genuinely mandatory and it expands to fill whatever capacity you give it. If nobody explicitly ring fences a share of capacity for strategic change, the urgent will consume the important, quarter after quarter, and everyone will be busy while nothing moves.
Alignment is asserted rather than scored. Every business case in the world claims strategic alignment, because the template has a box for it and the author fills the box in. A claim that nobody scores, compares, or challenges is not evidence. It is decoration, and it is why a portfolio can be 100 percent aligned on paper and obviously incoherent in practice.
The strategic alignment model (Henderson and Venkatraman)
If you search for a strategic alignment model, the thing you will find is the SAM, published by John Henderson and N. Venkatraman in the IBM Systems Journal in 1993. It is worth knowing what it is, mostly so you know when it is not what you need.
SAM maps four domains: business strategy, IT strategy, organizational infrastructure and processes, and IS infrastructure and processes. It relates them along two dimensions. Strategic fit is the vertical link between the external world (strategy) and the internal one (infrastructure and processes). Functional integration is the horizontal link between the business side and the IT side. From those it derives four alignment perspectives, each starting from a different driver: strategy execution, technology potential, competitive potential, and service level.
The enduring insight is the one people skip. Alignment is not a single arrow running from business strategy down to IT. Technology can be the driver, with a new capability reshaping what strategy is even possible, and the model was unusual in 1993 for saying so. That is still the most useful thing about it.
What SAM is not is a method for choosing projects. It gives you no criteria, no scoring, no ranking, and no way to decide whether the CRM replacement beats the pricing engine this quarter. It is a framework for thinking about business and IT alignment as a whole. When a search for "strategic alignment model" is really a search for "how do I rank these 40 projects against our strategy," the answer is the cascade below, not SAM.
How to align a project portfolio with strategy
Alignment is produced by a cascade that runs from objectives down to individual funding decisions. Each step is unremarkable. The discipline is in doing all five, and not stopping after step three, which is where most organizations stop.
1. Write the objectives down, and keep them few. You cannot align to a strategy nobody can state. Get to somewhere between three and six objectives for the year, specific enough to be falsifiable. "Grow revenue" is not an objective, it is a hope. "Reach 30 percent of new revenue from the mid market segment" is something a project can plausibly support or fail to support. Many US companies express these as OKRs, and the format helps, because the key results give you the measurable edge that makes scoring possible. What matters is not the format but that the objectives are written, ranked, and stable enough to score against for a quarter.
2. Turn objectives into alignment criteria. An objective is not directly scorable. Convert each one into a criterion with a weight, so "supports mid market growth" becomes a line in your project scoring model with an agreed weight and a defined scale. Weight them deliberately: if one objective genuinely matters more this year, its weight should say so, because equal weights across six objectives is a way of declining to have a strategy.
3. Score every project, including the ones already running. New proposals get scored at intake, which most PMOs already do. The step that actually produces alignment is scoring the existing portfolio, because that is where the drift lives. Score the in flight work against this year's criteria, not the criteria it was approved under. Expect this to be uncomfortable, and expect a couple of well liked projects to score badly.
4. Look at the portfolio in aggregate, not project by project. Sum the planned spend by objective. This single table is the most useful artifact in portfolio management, because it converts an argument into arithmetic. If the strategy says mid market is the priority and 9 percent of the change budget is pointed at it, no amount of enthusiasm in the steering committee changes what the numbers say. The portfolio prioritization process is where this table gets acted on.
5. Stop something. This is the step that separates aligned portfolios from annotated ones. Alignment is only real if a low scoring project actually loses its funding, because capacity is finite and every unaligned project is holding people that an aligned one needs. If nothing is ever stopped, the scores are theater. Stopping work is a governance act rather than an analytical one, which is why it needs the authority of the portfolio governance body behind it and a standing slot at the portfolio review meeting.
A strategic alignment example
Take a company with three objectives for the year. O1, grow mid market revenue (weight 50 percent). O2, cut cost to serve (weight 30 percent). O3, meet the new regulatory deadline (weight 20 percent). Each project is scored 0 to 5 on how strongly it advances each objective, and the weighted total is its alignment score. The figures below are illustrative.
| Project | O1 (50%) | O2 (30%) | O3 (20%) | Alignment score | Planned spend | Decision |
|---|---|---|---|---|---|---|
| Mid market self serve onboarding | 5 | 3 | 0 | 3.4 | $1.2M | Fund, accelerate |
| Regulatory reporting rebuild | 0 | 1 | 5 | 1.3 | $0.9M | Fund (mandatory) |
| Support automation | 1 | 5 | 0 | 2.0 | $0.6M | Fund |
| ERP module upgrade | 0 | 1 | 0 | 0.3 | $1.4M | Challenge, defer |
| Enterprise CRM refresh | 1 | 0 | 0 | 0.5 | $1.1M | Challenge, defer |
Now read it in aggregate, which is where it stops being an academic exercise. The top objective, worth half the strategy, is attracting $1.2M of a $5.2M change budget, which is 23 percent. Meanwhile $2.5M, nearly half the portfolio, is going to two projects with alignment scores under 0.6. Nobody set out to do that. It is simply what happens when projects are approved one at a time, each on its own merits, and never compared against each other in a single table.
Two honest caveats keep this from being naive. First, a low alignment score is not automatically a kill order. The regulatory rebuild scores 1.3 and is mandatory, because you do not opt out of the law, so mandatory work should be flagged as a separate class rather than pushed through a scoring model that will always rank it badly. Second, the ERP upgrade may be technical debt that will cause an outage in 18 months, and pure strategic scoring is blind to that. This is why serious portfolios score value and risk alongside alignment instead of treating alignment as the only axis, a point covered in project prioritization criteria.
How do you measure strategic alignment?
Alignment measured once is a workshop. Alignment measured every quarter is a management system. Four metrics do almost all the work, and each one produces a number a board can act on.
| Metric | How to calculate it | What it tells you |
|---|---|---|
| Spend by objective | Planned portfolio spend grouped by the objective each project serves | Whether the money follows the stated priorities. The single most revealing number in the pack. |
| Run versus change ratio | Keep the lights on spend divided by discretionary change spend | How much capacity is left for strategy at all. A ratio drifting toward run means strategy is being squeezed regardless of how well you score. |
| Share of spend below the alignment threshold | Spend on projects scoring under an agreed floor, as a percentage of the portfolio | The size of the drift. Track it quarter over quarter. It should fall. |
| Projects stopped for misalignment | Count per quarter, with the capacity released | Whether governance has teeth. A permanent zero means the scoring is connected to no decision at all. |
All four belong on the same page as delivery performance in your portfolio KPIs, because a portfolio that is perfectly on time and perfectly misaligned is an expensive way to go nowhere. And alignment at approval is only half the job. The benefits realization discipline is what checks, after delivery, whether the objective actually moved.
Strategic alignment, strategic planning, and portfolio management
Three terms get used loosely in the same meetings. Strategic planning is the process that produces the strategy: the objectives, the choices, the direction. Strategic alignment is the property you get when execution follows those objectives, and it is a condition rather than a process. Strategic portfolio management is the discipline whose whole job is producing that property, continuously, by connecting the plan to the funded work.
Put plainly: planning decides where to go, alignment is whether you are actually going there, and portfolio management is the steering. That is also why alignment cannot be an annual exercise bolted onto the budget cycle. Strategy shifts, projects overrun, and new demand arrives every month, so the portfolio has to be re-pointed on a rhythm, which is the argument for continuous planning over an annual set and forget.
Frequently asked questions
What is strategic alignment?
Strategic alignment is the degree to which an organization's resources, projects, and daily decisions support its stated strategy. In portfolio terms it means the projects that get funded and staffed are the ones that advance the strategic objectives. It is measured rather than asserted, and the practical test is what share of the change budget flows to each objective.
What is an example of strategic alignment?
A company whose top objective is mid market growth scores every candidate project against that objective, funds the self serve onboarding platform that scores 5 out of 5, and defers a CRM refresh that scores 1. The alignment is visible in the outcome: the largest share of the change budget sits behind the highest weighted objective, and a well liked project was deferred to make that true.
What is the strategic alignment model?
The Strategic Alignment Model (SAM), published by Henderson and Venkatraman in the IBM Systems Journal in 1993, maps four domains (business strategy, IT strategy, organizational infrastructure, and IS infrastructure) across two dimensions, strategic fit and functional integration, and derives four alignment perspectives. It is a business and IT alignment framework rather than a project scoring method, so it will not tell you which projects to fund.
Why is strategic alignment important?
Because capacity is finite. Every person working on a project that does not support an objective is a person unavailable for one that does, so misalignment is not a reporting problem, it is a direct tax on the strategy's chance of succeeding. Alignment also makes trade offs debatable in public against a shared score, instead of settling them by seniority.
How do you measure strategic alignment?
Score each project against weighted strategic objectives, then aggregate: total planned spend by objective, the share of spend on projects below your alignment threshold, the run versus change ratio, and the number of projects stopped for misalignment each quarter. The spend by objective table is the most revealing of the four, because it compares stated priorities against funded ones.
What is the difference between strategic alignment and strategic planning?
Strategic planning is the process that sets the objectives and the direction. Strategic alignment is the resulting condition, whether the funded work actually follows them. Planning happens in a room over a few weeks. Alignment either survives or erodes over the following year, depending on whether anyone scores the portfolio against the plan and is willing to stop the projects that no longer fit.
How do OKRs support strategic alignment?
OKRs give objectives a measurable edge, and a measurable objective is one a project can be scored against. The key results become the alignment criteria in a scoring model, so "supports the mid market objective" turns into a weighted line item rather than an assertion in a business case. The format is not essential. What matters is that objectives are written down, ranked, and stable enough to score a portfolio against.