archive.Joe Lamantia.com

“An artist, a guru, a coach, and a spy” is how David C. Baker and Michael Janiszewski describe enterprise architects in their article 7 Essential Elements of EA.
The full quote is, “An enterprise architect requires a unique blend of skills. At various times he or she needs to employ the characteristics of an artist, a guru, a coach, and a spy.” Besides being pithy because it sounds like the intro to one of those ‘____ walk into a bar’ jokes, this rings true for enterprise information architects. However, humorousness aside, this isn’t terribly useful. And overall, the article is a fine breakdown of what’s required to put enterprise architecture into practice, but it only offers the pioneer’s perspective on where enterprise-level architects come from.
Their take, “Enterprise architects grow from within the technical architecture ranks, learning how to be artists, gurus, coaches, and spies as they work their way from being technical specialists, through application or infrastructure architects, eventually to enterprise architects.”
This is an honest if after-the-fact apprasial of a self-directed career growth trajectory that is no stranger to veteran IAs. It’s not adequate as a way to expand the understood scope of information architecture roles to address the enterprise perspective. I feel comfortable saying Information Architecture is accepted as relevant and useful in many areas of business activity, from user research and experience design to product development and strategy, after a few lean years following the dot com crash. But I’m not comfortable saying we have appropriate representation or even access to the enterprise level. It’s here that the business and information perspectives come together in an architectural sense, and also here where we should strive to make sure we’re valued and sought out.
We need to discover, create and define the paths that lead Information Architects to enterprise level positions.to action>
The alternative is being left behind.

Related posts: