Implementation & empowerment · Thun · across Switzerland
I introduce processes and tools and leave the know-how behind – the goal is your independent team, not your dependence on me.
Implementation means: something stands. Empowerment means: it stays standing when I leave.
What that means
Many IT projects end with a system that works — and a team that doesn’t know how. Documentation sits somewhere. Know-how sits with the consultant. At the next problem, you call again.
I work differently: What I introduce, I document. What I set up, I explain. What your team should learn, it learns with me — not after me.
In the end your team should be able to act. Not me.
Processes and tools — cleanly documented, so implementation works in day-to-day operations.
Workflows, responsibilities, handovers — not as theory, but as your team actually needs them. What is documented, someone else can take over.
Ticketing systems, document storage, automations — what fits, not what happens to be in fashion. Introduced so your team knows what they are for and how they work.
Process descriptions, guides, decision bases — not for the drawer, but for when someone is missing or something changes.
Coaching, methodology, documentation — knowledge transfer instead of a black box.
I don’t explain in workshops what gets forgotten afterwards. I work with your team on real cases — and show along the way how to decide alone next time.
You don’t learn ‘this is how it’s done’, but ‘this is how you find out what fits here’. That survives a change of tool as well.
I have no interest in you needing me. No sales targets, no exclusive distribution, no portfolio of my own. If a referral is remunerated, you know that beforehand.
Accompany, hand over, make myself dispensable.
I’m there when processes are new and questions arise. Not as a permanent solution, but until the team is confident.
What I build belongs to you: documentation, access, decision bases. Nothing stays in my head or in my systems.
That is not a farewell ritual at the end. It is the goal from the start. If I see you no longer need me, I tell you.
From real-world experience
A Swiss SME with 20 sites wanted to digitise its accounts. Between receiving an invoice and posting it, there were 17 manual steps.
I didn’t digitise a single one. First I understood. Then I simplified. Then I automated.
What remained were four steps. Nobody had ever needed the other thirteen — they had simply never caught anyone’s eye.
From real-world experience
A Swiss subsidiary had to integrate with its parent company’s ERP. No choice, no leeway. Only: there were no documented processes — just habits that worked.
So I didn’t rewrite them. I worked out the processes with the accounts team — and we decided on them together.
A system can be connected in weeks. People cannot.
The first step
A conversation in which I listen and ask questions. If I see that you don’t need me, I tell you.
Implementation is one form. Sometimes you need clarity first — sometimes leadership.
No — and that is intentional. I stay until your team can act on its own. Some mandates last months, some a year. If I see you no longer need me, I tell you.
That your team knows what it is doing, why it is that way and what it can change — without calling me. Coaching in day-to-day work, not off-the-shelf training. Documentation someone else can read and understand.
Yes — and I write it so your team understands it, not only I do. Process descriptions, guides, decision bases. What is documented can be handed over.
No. No sales targets, no exclusive distribution, no portfolio of my own. If a referral is remunerated, you know that beforehand.