What is it that drives decisions at the exact moment of choice and action? – even in the most mundane, everyday action? If the choice-point itself is a true moment of chaos – a point where literally anything is possible – then what is it that guides us through each of those infinitesimal yet ubiquitous moments?
A lot of this is still tentative, very much ‘a work in progress’. Yet what I’ve found myself returning to again and again over the past few days, whilst working on the design and workflows for the SCAN app, is a pairing of two words: belief, and faith.
[Don’t worry, I’m not going to go all religious on you. (Well, probably not, anyway. 🙂 ) This is still the same enterprise-architecture exploration about the context of SCAN, about sensemaking and decision-making at real-time, particularly in what some would term the ‘Chaotic domain’.
Minor warning, though: this is written in English, and from the perspective of an Anglo culture. I think (believe? guess?) that what follows is close to generic across all human cultures, but note that you may well need to do some translation here, both linguistic and cultural.]
Where SCAN’s ‘Simple’ and ‘Not-simple’ are about about how to describe sensemaking, belief and faith seem more about decision-making – the actual moment of choice that immediately precedes each moment of action. In other words, decision-making in real-time. And because sensemaking, decision-making and action are all intertwined with each other within real-world practice, belief and faith also map onto the SCAN frame in much the same way as for real-time sensemaking.
[There’s also a mapping to the full SCAN, that extends this outward to the scope where there is more time available for review, but I’ll describe that in another post.]
In short, belief maps to the known, the certain, the Simple; whilst faith maps to the unknown, the uncertain, the Not-simple:
— over on the left-side, belief provides a straightforward black-or-white choice: true or false, right versus wrong, culturally ‘proper’ versus ‘politically incorrect’;
— over on the right, choices are more blurry, more uncertain, more ‘shades of grey’ – or more colourful, perhaps – and the only guide we have is faith or trust that what we do is right. (Right in its own way, but still ‘right’ in some sense.)
Both of these are actually about the individual, about ‘I’. Which it should be, of course, because that’s all we have at the exact point of action: our own choice, and our own ‘response-ability’.
Belief is fast, and importantly doesn’t demand any personal skill as such: the whole point is that they’re deemed to be ‘true’ for all who enact them, regardless of who or what enacts them. (A belief may be believed to apply only to self – such as ‘nothing goes right for me’ – but is still held as an ‘absolute truth’ in that sense.) This has both advantages and disadvantages, mainly relating to how well the belief does match up to actual reality. Advantages include:
- simple beliefs are useful when the person enacting them has only a limited level of skill and ‘response-ability’ – “just follow the instructions, kid…”
- even for those with skill, simple beliefs are useful as a structured fallback for whenever the faith falters in the context and in one’s own ability – “when all else fails, follow the instructions”
- advising acceptance that some contexts are constrained by ‘laws’ of some kind – particularly the physical-world constraints implied by ‘scientific law’ and the like
- beliefs are also useful as a disciplined means to temper excess enthusiasm – “trust to Allah, but tie the camel first”
A classic example of a structured belief of that last type is the checklist – mapping out essential safety-checks and other ‘known truths’ prior to or during any activity that is inherently uncertain.
The disadvantages of ‘prepackaged’ belief-structures are more complex, and often rather more subtle:
- the usefulness of beliefs ultimately depends on the myth of ‘control’, the myth of predictability and certainty – none of which may be valid in a real-world context
- beliefs themselves can and do act as perceptual filters, potentially rendering invisible essential contrary information from the context
- as guides for choice and action, beliefs can apply inappropriate constraints to action in any given context – following ‘the letter of the law’ rather than ‘the spirit of the law’
- in much the same way, beliefs can be used to evade difficult or challenging choices – for example, ‘morals’ as ‘the lazy-person’s ethics’
Faith is often the only choice-mechanism available whenever the context is inherently uncertain. It also correlates closely to skill – so much so that, in essence, ‘skill’ is a proxy for the real-world reliability of faith in one’s own ability to work with the inherent uncertainties of a given type of real-world context. In other words, skill is what determines whether we really can do what we believe or hope we can do in that kind of context.
Sometimes, though, it isn’t about skill: it’s just about faith, or trust. Every change of belief requires ‘a leap of faith’; innovation or experimentation always requires us to accept that we don’t know what the outcome will be. (That’s very different from belief, where we do expect the outcome to be what we expect.) A modal-logic of possibility and necessity is the only place where ‘the impossible’ first becomes possible – and thence, through skill, becomes probable, then predictable, and eventually something resembling certain, a kind of ‘law’ in its own right. It may end up as a checklist or some other pre-packaged set of beliefs – but it always starts with faith, in the midst of a moment of inherent uncertainty.
As with belief, there are disadvantages to faith too: not least what we might describe as ‘misplaced faith’, where lack of skill – or plain old lack of awareness – leads to inappropriate outcomes. Whether we like them or not, sometimes the constraints of belief do apply – such as in most (though not all) assertions of ‘scientific law’ and the like.
So in practice we need to be able to bounce back and forth along SCAN’s ‘horizontal’ axis of modality. Sometimes we need to hold to a Simple true/false belief; sometimes we need to let go into the Not-simple world of faith and trust. And of course, recursively, there are no set rules about which one should always apply at any given moment – which means that this too is a skill in itself. It’s Complicated, perhaps, or Complex… yet in real-time action we don’t even have time for either of those. All we have is this decision, right here, right now – no time for anything else. Belief that we know what to do; or faith that the results we need will arise from within the chaos itself.
All of which means that, as enterprise-architects, we need to understand how belief and faith work within our organisation and enterprise, and provide structures to support them in real-world practice.
It’s essential to draw a distinction here between the individual and the organisation. Belief and faith are expressed in practice directly by the individual, or indirectly by proxy, such as via the design or operation of a semi-autonomous machine or IT-system. Yet in an organisational context, it’s the collective belief and faith that we want expressed in action – expressed by the individuals on behalf of the organisation, the collective.
In effect, that’s the key role of organisational culture – and despite the wishes of executives and others, it’s not as simple as it looks… For enterprise-architects, it also means that we often have to address aspects of organisation-architecture that are more usually the territory of HR and change-management and the like – which means that we have to tread carefully at times, and engage in some potentially-challenging negotiations. But the payoff is an enterprise-architecture that really works – for everyone.
The organisation’s beliefs-in-action are expressed in definitive statements such as work-instructions, reporting-relationships and business-rules. One of the architectural concerns here is to provide support such that these business-rules and the like are actually implemented in practice, in real-time decision-making.
To make this work, we in effect need each individual to take up those shared-beliefs as if they are their own personal beliefs. This is especially important wherever these rules must normally be followed ‘to the letter’ – such as in regulatory compliance.
It’s crucial to understand, though, that rules cannot be imposed onto individuals from outside, whether by fiat or threat of force. Although as an organisation we can give ourselves the illusion that this has been done, it rarely works in practice: instead, there will usually be a myriad of small ‘failures’, ranging from unconscious errors to covert rebellion, which effectively sabotage the intended functional impact of the rules. (The former will tend to occur more often in collective-oriented cultures, the latter especially so in individual-oriented cultures.)
What does work is to engage people in the rules – the ‘why’ as much as the ‘how’ and ‘what’. To use the terms from Hagel, Brown and Davison’s The Power of Pull, we create that engagement by shifting from ‘push’ to ‘pull’. In an enterprise-architecture, we do this by treating organisational-beliefs in much the same way as for organisational-values. The Enterprise Canvas model describes a generic structure for this purpose:
- create awareness of the rules-structure, its purpose and rationale, and the context for its use
- build capability to apply the rules-structure in real-time practice
- apply the rules-structure in run-time decisions
- verify and validate the usage of the rules-structure
- derive lessons-learned from the (attempted) usage of the rules-structure
Working with HR, change-management, process-management and others, we create what is in effect a PDCA-type learning-loop, to develop, apply and revise the business-rules and other belief-structures for the organisation.
The faith-in-action side of that decision-making modality-spectrum deals with anything that isn’t covered appropriately by business-rules and the like – which is a large part of most real-world organisational contexts. For enterprise-architecture, the two key focus-areas are skills-development, to enhance individual ‘response-ability’; and vision, values and principles, to enhance consistency in decision-making across the collective.
The skills-issue is one that is almost completely missing from most current-enterprise-architectures, especially those of an IT-centric bent. That’s rapidly becoming a lethally-dangerous oversight – see the Sidewise post ‘Where have all the good skills gone?‘ – and one that we need to address, working in conjunction with HR, organisational-development units and suchlike. EA will come into the picture by mapping out skills-requirements and competency-levels needed within enterprise-capabilities; the actual skills-development would usually be out of scope for EA, of course, though overall much of it would follow that generic structure for values as above.
The values-issue is one I’ve been pushing for a very long time as the true core of the enterprise-architecture: for example, it forms the topmost layer of abstraction in Enterprise Canvas, and thence acts as the anchor for the generic structure described above for values-management services. The reason why it’s important is that if the organisation isn’t clear about its values, then what will be used instead – as the drivers for ‘faith’-type decision-making – will be whatever values happen to be around for that individual. Which could be anything at all. Including not just a destructive ‘me-first’, but a really destructive ‘me-only’. In other words, not a good idea… clarity on values matters.
A lot more that could be said on all of that, but I’d probably best leave that for the moment. The only point that does need to be added here is the importance of story – the enterprise as story, the enterprise is the story – as the ‘glue’ that holds all of this together.
Overall, the real point here is this: that at the point of action – and despite whatever we might plan beforehand – decisions seem to be taken primarily on the basis of belief, or of faith or trust. Which means that, architecturally, we need to design for that fact. Not a trivial point, then.
More on this in another post soon, but any comments so far, anyone?