Aggregated enterprise architecture wisdom
There are many challenges that CIO’s are facing in today’s cloudy, jargony, swirling maelstrom of Information Technology. But isn’t there something missing in the conversation that totally supersedes these challenges?
An architecture that is merely a PDF with a couple of generic line-box-arrow diagrams coupled with a few colorful “pancake” pictures isn’t really an architecture. It’s a marketing glossy. A white paper is too generic to be passed off as a real solution…
Title inflation/mis-direction is vermicious. Like a Knid.
An architecture for a solution requires understanding the problem at hand well enough that solving it can be described in terms that everyone understands. The architect speaks in terms of capabilities, not products.
The purpose of a company is to make money and to make that money while somehow imparting a positive effect to its customers. Can IT enable the business without a clearly laid out Vision? Without that sense of purpose, doesn’t IT typically make a mosh o…
Architecture is about holistically describing the system of people, process and technology. It can be abstract and conceptual, or it can be concrete and detailed. But it is never merely a specific product set from a specific vendor.