Why your AI strategy needs a portfolio view

Most organizations evaluate AI investments one project at a time. Each initiative goes through a business case, gets a budget, gets a team, and gets evaluated on whether it delivered. This is how most capital allocation decisions work, and it produces reasonable outcomes in stable, predictable environments.

AI investment is not a stable, predictable environment. The technology is changing fast enough that an investment that made sense twelve months ago may have been superseded by a cheaper, better alternative. The organizational learning from one initiative affects the viability of the next. The sequence in which investments are made determines which ones are feasible. And the political capital available to support AI work is finite and shared across all initiatives.

Portfolio thinking addresses these dynamics in ways that project-by-project evaluation cannot.

What portfolio thinking changes

Evaluating AI investments as a portfolio means asking a different question at the start. Instead of “will this project deliver value?”, the portfolio question is “what mix of investments, taken together, gives us the best expected outcome given our risk tolerance, capability constraints, and strategic priorities?”

The difference is not just philosophical. It changes which projects get funded, in what sequence, and with what level of commitment.

A project-by-project approach optimizes each initiative independently. If you have ten potential AI initiatives and you evaluate each on its own merits, you might fund the five with the best individual business cases. But those five might all be in the same domain, requiring the same organizational capability, creating the same kind of risk, and producing results on the same timeline. A portfolio view would look at that allocation and ask: are we too concentrated? Do we have anything that builds organizational learning we can apply to multiple areas? Do we have a mix of timelines, so we can show progress while the longer-term bets are developing?

The three horizons

A useful structure for AI portfolio allocation is a three-horizon framework, adapted from McKinsey’s original model to the specific dynamics of AI investment.

Horizon 1 (now, 0-12 months): Operational improvement. These are AI applications to existing processes where the data exists, the use case is well-defined, and similar applications have been deployed elsewhere. Examples: document processing automation, customer support triage, structured data analysis. These investments have relatively predictable outcomes, shorter payback periods, and produce credibility within the organization. A portfolio without horizon 1 investments has no near-term wins to sustain political support for the overall program.

Horizon 2 (developing, 1-3 years): Capability building and application expansion. These are investments in new AI-enabled capabilities that require building organizational readiness alongside the technology. Examples: AI-augmented product development, intelligent operations with meaningful human-AI collaboration, data infrastructure that enables future AI applications. These investments take longer to show returns and require more organizational change management than horizon 1. They often depend on horizon 1 successes to build the organizational credibility and data assets that make them viable.

Horizon 3 (emerging, 3+ years): Transformation bets. These are investments in AI capabilities that could fundamentally change the business model or competitive position. Examples: proprietary AI systems trained on unique organizational data, AI-native products that did not exist before, capability to operate at a scale or speed the industry has not seen. These investments are speculative by nature, have high variance, and often depend on horizon 2 capabilities being in place.

Most organizational AI portfolios are miscalibrated in one of two ways. They are either too concentrated in horizon 1 (safe, incremental work that does not build competitive advantage) or too ambitious in horizon 3 (transformation bets without the organizational foundation to execute or sustain them). The right allocation varies by organization, but a rough starting point is something like 70/20/10 across H1/H2/H3, adjusted based on organizational AI maturity and competitive context.

Sequencing matters

Portfolio thinking also addresses sequencing, which project-by-project evaluation misses entirely.

Some AI investments unlock others. Investing in data quality and infrastructure before building AI applications produces better applications, at lower cost, than the reverse. Investing in model evaluation capabilities before deploying AI systems in high-stakes contexts catches problems that cost far less to fix before deployment than after. Investing in AI literacy and change management capability early reduces the friction of every subsequent AI initiative.

The sequencing question (which investments need to come before which others, and which dependencies constrain the overall program) is invisible when each project is evaluated in isolation. It becomes visible when the investments are mapped as a portfolio and the dependency structure is made explicit.

A common sequencing mistake is treating infrastructure investments as separate from application investments, optimizing each layer independently, and then discovering the dependencies when it is too late. Data platforms get built without consideration for the AI applications they will need to support. AI applications get built without the data infrastructure to run them reliably. The result is expensive rework that could have been avoided with earlier coordination.

Risk calibration across the portfolio

Project-by-project evaluation also produces systematic risk miscalibration. Each project team advocates for its initiative, which creates pressure toward optimistic assumptions in individual business cases. The aggregate portfolio ends up with more risk than leadership intended and understands.

A portfolio view lets risk be managed at the level where it actually matters. If five concurrent AI initiatives all depend on the same organizational change capability, or the same leadership sponsor, or the same vendor, that concentration is only visible when the initiatives are viewed together. Individually, each looks like it has been through appropriate risk review. Together, they represent a correlated exposure that could fail simultaneously if the shared dependency fails.

Risk calibration at the portfolio level also clarifies the value of diversification. An organization that has three AI initiatives, each with a 60% probability of success, has a higher probability of at least one significant success than the same organization that has one AI initiative with 80% probability of success. The expected value calculation looks different at the portfolio level than at the project level.

What a portfolio view requires

Moving to portfolio thinking requires a few things that project-by-project approaches do not.

It requires visibility across initiatives. If AI investments are funded and managed through siloed business unit budgets without central visibility, portfolio-level analysis is impossible. This does not mean centralizing all AI investment decisions; it means creating the shared view that enables portfolio-level questions to be asked.

It requires explicit allocation targets. A portfolio without targets drifts toward whatever is easiest to justify project by project. Setting explicit targets for H1/H2/H3 allocation, for risk concentration, and for strategic theme distribution creates the constraint that makes portfolio management meaningful.

It requires review at the right cadence. Annual planning cycles are too slow for AI portfolios given how fast the landscape changes. A portfolio review cadence of quarterly or semi-annual, with lightweight monthly tracking, gives enough visibility to rebalance when circumstances change without creating excessive overhead.

And it requires willingness to defund. A portfolio that never removes projects accumulates initiatives that have been superseded, that have lost their champion, or that were always more speculative than the original business case suggested. The discipline of portfolio management includes regularly evaluating whether each investment still belongs in the portfolio, not just whether it is making progress against its original plan.

The organizations that build durable AI capability tend to treat AI investment as a portfolio management problem from the start. They allocate across time horizons intentionally, sequence investments with dependencies in mind, manage risk at the aggregate level, and adjust the portfolio as circumstances change. The ones that struggle tend to fund whatever has the strongest internal advocate at any given moment, evaluate progress against the original business case rather than current alternatives, and discover portfolio-level problems after they have accumulated rather than before.