Main article:
https://abaz786.substack.com/p/the-hand-that-thinks
On LinkedIn, Abdul posted/asked
New piece on Substack: The Hand That Thinks – complexity, causality, and the gap nobody manages.
Most critiques of complexity frameworks stop at the critique. This one tries to go further.
The argument in brief:
1) Senge’s famous line – “cause and effect are not closely related in time and space” – is self-defeating. It uses the reductive model to critique the reductive model.
2) Cynefin and Jackson’s SOSM and CSP are genuine advances. But even the most sophisticated pluralism, when organised as a process of methodological selection, leaves one question insufficiently examined: what kind of observer is doing the selecting?
3) Complexity is not a property of situations. It is a relational quantity – it exists between a system and a describing observer. Change the observer and you change the complexity.
4) Almost no methodology makes explicit the distinction between organising models (neurological – VSM, SSM, CSH) and structural models (anatomy and physiology – Enterprise Architecture, Agile, Organisational Design). The gap between them is where most transformation fails.
5) That gap cannot be managed with a one-off consultancy engagement that hands over to a unitary IT delivery. It must be perpetual. That is what the hashtag#ViableOperatingModel is designed to do.
Along the way: Maturana and Varela, Kauffman on Constraint Closure, Beer’s Triple Index, Gell-Mann on complexity as a relational quantity and a pragmatist reframing of what it means to develop as a practitioner.
And a Yorkshire verdict on where we currently find ourselves.
hashtag#EnterpriseArchitecture hashtag#DataMesh
Whilst general feedback is always welcome, I am especially interested in informed reactions to the specific hypotheses:
1) The organising model vs structural model distinction, how it could hold in practice
2) The Hand That Thinks metaphor as a way into the VSM
3) Complexity as a relational quantity and its dual implication for developing both situation and observer
4) The Systemic Performance Surface (not a dashboard) as the instrument that makes perpetual mediation operational
5) Domain-based VSM as a foundation for Data Mesh architecture
I am keen to follow up in individual conversations. This is not about right or wrong, or defending a particular approach. It is about developing understanding together.
I will tag a few people, who I believe are in the know, will push back, add to, or redirect where needed. These are people who live theory in practice and vice versa. If it helps a few others along the way, all the better.