Field

Processes & systems.

Which process should stay in place at all?

I plan how processes and software work together before anything gets bought.

Situations

Sound familiar?

Coordination“The same meeting every week. And every week the same questions.”
Tool“A new tool is supposed to fix it. It costs us every month.”
AI“We’ve got to start using AI now, or we’ll fall behind.”
Legacy system“The new system is paid for. The old one is still running anyway.”

What is different afterwards

  • Every process that stays has a reason.
  • What gets bought is what a decided process needs.

Projects

Decisions

Decisions made here include, for example:

  • Which process gets cut before someone automates it?
  • Buy, build it ourselves, or leave it?
  • A new CRM, or use the existing one properly?
  • Which data may an outside system see?
  • Which licence gets cancelled?
  • Which task stays with a person, because judgement is needed there?
  • One tool for everything, or the best one for each task?
  • Who decides whether a tool has proved itself?
  • Who maintains the system when the provider is gone?
  • When does the old system get switched off?

Is one of these on your desk?

Decided

“What the consultants recommend is simply too heavy.”

Core processes first, then software. Whatever nobody uses is dropped.

Found: Software was bought because everything was to be automated. Nobody had checked what was actually used.

A large share of software costs and maintenance went away. Anything new comes in only if it has a role.

First the use case, then the tool. The process is dropped.

One process and one tool fewer, and no running costs for them.

Introduce AI

Position

A short text in which I take a stand on this field:

Conversation

Tell me what is coming up.

Twenty minutes, free of charge, nothing to prepare. You describe your situation, I tell you whether and where I would start. You know what a format costs before we begin.

How the call works