Enterprise Architecture state and causes (iii)
While the customers and stakeholders are not complaining, little can be done. This is the main reason for the lethargy of EA.
Aggregated enterprise architecture wisdom
While the customers and stakeholders are not complaining, little can be done. This is the main reason for the lethargy of EA.

Architecture-by-definition is an anti-pattern.
The goal of a definition is to remove noise.
You add another layer of noise when your definitions are model-specific sub-definitions for commonly understood terms. For example: service, product, capability, or system.
Special definitions introduce an additional cognitive load that easily outweighs the benefits of a more sophisticated model.
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.
What happens when people get too fixated on the ‘boxes’ in our models and frameworks? And what can we do about it in enterprise-architecture? This one’s actually a follow-on to the previous post about ‘It depends…‘, but it starts with…
The key aspect behind this thinking can be found in my way of tackling complexity:
I like to use the analogy of walking:
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:
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.
What’s the one phrase that enterprise-architects use time after time, and that drives almost everyone else crazy? Well, it depends… “It depends.” Yeah, we know it prob’ly depends, but just gimme the answer, willya? Frustration indeed… Going back to a…
The next public dates for my workshops with Unicom are as follows.
Business Architecture Bootcamp (November 20th-21st)
Organizational Intelligence Workshop (November 22nd)
Architecture-Led Procurement (November 28th)
Please tell them you saw it on m…
@VenessaMiemis asks “If most people are self delusional, what’s the point of qualitative research?” @CoCreatr retorts “What if we are all self-delusional and need proof by qualitative research to become more accepting of it?”Of course organizations are…
“The IMF downgrades its growth forecasts and casts further doubt on Osborne meeting his debt target” reports @JJ_159 via @Spectator_CH. @EmmaLangman suggests (sadly) that that it is ‘our’ debt target by association. “What Chancellor chooses, the countr…
I saw the post by Forbes blogger Joe McKendrick in which McKendrick introduces a new term – Service Technology – which cements the concept of a service-oriented thinking that technically enables the realization of SOA within the enterprise followed by its sustained evolution to cloud computing. Continue reading →![]()
Social platforms, like Facebook, Twitter, and others are gaining traction within enterprises, but are they really useful and do they increase employee productivity? Well, according to Forrester’s Craig LeClair, the answer is no, until they are integrated with core business processes. OpenText’s Steve Russell recently joined Craig to discuss how dynamic case management (DCM) solutions, […]
Related posts:
Related posts brought to you by Yet Another Related Posts Plugin.