representing trust

I have been interested in the notion of trust for some time now, as it seems to me to evade explicit characterisation being partially embedded in the social infrastructure of culture and expectations, and only superficially in what is accessible to observation.

There are some phenomenon which it makes sense to explicitly represent as concrete data in a system. Details of persons and of business transactions for example, which correspond to items and facts in the real world, to put it somewhat niavely. They are if you like representable in the indicative mood  (descriptions of what is actual ) , but there are other highly significant, more phenomenonolgical ‘facts’ about situations that cannot be adequately dealt with so concretely. Trust is an example of such a phenomenon which may indicate its presence through the absence of other concrete elements so that the difference between cautious low trust environment for example and more casual, high trust environment might be characterised by the magnitude size of the information flows relative to the rationality of the process itself.

It is said that in rural towns where ’everyone knows everyone else’ it is not unusual for residents to leave their doors unlocked, or to engage in business transactions by word of mouth on the understanding that both parties will act appropriately purely on the grounds of an unspoken commitment to a common social bond of community. In these cases, the necessary precautions that would otherwise be taken when trust is low, are as it were ‘stored’ in the social and cultural field surrounding the participants so that both parties know that certain behaviour is unacceptable. The amount of information that the parties need to exchange in such a context may be very low indeed, because both participants share a background knowledge that does not need to be made explicit in each transaction, but which nevertheless co-determines the behaviour and expectations of both parties and of the extended community at large.

It is not easy to manufacture such a situation, as something like trust must be built up over time, through repeated sucessful interactions that are mutually beneficial. It is likely also that an outsider, looking in on such interactions and observing only the concrete content of the exchange, might miss the essence of the situation entirely. And it is unlikely that either party would be able to make the grounds of their interaction explicit or explain why it is reasonable to forgo specific precautions; or why they failed to mitigate specfic risks associated with the interaction. Trust is, as it were indivisible, and manifests itself in the very casualness and familiarity that troubled the outsider in the first place. So trust is perhaps a social and sometimes communal virtue, akin to friendship and loyalty, strengthened when exercised, threatened when neglected, evasive, valuable and resistent to explicit interrogation. And trust is pervasive, in that every community, whether it is a workplace, a sporting club, a family, or a market place will be grounded in a shared value system, unwritten rules of engagement and so on. Every interaction will be like the proverbial ice berg with the bulk of its mass below the surface of the water, and perhaps even below the awareness of the participants themselves.

This being the case, attempts to  ’reengineer’ the business processes through BPM for example or to automate aspects of the workplace, such as B2B initiatives, would have to find some way of making explicit everything that is ’below the ice’ and in such a way that trust-based features of the situation are not destroyed. They must effectively extract the background understanding from the socio-cultural field, and install it as an explicit component of some technical system. In so doing though, the dynamic that ensured that trust was re-inforced through being exercised is lost and the system must now enforce what has become policies and ‘business rules’ and these grow according to a different dynamic – one driven be the demands of efficiency, transparency, the need for risk mitigation, and so on. Perhaps this is simply a byproduct of the rationalisation of society, as discussed by Max Weber, but the phenomenon of trust is i believe actually a formal structure, which is significantly threatened by various re-engineering endevours, which might even including the whole enterprise architecture approach itself.

I am looking for a way to analyse the phenomenon of trust along similar lines to the way that Michel Foucault analysed power and knowledge, in ’Discipline and Punish’ as pervasive and indirect structures of expertise and practice. Heidegger’s notion of the referential totality of background understanding from ‘Being and Time’ also seems relevant, as loss of trust manifests itself as a break in community or disruption in everyday goings-on. Enterprise architecture is essentially a making-explicit, and involves bringing language to bear on conceptual structures such that what is thought can be made public and intelligible and eventually real. But where trust is found in concrete situations, it has been achieved through a process of repeated sucessful trustings and re-trustings that cannot be adequately expressed in a service agreement. Indeed, the very notion of contracts and agreements are perhaps manifestations of the loss of trust that i am alluding to and are themselves attempts to substitute something explicit and public for something more ephemoral and personal. Trust is perhaps an essentially communal asset grounded in the shared world of individual persons, and passed on through institutions, and where business re-engineering attempts to re-organise such relationships, can erect a replica, but the spirit of the original has already disolved into the atmosphere…. here endeth this rant.

a vector approach to enterprise architecture – part one

These ideas grew slowly out of a prolonged interest in cognitive science, ontology and phenomenology in particular. I will be more specific in later posts, but at present, i am resisting the temptation to turn this rudimentary idea into a monumental tome and while i believe that the concept and indeed the whole approach will prove fruitful in the end, i have decided to respect the blog form of publishing, and render my thoughts on such matters in small bite size pieces, that can be talked about and criticised by those who share my interest in exploring new approaches to Enterprise Architecture. The occasion for starting to write is a great conversation with my old friend Tom Graves in London almost two months ago now. Tom encouraged me to begin putting some of these ideas down, and although it has been a while, i hope that there may be enough material here to rouse some initial discussion, especially amongst those for whole the initial idea held some interest.

I first encountered the notion of a vector in physics back in high school, where they were presented as mathematical construct formed from more than one irreducible component, as opposed to scalars which were just ordinary numbers. Although the familiar arithmetic operations of addition and multiplication need to be redefined slightly, it still makes sense to talk of adding them together. The most familar vectors, have only two components, represented by a magnitude indicating a size and an angle indicating a direction in some co-ordinate system, bound together as a single unit. I remember diagrams of balls flying through the air, and cars banging into each other, and it is still easy to think of them simply as being little arrows of different lengths each pointing in different directions. Adding them means joining them head to tail in the specified order and seeing where you finish up, take four steps north, then two steps south east, then six steps west… and so on. this would be the same as going approximately three and a half steps west in the first place.

 basicvectors

This is a very simplifed way of introducing the notion but it captures the salient features.

Now as vectors include the notion of direction and distance, they imply a spatial structure which can be representing as sets of independent dimensions forming a co-ordinate systems - longitude and lattitude on a map, or the vertical and horizontal axes on a graph are familar examples. Points in such spaces, take a value from each dimension in the co-ordinate system, and vectors in the same space can be calculated if two such points are provided. Alternatively, given a starting point, and a vector, a second target point can be calculated. 

 Now in enterprise architecture terms, one could imagine the two points A and B denoting the traditional AS-IS and a TO-BE architectures respectively, with the resultant vector Z traversing all the intervening states yielding the traditional architectural paradigm. Alternatively, a single point A and the specific vector Z could denote the AS-IS architecture, and a specific transitioning action, taking the system to point B. The vector itself in this case denotes an effect arising from a characteristic action and the collections of such vectors constitutes a sort of tool box of transformational strategies, an integrated set of actions that together yield a collective effect. The point at the origin, O could be thought of as a sort of reference model RM, providing the necesary calibration for the dimensions in question. The meaning of such models and  transformations however, will depend on the specific dimensions chosen to define the space itself, but actions, dispositions, forces, tendencies, and general dynamic factors can all be denoted in this fashion alongside the more static representations. Although it is natural to think of the vector on the two dimensional surface as  being denoted by <x,y>, it will be more useful to decompose this further and to consider the image of this vector in each of the co-ordinate axes. This yields two simpler vectors, Zx denoted by <x,0> which has no Y component. and Zy denoted by <0,y> which as no X component. 

These can be considered magnitudes defined on the specific dimensional axes themselves. By assigning meanings to the graduations of the dimensions axes, we can effectively compose meaningful semantic units corresponding to both states and actions, dispositions and effects. And the diagrams above use vectors defined in only two dimensions, using letters as the labels for the dimensions as well as the names of the points and vectors, but this is not very meaningful and merely illustrates this perspective in formal terms. We could define spaces of higher dimensions and so have vectors of the form < a , b , c , d , e > with 5 characteristic vectors < a , 0 , 0, 0, 0 > , < 0 , b , 0 , 0, 0> … and so on each associated with a specific dimension..

The key to using such a representational framework is choosing a set of dimensions that will yield a vector definition that is both intuitive and defendable. Defining the dimensions of the space however, only determines the form of any point or vector in the space. Each dimension in the space must be assigned a metric, so that each point in the space can be denoted by a unique address. I mentioned in the twitter exchanges over a month ago now, that much of the grounding for this approach comes from an application of concepts from Gardenfors Conceptual spaces where, for example, perceptual graduations in such sensory registers as taste and colour perception are used to construct abstract spaces. Specific taste sensations being denoted by a point in the Taste-space defined by the dimensions of  < sweet,salty,sour,?> Our whole conceptual / perceptual apparatus is a system of such interlocking dimensions, and i believe that applying an analogous mode of reasoning to the domain of Enterprise Architecture would yield a powerful mechanism for mobilising, applying and monitoring the wealth of EA resources.

A multi-faceted and complex enterprise would manifest a virtually unbounded set of possible dimensions, so several abstracted representations would need to be produced based on connected and interlocking subsets of dimensions. Choosing the first subset of relevant dimensions constitutes developing what i call the primary abstraction of the enterprise. Partitioning this subset into smaller sets of connected dimensions should yield coherent and motivated viewpoints that together would ground an intelligible and parsimonious suite of representations. These subsets of dimensions would form the basis for specific perspectives on the enterprise, and might define specific model types. Once the space is defined, both static and dynamic characteristics of the enterprise can be denoted, and on the same model. The primary abstraction produces the underlying metamodel for the architectural pespective as a whole. The subsequent partitioning of this set, yields the metamodel for specific views and defines a space on which both state and transformation can be represented.

While i could rant on, i feel that it is enough for starters. I believe though that i have probably not yet risen to the challenge of making this notion accessible to the layman, but i hope to find the right level of presentation eventually.

starting to configure wordpress

i have downloaded a number of plugins and have started experimenting with them on the pages of the blog, bust still in draft form.

I have not started blogging seriously yet, but have a number of drafts in play. this will replace my diary, to some extent and the new format will take a little getting use to, but i am looking forward to the new approach. it requires that one be a little more articulate and ultimately, the fragmentary nature of my diaries will become a more coherent and intelligible rant.

Mysite

20110725-104126.jpg

This is the first post in what will hopefully be a long sucession of posts on interesting topics especially enterprise architecture and the application of insights from various branches of philosophy.

I am also interested in the visual presentation of information and have a number of ( what i think are…) useful approaches to presenting data models which i am looking forward to describing to you.
The site as it stands is a bit bare, and i will be populating the various pages with material and tarting them up as best i can. I am using wordpress, which is just the most wonderful program, and seems to make this whole exercise quite painless.
So bare with me for a little while, i’ll try and get the site moving as soonas possible.