The agile worker

The agile worker exists only because there are discrepancies between theory and reality
February 01, 2013

An important part of agile work is learning. Agile workers are knowledge workers who bring their mental models in contact with reality. The agile worker does only exist because discrepancies exist between theory and reality and because insights can be gained through these discrepancies. If the theory is not questioned by reality, if whether model nor reality play a role, then there is no learning. Then work does not require the quest for suitable solutions and work can be done by following instructions.

Authority

The agile worker is searching for insights. If insights should have a meaning, they lead to decisions. This is a further characteristic of the agile worker: she makes decisions.

The agile worker is acting best inside of a system where decisions will be taken at the level with deepest insights and not necessarily at the level with the most formal power.

Do not move information to authority. Move authority to where the information lives. [Marquet 2012:49]

Such kind af authority is a central part of the leadership process in agile organizations. It means also the ability to take risks, to change the organization and to develop. This is not primarily to reduce the work of managers but to come to best possible decisions [Appelo 2011:114].

Self-organization

Now self-organization, in dissociation to centralized control, comes into play. Jurgen Appelo very clearly shows that the most things in this world come along without a central controlling instance [Appelo 2011:99]. The functioning of life is self-organized. The origin of species, of the world, went well without management and will go ahead even without management. With that background we have to realize that masterminded, centrally controlled large organizations are the exception and not the normal case. The thought is valuable, that self-organization of teams, which is of such importance in agile procedures, is the default behavior.

Constraints

In any complex system, in small companies and in large corporations, self-organization takes place and the constraints of the system give the direction for the self-organization.

To give self-organizational forces a direction by setting constraints is the major task for leaders of agile organizations

Purpose

Of course, all human-created organizations have a purpose, a goal. The decisions, the actions and the results that any organization delivers must be aligned with that purpose. Therefore self-organizational forces need have a direction.

One example: In road traffic the established rules allow any road user to travel fast, save and to arrive at the desired destination. In the Netherlands roundabouts are a common way to organize traffic flow. In Germany instead traffic lights are being used to achieve the same result. We all have made the experience to wait in front of a red traffic light at an empty crossing. In a roundabout nobody is waiting if there is no traffic. Decentralized self-organization of road users is required and has a direction, because traffic rules are in place. On the other hand traffic lights correspond to a central controlling model with high controlling costs, where self-organization is largely inhibited and occasionally delays.

If a manager intervenes a current Sprint in a Scrum organization, the Scrum Team will start to behave like the driver at the red traffic light, which means waiting for signals - and not like a road user in a roundabout, which means autonomous searching a way.

What and how

It can not easily be answered how to give self-organizational forces a direction. But one important aspect is to set the right constraints. Leaders should talk more “what” and less “how”.
Identify the “what” that has a value and make it absolute clear!

Talk more “what” and less “how”

Decisions

The self-organizing team often makes decisions in a discourse. Possible solution spaces are being explored and divergent opinions have to be endured because best solutions can arise by affirming heterogenous perspectives about a topic. The decision does not need to be taken in a democratic way. We all deserve the same respect but in a specific context we are not all equal. Someone has more or less knowledge in the specific area of interest, is more or less experienced, can provide more or less orientation for the team to cope with the task. If really results have to be delivered and the team is committed to produce results, often a natural order of authority emerges which determines who has to or is allowed to speak the final word about a specific decision. A precondition for this is the collaboration oriented and committed attitude of the team. This attitude requires the individual to share the consequences of a decision even if one has a different opinion. This requires to put the operating needs of the team above the individual preferences.

To be against a decision is not the same as accepting and sharing a decision. In the first case the team has to go through a clarifying conflict. Artificial harmony does not help to go further. Are all facts on the table? Assistance for team oriented decisions can be found at the “Facilitator´s Guide to Participatory Decision-Making” by Sam Kaner [Kaner 2007].

Roles and professions

The weighed and reasoned decision can also be taken by a finally responsible person. For example the Product Owner in a Scrum Team has the right to speak the final word with regards to business relevant decisions. The IT-Architect can do the same with regards to architectural decisions. A team leader of a technical component team can speak the final word in a discourse that does not come to an end. Of course here power is being exercised but I see it positive. Such behavior can be a service to the team. If final instances for decision making are embedded into the process and if these instances are willing and are able to take the responsibility, this will help all actors to move one step further. Roles and professions should not vanish in the team process. Instead the ordering capabilities of different roles and professions have to be used for the better.

It is important how the decision is being derived, what is being learned during the discourse and how the decision can be reasoned. It is important to review if the decisions lead to a functioning system. Upfront we can not always be sure if a decision brings an improvement or not. Therefore the agile worker prefers to work in an empiric process model. The essential characteristic of this process model is the continuous inspection and adaption, the short cycled comparison of mental model and reality.

The defined process model, in which the a-priori planning allows to predict which actions lead to specific outcomes, is not important for the agile worker, because defined process models do not require learning and therefore no agile workers.

Stop. This is too simple. Defined processes, when functioning, are mental models that are anchored in reality. Functioning defined processes are part of the agile workers toolbox. They are building blocks that can be combined to new solutions. They lower the amount of energy that is needed to come to results. Indeed they are to some extent part of the professional identity of the agile worker because this is what has been learned and what can be picked up to come to results faster, with lower risk and less energy input. The learning process is empiric, the learned is defined and will be reused to learn the new.

Compare it to a child learning to tie the shoes. At first this is an empiric process with all senses sharp. From the first success to the automatic procedure some time is required and then no further thoughts go into it. Higher goals are to reach.

Sometimes the most difficult task is in the questioning of the already learned. What was successful in the past may no longer help in the future. The agile worker should be prepared to move out of the comfort zone and to stand in for new insights. The new insight often does not have a lobby nor is it mainstream. Instead the new insight will challenge the status quo. This will move boundaries and it comes along with giving up personal safety. Because all new has to cleave its way.

Like learning is in service to produce good decisions, good decisions are in service to produce good results. Agile workers deliver results. The more mature the agile worker is, the more the solving of problems is characterized by accepting, internalizing, being permeated by the problem until a solution arises.

Many of us

Is the idea of the self-determined, purpose-oriented and mastery-striving cooperative worker a model for many of us? I believe, yes. When we were children, we all started as agile workers. Then we have been socialized in schools, university and corporate structures. If you want to have an idea about what happens during that way, have a look at the marshmallow challenge - kindergarten children usually produce better results than business school graduates.

Ideas change the world. Taylorism has done that and left us behind with a-priori process planning and acting as resources in highly automated manufacturing processes. The changing world with new challenges and ever increasing complexity will ask for our place in this world. Routined good behavior will no longer be the answer to that question. Creativity, exploring, understanding, changing, will become the normal case. The agile movement is a promising new idea and at the same time a reality pattern that represents a deeper and ground breaking change that is already on the way.

References

[Appelo 2011] J. Appelo, “Management 3.0, Leading Agile Developers, Develop Agile Leaders”, Addison Wesley 2011

[Kaner 2007] S. Kaner et al., “Facilitator´s Guide to Participatory Decision Making”, Second Edition, Jossey-Bass 2007

[Marquet 2012] L. David Marquet, “Turn the ship around, A true story of turning followers into leaders”, Penguin 2012

[Wujec 2010] T. Wujec, “The Marshmallow Challenge”, http://marshmallowchallenge.com/Welcome.html