Author column

The IT portfolio as a business growth tool

Technology investment priorities should be determined by business outcomes, not by the number of projects launched. Managing an IT portfolio is first and foremost about managing investments, scarce resources and the company's development.


A leather portfolio with glowing project cards

When every project is a priority

In any large company, there are far more ideas than resources available to implement them.

The commercial director wants to launch new products faster. Operations calls for process automation. The CFO is interested in reducing costs. Regional divisions push for changes specific to their needs. And the IT team insists on upgrading infrastructure and addressing technical debt.

Each of them is right in their own way.

The problem arises when every executive considers their own initiatives the most important and decisions are made one at a time — as requests arrive or according to the influence of their sponsors.

The result is dozens of approved projects, overloaded teams and a constant struggle for resources.

Yet no one can confidently answer a simple question: how closely does the entire set of technology initiatives align with the company's strategic goals?

An IT portfolio is not a project list

I see the IT portfolio as a tool for managing the company's development.

It is more than a list of initiatives with budgets, timelines and statuses. It is a mechanism for comparing fundamentally different investments and selecting those that deliver the greatest business value within existing constraints.

This requires common evaluation criteria:

  • Business impact. Which metric will change: revenue, cost, productivity, service speed or quality?
  • Total cost. What will it cost not only to develop and implement the solution, but also to operate it over time?
  • Risks. What happens if the project is not implemented or is postponed?
  • Dependencies. Which other initiatives are needed to achieve the outcome?
  • Resources. What specialists, systems and management attention will be required?

With this model in place, discussions between business and IT become substantive.

Instead of arguing over whose project matters most, the conversation turns to which investments the company can afford and what outcomes it wants to achieve.

Not all investments should be assessed in the same way

One mistake in portfolio management is attempting to compare every initiative using a single financial metric.

I would distinguish three categories.

The first is mandatory investment: information security, resilience, regulatory compliance and addressing critical technical debt. Its value often lies not in generating additional revenue but in preventing losses.

The second is operational efficiency: process automation, reducing the cost of operations, and improving productivity and service quality. Here, it is usually possible to establish baseline metrics and calculate the expected impact.

The third is development and new opportunities: new products, digital sales channels, entry into new markets and experimental technologies. Such initiatives may have considerable potential, but also greater uncertainty.

These categories should compete for the same pool of investment resources, but under transparent rules. We cannot sacrifice resilience entirely for growth. Equally, we cannot keep upgrading infrastructure indefinitely without creating new value.

Management's task is to maintain a reasonable balance.

Who sets the priorities?

I consider it essential that IT should not remain the sole arbiter between business units.

The CIO should provide a professional assessment of complexity, cost, architectural implications and risks.

The business sponsor should be accountable for the expected impact and subsequent use of the outcome.

But the final decision about allocating scarce resources belongs to the company's leadership.

This issue is particularly acute in organizations with multiple divisions or lines of business.

If divisions set their priorities independently while headquarters can elevate its own initiatives above all others at any moment, the portfolio effectively becomes unmanageable.

A transparent decision-making mechanism is therefore essential: who may initiate a project, who assesses its value, who resolves conflicting priorities and who is accountable for the final outcome.

Prioritization rules must carry more weight than an executive's position or personal influence.

Knowing when to stop a project is also a result

Project management success has traditionally been measured by the number of completed initiatives, meeting deadlines and staying within budget.

But these indicators are insufficient for a portfolio.

Sometimes the best management decision is to stop a project that is no longer relevant, has changed substantially in cost, or no longer delivers the expected impact.

This is especially important for large programs, where initial assumptions can become outdated before development is complete.

I believe portfolio reviews should take place regularly, not just during the annual budgeting process.

And the company should have a normal practice not only for launching new projects but also for abandoning projects that have already been approved.

Otherwise, the portfolio gradually becomes a repository of commitments that no one dares to reconsider.

From project delivery to business outcomes

There is another important point.

A project may be completed successfully from IT's perspective: the solution has been developed, tested and launched.

Yet the business impact may never materialize.

Employees continue working as before. The new process is not embedded. Managers do not track changes in performance. The system's capabilities are only partially used.

Accountability for the outcome must therefore extend beyond implementation.

IT is accountable for the solution's operational reliability, architecture and technical quality. The business is accountable for changing the process, using the new capabilities and achieving the economic impact.

With this division of accountability, the portfolio becomes a portfolio of business changes enabled by technology rather than a collection of IT projects.

The guiding principle

For me, mature IT portfolio management begins with a company's willingness to make difficult decisions.

Not every good idea should be implemented. Not every project already launched needs to be completed. And not every demand from an influential executive should automatically become a priority.

The value of an IT portfolio lies not in the number of projects but in the company's ability to direct resources where they will deliver the greatest results.

That is when technology stops being a separate cost item and becomes a fully fledged tool for managing business development.