Today something happened to me that even embarrassed me a little. Because I couldn’t decide yet how our website strategy of one of my new companies should look like, I threw it into the room again in the office and annoyed my colleagues that I’m stuck and can’t get any further. And the tragedy had been going on for two months!
Thereafter my partner Carsten said if I hadn’t done Kubernetik about it? I had to admit hesitantly, no!
The obvious overlooked
Now I make several weekly Kubernetiks for myself, for my companies, for other people. Only in this case was I reluctant to use the Kubernetik for my complex problem. Why? Because I was so overwhelmed that I didn’t see Kubernetik as a solution. This seems paradoxical: the inventor of Kubernetiks does not apply Kubernetik himself in an emergency? Yes! I had simply forgotten to consult Kubernetik for this. For myself, it’s actually incomprehensible!
My attempt at explaining
The more I deal with a topic, whether in my job, partnership, etc., the more emotional it becomes. And then the rationality leaves you with pleasure sometimes. The actually obvious, namely to make a Kubernetik, is then no longer accessible to you. Only other people in your own environment can open your eyes.
And so Carsten challenged me with his indirect criticism in such a way that I immediately made the Kubernetik.
Unconsciously it was already clear to me why I had delayed this Kubernetik, although I have been writing down pro and contra points in lists for weeks. The problem is extremely complex for me and I had to make a decision. The high complexity was then clearly recognizable retroactively by the many, many networks in the relationship map. But that’s the way it is. The more complex a question, the more important it is to use Kubernetik as a method. In my experience, many people who already know about Kubernetik have enormous respect for the task, especially when it would actually be more necessary to take half an hour for Kubernetik. It would be so simple: just take a piece of paper and just make it.
Although I had finished the Kubernetik in 25min, this time it had taken me to overcome myself. But the brain power needed for the Kubernetik was as intense as giving a four hour lecture. The half hour was worth it!
What was the problem?
I just didn’t know how to proceed to set up a website strategy for our new products? Now I have several websites of my own on WordPress and I am reasonably fit. The new challenge, however, is that in my software company I am pursuing the strategy of launching a new product completely every month or founding within my own company. The central question, therefore, is whether each product should be placed under a main website or whether a separate domain plus landing page should be created for each product or company? There are really countless criteria that need to be weighed up.
I took a piece of paper – I don’t really need the canvas anymore – and scribbled the following Kubernetik:
Now I don’t want to go into more detail what the exact challenges of my question were. Nor do I want to go into the individual influence variables, what they mean and which concrete outcomes came out per response sentences.
This example should illustrate how a Kubernetik can look even without the printed Kubernetik canvas. And that as an experienced Kubernetik expert you can detect very complex systems in just a few minutes. Above all, I now have a solution for myself. Two new ToDos I started within one hour and have now made an important step forward.
Trust the method – it works!
If you sometimes find the Kubernetik too elaborate to apply, perhaps at first too complicated, then trust that it is possibly simply the fastest and most effective method ever for your complex problem. Not doing the Kubernetik can therefore be a mistake and you need a lot more time and nerves than if you don’t tackle it. Therefore:
Overcoming, doing, understanding, acting!
This also applies to me again and again, as my own blockade clearly shows. The Kübernetik must always be geübt.
Other people help
However, if I, as a Kubernetik expert, have not thought of using a Kubernetik when it would have been useful, what else does it need? The answer is simple: another person! Someone who wakes you up and knows the Kubernetik. Or someone who at least reminds you of the tool during a thought exchange. This can be a friend, acquaintance or coach. Because every one of us likes to be blind sometimes, when it concerns you and you are a little busy at the same time.
So if you are ever stuck or emotionally lost, condition yourself to ask people what you should do. And if you succeed in reminding yourself of the Kubernetik, make one 🙂