Gerbrandt van Santen

ICT architectuur, clouds, haiku's en dagelijks leven

Tag: Werken onder Architectuur (page 1 of 2)

Fire your IT architects and go for results

What has your IT architect done today? Did he -mostly male- deliver artefacts? Has he added value or enabled business? Or don’t you know what to do with architects?

Control and support them

Well, just like any other employee or consultant an IT architect must be controlled and supported on deliverables: just ask different questions and persevere on getting a timely answer you understand. Because that is what matters: you as a manager, team lead or business owner should feel comfortable with their output. Your problems should be avoided, solved or put on a roadmap that makes sense and is realistic.

Reason of existence?

The rule is that every organization needs some architects. For what? Is it for

  • perfecting a framework,
  • completing the description of the application landscape,
  • signing off designs,
  • inventing a new language called Archimate, for the innercircle of architects, leaving administrators and managers in despair about meaning and relevance of the output?

Philosophy required?

As the best technical expert an architect is not bothered anymore by business as usual. He is liberated to ponder on future moves. The future may be bright and consistent but the road towards this paradise is somewhat cloudy. Does this require a kind of philosophical endeavor as a solid basis for roadmapping? Intelligent and reasonable usage of philosophical concepts requires an in-depth analysis of alternatives and implications. Preferrably in such a way that people around you understand what you are hinting at. Yet, alternatives and real choices are a rare feature in IT architectures.

Effective Communication?

Communication of the paradise and the roadmap is hard to combine with showing omniscience. Nit-wit, know-it-all without feasable and viable next steps seems the key feature of architects. Look at this discussion (see image below): a multitude of seniors jump from biology, system theory into philosophy of science and psychology. Guess what, it looks like a discussion but it is merely a self-exposure without any result. How else could there more than 800 entries and still growing?

Solution

If someone should be able to solve your IT-problems as a manager and to solve the challenges of your designers and administrators, it should be an IT architect. You require technical insight, evangelism of your business goals as translated into realized IT features, processes and projectplanning, advise, design and support for people who implement and administer IT. Any feature lacking: sack them and get an efficient version.

How to discern whether your new version of the IT architect can assist you in enabling business? Ask different questions and persevere in getting answers you understand, because it is your business. Architecture without realization is a hobby and for sure I am not in the hobby business.

Contact me if you want efficient questions.

Just because it fits, doesn’t mean it’ll work.

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.

900% ROI on hiring an IT Architect is reality

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):

www.flickr.com/photos/stevendepolo/4015294949/

a guide on IT infrastructure

Proud of my contribution to a guide on IT infrastructure: simplify design process by decision trees, services and building blocks

80%

Recently I found a Japanese angle for my 2015 article “Give me an 80% solution, now!” Apparently 80% is better than 100%. The fun in IT architecture is to discover what a 80% versus perfect design is. The reward lies in the adaptation and adoption by readers: they could add their points too, so from now on it is their solution. What will you design today, for just 80%?

beheer is niet sexy

Innovation is sexy, governance mediocre and operations is the Cinderella. In 1969 an artist already set her marks for ‘maintenance as art’ in a manifesto. Why not declaring sustainability and maintenance as quality requirements in each IT-design?

Without execution an idea is a hobby

A great design and now what? Without execution it’s a hobby and we are not in the hobby business. I have created a visual summary of Good Strategy Execution Requires Balancing 4 Tensions

Older posts