Sensemaking and the flocking of Boyds
It began with an octopus; wandered into an accidental remark about “a flocking of Boyds”; and then drifted off somewhat sideways from there. But seems that this crabwise shuffle may be leading somewhere useful – for my current explorations of sensemaking and the like, at any rate.
The octopus bit was fairly straightforward, but hit like a bombshell. I’m currently reading Peter Godfrey-Smith’s ‘Other Minds: The octopus and the evolution of intelligent life‘, in which there’s a section in Chapter 2 where he’s talking about the evolution of cellular-level communication-mechanisms, leading to the development of the nervous-system. He points out that whilst most of the current scientific and other attention is still focussed on the action / sense / feedback loop of sensorimotor tasks, there’s another whole under-researched aspect of action-shaping tasks – the tasks to coordinate the action across the system as a whole.
What I’m beginning to suspect is that there’s a third set of mechanisms at play that don’t yet seem to have been addressed much at all – about how intelligent entities drive their learning tasks, at both an individual and collective level. I’ll come back to that in a moment: I need to set some groundwork first.
Even that first distinction between sensorimotor versus action-shaping was a significant bombshell for me. The reason why is that, in my own work, the sensorimotor part is described well in the ‘Sense / Make-sense / Decide / Act’ [SMDA] loop that crosslinks well with the SCAN frame:
That does describe well the kind of feedforward/feedback-loop mechanisms for sensorimotor tasks, that apply at the individual level. But where are the equivalent mechanisms for the action-shaping tasks – for coordination between entities? Thinking fractally, it’s clear there’s a sort-of equivalent of the SMDA loop at each level of collective action – but no description there of how the coordination to make those collective SMDA-loops actually happen, at any level. I have to admit it: right now that would seem to be a gaping hole in that model of mine.
Or maybe not. This is where that note about “a flocking of Boyds” comes into the picture. It was in a comment by Paul Beckford to an old post of mine, ‘More on principles and decision-time‘, from way back in January 2012. And even then it was actually an accidental pun: as he says in a later comment there, what he’d actually meant was “a flocking of boids”. Yet in practice both of those two terms are valid here: boid, as in a simple entity used in modelling of flocking or swarming behaviours; and Boyd, as the military theorist John Boyd – probably best known for the Observe / Orient / Decide / Act [OODA] model of sensemaking and decision-making, used particularly to describe contexts of real-time complexity.
In that SCAN / SMDA diagram above, boids would sit over on the left-hand side of the space, with real-time decision-making in the Simple domain. The boids each follow simple rules, such as separation, a rule to steer to avoid crowding local flockmates; alignment, a rule to steer towards the average heading of local flockmates; and cohesion, a rule to steer to move toward the average position, or centre of mass, of local flockmates.
This does explain basic flocking – a means to guide the inter-entity relationships within collective movement. Yet it doesn’t explain what drives the overall movement – such as in murmuration, where there is no distinct leader, yet still the evident presence of some kind of direction and purpose. Neither does it explain dynamic-leadership, such as in flight-patterns of geese, in which the V-pattern probably does arises from simple boid-like rules, but not the rotation of leadership as the leader of the migration tires and rotates back to a less strenuous position. Nor how, given that rotation of leadership, the group as a whole know how to navigate to a destination literally thousands of miles away, adjusting for weather and other hazards all the way along the journey.
A flocking of metaphoric Boyds would allow more complex sensemaking and decision-making, as per OODA:
On a SCAN frame, we would map all of that complexity more over to the right-hand side of the SCAN frame, as earlier above. We could also crossmap this to SCAN in terms of the frame’s edge-transitions:
(This graphic above is also crossmapped to the ‘swamp-metaphor’ roles: Artist, Technologist, Scientist, Believer. For more on that, see the posts ‘Sensemaking and the swamp-metaphor‘ and ‘Sensemaking – modes and disciplines‘.)
But on its own, even this doesn’t explain the process of collective decision-making and action. Boyd’s model describes what is primarily a solo dance – often in relationship and interaction with others, yes, yet still still essentially about the individual, not the collective as a whole. And whilst there is often no apparent ‘the Leader’, as in the grand hierarchies of Taylorism and the like, it’s clear there is leadership of some kind across the collective – yet Boyd’s model itself doesn’t really describe what that is.
So with a flocking of boids, we’d have relationship, but no real sense of direction, other than reactive at best. And with a flocking of Boyds, we could have a more proactive sensemaking and decision-making, yet little more than a ‘leadership’ of undirected anarchists – decision, yes, yet no apparent mechanism for shared decision-making or direction.
In short, neither boids or Boyds would seem to provide us with a way to understand how collective-action actually works – nor, perhaps more important, to make it work better.
Sure, there’s at least one well-known model of ‘complexity’ that might claim to provide an all-encompassing explanation for this. (I’d best not name names here, but long-term readers of this blog will know which model I mean.) But whilst that model does seem to work well enough for the collective level, it falls over in a chaotic heap as soon as it touches that crucial question of leadership – particularly the relationship between the individual and the collective, of the Not-known of uniqueness that ultimately underlies the complex Ambiguous choices made by the collective as a whole. It’s true that that model can describe a form of ‘push-marketing’ pseudo-leadership, a Cambridge-Analytica style of micro-targeting and suchlike to manipulate the individual to follow the predefined desires of a self-selected collective; but not the other way round, the literal ‘outleading’ from the individual to and into the collective, in the sense of the quote often attributed to Margaret Mead:
Never doubt that a small group of thoughtful, committed citizens can change the world. Indeed, it is the only thing that ever has.
Perhaps the only model I’ve found that does help in this is Stafford Beer’s Viable System Model [VSM]:
…which in that form is, yeah, not easy to read – and can also, all too easily, be misunderstood as a simple hierarchy, which it isn’t. Visually at least, we can simplify it down somewhat to this:
From a service-oriented perspective – describing relations between entities in terms of services – it may be useful to reframe this in the form shown by the Enterprise Canvas model, which is consistent for all types of services at every level, every scope, every scale:
In this diagram, the dotted-line box around the central cluster of subsidiary-services, and the small circle just above it, represent the ‘system-1’ of Viable System Model – the ‘service-in-focus’ that does the ‘Decide’ and ‘Act’ parts of the Boyd model. There are then all manner of service-interfaces to other services that inform the ‘Observe’ (sensing) and ‘Orient’ (sensemaking) parts of the Boyd model, represented in Enterprise Canvas by the arrowed-lines for flows of information and other exchanges, and by the ‘guidance-services’ – Direction-services, Coordination-services, and Validation-services. All of these guidance-services feed into the equivalent of the ‘Orient’ phase in Boyd’s model.
The Direction-services (or ‘Management-services’, in older versions of Enterprise Canvas, as in the diagrams below) are shown in Enterprise Canvas by the square-symbol above the connecting-circle for the ‘service-in-focus’. These are the equivalents of ‘system-3’ (direction, run-time management), ‘system-4’ (strategy, ‘future-outward’) and ‘system-5’ (purpose, identity) in Viable System Model:
The ‘Direction’ (‘system-3’) part provides the simple run-time rules that ‘a flocking of boids’ would require. These are influenced in turn by the strategy and policy parts, which support some of the more complexity-capable sensemaking in ‘a flocking of Boyds’.
All of this, as per Viable System Model, threads through a nested hierarchy or meshwork of services, in recursive or fractal fashion:
Put together, the connections to the outside world (OODA ‘Sense’), and between ‘system-1’ (OODA ‘Act’) and the recursive mesh of direction-services (as a simplified version of OODA ‘Orient’ and ‘Decide’), are perhaps enough to describe how sensorimotor tasks might work. Yet there’s nowhere near enough there to describe the mechanisms and links needed for action-shaping tasks or learning-tasks. Which is where those other two clusters of services in Enterprise Canvas – Coordination and Validation – come into the picture.
The Coordination-services support coordination between services – which in turn enable action-shaping tasks. In Enterprise Canvas, these are represented by an upward-facing triangle, and are a somewhat-expanded version of the VSM ‘system-2’ – the difference being that in Enterprise Canvas we draw distinctions in the ways in which coordination-services link between the equivalents of VSM’s ‘system-1’ (service-in-focus), ‘system-3’ (direction / management), ‘system-4’ (‘strategy’) and ‘system-5’ (policy / identity):
Again, these are fully recursive or fractal, weaving through the overall meshwork (‘horizontal’ connections) and hierarchies (‘vertical’ connections) of services.
To crossmap to OODA, the Coordination-services represent much of what happens across the ‘feedforward’, ‘feedback’ and ‘implicit guidance and control’ flows shown in the OODA diagram. Unlike in OODA, though, these are not solely internal to the service-in-focus, but also coordinate between this and other services, to enable action-shaping across the collective whole.
(Note that somewhat between the Coordination-services above and Validation-services below are what Stafford Beer describes as ‘algedonic links‘ – literally ‘pleasure / pain’ messaging that can connect anywhere-to-anywhere, bypassing the normal hierarchical and other more structured connected. For more on that, see the post ‘Pervasives and the VSM algedonic link‘.)
The Validation-services support how strategy and values pervade throughout all services – in effect feeding into the equivalents of the ‘Cultural Traditions’, ‘Genetic Heritage’ and (aspects of) the ‘Analyses & Syntheses’ elements within the OODA ‘Orient’ processes. As with the Coordination services, this supports collective action-shaping tasks, though the mechanisms are much slower – analogous with the limbic-system, rather than the faster nervous-system, within an animal body.
In Enterprise Canvas, these support-services are represented by a downward-facing triangle, and are a much-expanded version of VSM’s ‘system-3*’ – the latter covering only a tiny subset of the tasks for values-management, namely random-audit to confirm that service-actions remain on-track to overall intent. As with the Coordination-services, Validation-services interact in different ways with the respective Direction-services:
There are also distinct sets of services for each of the core values or concerns that apply to the broader collective: for example, for a commercial business, there would need to be distinct sets of Validation-services for security, health-and-safety, financial-probity, business-ethics, product-quality, environment and so on, along with industry-standards and regulatory-compliance – in short, any concern that is everyone’s responsibility.
In turn, we can split each of these sets into subsidiary services for distinct sub-tasks, applied to each service-in-focus within the respective scope:
- develop awareness of the importance of that concern to the collective-as-a-whole
- develop capability to enact the respective responsibilities
- where appropriate, oversee or guide run-time actions to enact that responsibility
- after action, support continuous-learning to improve skills, experience and competence in that responsibility
That last subset of activities are what support learning-tasks, for the individual, and, in combination with the Coordination-services, for the broader collective.
It’s important to note, though, that these three groups of support-services – the Direction-services, Coordination-services and Validation-services – are largely separate and distinct, following separate pathways and often using distinctly-different mechanisms. In effect, it’s useful to think of them as orthogonal to each other, in the ways in which they impact on and connect with any given service-in-focus:
The catch is that Taylorism and other ‘classical’ models of organisation barely recognise these distinctions at all, and either all-but-ignore the Coordination and Validation services:
Or, worse, try to subsume those two groups into a crudely-oversimplified concept of ‘management-services’, leading to a form of service-organisation that is literally back-to-front and upside-down from what actually works:
Which is definitely Not A Good Idea…
If all too common.
Anyway, all of the argument above is not complete, by any means – for it to be so, there’d need to be a lot more work done on this, much of it by people a lot better than me. But I think it does give a useful way to start thinking more about:
- the mechanisms and pathways that describe how sensorimotor-, action-shaping and learning-tasks all work, both for the individual and collective levels
- how sensemaking and decision-making actually work in practice, both at the individual and collective levels
- how Boyd’s OODA model can extend outward to the collective – ‘a flocking of Boyds’
- a stronger integration between Boyd’s OODA, Beer’s VSM, and similar models such as my own SMDA model, and with service-oriented models such as Enterprise Canvas
Worth exploring further, I’d hope? Over to you for comments and suchlike, anyway.