Strategic Portfolio Management

Classic annual planning is centrally gathered, detailed and therefore often wrong. It creates a false sense of precision, encourages buffers and commitment-based steering, and leaves no current overview when priorities shift. Rolling planning keeps the annual frame but reviews and adjusts it regularly, based on changes in projects, market conditions and new requirements.

Structure: plan everything that consumes capacity, i.e. services (run), projects and continuous improvement budgets (change). Start rough: whether a workload is 118 or 122 percent is secondary; what matters is that the conflict becomes visible. Precision comes with iteration. Put ownership where the work happens: project leads and service owners plan, not a central PMO. Establish the trio of rolling planning: capacity planning, employee self-planning for the current and next month, and time reporting of actual work. Set a cadence: monthly for projects, quarterly for continuous improvements and services, with plan versus actual feeding the next cycle. Our Rolling Planning Implementation Guide describes each step with practical examples and expert tips.

Once visible, they can be solved deliberately: by reprioritizing or deferring, shifting capacity between areas, bringing in external support at short notice, or hiring where a bottleneck is structural. Equally important: when a new request arrives, everyone, from the CIO to each employee, can point to the consequences for work already running.

Bee360 makes the overload visible with data, which turns "we are busy" into a fact-based conversation about priorities. Demand inflow is managed so that every demand is either executed, cancelled or deferred. When a more important demand arrives, the question becomes which existing one is removed. Run capacities are visible via the services, smaller requests are bundled in continuous improvement budgets instead of flying under the radar. The result is fewer topics in parallel, more topics completed, and a data basis that protects the organization against unrealistic expectations.

This is why we see transparency on available capacity as the first prerequisite for effective demand and portfolio management, and rolling planning as the way to create it.

Demands are then assessed against business and IT criteria, a capability Forrester highlights as a standout, and checked for fit with the target architecture. Who decides depends on the size of the demand: smaller demands are decided by the owner of the relevant continuous improvement budget, larger ones by the responsible category owner or an IT council. A regular portfolio cycle, for example every quarter with a look two quarters ahead, keeps priorities current. We also recommend keeping the assessment proportionate. Beyond a certain point, more time spent on evaluation does not lead to better decisions; it only ties up capacity that is needed for delivery.

Because both are planned in one system, the ratio between run and change becomes visible and steerable. You can see how much capacity operations consume, where efficiency gains free up room for transformation, and how continuous improvement budgets bridge the two. This is what makes strategic steering of the overall IT effort possible.