Business + Information + Architecture
Next Thursday I'll be working at a live event in New York hosted by Knowledgent Group and Information Management magazine. We're holding court on the topic of business architecture, or more specifically, business information architecture.
To me, this is a distinctive merging of terms. Business architecture as I've always thought of it is a construct of functions and roles, resources to be applied to operational objectives. Information architecture as I think of it is meant to describe the hierarchies of data, content and application stores in an organization. Both of these things traditionally fall under the overall rubric of enterprise architecture and sometimes an enterprise architect.
I'm completely sure Knowledgent didn't have any of my observations in mind for a second when the message rolled up for them, but where I sit, it's fertile ground for progress. This marriage makes at least as much sense as the moment we decided to allow business intelligence and business process management in the same room at the same time. Some times, acronyms collide to the great benefit and relief of all.
But I have been in touch with Knowledgent CTO Chris Blotto, who's been at this longer and more notably than most. I'm not surprised he is spreading an experienced message of top-down coordinated services that do a better job of aligning IT organizational capabilities to business strategies in a cost and resource constrained world.
What I'm hoping to take from our event is a better shared-services repeatable, standardized way of creating this. If I'm getting it right, Knowledgent's message is focusing the mix of information assets and business processes and people.
"We've heard a lot of the clients show us their centralized information and they are very proud to have these giant data models they have created as a point of governance," Chris says. "And when we ask for the lineage of how that model was created and how it serves the business, they don't know. That's where we focus, stop overprocessing and stop architecting more than we need to."
I've heard rising backlash to the reactionary churning of IT resources and the need to provide a better, smarter supply side of information assets. I'm glad to know a lot of experienced folks are on this stocked agenda and that's what I will be asking about next Thursday. I'd be happy to see you there or sound off here so I can add your thoughts and questions to what I'm already thinking.