2.2.2: Evaluating Portfolio against the Strategic Goals

Project Genesis and Strategic Categorization 

Not every project in a portfolio gets born the same way. Some come from careful planning. Some come from an emergency nobody saw coming. Treating all of them the same at intake is a mistake. Where a project comes from should shape how it gets funded and reviewed.

Where Projects Actually Come From?

Projects tend to come from a handful of common sources. Some come from a real business need, like a company wanting to grow into a new market. Some come from compliance requirements handed down by regulators. Some come from plain necessity, like fixing something after a system failure. Some exist just to support customers or internal teams who need ongoing help.

Other projects get triggered by forces completely outside the company. A natural disaster can force a company to launch a recovery project overnight. A government agency can hand down a new reporting system with a hard deadline attached. A sudden shift in a business partner's needs can spin up a project nobody planned for at the start of the year. None of these show up on a five-year roadmap. They just show up.

Key Definitions: Three Project Categories

• Emergent Projects: new opportunities that show up unplanned.
• Strategic Projects: deliberate, planned growth initiatives that come out of formal planning sessions.
• Compliance Projects: mandatory work driven by law or regulation, usually required no matter what the numbers say.

These three labels are not just for sorting paperwork. They decide how much scrutiny a project gets before it receives funding, and skipping that step causes real problems down the line.

Why the Category Changes the Governance Path

Each type of project deserves a different level of review. Compliance projects often skip the normal financial screening completely, since the business has to do them just to keep operating legally. Strategic projects go through the full prioritization process, competing against other planned initiatives for funding. Emergent projects need a fast, lightweight path so the company can react quickly without throwing the rest of the portfolio into chaos.

Seeing these three categories laid out is useful, but a portfolio manager also needs a second way to sort projects, one based on where the money actually goes and whether spending it is even a choice.

Investment Categorization Matrix

Every dollar a company spends on a project falls into one of two spending types. Capital investment builds something new, like a factory or a piece of software. Operational spending keeps something already running, like paying for electricity or routine maintenance. Separately, every dollar also falls into one of two choice types. Mandatory spending has to happen, usually because of a law or a safety requirement. Optional spending is a choice the company makes because it thinks the investment will pay off.

Putting these two ideas together creates a simple two by two grid. It helps a portfolio manager see at a glance what kind of spending they are actually looking at, and whether that spending can be delayed if money gets tight. Table \(\PageIndex{1}\): Capital Versus Operational, Mandatory Versus Optional Spending lays out four types of portfolio spending with a plain example of each.

Table \(\PageIndex{1}\): Capital Versus Operational, Mandatory Versus Optional Spending  

	Mandatory	Optional
Capital Investment	Building a new safety system because a new law requires it	Building a new factory to enter a market the company chose to target
Operational	Paying for a required safety inspection every year	Adding a nice-to-have customer service upgrade that is not required

This grid connects directly back to the three categories from earlier. Compliance projects almost always land in the mandatory column, whether they involve building something new or just keeping something running. Strategic projects almost always land in the optional column, since a company chooses to pursue them because it expects a payoff. Emergent projects can land almost anywhere on this grid, depending on what actually triggered them. That flexibility is exactly what makes emergent projects tricky to plan around in advance.

Myth: A Project's Category Is Fixed Forever

It is easy to assume that once a project gets labeled emergent, strategic, or compliance, that label sticks for good. It does not always work that way. An emergent project that starts as a quick fix can turn into a full strategic initiative once it proves useful. A strategic project can quietly become mandatory if a regulator later decides to require what the company was only doing by choice. Treating a project's category as permanent, instead of checking it again as things change, is the real danger. A portfolio manager who never revisits old labels can end up governing a project the wrong way for months without noticing.

That risk of an outdated label gets even more serious once mis-categorization actually collides with real funding decisions, not just paperwork.

What Goes Wrong When Categorization Fails

Getting this sorting wrong causes real damage. If a compliance project gets stuck competing with discretionary growth initiatives for the same limited pool of funding, the company risks an actual regulatory failure while everyone sits around debating return on investment. Correctly labeling a project the moment it enters the portfolio protects both the required work and the optional growth work from unfairly fighting each other for money.

A Compliance Project Stuck in the Wrong Line

A mid-size manufacturer once dropped a new environmental compliance requirement straight into its normal project scoring queue, right alongside a handful of optional growth projects competing for the same budget. The compliance project scored lower on return on investment than the growth projects, since meeting a legal requirement rarely produces a profit on paper. Sitting in that queue for three months, the deadline for the actual regulation kept getting closer. Only when someone realized the project was legally required, not optional, did it jump the line and get funded immediately. The company avoided a fine, but only barely, and only because someone happened to catch the mistake in time.

Most mis-categorization problems look exactly like that one, a single project stuck in the wrong queue. But sometimes an event is big enough to scramble the whole portfolio at once, not just one project inside it.

When a Crisis Rewrites the Whole Portfolio

A sudden crisis does not just add one new emergent project to the list. It can force the entire portfolio to reshuffle overnight, pulling money and attention away from planned, optional work and pouring it into mandatory, crisis-driven work instead.

The BP Oil Spill: A Portfolio Reshuffled Overnight

The 2010 BP oil spill in the Gulf of Mexico is a clear example of this. Before the spill, BP's portfolio included plenty of planned capital investments, new drilling projects, exploration in new regions, and other optional growth initiatives the company had chosen to pursue. After the spill, nearly everything shifted. Billions of dollars that had been set aside for growth suddenly had to go toward cleanup operations, legal settlements, and new safety requirements handed down by regulators. Projects that had been sitting comfortably in the optional column of the grid described earlier got pushed aside, while an entirely new set of mandatory capital and operational spending took over almost the whole portfolio.

This is exactly why the grid from earlier in this chapter matters beyond just sorting individual projects. A crisis can move a huge share of a company's spending into the mandatory column all at once, without any warning and without any choice in the matter. A portfolio manager cannot predict exactly when a crisis will hit, but knowing that this kind of sudden shift is possible changes how a portfolio should be built in the first place. A portfolio stacked entirely with optional, long-term growth projects and no flexibility to absorb a sudden mandatory shock is a portfolio one crisis away from real trouble.

Sorting projects correctly at intake, whether by origin, by the capital versus operational grid, or by watching for a crisis that can rewrite the whole picture overnight, protects a company on every front. It keeps required work from getting stuck behind optional work. It keeps optional work from quietly turning invisible while nobody rechecks its label. And it keeps the whole portfolio ready to bend, rather than break, the day something like an oil spill shows up without any warning at all.