We put knowledge to work

By combining hard and soft skills and fostering cooperation

  • Full Screen
  • Wide Screen
  • Narrow Screen
  • Increase font size
  • Default font size
  • Decrease font size


Make knowledge do the job

E-mail Print PDF

Games where the throne of the organisation is at stake

What happened in a time span of 30 years during which the values ruling business changed.

In the seventies I learned a corporation has responsibilities towards many stakeholders, society as a whole was one of them, and not the least. In the beginning of the twenty-first century the cry 'greed is good' is shouted over an economic graveyard where trust is the least available asset. Particularly where one would expect it: in the finance industry.

This article treats the bi-polar view on the forces in power of an organisation, the differences, the context within which they appeared, the threats they represent and finally what could be done to reduce the risks involved in each of the approaches.

Last Updated on Friday, 01 August 2014 04:48
E-mail Print PDF

On the value of definitions.

The term definition sounds quite definitive... Is that the reason why so many arguments are exchanged in the process of finding a consensus on a definition? Why otherwise is that process often so emotionally loaded? How much do formulations of definitions cost the organization in time and efforts? What is done with those definitions? Are they mental ankers to climb higher in mental constructs or are they tightening freedom of mind? To evaluate the value of definitions, I made a small experiment and formulated an alternative approach to the single truth, golden record,...

Last Updated on Friday, 01 August 2014 04:47
E-mail Print PDF

On architectures (Enterprise, business, IT, SOA, and solutions)

The first time that an IT professional showed me a plan of IT architecture, he shared a map of a plant on an A0 format (1 square meter). This map showed buildings with their IT infrastructure. This included the location of the servers, which software was running on which server, and even the cable layout. This map of IT architecture helped the poor man find his way around the servers that he had to administer. The plant in question was very big. His physical condition also deserved a lot of respect, because of this huge map roll that he had to carry everywhere he went, to save himself from getting lost. Compared to the Michelin guide you would use in a car, this man’s IT architecture map was hell (European city planning still seems to be popular as a framework for IT architecture).

E-mail Print PDF

The effect of coffee on the outcome of different meeting formats

Symbolism in management and their unexpected impact are fields of study on their own.

Strangely enough I experienced coffee as a symbol a few times in the work environment. To show social involvement, fair trade coffee was distributed in the organization. To show care for the health of the workers, organic coffee was adopted. When the organization wanted to display its cultural involvement the Italian coffees and sophisticated derivatives became available. In many organizations coffee was free of charge for many years. I remember the so called 'coffee ladies', unprecedented in popularity, bringing the liquid gold to the smallest and most remote offices in the buildings. The arrival of those ladies, with their caddies strategically placed, was the signal for the colleagues in the designated perimeter to meet. During those short meetings not only the last gossips were exchanged but also processes were being oiled. Meaning that, where blocked activities got unblocked. Priorities were adapted, again for the benefit of the process in which the meeting parties were involved. No agenda, so no work disturbance was experienced; problems were solved around a cup of coffee. Coffee was the catalyst around which colleagues found creative solutions to blocking situations and all kinds of issues.


Why not to use entity-relationship diagrams to describe semantic assets if OWL-DL ontologies are considered?

E-mail Print PDF

Entity Relationship diagrams get several notations. One of the most popular is the UML notation, then it is called a class diagram.

Abstraction made of the levels of detail which are possible in diagramming; the main reasons for not using entity-relationship models (ERM) are the following:


Page 2 of 4

You are here Home