Mastertutorial · Part 1
How do I deal with complex IT systems?
With Christian Liebich12 minSystems & architecture
In short
You get complex IT systems under control by first working out the use cases that bring revenue, then separating the system into clearly bounded subsystems, and renewing it in small, effective steps. Patchwork burns money, and rebuilding everything at once often ends in a nightmare. The change only succeeds if everyone involved supports the vision and the plan.
The video is spoken in German and has integrated English subtitles. The podcast episode and the blog article are in German. This page summarises the episode in English.
The video is loaded from YouTube only after you click. Data is then transferred to YouTube.
What you take away
- Work out the use cases clearly: what brings revenue, and where is time wasted?
- Separate instead of patching: isolate subsystems to regain structure.
- Transform together: the vision and the change must be supported by everyone.
- Take small, effective steps instead of rebuilding everything at once.
Topics of this episode
- Why systems outgrow their owners
- Clarifying the goal and purpose of the system
- Modularisation and clear responsibilities
- Visualisation, documentation and transparency
- Stakeholder management and prioritisation
- Automation with human control
Who it is for
For executives, heads of IT and product owners whose system landscape has grown so much that every change has side effects.
This episode as
Related service
Business Analysis & Modernisation
I speak the language of the business and the language of developers. That turns requirements into solutions that work in daily use.
Frequently asked questions
Why do IT systems become unmanageable over time?
Because many components, interfaces, processes and teams interact, changes in one place affect others unpredictably, and more and more stakeholders have a say. Rapid technological change adds to it.
Should a grown system be rebuilt from scratch?
Usually not in one go. The tutorial recommends isolating subsystems and renewing them step by step, starting with the use cases that bring the most benefit.
Where do you start?
With clarity about the goal: why does the system exist, who benefits from it, and which measurable goals will the renewal be judged by?
