Every significant IT decision anchors to one of two portfolios. And it’s almost always the designed one, because it’s visible.
Rationalization is where it shows first, and I’ve seen it happen on both sides.
When a consolidation starts with the catalog — services, categories, overlap to eliminate — a tool slated for retirement turns out to be carrying half a workflow somewhere else entirely, invisible to the program, obvious to the people who lean on it.
And the mirror image: nothing gets retired at all, because somewhere in the business there might be a power user buried in a workflow nobody can see. So the estate only grows, and everyone pays for services that may serve no one.
Both are the same blindness. With only the designed portfolio visible, a dead service and a quietly load-bearing one look identical.
Investment follows the same line.
Budgets flow along the catalog’s structure, because that’s the structure budgets can flow along — you fund what has a box. Capabilities delivered across boxes, or by tools nobody classified, sit outside the funding logic entirely. The services people depend on hardest are often precisely the ones that fit the catalog least — which means the dependency and the investment can run in opposite directions without anyone deciding that.
Vendor scope is negotiated against the catalog’s definitions. Chargeback allocates cost by the catalog’s boundaries. Roadmaps sequence work by the catalog’s categories. None of these decisions is made carelessly. Each is made by capable people on the most complete picture available — and the picture is one dimension of a multi-dimensional reality.
This is the quiet cost of anchoring to the designed portfolio. Not dramatic failures — those get noticed and fixed. The cost is accumulation: priorities slightly off, funding slightly misaligned, scope slightly wrong, each decision defensible, the drift compounding. Nothing announces it. The designed portfolio looks complete from the inside, and every decision anchored to it inherits the confidence of the map rather than the shape of the territory.
The two portfolios — the one IT designed and the one that’s consumed — are different shapes, and the difference is structural, not a maintenance gap. Which means the pattern above isn’t a performance problem to manage. It’s an anchoring problem — and it persists exactly as long as the consumed portfolio stays invisible.
What would your last rationalization have concluded if it could have seen the consumed portfolio?
The consumed portfolio leaves evidence. And the ability to read it is arriving.
