Organizations struggle with their own #data landscapes, because often they are framed to be only a tech (IT) problem.

But data processes are deeply intertwined with organizational aspects like shared understanding & effective functioning or power & diverging interests.
(1/5)

Data centric objects, like APIs, models, DBs & files serve as coordination points to synchronize different parts of the organizations on multiple levels.
Each part has a different focus and a different perspective (THEIR knowledge). Each of them changes at another speed.
(2/5)

The CSCW community calls such coordination points "boundary objects". They need to be adapted whenever one side changes their mental model.

The amount of change required depends strongly on the flexibility of the boundary object.
(3/5)

The more variation, both in precision of meaning & in complexity of structure is available, the better a boundary object adapts when processes evolve.

THIS is a key reason, why data vocabularies make enterprise data processes more agile, flexible & resilient.
#LinkedData
(4/5)

Diverging interests play an important role during modeling. The people and parties involved need to be aware that this process can not be reduced to domain knowledge and modeling skills, but is effectively a negotiation exercise balancing different interests.
(5/5)

Here is a continuation of this thread https://twitter.com/linked_do/status/1262693233643192320?s=20