Work Blog Contact

Find where the work leaks. Fix what is worth fixing.

This is how I approach process and AI work: first understand how the business really runs, then find where time and money go missing, then build the fix - AI where it earns its keep, plain automation where that is cheaper. The aim is a figure before and after, so it is clear whether a change paid off.

Four steps. Each one leaves something concrete.

A map, a list of problems, a build, a check of what it did. Every step shows what it produced - no black box.

Step 01 Map

I map how the work really runs

I sit down with the people who do the job - interviews and short workshops across teams - and turn what they tell me into clear process maps. Not the tidy org-chart version. The real one, with the workarounds, the copy-paste, and the steps nobody wrote down.

Result A clear map of how each team actually works. Most people are surprised what turns up.
Step 02 Find

I find where it leaks, and rank it

Every problem gets written down with where it comes from, how often it hits and what it costs. Then it is sorted worst-first, so it is clear at a glance where the money goes. Nothing on the list is a guess - each item traces back to something someone said or something I measured.

  • Each problem gets tagged: AI can fix this, a plain integration fixes this, or this is a people problem no tool will touch.
  • And the part most people skip - which problems are not worth fixing, so nobody spends money on them.
Result A worst-first list of what costs the most - and a straight answer on what to leave alone.
Step 03 Solve

I build the fix - and keep it portable

I pick tools that are not tied to one vendor. The AI model behind it can be swapped in an afternoon, so nobody is stuck with one provider's prices or roadmap. Where a simple rule does the job, I use a simple rule - it is cheaper and it does not break. AI goes in only where the job actually needs judgement.

  • EU AI Act and GDPR handled from the start, so there is no nasty surprise before launch.
  • I say up front what a person still checks and what runs on its own - and what I leave for a human on purpose.
Result A working system its owners can move to another AI model whenever they want, built to stay on the right side of the law.
Step 04 Check

I check whether it paid off

The goal is a before-and-after figure in euros or minutes: how things ran before the change and how they run after. Where nothing is measured yet, I say so instead of guessing. No "trust me, it is better".

Result A before-and-after where it can be measured, and an honest note where it cannot yet.
What the ranked list looks like - illustrative example
Customer Service
20 problems
Logistics
16 problems
ERP & Data
14 problems
Quality
13 problems
Sales
11 problems
Production
10 problems
Compliance
9 problems
Procurement
8 problems
IT & Security
7 problems
Finance
6 problems
Engineering
5 problems
HR
3 problems

Example only, to show the shape of the ranked list - not data from any real project. In practice each problem is tagged as one AI can fix, one a plain integration fixes, or one that is really about people.

How I work, in four lines.

01
I say when AI is the wrong tool

Sometimes a plain fix beats a model, and sometimes the honest answer is "do not automate this yet". I say so straight, before anyone spends money on it.

02
No lock-in to one vendor

The AI model behind a system can be swapped in an afternoon. Prices change, providers change - the system keeps running either way.

03
Legal is handled from the start

EU AI Act and GDPR are built in from the first day, not checked at the end. What a person still reviews is decided before anything goes live.

04
Measure the payoff, don't assume it

The aim is a figure in euros or minutes, before and after. Where there is no figure yet, I say so plainly instead of guessing.

Questions about the method?

Happy to compare notes on process mapping, AI tooling or the EU AI Act. Write to me through the form on the home page or on LinkedIn.