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.


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.


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.


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.

a model for participatory decision making

Decision Making

Let us start with a strong and perhaps bold assertion, based on Richard Barber’s tremendous work on systemic risk management.

“The greatest risk to an organisation is the quality of its decision-making!” 

The standard risk management approach assumes ALL risks can be identified, placed in a matrix, be allocated a pretty colour and by some magical process risks are “managed”.  How many organisations have risk matrices or risk registers where the quality of decision-making is mentioned? I would think only a few. There are a few that I know of, but only because they have worked with Richard and have been made aware of how narrow their view of risk has been.

If the quality of decision-making is the organisations greatest risk, then it is by default the greatest point of leverage for success. So how can an organisation support its leaders in making better decisions? Well for starters, a helpful decision making model will certainly go a long way.

Depending on the domain you are operating in (using the Cynefin framework as reference) there might be multiple plans or approaches  (A, B, or C) that are equally as good. It is the role of the leader to make the decision on which plan to proceed with. I have deliberately used the work leader here, as the Manager might not be the one leading the task. How that plan is developed with the contribution of the team is explained in the decision making model below.

Before I get to the model some assumptions about participative decision-making must be made explicit.  The model is based on the idea that better decisions are made when:

  • We assume that everyone on the team (and others) can add unique insights to the situation.
  • Challenging our assumptions can lead to unique and powerful outcomes and is therefore a valuable contribution.
  • Spending time and effort into really understanding the nature of the problem is critical.
  • Options, ideas and critical issues are explored openly as part of the process.
  • Good use is made of both analysis and intuition.
  • The leader is clear about the final decision and their accountability for it.

SETED  – A participative leadership decision-making model

  • Share Context and Purpose
  • Explore Critical Issues
  • Test Mental Models and Assumptions
  • Explore Options
  • Decide on Option

Share Context and Purpose

Context aims at setting the scene and provide clarity about what brought about the task, linkages to other tasks, and anything that could in any substantive way influence what we are trying to achieve. Depending on the size of the task at hand the context could vary in length and detail. Sometimes there is already shared understanding of the context but it is a good habit to always check this by assuming it is not.

The purpose is the reason for the work – not the work itself. It clarifies why we are we doing this and what do we hope to achieve by doing so?

Effective leadership behaviours at this stage include:

  • Taking the time to brief others properly.
  • Inviting questions and alternate views about the context.  Listening and reflecting.
  • Using dialogue to make sure the purpose makes sense to everyone, in the same way.
  • Avoiding setting filters or limiting exploration.
  • Making sure context and purpose are well understood before moving on to the next stage.

Explore Critical Issues

Critical issues are also known as showstoppers or challenges that unless resolved threatens the purpose.  They are different from constraints, as constraints are already known.  Critical issues are not certain and need be identified so that you can develop actions to address them – contingency planning.

A good way to frame Critical issues is to use the language of “What if…” and “How to…” The reason for this is to depersonalise the issue raised and to objectively analyse it. It is really good practice to develop the skills to identify critical issues as it can push the thinking to a higher level.  It may take a few iterations before you reach clarity of an issue.

Identifying and understanding critical issues a step that differentiates this particular model from many others. It is also the most difficult step to do well.  Part of the problem is that people want to move quickly to solution (ready-fire-aim) and become frustrated when asked to continue exploring critical issues.

This jump to action mentality is often very destructive and can create unintended consequences that due to the delay (see fixes that fail system archetype) are not connected and the hero fire-fighter can come save the day and get promoted even though they might have caused it. Unfortunately for the careful planner, diligent in planning for critical issues and with few or no fires, the reward is little, or no recognition.

Effective leadership at this stage behaviours include:

  • Staying in the “critical issues” stage until certain that there are no more to identify (at this point in time). Remaining disciplined, strong – avoid moving to solution too early.
  • Exploring views, inviting different thinking, challenging assumptions.  Listening, reflecting.
  • Seeking analysis, maverick views, and independent opinions – anything that might open new possibilities.
  • Matching the effort to the complexity and value of the challenge.
  • Ensure that critical issues and associated ideas are documented.

Test Mental Models and Assumptions

Mental models are “rules” we unconsciously apply to make it easy to make rapid decisions in familiar situations.

Assumptions are beliefs we apply without testing.

Effective leadership behaviours at this stage include:

  • Accepting that everyone has limiting mental models and make untested assumptions.
  • Valuing and exploring the perceptions and ideas of others even when they seem to be a ‘misfit’ to what we believe is possible.
  • Explicitly acknowledging and discussing assumptions and mental models and use conversation to try to generate new insights.
  • Reviewing the impact of identified assumptions on critical issues, context and purpose.
  • Actively listening to what everyone is saying and encouraging different views.

Michael Stange, a fellow Sydney Lean Coffee member  mentioned how he had his team view their assumptions from a different perspective. They had all written down the things they took for granted for a specific project. They were then asked to negate all those assumptions to see if that brought about any new critical issues. This could be a simple yet powerful method to get the ball rolling.


Image courtesy of Gaping Void

There is a possibility that this stage can identify that you are trying to address the wrong issue. This is of course a very powerful insight but often this stage is not even in the back of minds of people.

Edward de Bono’s Six Thinking Hats is another process used to generate deeper insights and better decisions.


Explore Options

By Options here I refer to the possible approaches or parts of approaches to dealing with the critical issues and the activities that need to be completed to deliver on the task.

Effective leadership behaviours at this stage include:

  • Getting organised to capture ideas, possibilities, and options
  • Listening to and exploring ideas
  • Probing the views, concerns and ideas of all stakeholders
  • Building an overall approach, strategy or theme and testing it with others
  • Critical review, testing and challenging even of obvious options
  • Continually bringing people back to solving the critical issues
  • Reflecting on and adapting the purpose and critical issues, as new insights come to light


Decide on Option

With multiple options or pathways available someone has to make a decision on which option to proceed with. Obviously my view is that the person accountable makes this call and in doing so accepts to be held to account for judgments and behaviours exercised when delivering on the task.

The decision making model is a tool that both leader and team member can refer back to if either is concerned the team is getting off track. Furthermore, not all decisions require participation and input from the team. The leader has to exercise judgement depending on the specific circumstances surrounding the decision.

Before I move on to a Task Assignment model, let me be very clear. The model above does not assume that the leader or Manager makes ALL decisions, far from it in fact, what is can do is support a social process of decision making. It is aligned with a view of organisations that believes that decisions in general should be made at the lowest possible level.

The decision making model is linked to the Task Assignment model as the options or plan will contain tasks that need to be clarified and assigned. When a task has been assigned (and accepted) a decision has to be made on how to deliver on the task.


Systems Leadership Theory consider this the work, i.e. working out the how and work is subsequently defined as “turning intention into reality”.

As this post ended up being longer than anticipated, I will continue with the Task Assignment Model and work as a social process in the next post.

foundations of good managerial leadership

Over the last year I have with a colleague of mine (Richard Barber), been working on a framework for leadership development built on a strong theoretical base but practical in its application. In this post I will outline the elements of the framework and in subsequent posts I will discuss the parts and how they fit together. The individual parts draw from a number of great organisational thinkers across different disciplines and together I think they provide a great practical guide for leaders at any level. I will try and provide links to the original material to the extent possible and maintain a high standard of referencing.

Some of the material come from a guide a wrote for a client a while back as part of a project designed to build operational leadership capability but as per usual, my thinking has evolved since then and I thought blogging would be a good way to my own thinking fresh. Hopefully these posts will serve a dual purpose; firstly to support my own thinking and development, and secondly, should anyone else happen to stumble upon it and see some value in it well then that fantastic. I would be delighted if you would comment on anything that you think is incorrect or unclear in anyway.

The topics I intend to cover are:

Managerial Leadership

  • Leadership AND Management
  • Decision making
  • Task assignment
  • Performance conversations

Understanding the work

  • Enhancing system performance
  • Enhancing people performance

Leading change

  • Issues with common change management methods
  • Systemic change


  • Understanding the domain (Cynefin)
  • Sensitive risks