10 Signs You’re Not REALLY a Director of IT
Title inflation/mis-direction is vermicious. Like a Knid.
Chris Lockhart
A Capabilities-based Architecture
As technology architecture professionals, we can only be successful and valuable to those who pay us if we frame our work in terms of capabilities at the outset. If we start with details, we’ll ultimately fail.
Architecture is Not: A Proof of Concept
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.
IT Made Simple
What would it take for your business to view IT as a valuable, essential partner instead of an annoying cost-center that they’re forced to deal with? Wouldn’t that be better for you and better for them?
Nogility
Large technology organizations don’t simply become agile. They’re either agile or not. If they’re not, the path to being so is via change, often radical change at that.
Is The CIO Necessary?
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 Not: a Vendor Product
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.
Unprincipled Architecture
Anything IT does should be seen as consistent. Using words like “Principle” with the definition most people have for it is a sure-fire way to disappoint folks. It turns out that instead of a iron clad ‘always-will-do’ thing, our Principles are merely s…