A company can be running well. Growing, even.
That does not show what people have to compensate for every day to keep it that way.
Nor does it show what more would be possible.
Distance changes what comes into view.
From the outside, I look at the mechanics behind the result.
I show what can stay, and whether anything needs to change.
What is already there is sharpened or put to better use.
Complexity is reduced. Separate parts are connected. What is unnecessary is removed.
If building is the answer, I build it with you.
In day-to-day operations, I support your team or take on agreed tasks.
The knowledge and control stay with your company.
Three entry points, not a program. You start where your question is.
Each works on its own. Together they go furthest.
What does this company really need? And what doesn’t it need?
A business model you want to take further. An offer that should reach new customers. AI, and the question of what it can set in motion in your company. An investment you are weighing up. Or a decision where you want more than the first plausible answer.
A good idea can get bigger. A big decision can get simpler.
I bring new possibilities to the table. Together we take them further and test what they would do for your business, and what it would take day to day.
For a single question, a project, or on an ongoing basis as a sparring partner. We work directly on a concrete question. If you need the overview first, we build it together.
Your question doesn’t have to fit an offer. And it doesn’t have to become a project.
0 observations. Not a diagnosis yet.
What matters is whether and how they connect.
Almost every observation arrives with an explanation attached, and almost every idea with an assumption. I look at what sits behind it: how the offer, decisions, workflows, knowledge and systems work together. Together we separate what has been observed from what is only assumed. Then I test what supports the first explanation, what contradicts it, and what remains open.
The task can change as a result. Sometimes less needs to change than expected. Sometimes the place to start is somewhere else. And sometimes one piece of information is still missing before a decision makes sense.
I make visible what your decision rests on.
FROM THE WORK
A lot seemed urgent, and from the outside it looked like a visibility problem. In conversation, the owner corrected that picture: inquiries were coming in, what was missing was how they were handled. So a different step came first.
READ THE CASEStorage was full, and more storage looked like the answer. The analysis showed it wasn’t the new work filling it, but old file versions. The team removed them, and I switched on automatic trimming. No extra storage was needed.
When it isn’t yet clear what matters first, you need a solid picture before anything else. That is what this entry is for: a short conversation. If it fits, three steps follow.
Without a clear picture, every engagement is a gamble.
That’s why this part is on me. No fee.
No small talk. No pitch. You describe how things run and what’s on your mind. I ask beyond the first explanation, and together we narrow the question down. What I ask depends on your situation. You come away with a first hypothesis and what the deep scan needs to test.
I test the hypothesis against further information and other explanations. What doesn’t hold is dropped. What stays open is named. Often this shows what has long been there and goes unused, and what is missing. I sketch possible approaches. That shows what can stay, whether anything needs to change, and what makes sense to do first.
It captures the tested picture, distilled to what matters now. I go through it with you, and we correct whatever doesn’t fit.
After 48 hours
What limits progress most right now, and why.
What makes sense to do first.
What stops and what can wait, so the first move has room.
What stays open on purpose, and what it takes to decide it.
Sometimes no is the right result.
If what you have holds, or a change doesn’t justify its effort, I say so. Even if we stop there.
Your team puts into practice what we have clarified. On its own or with a partner of your choice.
We go deeper on the question, or work on what comes up in your business on an ongoing basis. As a consulting engagement with an agreed scope and a fee.
We put into practice what has to change. At a single place or in how the parts work together.
02 ChangeDevelop the way you work, your knowledge and your systems. Enable your team, or take on agreed tasks.
03 Keep runningNo pressure. No lock-in.
Sometimes the decision is the result.
Sometimes it is where implementation begins.
What has to change? And how do we put it into practice?
A sharper offer has to land in the sales conversation. A clarified responsibility has to hold in the next decision. A new tool has to fit the tasks it was meant for. This is where implementation begins.
I develop the solution and put it to work with your team. On the offer and its route to the market. On workflows and handovers. On knowledge, decisions and the systems behind them. Sometimes we build something new. Sometimes we connect what has long been there. Sometimes work disappears because an unnecessary step is gone.
If your project is already clear, there is no detour: we check the goal and the preconditions and agree the implementation directly.
The direction is set.
Now comes the concrete work.
You can start with a concrete project or with the next step from our consulting work. We agree what has to work afterwards. That determines what we change, what we connect and what we build.
Bring a new offer to market. Simplify a workflow. Build an application or set up an entire working environment. We put the project into practice while the business keeps running, with the people who will work with it.
One project. One result. Landed in daily work.
A good offer alone doesn’t win a customer yet. A new tool alone doesn’t improve a workflow yet. Sometimes the answer isn’t in one place, but in how decisions, responsibilities, workflows, knowledge and tools work together. From the first inquiry through proposal and order to delivery and invoice, for example, with the knowledge that should be there again next time. That is where we connect and simplify what is there, and build what is missing.
The parts work together. You stay in control.
The work can start in different places.
What matters is what holds you back, or what becomes possible.
In strategy. In systems. Or somewhere you're not looking.
The trigger can be a bottleneck: what no longer fits, what was never built, what already exists but remains unused. Or a possibility you don't want to leave on the table.
Each example leads to the work behind it.
I think with you. And I put it to work.
I develop, design and build what your project needs. For example:
From a single solution to how everything works together. Brought into daily work with your team.
From your offer and sales process to workflows, knowledge and systems: explore the questions I examine and the changes I put into practice.
No one-size-fits-all.
Direction becomes a concrete job: What should work differently afterwards? Who works with it? What has to stay? How do we know the job is done?
With your team, on the real workflow, with real tasks and the documents you already have. Your team knows the day-to-day work. I look at how it connects across departments. I work on the system, not on the people.
If what you have holds, we use it. If an application, a workspace or an automation is missing, I build it. Not every good solution is a build.
Case: We built nothing newWe start with your work: What should become possible, and what does it really take? Then we use what holds, connect what belongs together and build what is missing. Software can be shaped around the business today. New technology should open up possibilities for you, not add another environment you have to look after.
Perspective: Software has become a materialEach stage has its own result and a clean end. The big picture is big. The next stage is small.
Working with it shows what works, where exceptions appear and what is still missing. That goes back into the solution. Access, responsibilities and guides are part of putting it into use. So is the question of what your team will change itself in future, and when it needs support.
That is why the handover starts during the work, not at the last meeting. Your own accounts, your own access, documented rather than told.
What gets built runs without me. Whether you run it yourselves or hand it to me is your decision.
The documents existed. Someone had to know which ones a new proposal needed. DD turned that knowledge into rules in a tool for the contractual part of a proposal and handed it over.
READ THE CASEA client asked for a folder structure for the AI. There was more behind it: the knowledge lived in two heads. DD organised it, connected it to access rights and templates and built an assistant on top. So the knowledge isn’t just filed away, but can be used in daily work.
READ THE CASEA project has an end.
The business keeps going.
What should your team be able to do itself? What do we take further? And what do you hand over, deliberately?
New offers. Different requirements. People joining. What emerges in daily work should take the company forward, not create new detours.
Together with you, I develop the way your company works. We pick up new possibilities, simplify what gets in the way, and make knowledge and good solutions usable for your team. So that more time is left for the work people were hired for: deciding, designing, selling, listening.
That applies to what we have built together. And to what has long existed in your company.
We strengthen your team’s ability to run things itself. Where you want support or relief, we agree what we do together and what I take over.
Leading it yourself doesn’t mean doing it all yourself.
What you learn in the market should take your company forward. We keep developing how your capabilities become an understandable offer, and how interest becomes a customer relationship that holds. Test a new offer. Sharpen a route to market. Use what customer conversations reveal for the next step. I combine the view from outside with your team’s work and implement with you what is still missing.
Positioning and go-to-marketWhen a workflow doesn’t hold up in daily work, I work with your team on the causes. We clarify handovers, simplify steps and adjust the tools behind them. I implement agreed changes with your team and support their use in daily work.
Process automation and systems integrationKnowledge should be available where the work happens. We make experience, methods and good solutions usable for existing and new employees. Working on concrete tasks builds confidence with new ways of working and with AI. What proves itself in the work flows back into methods, templates and working rules. That is how your company’s knowledge grows with the work.
Company knowledge for AI and peopleApplications, data and access have to fit the work and work with each other. I develop this environment with you, connect what exists and implement the necessary changes. Where you want to hand over the upkeep, I take on agreed tasks and operational responsibility.
Adapt and improve after launchWe agree what your team runs, where we work together and what I take over, to fit the task.
For every suitable task, you choose how we work together. Per task, not once and for all. In combination, too.
You give me the task. I bring it to the agreed result and stand behind it. You know where the work stands and when it needs your decision. And if it turns out along the way that the workflow could be simpler, I say so.
We work on your actual task. Your team sees how it’s done, tries it and clears up questions directly. As a workshop with the people who will work with it, if that helps.
The work should carry on even when I’m not in the room. For that, we make knowledge applicable: a clear guide, a usable template or a simpler workflow. It comes out of a project or as a job in its own right, with scope and price or a cost limit agreed beforehand. The result belongs to you.
What repeats doesn’t have to be solved anew every time. I suggest the way to get there myself. Your independence is a paid result for me, not a loss.
FROM THE WORK
A small consulting team had material, its own template and an AI assistant. What was missing was the path in between. I built it: from the first question, through a checked slide plan, to the presentation in the team’s own design. A way of working the team can carry on with by itself.
Keeping control doesn’t mean doing everything yourself. It means deciding for yourself what you hand over.
Maybe you don’t want to trigger a new job every time. You want to know that someone is looking after an area. Then we agree ongoing responsibility: what I run on my own, where it needs your decision and how you stay informed. I run the work, coordinate the people involved and put open points on the table.
I can also take over what I didn’t build. And what I have taken over stays yours. Accounts, data, documents and knowledge are kept so that you can carry on yourselves or pass the upkeep on in an orderly way.
You pay for the work or the responsibility you hand over. You know the price or the cost limit beforehand.
A new workstation. An access question. A fault that holds the team up. Or an area you want to hand over long term. Flex connects that choice with fixed prices or a cost limit, a credit balance and a clear overview of jobs and costs. An IT task doesn’t need the strategic diagnosis.
A client wanted to hand over her entire IT. Before saying yes, I wanted to know what she would actually be paying for. That question became Flex.
Daily work brings new questions. And new ideas. Then we clarify again. And you decide how it continues.
01ClarifyWork may move. Knowledge, access and control stay with you.
Two decades inside companies showed me the same thing again and again: a lot stays unseen. Not because anyone is doing anything wrong. Proximity changes what you see.
When you are inside something every day, you see it differently from someone looking in. That's not a flaw. That's part of reality.
At some point I stepped back myself. What grew out of it was something I hadn't had before: clarity.
That became Disruption Dynamics.
I bring the outside view back in, so you can see clearly and decide for yourself.
I bring into view what gets lost in the day-to-day.
An answer takes you as far as the next question.
Clarity takes you further.
Zürich · Remote · On-siteGerman · French · English
You decide what you run yourselves and what you hand over. Knowledge, access and control stay with you. Whether we clarify a question, change something together or keep working together day to day.
What I take on. What result or what support you get for it. What stays with you. What price or cost limit applies. Agreed clearly before the start.
The scope fits the work. So does the investment.
In the end one question matters: who helped you?
The work has to earn the referral. Marketing can't.
Four channels. Direct access. No gatekeepers.
An idea you want to test. A decision that is coming up. A concrete project. A way of working you want to take further. Or work you want to hand over.
Tell me where you stand. In the first conversation we clarify what you need and how we start sensibly. The first conversation comes without a fee. You know the scope and the costs beforehand.