Kai Schlüter

May I introduce the Enterprise Architect

by

It was a long time since my last post and I am sorry for that, but I am very busy these weeks and therefore the blog lost some of my attention. I will try to put more time and energy into it in the next weeks, but I do not know for sure yet if I truly …

Social EA Logo

by

It is time to brand my blog Social Enterprise Architecture a little. Therefore I have created a small and simple logo (with huge help of my wife who is way better in logo work than I am). From now on I will use this logo also as the favicon.That actual…

Categories Uncategorized

Cultivate Collisions

by

A couple of days ago a tweet flew by which deserved closer attention:Questions to ask about any method or approach: Who invented it? What problem one tried to solve? Do I have that problem? In the interaction with the author it became (once again) obvi…

Don’t Think You Are, Know You Are!

by

Today Tom Graves has neatly described Two Enterprise Architectures and by that explored the difference between Enterprise IT Architecture and Enterprise Architecture. I have touched that topic shortly in my post about Real Enterprise Architecture. I am…

Categories Uncategorized

Guide the Energy

by

As I have written in my last post Less is More reducing complexity to the absolute needed minimum is key to not add unneeded clutter and blurriness. I also touched shortly on the energy created if two (or more) ideas compete for the limited attention a…

Categories Uncategorized

Less Is More

by

In my last post I have written about the concept to compare Enterprise Architecture with the Matrix. In short: free your mind and open up for all the possibilities. There is no reason to stay inside the boundaries provided by the various frameworks and…

Categories Uncategorized Tags

The Enterprise Architecture Matrix

by
In my last post I have tried to express that I have given up on balance and I like it pretty much to be out of balance. It is kind of balance for me to be out of balance. No idea why, no idea where that leads to, no idea how long it lasts, but I accept the fact that I like it and that it gives me this perfect moment of being once with the flow. The flow I try to optimize with my daily work and which I tried to describe (fairly weak description so far) in my posts about GLUE Disease and Fixing Flows:

In this post I try to describe the way I approach Enterprise Architecture with my GLUE thinking in a different way. For that I will use a sequence from the movie Matrix and translate it into a dialogue between a Real Enterprise Architect and a Wannabe Enterprise Architect. For simplicity I use Wannabe and Real to point out who is speaking.


Wannabe: I know Enterprise Architecture.
Real: Show me.
Real: This is an Enterprise Architecture Activity. It follows the same basic rules than the Enterprise, rules like governance. What you must learn is that these rules are no different that the rules of a framework. Some of them can be bent. Others can be broken. Understand? Then solve it, if you can.

[Wannabe tries to solve the problem]

Senior: Good. Adaptation, improvisation. But your weakness is not your technique.Project Manager: The Junior tries to solve an Enterprise Architecture problem.

Real: How did I solve it?
Wannabe: Your knowing more than I do.
Real: Do you believe that my being more experieced or knowing more has anything to do with my Enterprise Architecture framework technique in this place? You think that’s air you’re breathing now? Hah. Again.
[Wannabe really tries to solve it]
Project Manager: Jesus Christ, he’s fast. Take a look at his neural kinetics, they’re way above normal.
[Wannabe is close to solving it]
Real: What are you waiting for? You’re faster than this. Don’t think you are, know you are. Come on. Stop trying to solve and start solving it.

Project Manager: I don’t believe it.

Wannabe: I know what you’re trying to do.
Real: I’m trying to free your mind, Wannabe, but I can only show you the door, you’re the one that has to walk through it. You have to let it all go, Wannabe, fear, doubt, and disbelief. Free your mind.

I truly hope that Enterprise Architects are waking up and walking through that door. The more the better. If you ask me then there is more to solve out there than we are ever able to sort, so if possible free your mind and enter the real Enterprise Architects leaving all the rules and boundaries behind you, but use them where reasonable.


given up on balance

by
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:

  1. In the simple domain there is no need to give up balance.
  2. In the complicated domain there is limited need to give up on balance, but in a very controlled way.
  3. In the ambiguous domain there is permanent need to give up on balance, but action can be done one by one.
  4. In the Not-Known domain balance does not exist.

I like to use the analogy of walking:

  1. Standing on both feet in balance
  2. Decide where to go (“automatic” after the initial decision where to go)
  3. During the step out-of-balance
  4. continue with 1

Therefore to move the Architecture from one state to the other (As-Is -> Transition Architectures -> To-Be Architecture) the whole system gets out of balance all the time, because it is the only way to move. The whole GLUE Division Discovery is completely dedicated to out-of-balance behaviour, so the same flow as walking with GLUE terminology:

  1. GLUE Division Defence (As-Is)
  2. GLUE Division Destination (To-Be)
  3. GLUE Division Discovery (Transition, get to the target)
  4. continue with 1

In a perfectly running GLUE the next To-Be is close to automatic (or at least very fast), which translates into a system where the change between balance and non-balance is done so fast and automatic that everything is perfectly in flow. In most cases I find (or throw myself at) systems where the flow is out of balance, but the system stable (and unwilling to change). Here I give up my own balance (entering willingly Not-Known) to create a momentum to change.

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.

I am a ChickenBrain

by
After trying out blogging for a bit more than a month I decided to invest a little time into using my own domain now for the blog. It is still hosted with Google Blogger, but now to be found under http://socialea.chickenbrain.de.
 
“We know nothing at all. All our knowledge is but the knowledge of schoolchildren. The real nature of things we shall never know.”
Albert Einstein (1879 – 1955)
 
 
The interesting (for me at least) thing about that domain is, that I found the name ChickenBrain at the age of 17 as a Character name for a Roleplay game (quite some years ago), before I explored the Internet. I quit roleplaying some years ago, but that nick kind of sticked to me. At that age I had a very good teacher for philosophy (looking back my school was really cool to offer that course, at that age I did not recognize the school to be cool). That (wise) man teached us in a good way that we do not know anything, so ChickenBrain became my pattern (and still is my main pattern).
 
I know that I know nothing and therefore I seek for answers (and will hopefully continue seeking for answers). Funny enough in one job interview (with a headhunting consultancy) I was told to not use my primary email adress kai@chickenbrain.de for sending the resume, but shall use something more professional. I was listening to the headhunting clerk and told him that I will not (and hopefully never) will be working for a company who does not value people who openly confess that they know nothing.
 
So, if there is one thing I know, than this is the message:
I am a ChickenBrain
Categories Uncategorized

Complexity SCANs in GLUE

by

In my lasts posts I was exploring complexity and how I tackle the problem of complexity by applying my GLUE thinking to it. Therefore here a short summary so that my thinking about complexity up to now is collected in one place. I am using the SCAN fra…

PACE SCAN

by

In my last posts I explored the world of complexity and started with Don’t Panic. An advice which does not only work for GLUE and Enterprise Architecture but is generally a fairly good advice. The some ideas collided in my head (which reminds me of the…