Context
«I have to explain who we are from scratch every time.»
What does it know about us?
Article coming

This is what we have connected, what runs differently because of it, and where it still sticks. No blueprint, just the result.
The parts work together. Between the steps, nobody copies anything from one program into the next.
Recurring work should not get faster. It should stop. When it does not, one of seven reasons is almost always in the way. One person can fix four of them in their own tool. For each one, we show what it looks like at ODCUS.
The checklist in the toolbox tells you which one is in your way.
«I have to explain who we are from scratch every time.»
What does it know about us?
Article coming
«It can do something similar, but not exactly that.»
What can it do?
Article coming
«Nobody here can judge whether this is good.»
Who works with it, and who owns it?
Article coming
«Nobody knows whether it made a difference.»
What does it bring?
Article coming
These three need company systems, approvals and someone with time. A better prompt does not help here.
«The numbers are somewhere else, so someone fetches them.»
What can it reach?
Article coming
«I cannot let it run alone, so someone checks.»
What is it allowed to do?
Article coming
«It used to work.»
How does it stay alive?
Article coming
Monday to Friday, an article goes out in German and English. Before it goes live, it is checked against our voice and our quality rules. Nobody has to be awake for it.
Next step
In 30 minutes, show us one piece of work that comes back every week. We tell you what is holding it up, and whether the next step is with us at all.
