Don’t become an Enterprise/IT Architect…

… really: don’t. It’s going to be nasty business.

I recently read:

Work was never meant to be fun. Consider the etymology of the French travail and the Spanish trabajo, each a translation of the English noun “work”: their Latin root is trepaliare, “to torture, to inflict suffering or agony.”

How the chicken nugget became the true symbol of our era

Right.

The same is true for the germanic Arbeit (German), arbeid (Dutch) which have their roots in ‘hard work’, ‘forced to do hard work’. There are links outside germanic, eg. Armenian arbaneak (servant), slavic rabŭ, robŭ (servant, slave), rabota (slavery — see robot). You get the drift.

Having done the usual digression upfront (one can always hope 😊), this post is about why — for many true professionals — Enterprise/IT Architecture/Strategy is getting more and more frustrating, and less and less the fun ‘let’s get this complex problem solved’ discipline it can be.

Enterprise landscapes (and society) are getting harder and harder to change, mostly as a result of increasing IT volumes. Technical decoupling may be rife, logical decoupling is a completely different story. Hence, adding to the landscapes is relatively easy(-ish…), which is why IT volume still grows fast, but that ‘ease’ masks the real difficulties regarding change. Growth masks the difficulties above all for those unaware of the reality of the shop floor (mostly found in ‘upper management’ of organisations and society — i.e. Boards of Directors, politicians, etc.).

In other words, yes, there are two speeds in IT: change is slow, growth is fast(-ish). Even if upper management (and many others, but the focus of this post is directed at the gap between ‘top’ and ‘bottom’) thinks they understand the complexity and effects, in reality, most of the time they have no clue as to the actual scale of the problem (there are always exceptions, of course, and lucky the Enterprise/IT Architect–Strategist who works for one).

The gap between upper management expectations for the capacity to change versus the reality of the difficulty to change also increases, because the difficulty to change grows much faster than upper management — without IT insight — can adapt to. Adaptation here amongst other things means: lowering expectations with regard to the capacity for change to make these expectations more realistic. It also means: saying goodbye to good-old trusted top-down ways of trying to manage the problem. To make matters worse, regarding the IT in their landscape, (upper) management is generally at phase one of the four stages of competence.

There is a strong irony here: upper management is often very focused on the difficulty getting the shop floor (the employees) to adapt to change. But it apparently escapes most of them that this holds for themselves too. Mirror, mirror…

Whatever assessment there has been of the success of enterprise architecture and other instruments to fight the results of the complexities of IT, one things has invariably be concluded: without engagement of top management (which of course will educate them to something they may currently be blind to), it is not going to work.

The world is somewhere on the rapid growth part of the S-curve of the information revolution. It is at the point that the S-curve is going into maturity that speed of change slows down. It is at that point that the gap between expectation of change capacity by upper management and the reality of the actual capacity for change is going to increase. And Enterprise/IT Architects–Strategists are amongst other things tasked with bridging that worsening gap.

Which means that — for Enterprise/IT Architects–Strategists and many more people who actually are active in shaping that digital landscape — as long as there is no true engagement of top management, the gap between them and their upper management looks like this red curve, which incidentally also represents how enjoyable/frustrating EA-like jobs are:

We’re in the period of rapid growth, the middle of the blue curve. That is also the period where (IT-related, which is much) change inside organisations (and society) gets more difficult every day, and thus noticeably slows down. Well run and successful projects that take more than five years are no exception. Conclusion: we are still in rapid growth, but the speed of growth is diminishing, the acceleration of growth seems to be over.

But as expectations of upper management follows past experience, expectations are still high, leading to many people in IT, and good Enterprise IT Architects–Strategists in particular, have jobs that put them on a psychological equivalent of the medieval torture rack (yes, I am exaggerating). They constantly are bearers of ‘bad news’, they try to convince people of different paradigms, which are not yet welcome as the expectations are still based on poor ideas about what is assumed to work. Making their life worse is a constant stream of bad Enterprise/IT Architects–Strategists that — generally as consultants — bring welcome (but faulty) good news to the top. Those bad Enterprise/IT Architects–Strategists experience less frustration, obviously. Ignorance is bliss…

Is your relation as an Enterprise/IT Architect–Strategist with upper management frustrating you because they do not truly engage and are clearly unaware of the actual complexities of reality? Brace yourself. It’s probably only going to get worse.

PS. Yes E., “speaking truth to power” is part of the job description…

Addendum (31 Jul 17:52): this article apparently has hit a nerve, given the reactions. To prevent misunderstandings, let me clarify some things:

• The title is of course firmly tongue in cheek (I’ve announced the post with a wink, I did not want that in the title). I do not seriously propose nobody should become an Enterprise/IT Architect–Strategist. Nor do I propose people should simply give up;
• I am not simply blaming ‘upper management’ for everything. I am laying out that the paradigm shift that comes with a slowly appearing ‘complexity crunch’ starts at the bottom, in the hard reality, and may be accepted by the top (who are as human as the rest of us in slowly adapting to paradigm shifts) the last;
• When I talk about frustration it is not the kind that comes from keeping your mouth shut. The Enterprise/IT Architect–Strategist has ‘speaking truth to power’ in the job description. One is supposed to be a trusted advisor and only in really toxic environments is it wise to keep your mouth shut (and look for another job). The frustration is that it will become harder to explain the ‘top’ what is going on and it will be particularly difficult to convince. This is especially true if that top has no interest in actually paying attention, because then it will be even harder as the first difficult step is to get them to hear you out.