Gerbrandt van Santen

ICT architectuur, clouds, haiku's en dagelijks leven

Tag: design (page 1 of 3)

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.

niets aan actualiteit ingeboet

In 2015 deelde ik dit artikel. Het is nog steeds richtinggevend:

Use data visualisations to tell stories and gain influence

 

Stop innovating, try renovating

“Buddhism with wooden shoes…if you really have to”, the Dalai Lama answered. The interview was about 40 years ago in the Netherlands. It still contains value.

The setting? After the flower-power hype more and more Dutch people where getting into Eastern religious ideas and practices. The Dalai Lama was rather curious whether this was not too easy, whether their own religion was really not suitable for their needs and lives.

The question? If Western people could not find peace in their own religion, what would be his advice.

The value? What you have might be better than you thought, saw and felt before. Perhaps look at it with a different perspective, renovate your shoes, your house, your work attitude. New Year’s resolutions are big hairy audacious goals (BHAGs)… we too often fail within only a couple of weeks. Whether in our personal life or in business: a new tool, a new diet, a new task will not make us happy.

Try adjusting and improving what has brought you so far, there is more to you than meets the blinking eye.

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.

I like constraints

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?

Improve, not change

Bored by new taxonomies? Unsatisfied with present technologies and financial potential? Don’t change IT architecturing, improve it. don’t change but improve

Value-adding context

IT architecture is not only about technology but also about putting objects and persons into a value-adding context

Older posts