Yet another perspective on POSIWID and complexity

I recently reflected on Stafford Beer’s concept of POSIWID – “The Purpose Of a System Is What It Does,” explored in Harish Jose‘s insightful article, available here A Constructivist’s View of POSIWID.

While I find substantial agreement with the principles of POSIWID as put in the article, it also reignited a question that I’ve been grappling with that intertwines with my ongoing exploration of complexity theory:

Is complexity primarily rooted in our limited knowledge (epistemic), or is it an inherent characteristic of systems themselves (ontological)?

As I read it, POSIWID seems to favour the epistemic lens over the ontological.

Does constructivism have limits in organisational contexts?

While constructivism posits that the observer defines the system’s purpose, I wonder if this perspective can be both limiting at times yet also essential. When each individual’s perception potentially redefines a system’s purpose, aligning these diverse views towards a unified organisational goal can become a formidable challenge. This multiplicity of perspectives, though innovative, risks operational inertia without a structured framework for integration, something that perhaps becomes more important for organisations that favour more decentralised decision making approaches. However, the capacity to view systems differently seems crucial as it prevents organisational ignorance to weak signals, essential for strategic pivots and ongoing viability.

Navigating purpose and adaptability in systems design

Consider a teacup used as a penholder. This simple reimagination by an individual might highlight the flexibility of POSIWID. Similarly, the repurposing of a luxury ocean liner to a floating hospital during wartime exemplifies POSIWID’s adaptability—shifting from leisure to utilitarian roles under external pressures, not individual whims. These different uses or new purposes for something that was originally designed and produced with a different intent in mind also raises questions about POSIWIDs broader impact on organisational coherence.

If there is no shared understanding or agreement of the boundaries and purposes of our organisational systems, is there not the potential for utter chaos? Granted that the boundaries and purposes also have a temporal aspect to them and are (and should be) subject to change. But right now, would we not need agreement on the basics? Are we designing and producing containers for hot beverages, pen holders, or paperweights or as in the other example, are we building a floating hospital or a luxury ocean liner?

Man-made systems like the ones we have in commercial organisations are clearly designed with some intent (which at a high level is to produce goods and/or services). The boundaries of these systems must be agreed at least enough, with the stakeholders involved to corral a level of coherence in the actions these people take in the pursuit of delivering on that purpose.

Some stakeholders are tasked with the responsibility and granted the authority to ensure that systems achieve their intended purposes. However, it’s not uncommon for these systems to remain static despite significant changes in their operational environment that should prompt revisions and updates. Often, instead of a redesign that realigns with the evolving landscape, organisational systems undergo piecemeal disconnected adjustments, no doubt with good intent but often creating local optimisation at the expense of the whole. This incremental approach can result in a patchwork of functions and features—akin to a Frankenstein’s monster—that no one would intentionally design from scratch if the system’s purpose were kept in focus. Such scenarios underscore the need for a more strategic approach to system design and evolution, ensuring that adaptations are thoughtful and cohesive rather than reactive and disjointed.

There will of course be challenges to this and to address these, the boundaries may need to be adjusted to better deal with these, hence why the boundaries can’t be completely fixed or rigid.

You may of course argue (and I for one often do) that the stated purpose of an organisational system hardly does anything remotely close to what’s on the tin. In fact more often then than, not it’s seemingly doing the complete opposite and system owners/custodians are blind to it (or choose to ignore it). Systems for collaboration and teamwork reinforces silo behaviours and reward systems entrench local optimisation efforts by focusing on individual bonuses.

Whilst Beer may have advocated for a Constructivist view, he also developed the Viable System Model which contains systems with defined purposes for organisational viability. System 2’s purpose is to coordinate the operations of system 1 for example. A school using a timetable to coordinate teachers and classes with its scares resources like rooms and equipment could not work if some teachers saw the timetable as a too limiting and decided to operate outside of it. They would of course be allowed to think this and have views on it, but they would have to accept it as an official coordinating system and work within those boundaries or try and engage in a process of redesigning it make it work better.

It seems to me that while individual interpretations of a system’s purpose can and will vary, not all can dictate its operational use. Someone (group or individual) must be able to have a final say on this, at least to lock something in at a point in time to enable people to converge on an agreed purpose. And maybe it’s time we stop relying on single individuals to do this and embrace the collective wisdom available to us already.

This tension between fluidity and fixity in organisational systems leads us into the internal debate about complexity that I’ve been grappling with. As we navigate these challenging waters, we confront the dual nature of complexity. It is in these scenarios where I wonder if POSIWID, viewed through a purely constructivist lens, always prevails.

Epistemic vs. ontological complexity: A dual perspective

This brings us to the core of my internal debate about the nature of complexity. Viewing complexity as epistemic suggests it arises from a lack of knowledge about a system. This form implies that acquiring more information or increasing capability could reduce the perceived complexity. What one person perceives as complex, another might not, owing to differing levels of knowledge or cognitive capability.

In contrast, viewing complexity as ontological means that it is embedded in the very fabric of the situation, independent of our understanding. Recognising whether the challenges we face are due to unknown variables or the inherent nature of systems can significantly influence our management strategies. I’m here reminded of Boulding’s observation that “few errors are more costly than treating systems that possess a high level of complexity with models and methodologies that lack the appropriate sophistication” which I interpret as speaking to the ontological perspective. And is this not exactly what Cynefin set out to help with, make sense of the situation to hopefully avoid or at least minimise this costly error? Risk management also speak about this in terms of the distinction it makes between epistemic risk and aleatory risk which seems to speak to the same two perspectives being present.

Integrating two systems concepts: The Darkness Principle and The Complementarity Law

There are two other systems concepts that come to mind where I think both an epistemic and ontological lens could be applied, at least in my interpretation of them (happy to stand corrected as always).

The Darkness Principle posits that no system can ever be fully known, aligning traditionally with epistemic complexity, where the complexity arises due to what we do not or cannot know. However, this principle also underscores ontological complexity by suggesting some aspects of systems are inherently unknowable—not merely due to current knowledge gaps but because they are intrinsically beyond complete comprehension.

The Complementarity Law underscores the importance of integrating multiple perspectives to achieve a more comprehensive understanding of a system. It highlights that different viewpoints, stemming from varying levels of knowledge and different worldviews among observers, may reveal truths about the system that are neither entirely independent nor entirely compatible. This synthesis of conflicting or complementary models helps appreciate the inherent complexity of a system, not as a limitation of our understanding but as a fundamental characteristic.

Operationalising systems thinking

To manage these complexities, organisations can employ methods like Critical Systems Heuristics (CSH) and Soft Systems Methodology (SSM) to foster an inclusive dialogue that accounts for both epistemic and ontological dimensions. These are of course not the only ones by any means, just two examples that I picked as they tend to deal with the politics of organisations quite well. By incorporating diverse, often marginalised perspectives, CSH and SSM can helps define clear system boundaries and purposes, integrating different worldviews, to arrive at organisational systems that are both effective and have a positive impact on stakeholders, or at last minimise the potential negative impacts.

Embracing dynamic consensus in complex systems

My ongoing reflection draws me closer to a view that we need to view complexity from both an epistemic AND ontological perspective and that whilst POSIWID can be extremely useful it can also detract unless the organisation has good mechanisms in place to explore, test and either embed or reject the infinite POSIWIDs that exist. This underscores the need for a dynamic consensus approach in organisations, one that embraces the dual nature of complexity.

Bayer is a recent example but it’s interesting to see that they need to face collapse before finding the courage to explore this. It will be intriguing to see how the parts of Bayer may reinvent themselves if they now have increased autonomy to embrace and integrate multiple interpretations of POSIWID across its new decentralised shared ownership structure. Will they be allowed to take it into new directions that better align with the sentiments of the new team and how they decide to interpret and agree on their shared purpose?

BetaCodex Network have several other examples and Corporate Rebels are building up quite the library of progressive organisations embracing new ways to thinking and acting in this space.

Organisations must continuously review and adapt their systems to remain relevant and effective, ensuring these adjustments reflect a comprehensive understanding of complexity that bridges theoretical insights with practical realities. An individual’s viewpoint, through the lens of POSIWID, may be the spark that ignites a critical pivot, but it needs to be embraced organisationally through inclusive methods like Critical Systems Heuristics (CSH) and Soft Systems Methodology (SSM) to have a lasting effect. These approaches foster dialogue that accounts for both the epistemic complexities of diverse perspectives and the ontological complexities inherent in organisational systems.

By investing in decentralised decision-making models that leverage the distributed capabilities within the organisation, companies can better match their internal complexity with the variety present in their external environment. This dynamic consensus approach integrates theoretical principles with a pragmatic understanding of the multi-faceted nature of complexity, enabling sustainable decision-making and strategic coherence in an ever-evolving landscape.

What’s your experience?

The concept of POSIWID—The Purpose Of a System Is What It Does—compels us to reflect on our own organisational roles and the systems we interact with daily. It challenges us to question whether we’re merely accepting systems as they are presented or engaging with them to reveal and even redefine their purpose. As we conclude this exploration, consider how POSIWID has influenced your approach to systems in your workplace. Have you leveraged this concept to gain deeper insights into the systems you’re a part of, or have you noticed instances where the stated purpose diverges from the actual functionality?

Moreover, complexity in our organisational systems can be both a knowledge gap to bridge and an inherent aspect of the systems we navigate. It’s a dual challenge that tests our adaptability and demands a nuanced approach. Think about how you confront complexity in your environment. Do you tackle it by seeking more information and increasing your understanding, or do you accept some of its mystery as a feature of the landscape you operate within? Or perhaps you blend these strategies, recognising that some complexities can be unraveled while others must be managed through insight and experience.

Share your experiences, strategies, and the methodologies that have empowered you to navigate this terrain.

understanding the work part 2

understanding the work part 2

In my last post when I spoke about systems of work, I also made a point that many Managers don’t really understand the system of work that they are accountable for. In this post I want to dig a bit deeper into this topic.

As you move vertically through the management structure of an organisation the work being done is different (or at least it should be). It is important to understand what is different about the work at different levels of management and that it is not just more of the same or more difficult work technically.

Complexity

So what is it that is different, what do we look for to make this distinction? The answer is – (as it usually is…) it depends. It depends on the level of work, as it is both the focus of the work and the complexity of the work that should shift as you move vertically in the organisation. Gillian Stamp from BIOSS developed a helpful framework to distinguish the difference that makes a difference with respect to the work at different levels of management. The product of this thinking is the idea of Work Domains and it builds on Jaques’ idea of  “levels of work” and I think presents it in a better way. Stamp and Elliot did work together for some time at BIOSS so no surprise that they share this view.

domainsincolour

Three Tools of Leadership

Increasing complexity means you as a Manager need a broader set of tools to work with. At lower levels your own behaviour is your main tool to influence the team together with and understanding of team dynamics (i.e. team leadership). Understanding and being aware of how your interpersonal leadership style impacts performance and how your team work together is of course critical at all levels of leadership but a lower levels i.e. supervisor and/or first level team leader the authority and accountability for organisational systems are not there so as leader you can only influence these, not authorise changes to them.

There is a saying that I first came across when working with a global mining company many years ago that had a great impact on me. They used it in the context of safety issues but it is applicable in a broader context:

“The standard you walk past is the standard you accept.”

In other word, your actions or inaction as a leader when unproductive or undesirable behaviours occur within the team sets the tone for what is accepted.

However, as we move up through the hierarchy relying on your interpersonal skills alone is no longer sufficient because you will no longer be able to have a personal relationship with everyone in the organisation.

So what other tools might leaders in more senior positions require?

Systems Leadership suggests that there are three tools; systems, symbols, and behaviour, that successful managers understand and use.

So whilst, role modelling is critical for challenging unproductive behaviours, it is not enough for sustainable change. You also need to align the systems and symbols of the organisation.  Having said that, if you as a leader cannot be bothered to actually live and behave in way that is consistent with what you want staff to do you might as well throw your change initiative in the bin straight away.

When I said earlier that many managers do not understand the system of work they work in or are accountable for this is exactly what I mean. There is lack of understanding of how the system is shaping and driving the behaviour of the people and overall performance. Without a theory for understanding this, changing it becomes a terribly difficult task.

The desire is of course for the authorised systems to be productive. Often they are either not as productive as they could be or they are productive despite of the manifest design. In other words the extant (or real) system is different from the official authorised system, usually became staff develop unauthorised “workarounds” to produce good customer outcomes.

Systems_Matrix_2

For senior executives it is essential to understand how systems work so that they can design appropriate organisations systems to deliver on the purpose of the organisation. Designing the organisation is the role of senior management; a role that I often see being delegated way down in the HR function to someone with no real authority, often lack the capability to do this level of work, and often with no real understanding of organisational design theories or organisational systems.

A helpful theory for understanding the critical functions in an organisation and the relationships between them is Stafford Beer’s work in Management Cybernetics – The Viable System Model. In a previous post there is a video by Javier Livas explaining the Universal Management System, which is the VSM in less complex language. If you want to watch an in-depth video of the VSM by Javier, you can email him to request access details from his YouTube account. I thoroughly recommend doing so it you can find the time to view the full 2 hour video.

In short, the VSM views an organisation as a system that requires five key functions to remain viable (i.e. maintain its existence). The five systems are recursive (or nested in each other like a Russian doll) so every system one is in turn made up by the five key functions:

System 1 – Operations

System 2 – Coordination

System 3 – Management

System 3* – Audit & Monitoring

System 4 – Development

System 5 – Policy

I will not go on in detail about the VSM as many other better writers and thinkers have done a great job of this already, Beer alone wrote at many books on the topic: The Brain of the Firm, The Heart of Enterprise, Diagnosing the System of Organisation to name a few.

I have found the VSM to be an outstanding theory to work with when diagnosing organisations. It provides immense value and insights and I can discuss the insights with clients without getting into the underlying theory in too much detail. The beauty of the VSM in my view is the recursive nature of the model, which means it is applicable for systems at any levels and Managers across an organisation, can all get value from it. It does require some investment in time to get your head around but it is well worth the investment.

Another “theory” I am a big fan of is the Vanguard Method. Its use in service organisations and it has greatly influenced my thinking and my work. Like any method it is not all-encompassing and I have found the mix of The Vanguard Method, Systems Leadership and The Viable System Model to be very powerful and insightful across multiple levels of organisational complexity.

In a service organisation, one of the quickest ways to make value creating more difficult, is to functionalise the work. This is just one of the many issues that emerge when applying tools and ideas that were designed to solve manufacturing issues in a service or knowledge environment. Functionalization of work is based on the assumption that someone with specialist skills will perform a task faster and to a higher quality. Whilst this seems to make sense it fails to account for the flow of the work and is based on Tayloristic view of the workplace.

If you read up on articles or books by John Seddon you will find that he keeps banging on about the damage from the “economies of scale” mentality that permeates most organisations. His point is that they should shift to understanding demand and design the flow of work accordingly. Seddon is trying to shift ingrained mental models of how organisations operate many of which came about due to Taylor’s theory becoming the mainstream one and the ideas of others such as Mary Parker Follett, were less successful at the time. Only now after the failings of the mechanistic view of organisations are we starting to embrace her ideas employee engagement and power with rather than power over. This is not to say that Taylor’s ideas were useless, they did help the industrialisation of the world. We can only guess how different the world of work might have been if Follett’s more humanistic ideas had been the dominant ones.

In the spirit of economies of scale we tend to measure activity (because being busy and high utilisation of our time is important…seemingly regardless of what we are doing) instead of measuring how well we deliver on what matter to the customer, treat all demand the same. John Seddon made life a bit easier by coining the term “failure demand” as he gave word and enhanced meaning to something I had come across many times but just treated as COPQ (cost of poor quality or rework). Its significance as leverage for improvement quickly became evident through Seddon’s work. For me earliest time I can remember identifying this was at a when doing some work to understand the complaints process in a public housing organisation where we came across an unreasonable amount of plumbing issues in relation to the amount of properties owned by the organisation. The practice was to just log the complaints about poor work, no shows and rescheduled visits as new jobs. This hid away the true volume of value work amongst all of the failure demand – i.e. demand created by a failure of doing the right thing for the customer the first time or failing to do it at all.

What Vanguard does really well is providing a method “Check –Plan – Do” for understanding the flow of the primary activities (System 1 in VSM language) at the level of recursion where the customer interaction occurs. For me the gap with the Vanguard method relates to how to embed constructive leadership behaviours and models to support a new way of thinking (and subsequently a new way of working) such as the decision making model and the task assignment model I outlined in a previous post. At higher levels in the organisations the work is more focussed on how all the other systems across multiple recursions are meant to work together to support value creation for customers.

Usually the feedback systems are in terms of hard numbers such as “productivity measures” or process output measures. More often than not, they are looking at the wrong things and provide little if any understanding of the system of work. Activity measures are in place to measure performance with a complete disregard for the inherent variety in demand that comes in and failure demand is treated as value demand.

Understanding demand, understanding variation, understanding the connections and feedback loops in “your” level of recursion (as part of the VSM), understanding the systems, symbols and behaviours that reinforce or contradict the desired culture are all important aspects for Managers to consider when they grapple with the difficult task of “understanding the work”.

It is not easy, it is a complex task but with some good theories and models it becomes less challenging.

Link

making work systems better

link to one of the best books I have come across in a long time – and it’s free! Luc Hoebeke’s Making Work Systems Better. Luc brings together the work of Checkland, Beer and Jaques – three people  whom I admire a lot. Their work have had a profound impact on my understanding of the workings of organisations. Luckily for me Luc is terribly bright and his synthesis provides great insight into the practical application of the work of these three great authors.

Link

Dynamic Governance Summary

The link provides an overview of the consent decision making process used in sociocracy – a different way of thinking about organisational governance, leadership, and structure. It is a fascinating concept and one that I am excited to learn more about. The fact that it is based on cybernetic principles makes all the time spent getting my head around Beer’s work on the Viable System Model even more well spent.