Archive for the ‘Management’ Category
A stupidity-based theory of organisations – a paper review
Introduction
The platitude “our people are our most important asset” reflects a belief that the survival and evolution of organisations depends on the intellectual and cognitive capacities of the individuals who comprise them. However, in view of the many well documented examples of actions that demonstrate a lack of foresight and/or general callousness about the fate of organisations or those who work in them, one has to wonder if such a belief is justified, or even if it is really believed by those who spout such platitudes.
Indeed, cases such as Enron or Worldcom (to mention just two) seem to suggest that stupidity may be fairly prevalent in present day organisations. This point is the subject of a brilliant paper by Andre Spicer and Mats Alvesson entitled, A stupidity based theory of organisations. This post is an extensive summary and review of the paper.
Background
The notion that the success of an organization depends on the intellectual and rational capabilities of its people seems almost obvious. Moreover, there is a good deal of empirical research that seems to support this. In the opening section of their paper, Alvesson and Spicer cite many studies which appear to establish that developing the knowledge (of employees) or hiring smart people is the key to success in an ever-changing, competitive environment.
These claims are mirrored in theoretical work on organizations. For example Nonaka and Takeuchi’s model of knowledge conversion acknowledges the importance of tacit knowledge held by employees. Although there is still much debate about tacit/explicit knowledge divide, models such as these serve to perpetuate the belief that knowledge (in one form or another) is central to organisational success.
There is also a broad consensus that decision making in organizations, though subject to bounded rationality and related cognitive biases, is by and large a rational process. Even if a decision is not wholly rational, there is usually an attempt to depict it as being so. Such behaviour attests to the importance attached to rational thinking in organization-land.
At the other end of the spectrum there are decisions that can only be described as being, well… stupid. As Rick Chapman discusses in his entertaining book, In Search of Stupidity, organizations occasionally make decisions that are plain dumb However, such behaviour seldom remains hidden because of its rather obvious negative consequences for the organisation. Such stories thus end up being immortalized in business school curricula as canonical examples of what not to do.
Functional stupidity
Notwithstanding the above remarks on obvious stupidity, there is another category of foolishness that is perhaps more pervasive but remains unnoticed and unremarked. Alvesson and Spicer use the term functional stupidity to refer to such “organizationally supported lack of reflexivity, substantive reasoning, and justitication.”
In their words, functional stupidity amounts to the “…refusal to use intellectual resources outside a narrow and ‘safe’ terrain.” It is reflected in a blinkered approach to organisational problems, wherein people display an unwillingness to consider or think about solutions that lie outside an arbitrary boundary. A common example of this is when certain topics are explicitly or tacitly deemed as being “out of bounds” for discussion. Many “business as usual” scenarios are riddled with functional stupidity, which is precisely why it’s often so hard to detect.
As per the definition offered above, there are three cognitive elements to functional stupidity:
- Lack of reflexivity: this refers to the inability or unwillingness to question claims and commonly accepted wisdom.
- Lack of substantive reasoning: This refers to reasoning that is based on a small set of concerns that do not span the whole issue. A common example of this sort of myopia is when organisations focus their efforts on achieving certain objectives with little or no questioning of the objectives themselves.
- Lack of justification: This happens when employees do not question managers or, on the other hand, do not provide explanations regarding their own actions. Often this is a consequence of power relationships in organisations. This may, for example, dissuade employees from “sticking their necks out” by asking questions that managers might deem out of bounds.
It should be noted that functional stupidity has little to do with limitations of human cognitive capacities. Nor does it have anything to do with ignorance, carelessness or lack of thought. The former can be rectified through education and/or the hiring of consultants with the requisite knowledge, and the latter via the use of standardised procedures and checklists.
It is also important to note that functional stupidity is not necessarily a bad thing. For example, by placing certain topics out of bounds, organisations can avoid discussions about potentially controversial topics and can thus keep conflict and uncertainty at bay. This maintains harmony, no doubt, but it also strengthens the existing organisational order which in turn serves to reinforce functional stupidity.
Of course, functional stupidity also has negative consequences, the chief one being that it prevents organisations from finding solutions to issues that involve topics that have been arbitrarily deemed as being out of bounds.
Examples of functional stupidity
There are many examples of functional stupidity in recent history, a couple being the irrational exuberance in the wake of the internet boom of the 1990s, and the lack of critical examination of the complex mathematical models that lead to the financial crisis of last decade.
However, one does not have to look much beyond one’s own work environment to find examples of functional stupidity. Many of these come under the category of “business as usual” or “that’s just the way things are done around here” – phrases that are used to label practices that are ritually applied without much thought or reflection. Such practices often remain unremarked because it is not so easy to link them to negative outcomes. Indeed, the authors point out that “most managerial practices are adopted on the basis of faulty reasoning, accepted wisdom and complete lack of evidence.”
The authors cite the example of companies adopting HR practices that are actually detrimental to employee and organisational wellbeing. Another common example is when organisations place a high value on gathering information which is then not used in a meaningful way. I have discussed this “information perversity” at length in my post on entitled, The unspoken life of information in organisations, so I won’t rehash it here. Alvesson and Spicer point out that information perversity is a consequence of the high cultural value placed on information: it is seen as a prerequisite to “proper” decision making. However, in reality it is often used to justify questionable decisions or simply “hide behind the facts.”
These examples suggest that functional stupidity may be the norm rather than the exception. This is a scary thought…but I suspect it may not be surprising to many readers.
The dynamics of stupidity
Alvesson and Spicer claim that functional stupidity is a common feature in organisations. To understand why it is so pervasive, one has to look into the dynamics of stupidity – how it is established and the factors that influence it. They suggest that the root cause lies in the fact that organisations attempt to short-circuit critical thinking through what they call economies of persuasion, which are activities such as corporate culture initiatives, leadership training or team / identity building, relabelling positions with pretentious titles – and many other such activities that are aimed at influencing employees through the use of symbols and images rather than substance. Such symbolic manipulation, as the authors calls it, is aimed at increasing employees’ sense of commitment to the organisation.
As they put it:
Organizational contexts dominated by widespread attempts at symbolic manipulation typically involve managers seeking to shape and mould the ‘mind-sets’ of employees . A core aspect of this involves seeking to create some degree of good faith and conformity and to limit critical thinking
Although such efforts are not always successful, many employees do buy in to them and thereby identify with the organisation. This makes employees uncritical of the organisation’s goals and the means by which these will be achieved. In other words, it sets the scene for functional stupidity to take root and flourish.
Stupidity management and stupidity self-management
The authors use the term stupidity management to describe managerial actions that prevent or discourage organisational actors (employees and other stakeholders) from thinking for themselves. Some of the ways in which this is done include the reinforcement of positive images of the organisation, getting employees to identify with the organisation’s vision and myriad other organisational culture initiatives aimed at burnishing the image of the corporation. These initiatives are often backed by organisational structures (such as hierarchies and reward systems) that discourage employees from raising and exploring potentially disruptive issues.
The monitoring and sanctioning of activities that might disrupt the positive image of the organisation can be overt (in the form of warnings, say). More often, though, it is subtle. For example, in many meetings, participants participants know that certain issues cannot be raised. At other times, discussion and debate may be short circuited by exhortations to “stop thinking and start doing.” Such occurrences serve to create an environment in which stupidity flourishes.
The net effect of managerial actions that encourage stupidity is that employees start to cast aside their own doubts and questions and behave in corporately acceptable ways – in other words, they start to perform their jobs in an unreflective and unquestioning way. Some people may actually internalise the values espoused by management; others may psychologically distance themselves from the values but still act in ways that they are required to. The net effect of such stupidity self-management (as the authors call it) is that employees stop questioning what they are asked to do and just do it. After a while, doubts fade and this becomes the accepted way of working. The end result is the familiar situation that many of us know as “business as usual” or “that’s just the way things are done around here.”
The paradoxes and consequences of stupidity
Functional stupidity can cause both feelings of certainty and dissonance in members of an organisation. Suppressing critical thinking can result in an easy acceptance of the way things are. The feelings of certainty that come from suppressing difficult questions can be comforting. Moreover, those who toe the organisational line are more likely to be offered material rewards and promotions than those who don’t. This can act to reinforce functional stupidity because others who see stupidity rewarded may also be tempted to behave in a similar fashion.
That said, certain functionally stupid actions, such as ignoring obvious ethical lapses, can result in serious negative outcomes for an organisation. This has been amply illustrated in the recent past. Such events can prompt formal inquiries at the level of the organisation, no doubt accompanied by informal soul-searching at the individual level. However, as has also been amply illustrated, there is no guarantee that inquiries or self-reflection lead to any major changes in behaviour. Once the crisis passes, people seem all too happy to revert to business as usual.
In the end , though, when stark differences between the rhetoric and reality of the organisation emerge – as they eventually will– employees will see the contradictions between the real organisation and the one they have been asked to believe in. This can result in alienation from and cynicism about the organisation and its objectives. So, although stupidity management may have beneficial outcomes in the short run, there is a price to be paid in the longer term.
Nothing comes for free, not even stupidity…
Conclusion
The authors main message is that despite the general belief that organisations enlist the cognitive and intellectual capacities of their members in positive ways, the truth is that organisational behaviour often exhibits a wilful ignorance of facts and/or a lack of logic. The authors term this behaviour functional stupidity.
Functional stupidiy has the advantage of maintaining harmony at least in the short term, but its longer term consequences can be negative. Members of an organisation “learn” such behaviour by becoming aware that certain topics are out of bounds and that they broach these at their own risk. Conformance is rewarded by advancement or material gain whereas dissent is met with overt or less obvious disciplinary action. Functional stupidity thus acts as a barrier that can stop members of an organisation from developing potentially interesting perspectives on the problems the organisations face.
The paper makes an interesting and very valid point about the pervasiveness of wilfully irrational behaviour in organisations. That said, I can’t help but think that the authors have written it with tongue firmly planted in cheek.
A performance review tragedy in five limericks
The yearly performance review
is something we all must go through.
So you may well know
the story below
…it may’ve even happened to you.
The boss, a hawk not a dove,
dictated the goals from above.
He said, “You will do
as I tell you to,
and that should be more than enough.”
The year whizzed by like a race.
(Isn’t that always the case?)
Soon it was time
for that moment sublime,
when performance would be appraised.
And as the review progressed,
the minion suffered much stress,
because it was clear
he’d be marked a failure
even though he’d given his best.
In the end he said, “OK, that’s fine,
but we were never aligned.
I know you don’t care
but it just ain’t fair
that these were your goals, not mine.
“Strategic alignment” – profundity or platitude?
Introduction
Some time ago I wrote a post entitled, Models and messes in management, wherein I discussed how a “scientific” approach to management has resulted in a one-size-fits-all approach to problem solving in organizations. This is reflected in the tendency of organisations to implement similar information technology (IT) systems, often on the “expert” advice of carbon-copy consultancies that offer commoditized solutions.
A particularly effective marketing tactic is to advertise such “solutions” as being able to help organisations achieve strategic alignment between IT and the business. In this post I discuss how the concept of “strategic alignment” though seemingly sensible, makes no sense in the messy, real world of organization-land. My discussion is based on a brilliant paper by Claudio Ciborra entitled, De Profundis? Deconstructing the concept of strategic alignment. The paper analyses the notion of alignment as it is commonly understood in the context of IT– namely as a process by which IT objectives are brought in line with those of the organization it serves.
Background
The paper begins with a short chronology of the term strategic alignment, starting with this highly cited paper published by Henderson and Venkataraman in 1993. The paper describes the need for alignment between business and IT strategies of companies. More importantly, however, the authors detail a “Strategic Alignment Model” that purports to “guide management practice” towards achieving alignment between IT and the business. However, as Ciborra noted four years later, in 1997, it was still an open question as to what strategic alignment really meant and how it was to be achieved.
Fast forward 15 years to 2012, and it appears that the question of what strategic alignment is and how to achieve it still an open one. Here are some excerpts from recently published papers:
In the abstract to their paper entitled, Strategic Alignment of Business Processes, Morrison et. al. state:
Strategic alignment is a mechanism by which an organization can visualize the relationship between its business processes and strategies. It enables organizational decision makers to collect meaningful insights based on their current processes. Currently it is difficult to show the sustainability of an organization and to determine an optimal set of processes that are required for realizing strategies.” (italics mine)
Even worse, the question of what strategic alignment is is far from settled. It appears that it means different things to different people. In the abstract to their paper entitled, Reconsidering the Dimensions of Business-IT Alignment, Schlosser et. al. state:
While the literature on business-IT alignment has become increasingly mature in the past 20 years, different definitions and conceptualizations have emerged. Several dimensions like strategic, intellectual, structural, social, and cultural alignment have been developed. However, no integrated and broadly accepted categorization exists and these dimensions are non-selective and do overlap…
This begs the question as to how meaningful it is for organizations to pursue “alignment” when people are still haggling over the fine print of what it means.
Ciborra dealt with this very question 15 years ago. In the remainder of this post I summarize the central ideas of his paper, which I think are as relevant today as the were at the time it was written.
Deconstructing strategic alignment
The whole problem with the notion of strategic alignment is nicely summarized in a paragraph that appears in Ciborra’s introduction:
…while strategic alignment may be close to a truism conceptually, in the everyday business it is far from being implemented. Strategy ends up in “tinkering” and the IT infrastructure tends to “drift”. If alignment was supposed to be the ideal “bridge” connecting the two key variables [business and IT], it must be admitted that such a conceptual bridge faces the perils of the concrete bridge always re-designed and never built between continental Italy and Sicily, (actually, between Scylla and Charybdis) its main problem being the shores: shifting and torn by small and big earthquakes….
The question, then, is how and why do dubious concepts such as strategic alignment worm their way into mainstream management?
Ciborra places the blame for this squarely in the camp of academics who really ought to know better. As he states:
[Management Science] deploys careful empirical research, claiming to identify “naturally occurring phenomena” but in reality measures theoretical (and artificial) constructs so that the messiness of everyday reality gets virtually hidden. Or it builds models that should be basic but do not last a few years and quickly fall into oblivion.
And a few lines later:
…practitioners and academics increasingly worship simplified models that have a very short lifecycle….managers who have been exposed to such illusionary models, presented as the outcome of quasi-scientific studies, are left alone and disarmed in front of the intricacies of real business processes and behaviors, which in the meantime have become even more complicated than when these managers left for their courses. People’s existence, carefully left out of the models, waits for them at their workplaces.
Brilliantly put, I think!
Boxes, arrows and platitudes
Generally, strategic alignment is defined as a fit, or a bridge, between different domains of a business. To be honest it seems the metaphor of a “bridge” seems to distract from reflecting on the chasm that is allegedly being crossed and the ever-shifting banks that lie on either side. Those who speak of alignment would do better to first focus on what they are trying to align. They may be surprised to find that the geometric models that pervade their PowerPoint Presentations (e.g. organograms, boxes connected by arrows) are completely divorced from reality. Little surprise, then, that top-down, management efforts at achieving alignment invariably fail.
Why do such tragedies play out over and over again?
Once again, Ciborra offers some brilliant insights…
The messy world, he tells us, gives us the raw materials from which we build simplified representations of the organization we work in. These representations are often built in the image of models that we have learnt or read about (or have been spoon-fed to us by our expensive consultants). Unfortunately, these models are abstractions of reality – they cannot and must not be confused with the real thing. So when we speak of alignment, we are talking of an abstraction that is not “out there in the world” but instead only resides in our heads; in textbooks and journal papers; and, of course, in business school curricula.
As he says,
…there is no pure alignment to be measured out there. It is, on the contrary, our pre-scientific understanding of and participating in the world of organizations that gives to the notion of alignment a shaky and ephemeral existence as an abstraction in our discourses and representations about the world.
This is equally true of management research programs on alignment: they are built on multiple abstractions and postulated causal connections that are simply not there.
If academics who spend their productive working lives elaborating these concepts make little headway, what hope is there for the manager who to implement or measure strategic alignment?
Is there any hope?
Ciborra tells us that the answer to the question posed in the sub-heading is a qualified “yes”. One can pursue alignment, but one must first realize that the concept is an abstraction that exists only in an ideal world in which there are no surprises and in which things always go according to plan. Perhaps more importantly, they need to understand that implementations of technology invariably have significant unintended consequences that require improvised responses and adaptations. Moreover, these are essential aspects of the process of alignment, not things that can be wished away by better plans or improved monitoring.
So what can one do? As Ciborra states:
…we are confronted with a choice. Either we can do what management science suggests, that is “to realize these surprises in implementation as exceptions, build an ideal world of “how things should be” and to try to operate so that the messy world that in which managers operate moves towards this model….or we suspend belief about what we think we know…and reflect on what we observe. Sticking to the latter we encounter phenomena that deeply enrich our notion of alignment… (italics mine)
Ciborra then goes on to elaborate on concepts of Care (dealing with the world as it is, but in a manner that is honest and free of preconceived notions), Cultivation (allowing systems to evolve in a way that is responsive to the needs of the organization rather than a predetermined plan) and Hospitality (the notion that the organization hosts the technology, much in the way that a host hosts a guest). It would take at least a thousand words more to elaborate on these concepts, so I’ll have to leave it here. However, if you are interested in finding out more, please see my summary and review of Ciborra’s book: The Labyrinths of Information.
…and finally, who aligns whom?
The above considerations lead us to the conclusion that, despite our best efforts, technology infrastructures tend to have lives of their own – they align us as much as we (attempt to) align them. IT infrastructures are deeply entwined with the organizations that host them, so much so that they are invisible (until they breakdown, of course) and even have human advocates who “protect” their (i.e. the infrastructure’s) interests! Although this point may seem surprising to business folks, it is probably familiar to those who work with information systems in corporate or other organizational environments.
A final word: many other management buzz-phrases, though impressive sounding, are just as meaningless as the term strategic alignment. However, I think I have rambled on enough, so I will leave you here to find and deconstruct some of these on your own.

