Grail Figure: What is the secret of the Grail? Who does it serve?
Perceval: You, my lord.
Grail Figure: Who am I?
Perceval: You are my lord and king. You are Arthur.
Grail Figure: Have you found the secret that I have lost?
Perceval: Yes. You and the land are one.
Doesn’t this sound like a conversation you overheard between several architects standing around the watercooler?
Do you feel like we have long forgotten the secret of The Architecture?
Have our knights been roaming the countryside through famine and plague searching for the Holy Architecture to no avail.
Where is Perceval!
I will not reiterate the whole saga of Arthur, his knights, the land, and the elusive Grail. There were many stories of Arthur but a powerful theme was that Arthur and the land were one. Arthur forgot that this was true. Being separated in spirit from the land around him he fell ill and the land fell into disarray. They could not be separated and the health of one depended on the other.
After years of failed attempts to find the Grail and its secret Perceval had a vision of the long lost secret. Perceval met with Arthur and reunited the secret with the king. Arthur was restored and the land was restored along with him.
cue the music, blooming trees, and galloping horses
What is the secret?
The Secret of Architecture is that the Business and IT are one.
Or more importantly that you must architect the whole. This isn’t a new idea but as we begin to move faster and as we take on new aspects of being agile we can’t lose this secret. Let’s look at three areas that will help prevent the downfall of the kingdom.
- Architecting is about optimization
- Architecture must be intentional
- You must architect the whole
We recognize architecture because we believe that we can optimize the situation. It takes skill, experience and cross area knowledge to understand how to realize these optimizations. That is the goal of architecting.
Everything has an architecture. The question is was it intentional?
Without it being intentional you can’t expect much from architecting. You can’t expect a particular result. With Intentional Architecture you try to guide the overall outcome to align with what is most valued.
No matter what you call yourself or what your area is there can be active architecture. You will have a scope and everything within that scope must be considered but not necessarily acted upon. This is the horizontal nature of architecting and is a primary difference between architecting and engineering.
Enterprise Architects look across the entire business (or they are supposed to anyway). Technical Architects should have a narrower scope and may not even be architecting at all. They may actually be just doing a really good job of engineering.
Trouble comes into play when we ignore items that fall within our scope. Setting a smaller scope is ok but do not make the scope large then leave areas to chance.
So go forth!
How do we expect that system optimization will happen when we only consider some of the parts?
You must architect the whole to have a better chance at obtaining the optimized results that you expect.
The missing piece to all of this is the how. Do we implement tools and processes to crush the people into submission? Probably not.
Start with the fact that you are architecting the whole. Start with the fact that you can’t architect the business and leave out information technology or any other piece that makes up the business. This shouldn’t be a secret but if we treat it like one we will never be successful as architects.
For next time, let’s go figure out how to build agile and reactive architectures for everyone.
As a side note if you have not seen Excalibur please run out and find a copy to view right away. Inspiration is everywhere. You just need to look around.