Author Archive
One evening at the station – a project management fable
It had been an eventful day but Jack was still not done. He needed to update the schedule to reflect the bad news from the vendor and his development team. Then there was the status report. He was not looking forward to the meeting tomorrow. The sponsor would go ballistic when he heard about the delay. “I’d better do the status report before I go home,” he thought to himself. “Damned project is more trouble than it’s worth. I should never have volunteered for it …”
The phone rang flashing his home number. He ignored it recalling the morning’s conversation with his wife – she was expecting him to be home an hour ago. “S**t, talk about conflicting priorities,” he muttered to himself as he shut down his notebook and stuffed it in to his satchel, “I’ll have to do the status report at home.”
He dashed off to catch the 8:05 train; with luck he might be home in an hour.
But luck was not on his side that evening. He heard the rumble of the departing 8:05 as he bounded down the escalator to the platform. “Oh no, that’s another half hour gone, I should’ve stayed at the office and finished the status report,” he said to himself, shaking his head in annoyance.
He must have said that out loud because a gentle voice from behind him asked, “Tough day at the office, huh?”
He turned around, annoyed at the intrusion, “Excuse me…” he stopped himself mid-sentence when he saw the voice belonged to a wizened old man with twinkling eyes. Yoda was the word that came to mind. Jack continued in a friendlier tone: “Yeah, you could say it’s been a hard day.”
“What do you do for a living?” asked the old man.
Jack didn’t want the conversation but didn’t want to offend the old man either, “I manage projects,” he replied.
“Forgive my ignorance,” said the old man, “but what is a project and what does it mean to manage one?”
Jack rolled eyes (well, he didn’t really, but he felt like). “A project is an initiative to create something…like a new product or service within a specified time and budget. And managing it involves doing what’s necessary to make sure the product or service is created on time and within the specified budget.”
“So how do you do that?”
Jack was starting to get a little annoyed at the intrusion and he certainly did not want to get into all that PM 101 stuff, so he simply said, “There are a bunch of standard processes and techniques to run projects efficiently. They work well when done right.”
“How are they working for you right now?” asked the old man.
“Not so well. Why? Do you have some advice to offer?” he enquired pointedly.
“Why aren’t they working well?” persisted the old man, oblivious to Jack’s irritation.
“Oh, all kinds of reasons: politics people etc. – it’s complicated.”
“And you didn’t see these complications before they occurred,” stated the old man, more as a fact than question.
“Obviously I didn’t,” retorted Jack.
“Sorry, I didn’t mean to annoy with these questions but I can’t help but wonder if …”
Jack had had enough. “Please mind your own business,” he said shortly. “And if you’ll excuse me, I have a half hour before my train arrives and a stack of work to catch up with.” So saying, he strode to a nearby bench and sat down. Reaching into his bag, he pulled out his notebook and turned his attention to his unfinished status report.
The old man shrugged and wandered off towards the other end of the platform.
Jack, totally engrossed in his reports and plans, paid little attention to the announcements and the hubbub of the platform. He was used to working at the station, and knew that the rumble of his train would alert him that he needed to board.
And so he continued working.
About half an hour later, he noticed that the noise around him had subsided somewhat. That didn’t feel right. He surfaced from his reports and looked around. There were very few people about. “What’s going on?” he muttered to himself.
“Ah, I see you missed the announcements.” He hadn’t noticed the old man approach.
“What announcements?” asked Jack, a tad bewildered.
“Trains have been cancelled because of an accident further down the line,” replied the old man, ‘you’ll need to find some other way to get home…”
“S**t, that’s all I need, doesn’t anything work in this damned place.”
“There were at least a couple of announcements but it appears you missed them,” said the old man.
It was going to be an expensive cab ride home or another half hour wait for a bus followed by a 45 minute commute. Jack, sighing resignedly, stuffed his computer back into his bag and got up to go.
“It is good to pay attention to what is actually happening rather than what you think will happen,” said Yoda.
“Yeah, whatever,” said Jack as he turned and walked away.
“Perhaps there’s a lesson here for your work too: timetables and plans are not reality” said the old man.
Jack was taken aback. He stopped in his tracks, turned towards the old man and asked, “What do you mean?”
“I think I’ve said enough,” came the reply. “Make of it what you will.”
The old man shuffled away, leaving Jack to contemplate the long ride home.
The paradoxes of organisational change
Introduction
It is a truism that organisations are in a constant state of change. It seems that those who run organisations are rarely satisfied with the status quo, and their unending quest to improve products, performance, sales or whatever makes change an inescapable fact of organizational life.
Many decision makers and managers who implement change take a somewhat naïve view of the process: they focus on what they want rather than all the things that could happen. This is understandable because change projects are initiated and plans made when all the nitty-gritty details that may cause problems are not yet in view. Given that it is impossible to surface all significant details at the start. is there anything that decision-makers and managers can do to address the inevitable ambiguity of change?
One of the underappreciated facets of organizational change is that it is inherently paradoxical. For example, although it is well known that such changes inevitably have unintended consequences that are harmful, most organisations continue to implement change initiatives in a manner that assumes complete controllability with the certainty of achieving solely beneficial outcomes.
It is my contention that an understanding of the paradoxes that operate in the day-to-day work of change might help managers in developing a more realistic picture of how a change initiative might unfold and some of the problems that they might encounter. In this post, I look at the paradoxes of organizational change drawing on a paper entitled, The social construction of organizational change paradoxes.
Paradoxes are social constructs
More often than not, the success of an organizational change hinges on the willingness of people to change their attitudes, behaviour and work practices. In view of this it is no surprise that many of the difficulties of organizational change have social origins.
Change makes conflicting demands on people: for example, managerial rhetoric about the need to improve efficiency is often accompanied by actions that actually decrease it. As a result, many of the obstacles to change arise from elements that seem sensible when considered individually, but are conflicting and contradictory when taken together. This results in paradox. As the authors of the paper state:
We propose that paradox is constructed when elements of our thoughts, actions and emotions that seemed logical when considered in isolation, are juxtaposed, appearing mutually exclusive. The result is often an experience of absurdity or paralysis.
Again it is important to note that change-related paradoxes have social origins – they are caused by the actions of certain individual or groups and their effects or perceived effects on others.
Paradoxes of organizational change
The authors describe three paradoxes of organizational change: paradoxes of performing, belonging and organizing. I describe each of these below, but before I do so, it is worth noting that paradoxes are often exacerbated by people’s reactions to them. In particular, those affected by a change tend to interpret it using frames of reference that accentuate negative effects. For example, employees may view a change initiative as a threat rather than an opportunity to improve performance. Paradoxically, their perceptions may become a self-fulfilling reality because their (negative) reactions to the change may reinforce its undesirable effects.
That said let’s look at the three paradoxes of organizational change as described in the paper.
Paradoxes of performing
A change initiative is invariably accompanied by restructuring that results in wholesale changes in roles and responsibilities across the organisation. Moreover, since large-scale changes take a long time to implement, there is a longish transition period in which employees are required to perform tasks and activities associated with their old and new roles. During this period, employees may have to deal with competing, even conflicting demands. This, quite naturally, causes stress and anxiety.
Paradoxes of performing relate to contradictions in employees’ self understanding of their identities and roles within the organisation. As such, these paradoxes are characterized by mixed messages from management. As the authors state, people faced with such paradoxes often express feelings of rising frustration with/distrust of management, doubt (inability to choose) or nihilism (futility of choice). This paradox isparticularly common when organisations transition from a traditional (functional) management hierarchy to a matrix structure.
Paradoxes of belonging
Another consequence of organizational restructuring is that old hierarchies and workgroups are replaced by new ones. Adjusting to this requires employees to shift allegiances and develop new work relationships. Leaving the safety of a known group can be extremely stressful. Moreover, since the new structures are rarely defined in detail, at least at the start, there is a great deal of ambiguity as to what it really stands for. It is no surprise, therefore, that some employees attempt to maintain the status quo or even leave while others benefit from the change.
At the heart of this paradox is a double bind where a desire to maintain existing relationships competes with the realization that it is necessary to develop new ones. People react to this differently, depending on their values, motivations and (above all) their ability to deal with ambiguity. Inevitably, such situations are characterized by antagonistic attitudes that accentuate differences and/or peoples’ defensive attitudes that provoke defensiveness in others.
Paradoxes of organizing
The fact that organisations consist of people who have diverse backgrounds, motivations and interests suggests that the process of organizing – which, among things, involves drawing distinctions between groups of people based on their skills – is inherently paradoxical. The authors quote a couple of studies that support this contention. One study described how, “friendly banter in meetings and formal documentation [promoted] front-stage harmony, while more intimate conversations and unit meetings [intensified] backstage conflict.” Another spoke of a situation in which, “…change efforts aimed at increasing employee participation [can highlight] conflicting practices of empowerment and control. In particular, the rhetoric of participation may contradict engrained organizational practices such as limited access to information and hierarchical authority for decision making…”
As illustrated by the two examples quoted in the prior paragraph, a manifestation of a paradox of organizing is that the (new) groups created through the process of organizing can accentuate differences that would not otherwise have mattered. These differences can undermine the new structures and hence, the process of organizing itself.
As the authors suggest, paradoxes of organizing are an inevitable side effects of the process of organizing. The best (and perhaps the only) solution lies in learning to live with ambiguity.
Conclusion
In the end, the paradoxes discussed above arise because change evokes feelings of fear, uncertainty and doubt within individuals and groups. When such emotions dominate, it is natural that people will not be entirely open with each other and may do things that undermine the aims of the change, often even unconsciously.
An awareness of the paradoxes of organizing may tempt one to look for solutions. For example, one might think that they might be resolved by “better communication” or “more clarity regarding expectations and roles.” This is exactly what professional “Change Managers” have (supposedly) been doing for years. Yet these paradoxes remain, which suggests that they are natural consequences of change that cannot be “managed away”; those who must undergo the process of change must also suffer the angst and anxiety that comes with it. If this is so, the advice offered by the authors in the final lines of the paper is perhaps apposite. Quoting from Mihalyi Czikszentmihalyi’s book Finding Flow, they state:
Act always as if the future of the universe depended on what you did, while laughing at yourself for thinking that whatever you do makes any difference . . . It is this serious playfulness, this combination of concern and humility, that makes it possible to be both engaged and carefree at the same time.
…and that is perhaps the best advice I have heard in a long time.
A consulting tragedy in five limericks
The consultant said, “be assured,
my motives are totally pure.
I guarantee
my inflated fee
is well worth my ‘best practice’ cure.”
Although it was too much to pay,
this argument carried the day:
consultants hired
can always be fired
and assigned much of the blame.
After the contract was signed,
only then did the client find
the solution bought
would definitely not
help leave their troubles behind.
Cos’ the truth was plain to see,
the ‘best practice’ methodology
had only led
to the overhead
of a ponderous bureacracy.
The shock, the horror, the pain-
all that money and effort in vain,
but the tragedy
is the powers that be
would do it all over again.

