Author Archive
Communication impedance mismatches on projects
Introduction
Most folks have been in situations where something they’ve said or written has been comprehensively misunderstood by the recipient of the message. When this happens it’s as if the other party is on a different wavelength, thus completely missing what’s conveyed. In this post I propose the term communication impedance mismatch to refer to this phenomenon. Below I explain why this bit of jargon, which has its origins in electrical engineering, is an appropriate one to use in this context. I also look at some reasons why communication impedance mismatches are so common on projects. In this connection, readers may also want to have a look at my earlier post on obstacles to project communication.
What’s an impedance mismatch?
So, what is an impedance mismatch? A good place to start is with some definitions from Wikipedia. Electrical impedance is essentially a measure of opposition to the flow of alternating current in a circuit. The impedance of a circuit component depends, among other things, on the frequency1 of the alternating signal. Now, for a fixed frequency, it is possible to adjust the circuit impedance so that power transfer through the circuit is maximised. This is called impedance matching. Basically, if impedances aren’t matched, power transfer through the circuit isn’t optimal.
Impedance matching is the principle behind radio tuning (and hence a connection to communication). In brief, radio tuning works as follows: impedance varies with signal frequency (or wavelength); so, for a fixed impedance, signals of a specific frequency – the tuned frequency – will be “let through” while the others will be “blocked”2. Although I’ve been using frequency as the variable here, I could just as well have used wavelength as the two are related. So, the wavelength metaphor that I used earlier is really quite apt- if the other party is on a different wavelength they will not get the message.
Anyway, this technical term from physics and electrical engineering has a history of being appropriated by other fields (see this post, for example). As an example from software development, the object-oriented programming crowd use the term to refer to the mismatch between data representations in a relational and object-oriented worlds. The term has a nice “jargony” feel about it. And seeing that it’s been appropriated by others before, I have no hesitation in appropriating it for the communication lexicon.
Why are communication impedance mismatches common on projects?
OK, so why am I so fussed about communication impedance mismatches on projects? Here why: at least one study claims that poor communications are the most frequent cause of project failure. It is therefore worth looking at why communication impedance mismatches are so common on projects. Here are some reasons that come to mind:
-
Team members don’t know each other well: A project is, by definition, a time-bound undertaking with a clear start and finish. Hence, in many cases, the people involved in a project would not have worked with each other before. Even worse, they may not even know each other. Such a situation is fraught with the potential for communication impedance mismatches. To alleviate this, it is sometimes recommended that team members spend time getting to know each other before the project begins. This is often done via team building activities, which I confess I’m not a great fan of. I much prefer letting people find their own niche within a team, rather than forcing a false sense of togetherness through contrived activities. Either way, a project manager has to be conscious of the potential for misunderstandings caused by team members simply not knowing each other well enough.
-
Projects are high-stress environments: Projects can be high stress environments, especially when things aren’t going well. Paradoxically, it is when things aren’t going well that good communication is needed. However, in times of stress, one generally finds that communication impedance mismatches rule. Minor misunderstandings can be blown all out of proportion. At such times, a good project manager acts as an impedance matching device, getting all involved parties to communicate with each other on a common wavelength.
-
Communication gap between the customer and supplier: The objectives of customers and suppliers on projects are typically different, and often even contradictory (for example, the customer wants it done cheap whereas the supplier wants to make as much money as reasonably possible). This fundamental tension between the two parties often leads to communication impedance mismatches. These can be resolved by a project manager who understands both points of view, and looks for negotiated, or collaborative, solutions that take into account both parties’ objectives.
These are just some of the reasons for the ubiquity of communication impedance mismatches in project environments. There are a host of others, which I’m sure you may have come across in your work. I’d welcome additions to the list through your comments.
In Conclusion
Communication impedance mismatches occurs whenever communications – written, verbal or otherwise – are misunderstood. They often occur in a project environment because of the temporary and time-bound nature of projects, and also because projects are comprised of parties with conflicting interests. A project manager has to be aware of the potential for communication impedance mismatches, so that he or she can act to reduce them before they cause unnecessary strife.
1The standard mains frequency is 60 Hz (or cycles/second) in the US and 50 Hz elsewhere..
2I couldn’t find any good, non-technical online references, but see this short explanation or this longer one in Yahoo Answers for more..
A memetic view of project management
A few days ago I came across an interesting perspective on project management put forward by Jon Whitty, an academic who teaches at the University of Southern Queensland. Whitty’s view, which he published in a paper entitled A Memetic Paradigm of Project Management, presents a somewhat heretical take on the discipline of project management. In this post I outline and comment on some of the essential points made in the paper.
Whitty begins with the uncontroversial statement that project management, by and large, fails to live up to the expectations of stakeholders. This is well documented by studies such as the Standish Report, so needs no further explanation. To quote Whitty, this widespread failure suggests that academics and practising project managers “…still do not really understand the nature of projects, and that too much research effort has been directed towards clarifying the reasons for project success and failure, while downplaying research on why projects exist and behave as they do …” Whitty believes that the current paradigm of project management cannot help us understand the true nature of projects. Instead, a more critical approach, which considers projects to be a “…human construct, about a collection of feelings, expectations and sensations, cleverly conjured up by the human brain…” might be a more fruitful way of looking at projects. Here’s where the memetic bit comes in. I expand on this in the following paragraph.
The term meme was coined by the evolutionary biologist Richard Dawkins in his book The Selfish Gene, in which he presents the idea that the genes that survive evolution (i.e. those that are passed on) are the ones whose characteristics serve their own interests. In other words, genes act “selfishly”, to propagate themselves. In the book he draws an interesting parallel between this view of biological evolution and that of the evolution and propagation of ideas. Ideas, according to Dawkins, propagate themselves through assorted means ranging from education to mass media. A meme is basically an idea (or any unit of information) which gets transmitted (from person to person) through communication or repeated action. It is important to note that a meme isn’t just any random, fleeting thought; it is an idea that is transmitted with a fair degree of fidelity. Some examples of memes are: a folk tale or a joke (or even a methodology!).
Now, with that explanatory detour out of the way, I can get back on topic. In the paper, Whitty suggests that the discipline of project management should be viewed as a collection of related memes which propagate as a group (such groups of memes are called memeplexes). With the background of the previous paragraph, this isn’t surprising at all- basically any academic discipline or professional practice can be considered so. The implications of considering project management to be a memeplex are interesting, and form the main focus of Whitty’s paper. I look at a few of these in the following paragraphs.
A basic consequence of a memetic view (of any discipline) is that it turns the notion of knowledge being created by scholars or practitioners on its head. Memes create the scholars and practitioners, rather than the other way round! This isn’t as strange as it sounds, if one thinks about it for a while. For instance, project management as a discipline has given rise to various standards, bodies, certifications etc. thus legitimising it as a profession. To gain acceptance into the community of project managers, an aspirant subscribes to standards, joins professional bodies and gains certifications, thus being created by the memeplex.
The rapid development of project management as a discipline is a memeplex characteristic. In the last decade or so, there has been a huge growth of membership in professional bodies. Further, in universities and business schools, project management has gained legitimacy as a sub-discipline of management, with all the attendant trappings such as journals, academic conferences, textbooks etc. In a memetic view, all this only serves to propagate the memeplex. Whitty raises the concern that “…a large amount of memes in the PM memeplex are today being generated and replicated by University Business Schools. Moreover, as we continue to define organisational success in monetary terms our education sustems seem more naturally an extension of corporate training…” The implication being that the memes propagated aren’t necessarily good or correct, because their propagation is driven by a lopsided notion of what is good.
One can take the argument even further. Project management, as it is practised, consists of a set of mental models – ways of looking at how things work in the real world. One example of such a model is a project plan, which serves as a representation of the project from start to end. Project management texts are vehicles for recording and propagating such mental models (which are nothing but memes). The important point is that new knowledge is always seen through the filter of existing knowledge. So, the chances of a radically new idea making it through to mainstream are small, simply because it is seen through the lens of existing ideas. Radically new ideas are typically discarded as the memeplex propagates or evolves. This, too, isn’t a limitation of project management alone; it’s true of any discipline.
The paper has a lot more than I can go into in the space of a blog post. So, rather than continue my second-hand account, I’ll refer you to the original piece for more. I’ll sign off here with one final nugget from the paper: Whitty draws attention to the fact that false memes frequently get propagated along with true ones. The point is, once ensconced in mainstream thought, an incorrect idea gets the stamp of legitimacy and thus becomes almost impossible to question or correct. In contrast, a memetic approach – wherein it is known that propagated memes aren’t necessarily correct – recommends that practitioners be critical of ideas and practices handed down by authority. That, in the end, is excellent advice for us all, regardless of whether or not we agree with Whitty.
Capturing and using knowledge in project-based organisations
Many organisations find it hard to capture and use knowledge effectively. This problem is especially acute in project-based organisations because project teams – the primary “generators” of knowledge in such organisations – are temporary structures which are disbanded when a project’s completed. Hence most project-based organisations emphasise (and enforce!) the capture of knowledge through end-project activities such as project post-mortems, documentation etc.
That’s fine as it goes, but capturing knowledge is only a part of the story. There is the other (not so small) matter of using it. Here’s where most efforts fall flat – all that supposedly useful knowledge is rarely used. This is the point addressed by Katrina Pugh and Nancy Dixon in a short note entitled, Don’t Just Capture Knowledge–Put It to Work, published in the May 2008 issue of Harvard Business Review. Pugh and Dixon suggest using what they call a knowledge harvest– an approach aimed at capturing knowledge and putting it to use. In brief, a knowledge harvest consists of:
-
Identifying those who might find the knowledge useful. Pugh and Dixon call these people knowledge seekers. These folks are interested in the knowledge on offer and so already have the motivation to learn. In projectised organisations, programme managers have a broad view of project activity, and can thus help identify suitable seekers to participate in knowledge capture (or harvesting) sessions.
-
Involving knowledge seekers in harvesting sessions. The idea here is that seekers, being self-motivated, will ask pointed questions aimed at extracting information that is often left out of typical post-project documentation. They might, for instance, ask probing questions regarding what went wrong and why; points that are often glossed over for political or other reasons.
In their note, Pugh and Dixon present a case study where this method was used successfully in a project situation. Following the initial success of the technique, it has been adopted by other programmes within the organisation that was the subject of the study.
This simple technique has much to commend it. For one, conversation is a more effective way (than documentation) to get at tacit knowledge. The presence of knowledge seekers at harvest sessions improves chances that the right questions – i.e. those that “tease out” tacit knowledge – will be asked. Secondly,the captured knowledge will almost certainly be used since seekers are identified by their interest in what’s on offer. Finally, if seekers find the knowledge gained to be useful on their own projects, they’ll pass it on to other seekers in harvesting sessions down the line, thus ensuring what’s learnt becomes a part of organisational memory.

