Mummified architects

CIO Blogs
IT Blog Awards

About the authors

Navigate

Search the blog

« Why couldn’t I get the airline upgrade? — turned out to be an Architectural question! | Main | Why e mail is killing us, and the real root of the problem »

Yes, we’ve heard it all before. A good IT or Enterprise Architect is supposed to be able to bridge the gap between business objectives and technology solutions. In order to do that, architects still need thorough analytical skills: even with (some might argue 'thanks to') service-orientation the solutions landscape seems to be more complex than ever. Clearly, there is also a need for excellent communication skills: no architecture will be successful if it is not properly discussed, explained and driven through all layers of stakeholders. And then – of course- there’s also the political skills that an architect should possess in order to carefully align all parties involved. Looks like the portfolio of a mature, experienced professional that has seen it all and indeed, not many architects are likely to come fresh from university. But is it enough to have seen it all? Or is it a good recipe for mummification?

Some architects in the IT profession seem to believe that there’s no point in keeping up to date with new technologies and trends. They will claim that it is really all the same, that they’ve been doing similar things already in the seventies and that too much inside knowledge of new technologies will only corrupt the sheer beauty and well, like total conceptualness of the architectures they design.

Some good points there too.

But not if it leads to beautiful, conceptual architectures that are impossible to implement or simply miss the opportunities of advancements in technology. An architect should be an inspiring leader and mentor who visits the building place regularly and fully takes account for the designs that have been brought in. An architect should not be the mummified illustration of Peters Principle, only touching the very first part of the life cycle of a project and then quickly vanishing into history again.

This is why architects should update their technology skills over and over again, bringing them selves in sync with whatever is buzzing in real projects, in communities of practices, in universities and in the labs of technology providers.

Sounds like a busy schedule? Well, that’s what you get when you want to be an IT architect in the first place. Serves you right.

As a sort of diagnosis tool, I think it is a good idea to maintain a list of signs that prove you need an IT update. I will start with a few over here and I sincerely hope that you – dear readers – will bring in some of your own. I will certainly publish the list regularly, just to keep you sharp a bit.

Signs that prove you need an IT update

- You are convinced that the last important event in IT was the announcement of ALGOL68
- You have heard of NetWeaver, it’s one of these new, fancy web publishing tools by Macromedia
- You think that funny penguin is the Google logo
- You pronounce Microsoft’s newest programming language as ‘C Hash Sign’

Don’t be worried by the way, if you have never heard of ALGOL68. It’s fine. You’re just too young.

(Thanks to Wiebe Wiersema, definitely not a mummified architect).

Posted by Ron Tolido on June 9, 2006 in Architecture | Digg this | Seed Newsvine

TrackBacks

TrackBack URL for this entry: http://www.capgemini.com/cgi-bin/blog/mt-tb.cgi/29

Listed below are links to weblogs that reference Mummified architects:

» Mummified and Imposter Architects from Business-Driven Architect
Obviously, I'm spending a little time in 'the lounge' this afternoon. [Great feed reader by the way - well worth the nominal $5/month fee.] As most know, one of my soapbox topics for enterprise architects is: The business-driven enterprise architect'... [Read More]

» Diaper Bags from Diaper Bags
I think you have a really nice site. [Read More]

Comments

# on June 9, 2006 4:54 PM, Loek said:

Nice post, even though I already knew about your affection for architects. I have some more suggestions for the "list of signs that prove you need an IT update": http://loekb.blogspot.com/2006/06/do-you-need-it-update.html

# on June 9, 2006 5:17 PM, Ron Tolido said:

Thanks! As a lost, die-hard Apple fan, I particularly liked this one:

- You are surprised that the Beatles' record company is selling music players now

I am afraid though, that the same people that don't get the ALGOL68 stuff, won't understand this one either...

# on June 12, 2006 11:38 AM, Andy said:

I'm a young'un, and while I get the Beatles reference (only due to their recent legal engagements), I certainly don't get the ALGOL68 stuff!

# on June 12, 2006 1:24 PM, Ron Tolido said:

Well, as I said, not to worry...
Anyway, have a look at http://en.wikipedia.org/wiki/Algol68 for some good, old history.

# on June 12, 2006 3:31 PM, Brian Murray said:

Great article - I think the link between architecture and understanding the (potential) materials you are constructing the (potential) solution with is becoming more important by the year/decade .... this applies in the realms of IT too!

p.s. whats all this trendy algol68 stuff? Nothing wrong with good old Fortran I!

# on June 14, 2006 8:59 PM, Rajesh Sharma said:

One of the missing links in Architecture Teams is the Business Architect. A person whose primary skills lie in the knowing the business but someone who also knows how current systems in the enterprise fulfill that business.

Such a person has also ‘seen it all’ from a business perspective but has a fair understating of technology. Just as a technical architect cannot be a technical purist, an enterprise has to rear well rounded Business Architects.

Neither type of architect can be mummified.

# on June 16, 2006 10:30 PM, Martin said:

Maybe we're expecting too much of IT or Enterprise Architects. In building architecture there are probably few architects who can really bridge the gap between designing a structure and actually living in it - if they could we wouldn't need interior designers. The exceptions are often found when the people who will live in the structure have a strong role in generating the design based on their philosophy of living.

Note to SAP: Develop new training course - Certified SAP Interior Designer

But seriously, I agree that keeping up with developments in technologies/materials is imperative - its the way to realise concepts, ideas and dreams that previously were not possible, and will hopefully last into the future - just ask the ancient Egyptians.

# on June 19, 2006 9:38 PM, Ron Tolido said:

@Martin: We don't expect an architect to use (or 'live in' if you like) the systems that he has architected. But we definitely should expect from architects to be the building master when the system is initially being developed. And then, when it's all finished, the interior designer can come in....

# on August 4, 2006 6:08 AM, drew said:

The list of the tools that they used is what I wanted to know

please answer me if u knom or not.

# on September 26, 2006 3:11 PM, karelg said:

Ron writes: "indeed, not many architects are likely to come fresh from university"

Now, this is true in real life but nonetheless puzzles me. IT Architecture is often compared with "Building/City/Landscape" Architecture. But, where an IT student from a university spends the first X (5?, 10?, 15?) years of his/her career programming before eventually ending up as an IT Architect, a "Buidling" architect does not do masonry or carpentry the first 5-15 years after graduation..... WHY?

# on February 3, 2007 6:41 PM, Meds Man said:

Many people suffer because of diagnosis incorrectly put initially why that physicians do not hurry to recognize the fault, whether there are the successful judicial claims, won by patients? Where about it is possible to esteem? WBR LeoP

CTO Blog

Subscribe

Recent Posts

Navigate

Search the blog