Skip to content

Editorial

Crown Jewels Should Change the Conversation

Kip Fanta ·
Crown Jewels Should Change the Conversation

Not every application deserves the same level of attention.

Some applications are important. Some are expensive. Some are technically complex. And some are so critical to the business that a serious failure would immediately affect customers, revenue, operations, safety, compliance, or the ability of employees to work.

Those applications are different, and they should be managed differently.

Criticality Should Influence Priority

Application portfolio management often focuses on business value and technical health. Those are important dimensions, but they do not always tell leadership how much disruption an application failure would create.

A system can have average business fit and still be operationally essential. It may not be loved by users or viewed as strategic, but if it supports payroll, order processing, manufacturing, customer transactions, or another core business process, its failure could have immediate consequences.

That is why criticality needs to be visible alongside other application attributes. It helps leadership distinguish between applications that matter and applications that simply exist.

Crown Jewels Need More Scrutiny

The most critical applications should naturally receive deeper attention.

That means understanding their technical health, lifecycle exposure, vendor support, recovery capabilities, security posture, dependencies, and ownership with greater precision. It also means making sure their future direction is clear rather than assuming they will simply remain in place indefinitely.

When an application is central to business continuity, small weaknesses can carry larger consequences. An aging platform, weak disaster recovery capability, unsupported component, or unresolved vendor issue becomes more important because of what depends on it.

The criticality changes the risk.

Risk Tolerance Should Not Be Uniform

Organizations often apply the same scoring frameworks across the entire portfolio. That can be useful for consistency, but it should not imply that every application can tolerate the same level of technical or operational risk.

A low-impact internal tool may reasonably operate with some aging technology while the organization focuses investment elsewhere. The same tolerance may be unacceptable for an application that supports a critical business service.

This is where portfolio management becomes more nuanced. The question is not simply whether an application has technical debt. The question is whether the organization can afford the consequences associated with that debt.

Criticality helps answer that.

Investment Should Follow Importance

Crown jewels should also influence where modernization and resilience investment goes.

If leadership has limited funding, critical applications with significant risk should rise in priority. That does not mean every business-critical system needs immediate replacement or expensive modernization. It does mean those decisions should be made with full awareness of the exposure.

The same logic applies to disaster recovery, vendor management, testing, architecture, and succession planning for key technical expertise. The more critical the application, the less room there is for ambiguity about how it is supported and where it is headed.

Investment should reflect consequence, not just visibility.

Criticality Should Shape the Roadmap

Application criticality should also affect timing.

An application that supports a core business process and is approaching end of support may require action years before the actual deadline. Migration planning, funding, testing, business change, vendor selection, and dependency work can all take significant time.

If the organization waits until the technical problem becomes urgent, it may have fewer options and much higher execution risk.

The roadmap should therefore reflect not only what needs to change, but how important it is to the business and how much preparation the change requires.

That is a much stronger basis for sequencing investment.

Know What Must Not Fail

One of the simplest questions leadership can ask is: which applications can we least afford to lose?

The answer should be clear.

If it is not, the organization may be treating business-critical applications exactly like everything else in the portfolio. That makes it harder to focus risk management, modernization, funding, and leadership attention where they matter most.

Application portfolio management should help create that distinction.

Because not every application is a crown jewel.

But the ones that are should change the conversation.

Share this post

LinkedIn X

Ready to see your portfolio clearly?

GetInSync gives IT leaders a structured view of what they run, what it costs, and what to do next.