Let’s start with a common problem: “application sprawl.” This is what happens when an organization ends up with too many redundant, low-value applications. The goal of a comprehensive application rationalization methodology is to get this under control by making smart decisions about which systems to retire, retain, or replace. But as a portfolio grows, it becomes incredibly difficult to compare the cost, value, and risk of every single application. This is where companies struggle, as duplicated tools and fragmented data pile up, making it easy to overlook obsolete systems.
Bubble charts cut through this complexity. They offer a simple, visual way to plot all these dimensions at once on a single scatter plot. For example, the x-axis can show an app’s cost, the y-axis its business value, and the size of the bubble its technical risk. This high-level overview instantly makes the conversation easier. Stakeholders can see which apps deliver high value at a low cost and which are just draining resources. It allows decision-makers to triage the portfolio, focus on urgent actions, and get everyone on the same page.
Hands-on training covering model setup, portfolio attributes, and dashboard configuration for Application Portfolio Management (APM) use cases.
Understanding Bubble Charts in the APM Context
At its core, a bubble chart is a simple tool for comparing three or more variables at a glance. In the world of Application Portfolio Management (APM), this becomes very practical, fitting into the key components and phases of APM as a powerful visualization tool.
For example, you could set the x-axis to show an application’s annual operating cost, the y-axis to show its business value score, and the bubble size to represent the number of active users. Right away, you can compare multiple applications and spot the high-value players.
When you design a chart, think carefully about the metrics. “Cost” could mean annual license fees, or it could be the total cost of ownership (TCO). “Value” might be a score based on business impact, user satisfaction, or how well it aligns with strategic goals. “Risk” could include technical age, vendor stability, or compliance issues.
Plotting these different factors is key. It shows that rationalization isn’t just about one thing—it helps everyone avoid making decisions based only on cost, for example. You can also use colors to add a fourth dimension, like sorting apps by business unit, technology stack, or lifecycle phase (e.g., Active, Retiring).
Key Use Cases for Bubble Charts in Application Rationalization
Identify redundant apps
When you see a tight cluster of bubbles in the “low value, high cost” corner, it’s a major red flag. This often means you have multiple applications providing overlapping functionality. The chart highlights these redundancies so you can consolidate them, a key step in cost optimization through application rationalization.
Support “Retire, Retain, Replace” Decisions
Plotting apps by cost and value helps leaders make the “Retire, Retain, or Replace” call quickly.
- Retire: These are the low-value, high-cost systems.
- Retain: These are high-value, low-cost. Don’t touch them!
- Replace: A system might be high-value but also high-risk (e.g., running on an unsupported platform). This makes it a prime candidate for replacement or modernization.
Align IT with Business Value
Applications sitting high on the “value” axis are clearly aligned with what the business is trying to achieve. Bubble charts help IT organizations justify shifting money and resources toward these high-impact systems and away from the low-impact ones.
Beyond these main uses, bubble charts are also great at spotting hidden problems, like dependencies. For instance, if you see that several high-risk applications (big red bubbles) all support a single business capability, you know you have a weak point that needs a contingency plan.
How to Build Effective APM Bubble Charts
A bubble chart is only as good as the data behind it. To build one that actually leads to good decisions, you need a solid process.
- Get your data in order: This is the foundation. You need to gather cost, usage, business value, and risk scores for each application. Make sure this data is current and, most importantly, measured the same way for every application. Supplementing this with feedback from stakeholders is also a great idea.
- Choose your dimensions: Decide what matters most. What will you plot on the x-axis, y-axis, and what will bubble size represent? Common pairings are Cost vs. Value or Risk vs. Value. A good starting point is to use color to show the app’s lifecycle stage (e.g., active, modernization, retirement).
- Set clear thresholds: Define what “high” and “low” actually mean. This creates the quadrants for your chart. Cost thresholds might be based on annual budgets, while value thresholds could come from your strategic scoring.
- Look for patterns: Now, look at the finished chart. Where are the clusters? Are there any obvious outliers (e.g., a single app costing a fortune)? Use these insights to propose actions, like consolidating two similar tools or renegotiating a license.
- Review and refine (and repeat): This isn’t a “one and done” exercise. Your business priorities will change, and your data will get better over time. Regularly review the chart with stakeholders and be willing to adjust it to keep it relevant.
In many popular APM tools, these charts can be linked directly to your model data, so they update automatically. This allows users to get more details by clicking on a bubble to see its dependencies, technology stack, and more.
Interpreting Bubble Chart Patterns for APM
Looking at the chart is one thing; knowing what to do with it is the real goal. Most organizations find it helpful to think in quadrants:
- Tolerate (Low Value, High Technical Fit): These apps work fine from a tech standpoint but don’t add much business value. Keep them running with minimal support, but if costs go up or usage drops, they’re first on the chopping block.
- Invest (High Value, High Technical Fit): These are your top performers. Keep funding them, protect their service levels, and look for ways to expand their use to sustain the benefits.
- Migrate (High Value, Low Technical Fit): These apps are important to the business, but their underlying technology is a problem (e.g., old, costly, high-risk). The goal here is to find a way to shift the business function to a more modern, cost-effective platform.
- Eliminate (Low Value, Low Technical Fit): These are the easiest decisions. These apps don’t help the business and they are technically poor. Make a plan to decommission or consolidate them, and move their budget to higher-value systems.
When you align each quadrant with a specific action, the bubble chart becomes a powerful decision-making tool.
Addressing Data Quality and Bias using APM Bubble Charts
This is a critical point. A chart based on bad data is worse than no chart at all. Stakeholders will lose trust if the data feels wrong. Here’s how to keep it clean:
- Define your terms: Be crystal clear on what “cost,” “value,” and “risk” mean. Document the data sources and how each score is calculated so everyone scores apps the same way.
- Get a second opinion (and a third): Don’t rely on a single person to score an application. This is a quick way to introduce bias. Collect input from multiple stakeholders (e.g., business, finance, IT) and hold workshops to calibrate the scores.
- Use a consistent model: Document the criteria and weights you’re using (e.g., strategic fit = 40%, user adoption = 30%…). Keep the model simple enough to be applied consistently.
- Audit and refresh your data: Set a regular schedule (like quarterly) to update the data. Assign clear owners for different data points to ensure accountability.
- Show uncertainty: If some data is just an estimate, be open about it. It’s better to show a range or add a note than to present a guess as a hard fact.
- Write down your assumptions: If you had to make adjustments or use a proxy for a certain data point, log it. This transparency is key for building trust in the chart.
Customizing Bubble Charts for Stakeholders
One size does not fit all. An executive and an engineer are looking for completely different information from the same chart. The most effective visual dashboards for APM are tailored to their audience.
Executives (Strategy & Spend)
- What they care about: Cost vs. Value.
- Bubble Size: Strategic Impact.
- Color: Lifecycle or cost bands.
- Key Views: Top 10 investments, budget scenarios.
Architects / Engineering
- What they care about: Risk vs. Complexity.
- Bubble Size: Number of dependencies or technical debt score.
- Color: Technology lifecycle (e.g., emerging, mainstream, sunset).
- Key Views: Candidates for modernization.
Product / Process Owners
- What they care about: User Adoption vs. User Satisfaction.
- Bubble Size: User Count.
- Color: Business Capability it supports.
- Key Views: Opportunities for quick-win improvements.
Governance / PMO
- What they care about: Roadmap Status vs. Delivery Risk.
- Bubble Size: Total Investment.
- Color: Program or funding source.
- Key Views: Tracking decisions and approvals.
The key is to provide filters and saved views so each role can get their questions answered quickly and consistently.
Practical Examples of Rationalization Using Bubble Charts
Let’s make this concrete. Here are a few real-world examples of how this works:
Scenario: Rationalizing collaboration tools
- The Problem: The company has three different chat and video conferencing tools, all with different costs.
- The Solution: Plotting “Annual Cost” vs. “User Adoption” on a bubble chart.
- The Insight: The chart immediately reveals that two high-cost tools have very low adoption, while a free or low-cost solution is used by almost everyone. This makes the decision to consolidate onto the one tool simple and easy to justify.
Scenario: Visualizing applications by business unit
- The Problem: The central IT team needs to understand which departments are relying on high-risk technology.
- The Solution: Create a “Risk vs. Value” bubble chart and use a filter for each business unit.
- The Insight: The chart shows that the Finance department relies on three high-risk (old, unsupported) applications for critical functions. This allows the Enterprise Architects to target their modernization efforts directly at that business area and engage the right stakeholders.
Scenario: Comparing legacy vs. modern platforms
- The Problem: A legacy billing system is expensive to maintain, but leadership is hesitant to fund a replacement.
- The Solution: Plot the legacy system on a “Cost vs. Risk” chart alongside a proposed cloud-native alternative.
- The Insight: The legacy system appears as a large, red bubble (high cost, high risk), while the new solution sits in the low-cost, low-risk quadrant. This visual makes the case for migration clear and compelling.
Scenario: Assessing vendor concentration
- The Problem: Is the company too dependent on a single software vendor?
- The Solution: Plot all major applications on a chart and use “Color” to represent the vendor.
- The Insight: The chart shows a large cluster of high-value applications all tied to one vendor. This isn’t necessarily bad, but it highlights a business risk and can start a strategic conversation about diversifying suppliers or negotiating a stronger contract.
In every case, the visual clarity of the bubble chart gets business and technical stakeholders talking, which is the first step to making a smart decision.
Our Experts can help jumpstart your APM with well-defined decision-grade metrics, aligned governance and role-based dashboards.
To wrap up, application rationalization is a vital part of running a modern, cost-effective IT operation. It’s not just about cutting costs; it’s about reducing complexity and making sure your tech investments are actually pushing the business forward.
Bubble charts are a powerful tool in this process. They provide a simple, data-driven way to compare cost, value, and risk across an entire portfolio, helping teams spot redundancy and prioritize high-value work. By using clear data, setting up smart quadrants, and tailoring the views for different stakeholders, any organization can turn a simple chart into an actionable plan.
This is where tools like Sparx Enterprise Architect and Prolaborate become invaluable. They connect directly to your live architecture models, allowing you to generate real-time bubble charts and other interactive dashboards that are always up-to-date, turning your application data into an actionable, visual plan.
