Simplify your application landscape, cut costs, and make smarter IT decisions.
The Application Portfolio Rationalization Playbook is a practical, end-to-end guide to evaluating, streamlining, and modernizing your application landscape. It walks through when and how to launch a rationalization effort, build a reliable inventory, assess business value, technical health, cost, and risk, and make clear decisions across retire, replace, consolidate, or modernize options. With guidance on governance, prioritization, execution, and change management, the playbook helps organizations reduce complexity, lower costs, improve resilience, and establish ongoing discipline for managing their application portfolio.
Table of Contents
Chapter 1. What Application Portfolio Rationalization Is
1.1 Definition and Objectives of Application Portfolio Rationalization
1.2 Common Drivers: Cost Pressure, Complexity, Risk, and Modernization Needs
1.3 What Sits in Scope: Applications, Platforms, Interfaces, Databases, and End-User Tools
1.4 What Good Looks Like: Outcomes, Metrics, and Typical Value Created
Chapter 2. When to Launch an Application Rationalization Effort
2.1 Trigger Events: M&A, ERP Replacement, Cloud Migration, Cost Reduction, and Cyber Risk
2.2 Symptoms of an Unhealthy Application Portfolio
2.3 When a Full Portfolio Review Is Warranted vs. a Targeted Review
2.4 Typical Pitfalls in Under-Scoped and Over-Scoped Efforts
Chapter 3. Framing the Ambition and Defining the Scope
3.1 Setting the Ambition Level: Cost Takeout, Simplification, Modernization, or Control
3.2 Defining Business, Geography, Function, and Technology Scope
3.3 Deciding Which Application Types to Include: SaaS, Custom, Legacy, Shadow IT, and End-User Computing
3.4 Establishing the Time Horizon and Success Criteria
Chapter 4. Governance, Sponsorship, and Team Structure
4.1 Executive Sponsorship and Decision Rights
4.2 Roles for Business Leaders, Enterprise Architecture, Infrastructure, Security, Finance, and Procurement
4.3 Working Team Structure, PMO, and Cadence of Decision Meetings
4.4 Escalation Paths for Disputed Ownership, Funding, and Risk Decisions
Chapter 5. Building the Application Inventory
5.1 What Fields the Inventory Should Contain
5.2 Sources of Data: CMDB, Finance Records, Architecture Repositories, Contracts, and Interviews
5.3 How to Identify Duplicate, Redundant, and Unknown Applications
5.4 Practical Template for a Minimum Viable Application Inventory
Chapter 6. Collecting the Right Facts
6.1 Business Usage Data: Users, Processes Supported, Frequency, and Criticality
6.2 Technology Data: Age, Architecture, Integrations, Hosting, Performance, and Support Model
6.3 Financial Data: Licenses, Infrastructure, Vendors, Internal Labor, and Project Spend
6.4 Risk Data: Security, Compliance, Resilience, Audit Findings, and Data Retention Needs
6.5 How to Gather Data Quickly When Records Are Incomplete
Chapter 7. Segmenting and Classifying the Portfolio
7.1 Classification by Business Domain and Capability
7.2 Classification by Application Type: System of Record, System of Differentiation, and Utility
7.3 Lifecycle Status: Strategic, Tolerate, Invest, Contain, Retire
7.4 Grouping Applications Into Decision Clusters Rather Than Reviewing One by One
Chapter 8. Assessing Business Value and Criticality
8.1 Measuring Business Importance and Operational Dependency
8.2 Assessing User Adoption, Pain Points, and Business Fit
8.3 Evaluating Uniqueness vs. Replaceability
8.4 Practical Scoring Model for Business Value and Criticality
Chapter 9. Assessing Technical Health and Risk
9.1 Technical Debt, Maintainability, Supportability, and Vendor Viability
9.2 Security, Resiliency, Privacy, and Regulatory Risk
9.3 Integration Complexity and Upstream-Downstream Dependency Risk
9.4 Practical Scoring Model for Technical Health and Risk
Chapter 10. Understanding Cost and Economic Value
10.1 Total Cost of Ownership by Application
10.2 Hidden Costs: Interfaces, Manual Workarounds, Reporting Layers, and Local Support
10.3 Estimating Savings From Retirement, Consolidation, Renegotiation, and Modernization
10.4 Building a Simple Economics Model to Support Decisions
Chapter 11. Rationalization Decision Options
11.1 Retire, Replace, Consolidate, Modernize, Replatform, and Retain
11.2 Decision Criteria for Each Option
11.3 How to Handle Applications With Split Decisions (e.g., Retain Now, Replace Later)
11.4 Typical Decision Patterns by Application Archetype
11.5 Decision Tree Template for Rapid Triage
Chapter 12. Designing the Target-State Application Landscape
12.1 Target-State Design Principles
12.2 Capability-Based Mapping of the Future Landscape
12.3 Standardization Choices: Enterprise Platforms, Suites, and Best-of-Breed Tools
12.4 Guardrails for Cloud, Data, Integration, Identity, and Security Architecture
Chapter 13. Prioritizing the Portfolio and Building the Roadmap
13.1 Quick Wins vs. Longer-Horizon Moves
13.2 Prioritization Criteria: Value, Risk, Feasibility, Timing, and Dependency Load
13.3 Sequencing by Business Calendar, Contract Timing, and Technology Readiness
13.4 Building a Wave-Based Roadmap
13.5 Example Roadmap Formats and Steering Committee Materials
Chapter 14. Executing Rationalization Decisions
14.1 How to Retire Applications Safely
14.2 How to Consolidate Overlapping Applications and Migrate Users
14.3 How to Replace Legacy Applications With New Platforms
14.4 Data Migration, Archival, and Record-Retention Requirements
14.5 Controls to Prevent Portfolio Sprawl From Reappearing
Chapter 15. Change Management, Communications, and Adoption
15.1 Stakeholder Mapping and Resistance Points
15.2 Communication Plan for Business Users, IT Teams, and Leadership
15.3 Training, Cutover Support, and Post-Go-Live Stabilization
15.4 Handling Political Issues, Local Exceptions, and Application “Owners” Who Resist Retirement
Chapter 16. Vendor, Contract, and Licensing Actions
16.1 Using Contract Timing to Accelerate Rationalization
16.2 License Optimization and Elimination of Shelfware
16.3 Vendor Negotiation Strategies During Consolidation and Exit
16.4 Managing Third-Party Risk During Transition
Chapter 17. Tracking Benefits and Sustaining Portfolio Discipline
17.1 Benefit Tracking: Cost Reduction, Risk Reduction, Simplification, and Productivity Gains
17.2 KPIs and Dashboard Design
17.3 Operating Model for Ongoing Application Portfolio Management
17.4 Intake Controls and Architecture Governance to Prevent Future Proliferation
Chapter 18. Tools, Checklists, and Templates
18.1 Application Inventory Template
18.2 Business Value and Technical Health Scoring Templates
18.3 Decision Log, Roadmap, and Steering Committee Templates
18.4 Retirement Checklist, Migration Checklist, and Communication Checklist
Chapter 19. External Advisors and Consultants to Consider
19.1 When to Use External Support and Where It Adds the Most Value
19.2 Large Consulting Firms: Strategy, Enterprise Architecture, Transformation Delivery, and PMO Support
19.3 Specialized Boutiques: Licensing Experts, Cloud Migration Firms, and System Integrators
19.4 Independent Management Consultants Engaged Through Umbrex
19.5 How to Choose the Right External Support Model for Your Situation
