Do you love fun… in IT design? Well I do.
Ogilvy South Africa has created a few provoking images. These images express the awkward situation of IT design that concentrates merely on technology:
- Just because it worked before, doesn’t mean it will work now
- Just because it’s supposed to work, doesn’t mean it will
- Just because it works, doesn’t mean it’s fixed; and finally
- Just because it fits, doesn’t mean it’ll work
The bliss of IT architecture is combining technological options with non-technical requirements: is it sustainably manageable, operationable, to whom does it bring -long term- value? The fun of IT architecture is detecting fallacies in thinking -if all conditions work as supposed, it will work- and steering towards rediscovering the goals, outside IT.
And, to put it in Thomas Edison’s words: Just because something doesn’t do what you planned it to do doesn’t mean it’s useless.
This was a successful year for my customers.
I have created new capabilties and prepared some proper strategic support. Metrics for capabilities and support are still hard to define and to use. Those measurements are on the radar for next year.
I have, however, advised, designed and controlled to save structurally more than 1.5 million Euros. This makes a general ROI of 900%.
That is not bad for an architect. That is what I call an executable architect, a true enterprise architect. Or would you prefer to “profitable architect“?
Image origins (unchanged usage):
Invited to a meeting, I accept…. but no agenda, no meeting! Use Subtle Cues to Encourage Better Meetings
Great fun to apply Phil McKinney‘s antibodies corporate antibodies on architecture on the KPN IT architects’ day, 120 participants. Discussing tools to cope with resistance against architecture. Let’s make IT results with IT architecture. With eg Ronald Muijrers, Paul Goyen Sander Visser
Niks ‘outside’, maar juist ‘inside-the-box’ denken: je beperken tot wat er al is leidt vaak tot beter uitvoerbare en goedkopere oplossingen.
Given enough time and money, any competent organization can emulate something that succeeded in the past. But when limited resources take the tried-and-true off the table, the only option is to come up with something new. … and what is the re present situation we’re in now?
Bored by new taxonomies? Unsatisfied with present technologies and financial potential? Don’t change IT architecturing, improve it. don’t change but improve