Why Your PMO Gets 200 Requests But Funds 80 Misaligned Projects and How to Fix it

TL;DR

Most organizations spend significant energy on portfolio prioritization methodology, scoring criteria, weighted matrices, and gate reviews. The misalignment problem they are trying to solve at prioritization was created six months earlier, at intake. When business units submit requests without a structured strategic linkage, the PMO inherits a pipeline of misaligned proposals and must filter them at the point of decision. The fix is moving the strategic alignment conversation to the moment of submission, before a business case is written, before organizational capital is invested, and before the imbalance is already baked into the pipeline.

Your organization has five clearly defined strategic objectives. They were developed over months of alignment on leadership. They appear in board presentations, quarterly reviews, and the company intranet. Every business unit leader can recite them.

And yet, when you look at your intake pipeline, the connection between those objectives and the projects being funded is tenuous at best.

Some strategic priorities have forty competing requests. Others have two. Your PMO team spends weeks reviewing proposals that had no genuine strategic alignment from the moment they were submitted. By the time the portfolio review identifies the imbalance, you are already six months into executing projects that advance local agendas rather than enterprise objectives.

The problem is not your prioritization methodology. The problem is what arrives at prioritization. The strategic misalignment problem in most portfolios starts earlier than anyone looks for it at demand intake, not at prioritization.

The Real Cost of Misalignment at Scale

Strategic misalignment is not a governance abstraction. It has a direct financial consequence.

For illustrative purposes: on a $100M annual project portfolio, if 30% of approved projects are misaligned with declared strategic priorities, advancing divisional interests rather than enterprise objectives, that is $30M in annual investment that is not advancing the organization’s declared direction. Before accounting for the opportunity cost of what those resources could have delivered if allocated to genuinely aligned work.

A 2024 Gartner case study of IndigoPillar, a public sector organization with over 12,000 employees, documented exactly this pattern. Gartner found that “business stakeholders often struggle to align unit-level priorities with enterprise strategy during demand intake,” leading to what the research termed a “scattergun approach”: fragmented, strategically misaligned ideas submitted at intake that create a domino effect of missed value realization.

The operational consequences compound the financial ones. Incorrect effort estimates. Flawed resource planning. Prioritization decisions are made in an incomplete strategic context. And a PMO that discovers the portfolio is strategically unbalanced only after significant organizational capital has been invested in misaligned proposals.

The cost of strategic misalignment is not discovered at prioritization. It is confirmed there. It was created at intake.

Why Business Units Submit Misaligned Requests, and It Is Not Bad Faith

The most important thing to understand about strategic misalignment at intake is that business units are not gaming the system deliberately. They are responding rationally to a system that is poorly designed.

Three structural reasons explain why misalignment happens consistently:

1: Strategic objectives are too abstract to be actionable at the intake level.

“Improve operational efficiency” sounds clear in a board meeting. At the intake stage, it is genuinely ambiguous. A manufacturing director interprets it as automating production line monitoring. A finance director interprets it as automated invoice processing. An IT director interprets it as data center consolidation. All three interpretations are reasonable. None of them is necessarily wrong. But without a shared, specific definition of what the objective means at the enterprise level, three competing requests fragment the portfolio rather than concentrating it.

2: Business units have no visibility into what peers are submitting.

When manufacturing submits five efficiency initiatives and finance submits twelve, neither knows they are collectively creating a portfolio imbalance. The oversubscription of some objectives and the starvation of others is a portfolio-level pattern that is invisible at the business unit level. No individual submitter can see it because the pipeline view that would reveal it belongs to the PMO, which discovers it only after submissions arrive.

3: PMOs discover imbalance too late to prevent it.

By the time the PMO identifies that certain strategic objectives are oversubscribed and others are underfunded, proposals have been written, reviewed, and scored. Organizational capital has been invested. Stakeholder expectations have formed. Reversing the imbalance at that stage carries political costs that create pressure to fund misaligned work rather than reject it.

The fix is not a better scoring model. It is a different conversation, one that happens before the business case is written.

The Three Questions That Move the Conversation Earlier

The IndigoPillar EPMO solved the misalignment problem by restructuring intake around three questions that every request must answer before a business case is drafted. Not at submission. Before submission.

1: What Specific Strategic Outcome Does This Support?

The breakthrough IndigoPillar made was recognizing that strategic objectives alone are not sufficient anchors for intake alignment. Every objective needed to be deconstructed into specific, measurable outcomes across defined time horizons: near-term (0–12 months), mid-term (1–2 years), and long-term (2–3 years).

Instead of asking business units to align on a high-level objective, the EPMO defined the specific outcomes each objective was designed to achieve. These became the structured menu from which intake requests had to select, not free-text strategic justification, but a specific, pre-defined outcome node in the strategy tree.

What this looks like in practice:

Abstract Strategic Objective	Specific Actionable Outcome (Intake Anchor)
“Improve operational efficiency”	“Automate manual compliance reporting to reduce processing time by 40% within 12 months”
“Enhance customer experience”	“Reduce average customer query resolution time from 5 days to 24 hours by Q3”
“Strengthen digital capability”	“Migrate 80% of customer-facing services to self-service digital channels within 18 months”

For organizations using OKR frameworks, Key Results already serve this purpose. The intake process should require requesters to select the specific Key Result their initiative advances, not the Objective. The difference is the difference between “this supports our growth objective” and “this directly advances KR2: increase net revenue retention from 88% to 95%.”

2: What Business Outcome Will This Deliver and How?

Linking a request to a strategic outcome is necessary but not sufficient. IndigoPillar required business units to articulate a structured solution hypothesis: the business problem being solved, the proposed solution, and the explicit mechanism by which the solution produces the strategic outcome.

This requirement does two things simultaneously. It prevents gaming the system; business units cannot link a request to a popular strategic outcome without justifying the connection specifically. And it gives the PMO a substantive basis for early-stage evaluation before a full business case is invested.

The difference this creates:

Without Solution Hypothesis	With Solution Hypothesis
“This initiative supports our customer experience objective.”	“Automating customer follow-up within 24 hours of ticket resolution will increase our NPS from 42 to 55, directly contributing to KR2 of the customer experience objective.”
Checkbox governance	Real governance
PMO cannot evaluate alignment without reading the full business case	PMO can evaluate alignment from the intake record

Gartner’s research confirmed that IndigoPillar’s EPMO leader credited this approach with a measurable increase in the accuracy of strategic alignment claims: “Stakeholders often linked business cases to any strategic objective. We broke the strategy down and helped our stakeholders draft their business cases accordingly. We’ve seen an increase in accuracy of alignment and a healthy balance of work in the portfolio.”

3: Shift Portfolio Balance?

Strategic alignment is binary; a request either advances a declared outcome or it does not. Strategic balance is continuous, and you can have 100% of requests technically aligned while still having a strategically imbalanced portfolio if some outcomes are oversubscribed and others are starved.

IndigoPillar built three portfolio views that made balance visible at the intake stage before prioritization decisions were made:

1: Intake Pipeline by Strategic Outcome
Pending requests are grouped by strategic outcome, showing both the count and total budget requested per outcome. Oversubscribed and undersubscribed areas become immediately visible, with updates happening in real time as new submissions arrive.

2: Current Portfolio by Strategic Outcome
Approved and active projects are mapped against strategic outcomes, making investment concentration clearly visible. This view highlights how well the current portfolio aligns with declared strategic priorities and exposes any imbalance.

3: Scenario Planning View
Simulates the impact of approving a new batch of requests, showing how the overall portfolio balance would shift. It reveals which strategic outcomes would be reinforced and which would become further underfunded.

These are not complex analytics. They are simple aggregations of intake data count, budget, and outcome tag that surface strategic information at the moment the PMO needs it, rather than weeks after prioritization decisions have been made.

What IndigoPillar Achieved

The Gartner case study documented measurable outcomes from the restructured intake approach. IndigoPillar doubled the number of high-quality, strategy-aligned business ideas received from business units. Not the total volume of requests, but the quality of them.

The EPMO was able to standardize demand evaluation against clear strategic criteria rather than subjective assessments. Visibility into initiative pipelines improved across all business units. And the cultural shift was as significant as the operational one; business units stopped viewing intake as a hurdle to clear and began to view it as a strategic conversation. The EPMO shifted from being the function that filters what arrives to being the function that shapes what gets submitted.

The Implementation Sequence

The framework is straightforward. Successful implementation requires four decisions made in sequence.

1: Deconstruct strategic objectives into measurable outcomes.

Work with the strategy team to define two to four specific outcomes for each strategic objective, distributed across time horizons. If your organization uses OKRs, your key results already serve this purpose; the intake process should anchor to them directly. Outcomes must be concrete enough that a business unit can definitively say yes or no to alignment; vague outcomes defeat the purpose of the entire framework.

2: Redesign intake to require strategic linkage at submission.

Make strategic outcome linkage mandatory, not optional. Every request must select a specific outcome node. Every request must include a structured solution hypothesis of 100 to 200 words explaining the problem, the solution, and the outcome mechanism. Requests that cannot articulate this clearly do not advance. This is not bureaucracy. It is the quality gate that prevents misalignment from entering the portfolio in the first place.

3: Build the three portfolio balance views.

Create the intake pipeline view, the current portfolio view, and the scenario planning view as live dashboards updated as submissions arrive and decisions are made. The goal is to ask the question “Are we building a strategically balanced portfolio?” answerable in real time rather than retrospectively.

Step 4: Incorporate balance assessment into prioritization.

Before approving a batch of requests, run the scenario view: if these are approved, how does portfolio balance shift? This does not mean enforcing perfect balance, some objectives genuinely require more investment. But the decision to concentrate investment should be made consciously, not accidentally.

The prerequisite for all four steps: executive alignment. If leadership has not defined strategic outcomes clearly and will not reject requests that lack genuine justification, even from powerful stakeholders, mandatory strategic linkage becomes checkbox compliance. The technical mechanics are simple. The organizational commitment is the harder and more important variable.

Quick Audit: Is Your Intake Process Creating Strategic Misalignment?

#	Question	Yes	No / Partial
1	Can you see, in real time, how pending intake requests are distributed across your strategic outcomes?
2	Does every intake submission require selection of a specific strategic outcome, not just a high-level objective?
3	Does every submission include a structured explanation of how the proposed solution produces the strategic outcome?
4	Can your PMO run a scenario showing how portfolio balance shifts if the current intake pipeline is approved?
5	Does your intake process prevent advancement of requests that cannot articulate specific strategic linkage?

Three or more “No / Partial” answers mean your PMO is discovering strategic misalignment at prioritization after organizational capital has already been invested in proposals that should never have advanced.

Frequently Asked Questions

By the time misaligned requests reach the prioritization stage, organizational capital has already been invested in the written business cases, stakeholder expectations formed, and political positions taken. Rejecting misaligned work at prioritization carries costs that create pressure to fund it anyway. Moving the alignment conversation to intake, before the business case is written, prevents misaligned proposals from accumulating those protective costs.

What is a solution hypothesis in demand intake?

A solution hypothesis is a structured intake requirement that asks the submitter to state the business problem, describe the proposed solution, and explain the explicit mechanism by which the solution produces the declared strategic outcome. It prevents business units from claiming strategic alignment without justifying the connection specifically and gives the PMO a substantive evaluation basis before a full business case is invested

What is the difference between strategic alignment and strategic balance?

Strategic alignment is binary: a request either advances a declared strategic outcome or it does not. Strategic balance is continuous; it describes whether investment is distributed across strategic outcomes in a way that reflects organizational priorities. A portfolio can be 100% aligned, every project connected to a declared outcome, while still being strategically unbalanced if certain outcomes are oversubscribed and others are consistently underfunded

How do OKRs connect to demand intake governance?

In organizations using OKR frameworks, key results serve as the specific outcome nodes that intake requests should anchor to, not objectives. Requiring submitters to identify the specific key result their initiative advances and explain the mechanism by which it creates the contribution makes alignment claims verifiable rather than asserted. The objective level is too abstract for intake governance; the key result level is specific enough to evaluate

What executive commitment is required for this framework to work?

Executives must be willing to reject requests that lack genuine strategic justification, including requests from powerful stakeholders. Without that commitment, mandatory strategic linkage becomes checkbox compliance: submitters select an outcome node that technically fits and write a justification that technically satisfies the requirement, while the underlying misalignment persists. The technical mechanics of the framework are straightforward; the organizational commitment to enforce them is the harder and more important variable.