Concrete.
Not abstract.

A company that had been successful for many years and had built up a very broad portfolio over time, because almost every client request was made possible individually. What had long been a strength turned into a problem: from the outside it became ever harder to see what the company stood for and what set it apart. The question was therefore not which services to drop, but which core a specialisation could grow from.

• Two-day why process with the leadership team
• Working out the shared core instead of drafting a mission statement
• Translation into sprints for the following quarter
• Strategic clarity and operational delivery in one arc

At the end there was an answer to the question of what the company stands for beyond individual products, and next to it a work plan for the coming quarter that would show whether the new direction holds up in daily business. A well-phrased sentence on its own would have moved nothing.

The performance of an operational area fell short of what management expected. Workflows looked inefficient, productivity was too low, and the obvious assumption was that the processes themselves were the problem and could be brought under control with a proper analysis. The brief was cut accordingly: process analysis.

• Working alongside the staff in daily operations over a longer period
• Following every step until I could have reproduced it myself
• Analysis only afterwards: routes, sequences, points of friction
• Placing the findings in feedback rounds with management

There was room to improve the workflows, only that would not have touched the core. Parts of the team were not delivering the expected performance, and the causes lay in leadership and organisation: performance management that had no effect, unclear expectations, and conditions grown over years in which this behaviour could develop. Setting that out clearly for management turned out to be the more important part of the brief.

A company was introducing a new central system. The technical rollout ran as its own project; the decisions had long been made by the time the workforce heard about them. For many, routines that had worked for years were about to change, and the reactions ranged from open rejection through scepticism and quiet endurance to a few who saw something in the change from the start.

• A fixed interface between the project and the workforce
• Collecting feedback, catching questions and uncertainties
• Translating project decisions into the language of daily work
• Feeding observations from the organisation back to those in charge

The first step was to understand the resistance: which worry was justified, which information was missing, where someone felt passed over. Over the months, opponents became tolerators, tolerators became supporters, and some of them became people who drove the change themselves. The system would have been introduced without this work as well; what was decided in those months was how it would be used.

A leader in transition. Management doesn't want a one-off training, but support that runs alongside for months and actually changes something.

• A shared kickoff day as the starting point
• Then a fixed rhythm, e.g. twice a month
• Individually or for a small leadership team
• Duration individual, usually 6–12 months

A fixed, protected space outside the day-to-day. Not every session moves the same amount — but the rhythm carries through the weeks when everyday life is louder. It shows in less friction and more confidence in the role.

An industry where day-to-day business is heavily relationship-driven: difficult customer and employee conversations are part of everyday life, and leaders often operate in reaction mode instead of their actual leadership role.

• Half-day or full-day seminars, bookable individually
• Four topics, one consistent standard
• Practical workshop with participants' own cases
• Together they form a curriculum for the industry

What a single seminar can achieve is limited — which is why each one has its own narrow focus: clarity about your own role, and tools concrete enough to try out on the next working day.

Eight employees are stepping into a leadership role for the first time — with no prior training and no shared language for leadership in the company. Management didn't want a theory lecture, but a complete, practice-oriented introduction.

• 2 days on site, 8 hours each
• Input, individual and group work, role plays
• Flipchart instead of slides — the group works it out together
• Core topics: leadership, expectations, commitment, conversations, feedback

Nobody leads perfectly after two days — that would be an empty promise. What the eight took with them: a shared understanding of what leadership means in their context, their own written-out expectations of their teams, and first practised confidence for difficult conversations. The rest develops in everyday work.