The data situation first
What sits in completed cases is verifiable. What is said in a conversation is the memory of the last conspicuous case.
Consulting brings clarity on priorities, target vision and actionable next steps.
A professional consulting approach translates strategic goals into concrete fields of action. What matters isn't the number of ideas, but the ability to derive robust priorities from analysis and realistic measures from those.
What sits in completed cases is verifiable. What is said in a conversation is the memory of the last conspicuous case.
„The loss sits in these lanes and is of this order of magnitude“ can be checked. „The processes could be improved“ cannot.
A method that only runs while the consultant is there is not a result but a dependency.
It starts with a question, not a solution. Usually the stated question is not the real one.
Stocktaking, analysis, recommendation, slide deck — then the business takes over, and the recommendation meets a working day in which nobody has capacity for it.
The result is rarely resistance, more often agreement without implementation. What was paid for then was insight, not effect.
Not from consulting but from operations: from the question of how dispatching, awarding and invoicing actually connect when the day is full. What does not fit into the working day does not get done.
That also shapes the honesty about limits: A method that does not beat existing practice is not progress. That statement occasionally costs an engagement.
With a question and a look at what is there anyway: a testable hypothesis and an estimate of how much depends on it. Only then is the question of scope and effort worth asking.
Weeks, not months — with a visible result at the end of each stage. Larger projects are split so that after each stage it can be decided whether to continue.
On request and depending on scope. What is promised is that the effort is fixed before the start and does not grow along the way.
Yes, and there the effect is often greater because the path from insight to implementation is shorter. The requirement is not size but usable records of completed cases.
Yes, otherwise it is not implementation. Defined beforehand: what I build, what the business builds, and what it is measured against. The handover is part of it in any case.
A brief description of the situation is enough - an assessment follows quickly.