Enterprise Architecture: The Godfather of Buzzwords (and Why it Still Matters)Buzzwords. Trends. You know them. You've seen them. You've heard them.

Big Data. The Internet of Things. The Customer Experience. I could go on, but I probably don’t need to. We’ve fallen so in love with the idea of fast-moving technology trends that we've reclaimed the concept from its place as noun and returned it -- obnoxiously -- (see “trending”) into a verb that now gets used in contexts from sports to entertainment.

The temptation, of course, is to dismiss these trends and buzzwords as simply marketing fluff, stuff and nonsense, sound and fury that’s 75 percent talk and 25 percent substance. Certainly the very nature of enterprise IT makes it a place where change has traditionally been embraced slowly, a place where “what’s trending” goes to be slowly chewed up and quietly digested over time. And that digestion’s not always been smooth, either.

But just when you think that you’re out, they pull you back in.

The times are changing. While that darling trend of 2012 -- the “Consumerization of IT” -- may not yet be reflected in your spellchecker (try it and see) it’s definitely had a lot to say about the pace of change. Mobile devices, BYOD and of course, the all-encompassing cloud have all pushed their way into the party and now change really is something that happens more and more often, more and more effectively.

How on earth did we get here? One former trend in particular, one buzzword from the late 1990s, rings true as a harbinger of all we've come to expect in modern enterprise IT.

Enterprise Architecture.

A Trend with Lasting Impact

In 2014, the words “enterprise architecture” (EA) have come to mean a lot of things. I've seen people use them to refer to a reference diagram, an infrastructure plan or an approach to governance. “Enterprise Architect” might be one of the more open-ended job titles out there today. But when Enterprise Architecture first emerged as a discipline -- and where it is practiced in its truest form today -- it was the application of a disciplined, strategic approach to the interaction of people, process and technology and their roles in the enterprise.

It was the sort of strategic planning that perhaps wasn't necessary when everything was done on mainframes, but became essential as workloads and applications splintered into various architectures and methods of delivery. Of course, enterprise architecture didn't just enable the enterprise; it also helped to define the enterprise as we know it.

Using an architect’s approach of logical models, patterns -- essentially blueprints -- and other means to achieve consistent, repeatable outcomes and understanding, enterprise architecture gave us a clear, methodical way of looking at business and the information technology that we use to support it.

That information technology, of course, comes in onrushing waves. Trends. And enterprise architecture -- now more or less embedded in how we plan, govern, and think about IT -- gave us the tools to manage how we accept it. If you consider today’s main trends from an enterprise architect’s perspective, you can get a much better feel for how they will impact your business in one, three, or five years down the road.