Insight

Delivered on time, used too late

Your change was delivered on time, on budget, and it works. Three months later it is still sitting there unused, because the department that has to work with it had no room. A portfolio asks for capacity once, about building. The second question, when the organisation can take it on, decides when something starts paying off.

building people skills planning taking it on free attention time to learn the running work a portfolio usually counts only the left column
Frame 1 · Two questions

Capacity is asked for twice

Can we build this, with the people and the skills we have. And can the organisation take it on, alongside the work that is already running today. Most portfolios count only the first column, because that one can be expressed in hours.

Q1 Q2 Q3 Q4 build team free business free two quarters in between waiting costs, or the delivery ages
Frame 2 · Rarely free together

The two are rarely free at the same time

The build team has room in the first quarter. The department that has to work with it, only in the third. Look at the build team alone and you put the delivery in Q1 and leave it lying for half a year. By the time the department gets to it, the context has changed.

sponsor A sponsor B sponsor C the same department, the same quarter each plan holds on its own together they do not fit
Frame 3 · Adding up

Every plan holds, together they do not

Every sponsor plans their own change, and each of those plans is defensible. Only when you lay them side by side do you see that three of them ask for the same department in the same quarter. Nobody adds that up on their own, because on their own nobody has an interest in it.

TIME VALUE without the brake everything phased minimal disruption phases its way to a standstill
Frame 4 · The brake

Minimal disruption phases its way to a standstill

As soon as as little disruption as possible becomes the criterion, every change moves out until it no longer touches the running work. Each decision is sensible in itself. Together they bring the plan to a stop, and nobody notices, because nothing goes wrong anywhere.

closer together the work takes a knock further apart the value leaks away risk is the scale the benefit owner sets it per change, not in general
Frame 5 · The scale

Acceptable, not minimal

Planning them closer together makes it more likely the daily work takes a knock. Further apart makes it more likely the value walks away before it is harvested. Risk is the dial between those two. The one who sets it is the person answerable for the result, not the person planning.

When is it finished? When can the organisation take it on? and what does waiting cost
Frame 6 · The question

Not when is it finished, but when can it land

A delivery date says when something exists. It says nothing about when it gets used, and so nothing about when it starts paying off. Ask the second and the first follows on its own.

Capacity is asked for twice

In a portfolio conversation capacity almost always means building: do we have the people, do they have the right skills, does it fit the planning. That is half of it. The other half is whether the organisation can take it on, alongside the work that simply keeps running. That second question is rarely asked, because it is harder to express in hours. It does decide when something starts paying off.

The two are rarely free at the same time

The build team has room in the first quarter, the department that has to work with it only in the third. Look at the build team alone and you plan the delivery in Q1. After that it lies waiting. By the time the department gets to it, the context has changed, people have left and part of it has to be done again.

The reverse exists too. The business can in Q2 and would like to, but the only people who can build it are on something else until the summer. Then the answer is not a later date but a choice: stop something else, strengthen the team for a while, or shrink the scope to what can be done.

What three months of waiting costs

A worked example with round figures. A software change costs 300,000 euro, spread over five months at 60,000 euro a month. The expected return is 450,000 euro. It is delivered on time, on budget, and it works.

Except that the delivery falls in the busiest period of the business. The department that has to work with it has no room for the first three months. After that the learning begins, and that too takes time before anything comes out of it, say another three months. So the first real return falls half a year after the delivery.

Lay the other scenario beside it. The same change starts three months later. It is delivered at the moment the department does have room, the learning starts straight away, and the first return falls on exactly the same date as in the first scenario.

The difference is not in the return. It is in what stayed available three months longer. Three hundred thousand euro that had not been spent yet. At three percent a year that is about 2,250 euro in interest, and that is the smallest part of it. The real difference is that that money and those people could have worked on something else for three months, on something that could be used straight away.

One change, once. Do the same exercise across a whole portfolio and the sum is investment room you do not have today.

Every plan holds, together they do not

Ask every sponsor for their timeline and you get as many defensible plans as there are sponsors. Each of them optimises for their own change, and that is their job. The clash only becomes visible when somebody lays them side by side and sees that three changes ask for the same department in the same quarter.

That adding up does not happen on its own, because on their own nobody has an interest in it. It is exactly the work a portfolio practice exists for. A portfolio that only collects what the sponsors hand in is a reporting layer.

Minimal disruption is a brake

As soon as as little disruption as possible becomes the criterion, every change moves out until it no longer touches the running work. Each separate decision is sensible. Together they bring the plan to a stop. And that does not stand out, because nothing goes wrong anywhere, there is simply nothing happening.

The usable criterion is acceptable disruption, weighed against the value and against the window in which that value still counts. Putting a department under pressure for three weeks for something that delivers nothing next year is unwise. The same three weeks for something that pays off every quarter afterwards is a good trade.

What this means in practice

We ask every sponsor not only when their change is finished, but also which department is asked for when. We lay those timelines side by side and make the clashes visible, with the scenarios alongside. The choice then sits with whoever is answerable for the result. Read how we set up governance →

Who decides what is acceptable

Not the planner, and not the sponsor who wants to push the change through. The person answerable for the result decides how much disruption that result is worth. That is a board decision, because it weighs today’s service against tomorrow’s return, and that is not a planning question.

What the portfolio practice does do is make that choice possible: show the clash, lay the scenarios beside it, and record what was decided and on what grounds. So that afterwards it is traceable why something was moved, and so that the next choice is better than the last.

Why this matters

A change delivered on time and only used two quarters later is not on time. The value starts counting when the organisation works with it, not when it is finished. Plan capacity in both directions and you put the date it lands in the middle, and let the delivery date follow from that.

What is sitting ready with you and not being used yet?

In a conversation we lay the timelines of your changes side by side and look at where they ask for the same department in the same period.