Strategic initiatives rarely fail at the concept stage. They fail at implementation.
The decisive months are those between a decided strategy and an organization that carries it. That is exactly where my work begins.
Successful transformations rest on three pillars: a clear strategy, a sound implementation, and an organization that carries the change. If one pillar is missing, the project fails. My engagements address the pillar where you have the greatest leverage. Sometimes that is strategy, more often implementation, and almost always how people who carry the change are involved.
I typically work in three fields:
Strategy work does not only fail at implementation. It often fails earlier: from too many goals pursued in parallel, from numbers that are not reliable, or from investment decisions made on insufficient grounds. Before implementation begins, there must be clarity.
Engagements in this field often begin with one of these questions:
Our strategy is formulated, but it is not coming into implementation. How do we close the gap without starting over?
We have several investment options. Which of them withstand a critical examination of the assumptions and should be implemented first?
The executive board has set the increased use of AI as a strategic goal. Where should we specifically start, and which use cases are economically worthwhile?
Our steering system has grown over the years. Which key figures should we focus on, and how can the reporting be pragmatically adapted and made flexible for future adjustments?
Regulatory requirements are growing, the business model is under pressure. How do we bring both into balance?
A supra-regional energy provider had twelve AI use cases in the backlog. The executive board wanted to see progress, the team was overloaded, the CFO skeptical. In three weeks, a maturity analysis, an assessment of the value contribution per project, and a clear prioritization were developed.
The result: four projects approved, five placed in the idea pool, three with a clear stop. As a result, several million euros of misinvestments were avoided. The application roadmap that emerged could be carried forward by the team independently.
Prioritization over parallelism.
Digitalization and optimization initiatives rarely fail at the concept stage. They fail at scaling, at unclear responsibilities, at data that is not consistently available, or at processes that were not considered alongside the solution. For technology to work, it must reach regular operations.
Engagements in this field often begin with one of these questions:
Our pilots show good results, but the step into regular operations is not succeeding. Where does scaling fail?
The data strategy has been adopted, but implementation has stalled. How do we manage the rollout alongside day-to-day business?
Our processes have grown historically. Where is standardization worthwhile, and where do we deliberately need flexibility?
Compliance and reporting obligations are tying up increasing resources. How do we automate mandatory tasks without losing control?
Our data foundation is reliable, but it does not systematically flow into decision-making. How do we support decision processes through targeted automation?
A grid operator handled incident processing in five regional units with five different approaches. The units defended their respective particularities – historically grown, regionally justified, culturally anchored. A blanket standardization was politically unenforceable; maintaining the status quo was economically unsustainable. A planned digitalization of the processes would have cemented the heterogeneity instead of resolving it. Instead of a top-down standard, a two-tier model emerged: a binding core process with clearly defined handover points and steps tied to key figures, supplemented by regional flexibility in precisely named sub-steps. On this basis, the processes were implemented end-to-end digitally – from incident reporting through dispatching to documentation.
The result: consistent controllability at group level, without undermining regional self-responsibility. Processing time fell on average by one fifth, while acceptance in the regions was preserved.
Standardization before digitalization. Clarity before speed.
Organization and change questions are the most common reason transformations fail. Not because employees fundamentally reject change, but because in many companies change is treated as a communication task, when in fact it is a leadership task. Anchoring does not succeed through communication, but through structures, roles, and leadership behavior.
Engagements in this field often begin with one of these questions:
The strategy has been communicated, but nothing of it is taking hold in day-to-day business. How do we achieve real anchoring in the organization?
Our leadership team is divided. How do we establish a shared direction that everyone supports?
We are introducing new tools and processes. How do we ensure the organization actually adopts them?
I need a sparring partner outside the line organization, with whom I can prepare difficult decisions. How do I integrate this role so that it complements the leadership team rather than disrupting it?
We have launched several change initiatives in recent years. The organization is exhausted. How do we make a new start without falling into the same patterns?
A municipal utility had decided on a strategic realignment. Six months after the kickoff, the implementation rate was barely measurable. Initial analyses pointed to a lack of acceptance in the workforce. The actual cause lay one level higher: the leadership team itself was not aligned on prioritization. Within the leadership circle, the strategy was interpreted differently and consequently carried into the organization inconsistently.
With a structured alignment process within the leadership team, clear decision rights, and a unified communication line, the dynamic changed noticeably within three months. Measurable in decision speed, in the consistency of messages, and in visible progress on the prioritized initiatives.
Leadership before communication. Clarity before consensus.
You work directly with me. No escalation chains, no changing contacts. If something critical arises in a project, you are informed by me personally. When a decision requires accountability, I take it.
A deliberate choice against scaling also means that this model is not suitable for engagements with a short-term need for larger advisory teams or for broad parallel work. For such constellations, larger consulting firms are the more appropriate choice.
My engagements do not end with concept delivery. They end when the team itself can carry on. As a rule, this means support up to go-live or up to the first reliable operational cycle. Methodology, decision bases, and handover are documented so that your team can continue independently.
This approach requires longer support than pure concept engagements. For questions where a strategic recommendation without implementation support is sufficient, traditional strategy consultancies are often the more efficient choice.
Documents are designed so that your team can develop them further independently. The methodology is explained, not just applied. Decision bases remain traceable after the project ends. The goal of the collaboration is your independence, not the extension of the engagement.
This way of working reduces the probability of follow-up engagements and is therefore economically less favorable for me. It nonetheless corresponds to how I see my role and is deliberately chosen.
I sell no licenses, no tools, and no implementation packages from third parties. I receive no commissions, conclude no sales agreements with technology providers, and have no additional sales targets.
This means I have only one interest: the success of your project.
From the first inquiry to project completion, I work through four phases with you:
01
A phone call or video call of 30 to 60 minutes, non-binding and with no further effort on your part. We examine whether your question falls within my area of experience. If I am not the right partner, I say so openly.
02
After a positive initial consultation, a clearly defined scoping phase of one to two weeks follows. The question, expectations, scope, and stakeholders are clarified. The result is either a concrete proposal for the further approach or the open statement that an external engagement is not the right path.
03
Duration, scope, and working method are agreed in writing in advance. Interim results are discussed regularly, not presented only at the end of the project. In the case of substantial deviations, we talk about them early, not only when they have become a problem.
04
At the end, you have working documents, a documented methodology, and an organization that can take the next step independently. The collaboration ends with the achievement of clear goals and milestones.
A phone call or video call of 30 to 60 minutes. Completely non-binding. We clarify three questions: whether your matter falls within my area of experience, which approach would make sense from your perspective, and whether the collaboration would be effective.
That is enough for a well-founded decision.
Book initial consultation