Application rationalisation and target state
Connect business capabilities to an application landscape that can evolve in manageable steps.

The situation.
Overlapping applications make change expensive and ownership unclear. The useful starting point is a shared view of which capabilities each application supports, who depends on it and what would be affected by replacement or retirement.
A practical approach.
- 01
Map the landscape
Connect business capabilities to applications, data ownership, interfaces and operating costs.
- 02
Compare the options
Examine retain, improve, consolidate and retire options against business priorities and dependencies.
- 03
Sequence the change
Describe transition states with migration owners, acceptance evidence and decision checkpoints.
What to validate
- Validate application usage with business and support teams.
- Include data retention and dependent integrations in retirement decisions.
Typical outputs
- Capability-to-application map
- Rationalisation options and rationale
- Transition roadmap
Example measures
- Applications with confirmed ownership
- Duplicated capability addressed
- Dependencies resolved before migration
Agree a baseline and acceptance criteria for the specific project.
Illustrative scenario and conceptual imagery. Scope, deliverables and acceptance evidence are agreed for each engagement; example measures are not achieved results.
