Dependency analysis, risk assessment and business value per system — that yields a prioritised roadmap instead of a wish list.
Most modernisation projects fail not on technology but on sequence. Work starts where the noise is loudest instead of where the leverage sits. An assessment costs weeks and saves quarters — because afterwards you know what you may touch, what can wait and what you had better never touch.
Every system is rated on the same three axes. Only their interplay shows what has priority.
Who calls whom, over which interface, with which data structure. Only when the edges are visible does it become clear which system you can touch without dragging three others down.
End-of-life dates, missing maintenance, single points of failure, knowledge held in individual heads. Risk gets quantified, not sensed.
What does this system contribute to the business, how many users depend on it, what does an hour of downtime cost. Technically old does not automatically mean commercially unimportant.
Systems, versions, interfaces, hosting locations and ownership. We work with what exists — documentation, configurations, conversations.
Place every system on the three axes. That produces a matrix showing where risk and business value meet.
Keep, encapsulate, migrate, replace or retire. One recommendation per system with rationale, effort and risk.
Sequenced by leverage and dependency, cut into steps that deliver value on their own. No twelve-month block without an interim result.
A map of your system landscape with interfaces and data flows — useful far beyond the project, for audits and contingency planning.
Every system placed by risk and business value. The discussion shifts from opinions to positions in the matrix.
Concrete steps in an order that respects dependencies — with an effort estimate per step and a clear first result.
A document you can move budget with internally: what happens if nothing is done, what each path costs, which benefit arrives when.
weeks to the decision paper — not months to a first interim report.
expensive rework because a dependency nobody knew about surfaces mid-project.
shared factual basis for IT, the business and management.
30-min intro call — free.
No standard pitch. I listen, ask the right questions and give an honest assessment — even if we are not the right partner.
