IT modernisation projects often fail not because of the technology, but because of the approach taken. With Asset-based Modernisation, we present a model that starts not with the target architecture, but with the existing systems. It provides clarity on potential, risks and next steps – in a systematic, realistic way that is adaptable to organisations of all sizes. The four phases of our model help companies to develop their IT sustainably and without operational risk – from the initial analysis through to the implementation of change.
Many companies know that their IT landscapes need to be modernised – but few know how. Caught between operational pressure, legacy technology and growing complexity, modernisation quickly becomes a balancing act: initiatives are launched without a strategic foundation. Technologies are introduced without getting the organisation on board. And systems are replaced before they have even been properly understood.
The result: projects get bogged down, resistance builds up, and the long-term impact fails to materialise. Not because the tools are poor – but because the process is missing.
This is precisely where our approach comes in. With Asset-based Modernisation, we have developed a process model that makes modernisation systematic and transparent – from the initial analysis right through to actual implementation. We never view modernisation in isolation – for us, it is always a means to an end: setting up IT in such a way that it genuinely drives the business, teams and products forward. It structures the journey into four clearly defined phases – using tried-and-tested methods and with enough flexibility to address any starting point.
Many approaches to IT modernisation focus on target states. Where do we want to go? What needs to change? Which technology fits the strategy? These questions are important, but they often fall short. After all, modernisation does not begin with the target state, but with the existing infrastructure.
Asset-based modernisation first turns its attention to what others often just want to rush past: the existing infrastructure. The term refers to an approach that does not view existing IT systems, architectures and processes as legacy burdens – but rather as a starting point for targeted further development. Operations remain guaranteed at all times: instead of a radical ‘big bang’, we focus on continuous improvement, ideally without any disruption to business operations.
The core of the model:
We modernise not ‘in spite of’, but on the basis of the system. And we do not do this alone: the analysis and assessment are always carried out in collaboration with our client teams, underpinned by a shared understanding of the system rather than external assumptions.
This means:
This approach achieves more than just efficiency: it reduces risks, safeguards knowledge – and significantly increases the feasibility of modernisation projects.
Every sustainable modernisation begins with understanding. In the first phase of asset-based modernisation, we analyse the actual state of the existing IT landscape – not only from a technical perspective, but also in terms of organisation and processes. The assessment is carried out in close consultation with the relevant stakeholders: through interviews with business owners, developers and specialist departments, as well as with decision-makers from management and strategy. In this way, alongside architectural and code analyses, overarching objectives and new challenges are incorporated into the assessment at an early stage.
We utilise established methods from our portfolio, foremost among which is the System Health Check – a structured analysis that systematically assesses architecture, code quality, performance and security aspects. In addition , where necessary, we utilise the System Review, which goes beyond the purely technical perspective to also examine processes, interfaces, team structures and governance issues. Both the System Health Check and the System Review offer a 360° perspective on the existing IT infrastructure, although they differ in their focus: the System Health Check serves to provide a neutral assessment of the status quo, whilst the System Review goes further by identifying a potential modernisation path.
In many cases, it becomes apparent that the greatest challenges lie not in the obvious legacy code, but in hidden dependencies, a lack of documentation or structures that have evolved over time and which nobody can fully grasp anymore. That is why we delve deeper where it makes sense – using qualitative interviews, technical analyses and, where appropriate, automated code metrics or AI-assisted tools.
The aim of this phase is not to pass judgement, but to gain a clear picture. What works reliably? Where has technical debt accumulated? Which modules are particularly critical or, where relevant, support the new challenges? And which systems rely on just a few key individuals? All of this contributes to a sound understanding of the current state – and forms the basis for the next steps.
Based on the findings from the analysis, the next step follows: strategic direction. In Phase 2, we develop a realistic target vision – not as an ideal, but as an actionable future scenario tailored to the analysed system, the organisation and the business objectives.
The key question is: what does an architecture look like that is both robust and adaptable? How can the path to achieving this be described in a structured way? This is where methods from Domain-Driven Design (DDD) come into play in particular. They help us to rethink the business domains and system boundaries and to clearly delineate them from one another. This results in a model of the future system landscape that is comprehensible not only from a technical perspective but also from a business perspective.
At the same time, it is essential to embed the necessary changes within the organisation. Here, we draw on principles from Lean Change Management: an iterative approach, the close involvement of stakeholders, and a consistent focus on benefits and feasibility. Collaboration on an equal footing is crucial here, as this is the only way to foster genuine acceptance of change and create a roadmap that is not only understood but can also be implemented within the organisation. The insights gathered and discussions held result in a roadmap that not only identifies measures but also prioritises them and sets them within a realistic timeframe.
The outcome of this phase is a viable plan: a combination of target architecture, migration strategy and manageable stages – usually in the form of recommendations for action, known as ‘epics’ or ‘transformation blocks’, which serve as guidelines for implementation.
Whilst strategic planning outlines the target vision, tactical design focuses on mapping out the specific path to achieving it. In this phase, it is determined how the technical implementation can be carried out – in what order, using which technologies, and in which sub-steps.
A key component is the selection of a suitable migration strategy. Depending on the initial situation, this may involve incremental refactoring, the targeted replacement of individual modules or – in rare cases – a complete rebuild. It is crucial that the chosen solution is suited to the organisation, the technical reality and the scope for change available.
Architecturally, too, things are now becoming more concrete. Microservices, modular architectures or domain-specific platforms are often the target structures – but not as an end in themselves, rather because they ensure long-term maintainability, scalability and development speed. In this phase, we work with the client to decide which technologies to use, how data flows should be designed and which infrastructure is suitable.
Tactics form the link between vision and reality: they translate objectives into technical steps, make the effort and complexity tangible – and create a robust foundation for implementation.
Even the best strategy remains ineffective if its implementation stalls. The final phase of asset-based modernisation is therefore about not just initiating change, but integrating it into the system in a stable and manageable way. No ‘big bang’ migrations, but structured transitions tailored to the environment and the organisation’s resilience.
Two aspects are central to this: firstly, the technical migration – that is, the transfer of data, processes and applications into the new environment; secondly, decommissioning – the phasing out of old components without jeopardising day-to-day operations. In many cases, both systems run in parallel for a period of time. This reduces risks, accelerates the learning curve and provides transparency regarding progress.
What is particularly important to us here is that the transition is not merely a deployment. It is a major organisational and technical undertaking – one that is most successful when all stakeholders are fully engaged. That is why we provide support not only through technology, but also through communication, monitoring and methodological clarity.
The end result is not a perfect future – but a system that is moving step by step towards the future. And that is often more sustainable than any radical fresh start.
Figure: The four phases of asset-based modernisation.
The concept of asset-based modernisation is not merely a theoretical framework – it has proven to be practical and effective across a wide range of projects and sectors. The key difference is that, rather than rushing straight into implementation or prescribing specific technologies, the model first provides direction. It answers the question: Where do we stand – and what is actually feasible in our situation?
This provides reassurance not only to the project teams, but above all to the decision-makers. The analysis phases provide clarity on risks and potential, whilst strategic planning highlights what is realistically achievable – and how quickly. At the tactical level, this translates into concrete technical steps that are not only technically feasible but also manageable from an organisational perspective. And thanks to the structured transition, business operations remain stable – whilst the technology continues to evolve.
What makes this model special is its adaptability: it works just as well in corporate structures as it does in SMEs, and in highly regulated sectors just as effectively as in agile product organisations. This is because it does not rely on specific technologies, but on a sound understanding of a company’s own assets – and on a collaborative approach that brings together technology, organisation and business.
IT modernisation is neither a sprint nor a matter of individual technologies. It is a process that only works if it is structured, interoperable and planned realistically. This is precisely what asset-based modernisation stands for: a methodological framework that does not start with the target architecture, but with the existing systems – and from there develops a viable, achievable path.
Instead of replacing systems across the board, a differentiated assessment is carried out. Instead of abstract roadmaps, concrete milestones are established. And instead of blind, reactive action, the model creates clarity, structure and trust – for everyone who views modernisation not as a project, but as part of strategic development.
Do you have any questions or need assistance?
You can find out more about the possibilities for IT modernisation for your business on our website. Feel free to contact us or arrange an appointment.