A blog post of Amanda Fenton about balance reminded me about a core concept I use in the space of GLUE and the change introduced via GLUE. In my post Fixing Flows I wrote about the joy of getting something to work and therefore eliminating a GLUE Disease. Maximizing the throughput in the GLUE Space in each and every domain is what I am aiming for and unfortunately the slowest domain decided upon the speed of the whole GLUE Space.
So what is my key to success here? I try to achieve balance (all domains do have almost the same throughput) by giving up on balance myself. Now that seems to be counter intuitive, but it is exactly what I do:
To achive balance I give up on balance!
The key aspect behind this thinking can be found in my way of tackling complexity:
- In the simple domain there is no need to give up balance.
- In the complicated domain there is limited need to give up on balance, but in a very controlled way.
- In the ambiguous domain there is permanent need to give up on balance, but action can be done one by one.
- In the Not-Known domain balance does not exist.
- Standing on both feet in balance
- Decide where to go ("automatic" after the initial decision where to go)
- During the step out-of-balance
- continue with 1
- GLUE Division Defence (As-Is)
- GLUE Division Destination (To-Be)
- GLUE Division Discovery (Transition, get to the target)
- continue with 1
And I do not know why, but this flow of events is kind of a Zen feeling for me: things happen unpredictable and real time around, with and due to me while I try to categorize (EPIC SCAN) them, set a direction (WISE SCAN) and support the execution (PACE SCAN). In most cases this require to be very flexible with the methods and tools and therefore I apply most of the time (80%) agile techniques. And here the technical tool I use is a whiteboard and markers.