Eight to Late

Sensemaking and Analytics for Organizations

Archive for the ‘Management’ Category

Understanding “flexibility” – a close-up view of an organizational platitude

with 12 comments

Introduction

Flexibility is one of those buzzwords that keeps coming up in organizational communiques and discussions. People are continually asked to display flexibility, without ever being told what the term means:  flexible workplaces, flexible attitudes, flexible jobs – the word itself has a flexible meaning that depends on the context in which it is used and by whom.

When words are used in this way they become platitudes – empty words that make a lot of noise. In this post, I analyse the platitude, flexibility, as it is used in organisations. My discussion is based on a paper by Thomas Eriksen entitled, Mind the Gap: Flexibility, Epistemology and the Rhetoric of New Work.

Background – a bit about organizational platitudes

One of the things that struck me when I moved from academia to industry is the difference in the way words or phrases are used in the two domains. In academics one has to carefully define the terms one uses (particularly if one is coining a new term) whereas in business it doesn’t seem to matter, words can mean whatever one wants them to mean (OK, this is an exaggeration, but not by too much). Indeed, as Paul Culmsee and I discuss in the first chapter of The Heretic’s Guide to Best Practices, many terms that are commonly bandied about in organizations are platitudes because they are understood differently by different people.

A good example of a platitude is the word governance. One manager may see governance as being largely about oversight and control whereas another might interpret it as being about providing guidance.  Such varying interpretations can result in major differences in the way the two managers implement governance:  the first one might enforce it as a compliance-oriented set of processes that leave little room for individual judgement while the other might implement it as a broad set of guidelines that leave many of the decisions in the hands of those who are actually doing the work. Needless to say, the results in the two cases are likely to be different too.

Flexibility – the conventional view

A good place to start our discussion of flexibility is with the dictionary. The online Oxford Dictionary defines at as:

Flexibility (noun):

  • the ability to be easily modified
  • willingness to change or compromise

The term is widely used in both these senses in organizational settings. For example, people speak of flexible designs (i.e. designs that can be easily modified) or flexible people (referring to those who are willing to change or compromise). However,  and this is the problem:  the term is open to interpretation – what Jack might term a flexible approach may be seen by Jill as a complete lack of method. These differences in interpretation become particularly obvious when the word is used in a broad context – such as in a statement justifying an organizational change.  An executive might see a corporate restructure and the resulting changes in jobs/roles as a means to achieve organizational flexibility, but those affected by it may see it as constraining theirs.  As Eriksen states:

Jobs are flexible in the sense that they are unstable and uncertain, few employees hold the same jobs for many years, the content of jobs can be changed almost overnight, and the boundaries between work and leisure are negotiable and chronically fuzzy.

Indeed, such “flexibility” which requires one to change at short notice results in a fragmentation of individual experience and a resulting loss of a coherent narrative of one’s life. It appears that increased flexibility in one aspect results in a loss of flexibility in another. Any sensible definition of flexibility ought to reflect this.

Understanding flexibility

Consider the following definition of flexibility proposed by Gregory Bateson:

Flexibility is uncommitted potential for change

This deceptively simple statement is a good place to start understanding what flexibility really means for projects, organisations …and even software systems.

As Eriksen tells us, Bateson proposed this definition in the context of ecology. In particular, Bateson had in mind the now obvious notion that the increased flexibility we gain through our increasingly energy-hungry lifestyles results in a decrease in the environment’s capacity to cope with the consequences. This is true of flexibility in any context: a gain in flexibility in one dimension will necessarily be accompanied by a loss of flexibility in another.

Another implication of the above definition is that a system that is running at or near the limits of its operating variables cannot be flexible.  The following examples should make this clear:

  • A project team that is putting in 18 hour workdays in order to finish a project on time.
  • A car that’s being driven at top speed.
  • A family living beyond their means.

All these systems are operating at or near their limits, they have little or no spare capacity to accommodate change.

A third implication of the definition follows from the preceding one:  the key variables of a flexible system should lie in the mid-range of their upper and lower limits. In terms of above examples:

  • The project team should be putting in normal hours.
  • The car should be driven at or below the posted road speed limits
  • The family should be living within its income, with a reasonable amount to spare.

Of course, the whole point of ensuring that systems operate in their comfort zone is that they can be revved up if the need arises. Such revving up, however,  should be an exceptional circumstance rather than the norm – a point that those who run projects, organisations (and, yes, even vehicles) often tend to forget. If one operates a system at the limits of its tolerance for too long, not only will it not be flexible, it will break.

Flexibility in the workplace

As mentioned in the introduction, the term flexibility keeps cropping up in organizational settings: corporate communiques exhort employees to be flexible in the face of change.  This is typically a coded signal that employees should expect uncertainty and be prepared to adjust to it.  A related manifestation of flexibility is the blurring of the distinction between work and personal life. As Eriksen puts it:

The term flexibility is often used to describe this new situation: Jobs are flexible in the sense that they are unstable and uncertain, few employees hold the same jobs for many years, the content of jobs can be changed, and the boundaries between work and leisure are poorly defined.

This trend is aided by recent developments in technology that enable employees to be perpetually on call. This is often sold as a work from home initiative but usually ends up being much more.  Eriksen has this to say about home offices:

One recent innovation typically associated with flexibility is the home office. In Scandinavia (and some other prosperous, technologically optimistic regions), many companies equipped some of their employees with home computers with online access to the company network in the early 1990s, in order to enhance their flexibility. This was intended to enable employees to work from home part of the time, thereby making the era when office workers were chained to the office desk all day obsolete.

In the early days, there were widespread worries among employers to the effect that a main outcome of this new flexibility would consist in a reduction of productivity. Since there was no legitimate way of checking how the staff actually spent their time out of the office, it was often suspected that they worked less from home than they were supposed to. If this were in fact the case, working from home would have led to a real increase in the flexibility of time budgeting. However, work researchers eventually came up with a different picture. By the late 1990s, hardly anybody spoke of the home office as a convenient way of escaping from work; rather, the concern among unionists as well as researchers was now that increasing numbers of employees were at pains to distinguish between working hours and leisure time, and were suffering symptoms of burnout and depression. The home office made it difficult to distinguish between contexts that were formerly mutually exclusive because of different physical locations.

It is interesting to see this development in the light of Bateson’s definition of flexibility: the employee gains flexibility in space (he or she can work from home or from the office) at the expense of flexibility in time (organization time encroaches on personal time). As Eriksen states:

 There seems to be a classic Batesonian flexibility trade-off associated with the new information technologies: increased spatial flexibility entails decreased temporal flexibility. If inaccessibility and ‘empty time’ are understood as scarce resources, the context of ‘new work’ thus seems to be an appropriate context for a new economics as well. In fact, a main environmental challenge of our near future will consist in protecting slow time and gaps from environmental degradation.

In short, it appears that flexibility for the organization necessarily implies a loss of flexibility for the individual.

Conclusion

Flexibility is in the eye of the beholder: an action to increase organisational flexibility by, say, redeploying employees would likely be seen by those affected as a move that constrains their  (individual) flexibility.  Such a dual meaning is characteristic of many organizational platitudes such as Excellence, Synergy and Governance. It is an interesting exercise to analyse such platitudes and expose the difference between their espoused and actual meanings.  So I sign off for 2013, wishing you  many hours of platitude-deconstructing fun 🙂

Written by K

December 11, 2013 at 8:34 pm

Organisational surprise and its relevance to project management

with 4 comments

Introduction

As humans, we tend to believe that events and processes will unfold in the way we expect them to.  Unfortunately things rarely go according to our expectations and we end up being, well… surprised! But it isn’t just individuals, entire organisations can be caught unawares by events. In this post I draw on a paper entitled, Clues, Cues and Complexity: Unpacking the Concept of Organisational Surprise, to elaborate on the different ways in which surprises can crop up in organisational settings and in particular, in projects.  My focus is on the latter because the temporary and one-off nature of projects seems to render them particularly prone to surprises.

Organizational surprise

The authors define organizational surprise as, “any event that happens unexpectedly or any expected event that takes an unexpected shape.”  One does not have to look far to see examples of organizational surprises. It is almost certain that any experienced project manager would have encountered a number of surprises in the course of his or her professional work. These could be unforeseen events (such as a project sponsor leaving for greener pastures) or unexpected twists and turns in what ought to have been a straightforward process (such as a software upgrade turning out to be more complicated than expected).

The ubiquity of organizational surprises begs the question as to why we are still “surprised by surprises.” The short answer is that this happens because we tend to overestimate our ability to control the future.  The authors suggest that we would be better served by regarding surprise as an inherent property of all open systems  (which includes entities such as organisations and projects). After living through the consequences of many over-optimistic managerial actions (both, my own and those of others), I would have to agree.

Classifying surprise – a typology of surprises

Nothing I have said so far would be surprising to readers: indeed, project management is largely about managing uncertainty…and all project managers know that. What might be new, however, is a classification of surprises proposed by the authors of the paper. I have hinted at the classification in the previous section where I gave one example each of a surprising event and a surprising process. It is now time to generalize this to a typology of surprises.

The authors classify surprises along two dimensions:

  • Issue – An issue can occur in one of two ways:
    • When something unusual happens.
    • When something that usually happens does not happen.

    It is important to note that although the term issue has negative connotations in project management parlance, it is used here in a neutral sense – i.e. issues can be either positive or negative.

  • Process – a process is a chain of related events that unfolds in an unusual manner. For example, when an ATM cash withdrawal fails because the machine does not have enough money left to process the withdrawal.

From the perspective of surprise, issues and processes can be either expected or unexpected. This gives us the four categories illustrated in Fig 1.

Figure 1: A typology of surprises

Figure 1: A typology of surprises

Let’s take a tour of the four categories

  1. Expected issue and process: This is the zone of predictability where one-off events tend to go as foreseen.  An example of an expected issue that was successfully dealt with through planning was the Y2K problem. Another example is provided by (successful) risk management activities that are triggered when a foreseen risk eventuates.
  2. Unexpected issue, expected process:  This is where a surprising issue occurs, but the consequences follow are expected. An example this would be a chance occurrence (say, a project team member on a troubled project stumbles on a novel technique that saves development time), and this leads to the project being completed within time and budget (expected process following the event).
  3. Expected issue, unexpected process:  This occurs when an expected event evolves in an unexpected way – i.e. leads to a surprising process. A common example of this in a project environment is when a  front-end project  decision unfolds in unexpected ways.   Another common example is an organizational change that has unintended consequences.
  4. Unexpected issue, unexpected process: This is a situation where both the event and the processes around it are counter to  conventional wisdom. In this case, those involved need to understand, or make sense of the situation and hence the term sensemaking crisis. An example of this is when project managers fail to anticipate factors that turn out to have a major influence on the way their projects evolve.  One could argue that many high profile project failures were the result of such crises.  The Denver Baggage Handling System and the Merck Vioxx affair are good examples. In both cases, the projects failed because those responsible failed to react to certain events that changed the trajectory of the projects irrevocably.

Let’s now take a brief look at the usefulness of this classification.

Coping with surprise

Managers expend a great deal of effort in attempting to predict surprises and hence corral them into the zone of predictability (Reminder: this is the bottom left quadrant in Figure 1).  As mentioned earlier, this is difficult because organisations are open systems, and novelty is an inherent property of such systems. The main implication of this is that surprises in quadrants other than the zone of predictability cannot be foreseen.  So, instead of worrying about predicting surprises, project and program managers would do better by focusing their efforts on creating an environment that enables team members to cope with nasty surprises and take advantage of good ones.

What might such an environment look like?

This question is best approached via a related question: what are the qualities displayed by project teams that are able to cope with surprises?

Here are some essential ones that are mentioned in the paper:

  1. Vigilance / problem sensing– a deep awareness of the project environment, with the ability to sense any changes in it.
  2. Resilience – the capacity to adjust to changes in the internal and external environment.
  3. Ability to improvise– the ability to respond to the unexpected by devising appropriate courses of action under pressure

The striking thing about these qualities is that they are impossible to create or engender by management fiat: teams will not improvise unless they feel empowered to, nor will they be resilient or vigilant unless they are intrinsically motivated to be so.These characteristics are emergent in the sense that they will be displayed spontaneously by teams that are in a frame of mind that comes out of being in  the right environment.

The primary task of a project manager, or any manager for that matter, is to create such a  holding environment that provides psychological safety to the team and encourages rational (or open) dialogue  between all project stakeholders (yes, including project sponsors). I won’t elaborate on these terms here  since they are dealt with at length in the articles that I have provided links to in the previous sentence.

Different types of surprise require different approaches

Having the right environment is the key to dealing with all four kinds of surprises. However, even within such an environment, it is important to note that different types of surprises have to be tackled in different ways. In particular:

  1. Predictable surprises are best tackled through traditional management approaches (as discussed in PMBOK, for example). In view of the prevalence of such approaches, I should perhaps emphasise again that they work only for a small subset of all possible surprises (only those that lie in the first quadrant)
  2. Surprising events and surprising processes are best dealt with by the people who are at the coalface of the problem since they are intimately familiar with the context and history of the problem.
  3. Sensemaking crises are best handled by collaborative problem solving approaches such as Dialogue Mapping.

The above yet again underscores the importance of the creating the right environment, for although predictable surprises can be tackled through traditional approaches to project management, those that lie in the other three quadrants cannot.

Conclusion

A fact of organizational life is that project managers are often caught unawares by unforeseen events and their dynamics. In this post, I have summarized a typology of organizational surprises and have elaborated on its relevance to project management.  I have also briefly discussed the ways in which different types of surprises can be tackled, emphasising that the key to tackling surprise lies in creating an environment that provides psychological safety and encourages open dialogue.

In closing, I reiterate that projects and organisations are open systems, and surprises are characteristic of such systems. The biggest surprise, therefore, is that we are continually surprised by some of the events and processes that occur within them

Written by K

November 27, 2013 at 9:38 pm

On the decline and resurrection of Taylorism

with 8 comments

Introduction

A couple of years ago  Paul Culmsee and I wrote a post on the cyclical decay and recurrence of certain management concepts. The article describes how ideas and practices bubble up into mainstream management awareness and then fade away after the fad passes…only to recur in a morphed form some years later.

It recently occurred to me that this cycle of decay and recurrence is not restricted to good ideas or practices: ideas that, quite frankly, ought to remain consigned to the dustbin of management can also recur. Moreover, they may even do better the second time around because the conditions are right for them to flourish.  In this post I discuss  how the notion of scientific management, often referred to as Taylorism, after its founder Fredrick Winslow Taylor, has ebbed and flowed in the century or so since it was first proposed.

Taylorism and its  alleged demise

The essence of Taylorism  is summarised nicely in this quote from Taylor’s monograph, The Principles of Scientific Management:

This paper has been written…to prove that the best management is a true science, resting upon clearly defined laws, rules and principles, as a foundation. And further to show that the fundamental principles of scientific management  are applicable to all human activities, from our simplest individual activities to the work of great corporations, which call for the most elaborate cooperation. And briefly, through a series of illustrations, to convince the reader that whenever these principles are correctly applied, results must follow which are truly astounding…

According to standard storyline of management, Taylorism had its heyday in the first few decades of the 20th century and faded away after the notion of the worker as an individual emerged in 1920s.  In his wonderful paper, Understanding Taylorism, Craig Littler summarises this mainstream view as follows:

From 1900-20 Taylorism provided the dominant ideas about the worker and worker motivation. But money was not enough and  ‘a great new ideas was taking root. The view of the worker as an individual personality emerged strongly around 1920 to command the stage.’ From 1920-1940 the worker was seen as a psychological complex, but then ‘Psychological Man’ (sic) faltered and sociology entered industry: Man (sic) had neighbours!

In short, the official story is that Taylorism was declared dead, if not quite interred, some ninety years ago.

But as we shall see, its ghost still haunts the hallways of the modern, knowledge-based corporation…

The ghost of Taylorism

The standard storyline views Taylorism as a management ideology – a set of ideas that guide management practice.  However, as Littler tells us, it is more instructive to see it primarily as a means of organizing work, in other words as a management practice. As Littler tells us,

If we look at Taylorism as a form of work organization then we can proceed to analyse it in terms of three general categories: the division of labour, the structure of control over task performance, and the implicit employment relationship.

To elaborate: Taylorism emphasised a scientific approach to enhancing worker productivity through things such as time and motion studies. In practice this lead to a  rigid fragmentation and division of labour coupled with time/effort measurements that enabled top-down planning. Although these efforts were focused on increasing production by improving worker efficiency, they also had the effect of centralising control over task performance and skewing the  terms of employment in management’s favour.

…and its new avatar

Even from this brief summary one can see how Taylorism sneaks into the modern workplace. As Martha Crowley and her co-workers state in the abstract to this paper:

The last quarter of the twentieth century has seen an erosion of job security in both manual and professional occupation…employee involvement schemes in manual production and the growth of temporary employment, outsourcing and project-based teams in the professions have influenced working conditions in both settings…these practices represent not a departure from scientific management, as is often presumed, but rather the adoption of Taylorist principles that were not fully manifested in the era of mass production.

Indeed, there is a term, Neo-Taylorism, that describes this newly resurrected avatar of this old ideology.

The resurrection of Taylorism is in no small part due to advances in technology. This is indeed an irony because the very technology that gives us “cognitive surplus” (if one believes what some folks tell us) and enables us to inform the world  about “what we are doing right now” also makes it possible for us to be monitored at the workplace in real time.  A stark manifestation of this the call centre  – which Phil Tailor and  Peter Bain refer to  as an electronic panopticon and, in a later paper an assembly line in the head.

Of course, one does not need to work in a call centre to see Neo-Taylorism at work;  the central ideas of scientific management permeate many modern workplaces.    The standard HR cycle of goal-setting, review and performance evaluation, familiar to most folks who work in organisation-land,  is but a means of evaluating and/or ranking employees with a view to determining an appropriate reward or punishment. This often does more harm than good as is highlighted in David Auerbach’s critique of Microsoft’s stack ranking process: there is nothing more effective than the threat of termination to ensure a compliant workforce…but engendering team spirit and high performance is another matter altogether.

Concluding remarks

To conclude: the resurrection of Taylorism is no surprise. For  although it may have become an unfashionable ideology in the latter part of the first half of the 20th century, its practices and, in particular, the forms of work organisation embodied in it live on.  This is true not just in industry but also in the academic world. Indeed, some of the research done in industrial engineering departments the world over serves to burnish and propagate Taylor’s legacy. Taylorism as an ideology may be dead, but as a management practice it lives on and flourishes.

Acknowledgement

Thanks to  Greg Lloyd for his pointer to David Auerbach’s critique of Microsoft’s stack ranking process.

Written by K

August 28, 2013 at 8:44 pm