Skip to content

Tony Kenck insight

All Business Decisions Are Portfolio Decisions

Why the enterprise context, and the opportunity cost of every yes, decides whether a good project is actually a good decision.

The apparently good project

Most investment cases are built to stand on their own. A team assembles the economics, shows a positive return, and asks for approval. On its own terms the project looks sound, so it is approved. Repeat that a few dozen times and you have a plan.

The trouble is that no project happens on its own. It draws on the same capital, people, rigs, permits, attention, and balance-sheet capacity as everything else the organization is trying to do. A project that is attractive in isolation can still be the wrong thing to do this year, at this scale, ahead of these other commitments.

What standalone economics can and cannot tell you

Standalone metrics answer a narrow question well: is this opportunity worth more than it costs, given a set of assumptions? They do not tell you what the opportunity displaces, whether a smaller or later version would free resources for something better, or how it changes the risk of the whole enterprise.

Those are portfolio questions. They only appear when you compare the company that does this against the company that does something else with the same constrained resources.

All business decisions are portfolio decisions.

Tony Kenck, Strategic Business Portfolio Management

Every yes displaces something

Opportunity cost is the quiet center of portfolio thinking. Approving a project is also declining the alternatives it crowds out, whether or not anyone names them. When alternatives are never made explicit, the displaced option is invisible, and the organization congratulates itself on a decision it never actually compared.

The portfolio lens

A portfolio view keeps the same project and asset information you already use and adds context: the working inventory, meaningfully different alternatives, timing, constraints, dependencies, uncertainty, and enterprise objectives. It reframes the question from is this project good to which coordinated set of choices gives the enterprise the best future it can defend.

A simple two-asset example

Imagine two assets competing for one year of capital. Each team optimizes its own case and asks for full funding. Fund both at full scale and you breach the budget; fund the louder one and you may starve the better long-term position. A portfolio comparison tests coordinated options, phased funding, a smaller start on one, acceleration of the other, and often finds a combination that beats either standalone request.

Questions leaders should ask

What does this displace? What alternatives did we compare, not just describe? How does this change enterprise risk over time, not only this year's metric? If the answers are thin, the decision has not yet been made in portfolio terms.

A practical first step

You do not need a new platform to start. Name the decision, list the working inventory, and force two or three genuinely different portfolio alternatives onto the same page. The comparison itself usually changes the conversation.

Put the idea to work

Take the next useful step

Go deeper in the field manual, or start a low-pressure conversation about the decision in front of your team.

Buy bookConnect with Tony