Gerbrandt van Santen

ICT architectuur, clouds, haiku's en dagelijks leven

Tag: ICT architecture (page 1 of 4)

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.

Become an Anti-Critic

A great article. Flip your (work) script: evaluate and fix forward instead of comfortably leaning backwards after pinpointing the weak points in someone/thing else.  Stop the Negativity: Become an Anti-Critic

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.

Imperfect IT is ok and the best you want: 3 tips

I had worked so hard to create the perfect situation that in the end nobody could enjoy the results. Yes, I have ruined quite a lot of things, relationships and processes. Of course with the best intentions. At work, I see bright and intelligent people trapped in similar battles. Scared to make a decision or in doubt on a solution? Point at the imperfect nature of a someone else’s solution: “this is not a total solution, so go back to the drawing board”.

The Nirvana fallacy: the lie of the perfect solution

Some years ago I called this the Nirvana fallacy. It is simple and widespread in IT way of working: you compare a solution with an ideal and not with an alternative solution. This is great for killing any initiative and keep the status quo. How inconvenient that situation may be: the solution is not perfect so we have to reject it.

A fine variant is “we have to wait for the outcome” of another project, of another meeting. Leaders should be alert and ask for an alternative way of working or an alternative solution. Yet, we run the risk that no one in the meeting is alert. This is quite convenient for the Nirvana player. He/she shows the “real” solution. He/she is quite a colleague because he/she knows what is best for the organization.

Why this fallacy works in any imperfect situation

The moment an application or hardware comes out of the box the imperfection starts. It needs to be combined with other applications, hardware and requirements. There is no manual for that combination. Since our organization is unique -that’s what most members think of their own organization- the combination is unique. And since we want the best for our organization….

Wabi-sabi: beauty within constraints

A fruitful perspective is wabi-sabi. This Japanese and buddhist concept concentrates on the beauty of everything not perfect. Individuality, authenticity and imperfection are important values in this form of art. Hey, those values sound familiar for every unique organization. Yes but, that is art, we cannot compare it to complex IT applications and processes.

Option B: a way out?

In her book Option B Sheryl Sandberg quotes a friend, promising her to deal with deep adversities: “Option A is not available”. He then promised to help her make the most of Option B. We all live some form of Option B.

Yes, but, -always this “yes but”- that is on personal life. We IT geeks work with binary stuff, good and bad, black and white, functioning and not functioning. Well, let us be fair: how many times have we said of our own work “in principle it is ready” or “normally it works”. We are quite forgiving on our own products, processes. Why not give others the same amount of credits? And improve transparently in small steps?

Metrics

A few years ago I had to take over a project and assess the results of the developers. I was fed up with all the “in principle”, “nearly ready”, “90% ready” so I started asking whether the results could be set in production tomorrow. Additionally I requested the following answers: pregnant or not pregnant. All the green lights turned into red lights and program management freaked out. One of my present customers prefers absolute transparancy since it clarifies what needs to be done. His courage lies in transparancy, regardless of the outcomes. His power lies in clearly defined goals. I like to go further. Clearly defined goals are important but measuring the results as well. That’s what I like in Scrum:

  • large scale epics are cut into smaller user stories
  • only some of those smaller stories are realised in upcoming work
  • previously, we had agreed upon the definition of done to assess the results

So imperfect, real curves and corners are ok, the best we want and they give way for improvement:

  1. ask for alternatives when confronted with the Nirvana fallacy
  2. accept the imperfection of your organization, yourself … and your colleagues
  3. create a roadmap with small, clear and measurable results

… Just do it

Some tasks paralyze us. They are big, hairy and audacious. From present innovation culture we can learn the acceptance of failure, learning from failures and failing forward. In my work I present fast to provide others with the opportunity to improve and take ownership of solutions. Just start the discussion forward with the risk of rejection and the opportunity of cooperation.

Happy hunting.

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/

Invited to a meeting, I accept….

Invited to a meeting, I accept…. but no agenda, no meeting!  Use Subtle Cues to Encourage Better Meetings

Older posts