Making Processes Visible

Identify friction before new tools are introduced

Many digital problems are rooted in the process, not the tool. Information is searched for, copied, forwarded, and maintained multiple times. I reveal where time and quality are lost and where AI or automation can be effectively applied.

View process More on Impact Day

What it's about

The spectrum ranges from simple tasks to complex change management. We stay close to the concrete working reality, without heavy organizational consulting. Together, we look at a task that regularly generates effort today and answer further questions: What should be achieved, what is happening, what does it cost, and what could be simpler?

As an industrial IT specialist, data and process analyst, and with extensive experience in various industrial processes, new challenges fascinate and motivate me. Challenge me. For topics outside my direct expertise, I will moderate and guide you together with AI as a digital thinking partner.

Typical Starting Situations

Too many manual steps.
Information is scattered across emails, files, chats, and storage locations.
Status reports are regularly rebuilt.
Decisions take longer than necessary.
Knowledge disappears after meetings or handovers.

How it works

Select a task. A real routine that occurs frequently and noticeably generates effort.
Visualize the current process. Steps, participants, media breaks, data sources, and sources of error.
Estimate effort. Frequency, time, rework, and waiting times.
Derive levers and define a test. A concrete proposal, small enough for a test and relevant enough for impact.

Result

An understandable process sketch
Visible friction points
A rough effort estimate
Prioritized improvement levers
A concrete next test step

Suitable Formats

Process Review: a focused look at a process. Duration: 60 to 120 minutes plus a brief evaluation.
Impact Day: analyze a routine, rebuild it, and calculate the difference in time, effort, and benefit. Duration: one working day or two compact appointments.
Workflow Prototype: a first usable process, for example with Microsoft 365, Power Automate, or AI support. Duration: 1 to 3 weeks until the first test.

Method

Real task, visible proof, clear anchoring. I start with a concrete task, check the difference in everyday life, and secure the result so that it can be used further.