Approach

1 · Taking stock

Analysis of processes, data and systems together with the people who work with them every day. It is the users who know best which file actually carries the operation, and I surface that knowledge early.

2 · Target picture and roadmap

Prioritisation by effort and benefit. Every measure with its effort, expected benefit and sequence, brought together into a decision paper the management can work from directly.

3 · Architecture and standards

Design of the supporting structure: layers, interfaces, separation of data and evaluation, configurable processes. Plus coding guidelines and a test concept. This step is what makes step five possible in the first place.

4 · Implementation

Steering the service providers or implementing it myself, whichever is faster and more economical. Functional specification, plausibility checks, testing, acceptance.

5 · Embedding

Training, documentation and standards, so that your team runs and adapts the solution itself. That is how the investment still pays off five years later.

Throughout: communication

Who is involved and when, how responsibilities shift, who carries the change. This is the part that decides the outcome of every initiative.

Starting with a self-contained assignment

If you would first like an assessment: an inventory with a written result over one to three days is a common way to begin. You then decide on a sound basis whether and how to continue.