IT‑IS‑Networking
Technology › Enterprise Architecture & Governance

Application Rationalization

Reducing a portfolio assembled independently over decades — platform consolidation, technology lifecycle planning and technical debt reduction.

Left to right is time. Each row is one of the 6 disciplines this one worked alongside, ordered so kindred disciplines sit next to each other rather than alphabetically — a landscape only means anything if neighboring rows belong together. Height is the work running in that domain in that year, weighted by what failure would have cost — life-safety ×3, a statutory obligation ×2.2, the estate itself ×1.5, an evaluation ×1. Every project declares which of those it was, so each ridge traces to an entry you can open and disagree with. Only the work that used this technology is counted, so what shows here is the company it kept rather than the record around it. Height and color are on the record-wide scale rather than this page’s own, so a modest estate draws a modest landscape and any two of these pages can be read against each other.

Driving application rationalization, platform consolidation and technology lifecycle planning across a portfolio of 300-plus applications assembled independently over decades by agencies that each bought for themselves.

Rationalization in a federated estate is not a de-duplication exercise. Two agencies running the same function on different platforms may both be right, because their obligations differ; the work is establishing which duplication is accidental and which is structural.

Also searched as

  • business architecture
  • business capability model
  • BIZBOK
  • capability-based planning
  • value stream