A long time ago, I proposed an important change to a committee of senior colleagues. The overall intent was hardly arguable, and I had carefully thought out the details. Overall, it got a good hearing. But then the trouble started. One manager picked on a point of detail which he didn’t like. OK, I thought, I can find a way round that. But then other managers piled in, some supporting my position on that, but objecting to different details. The discussion descended into a squabble about detailed points on which no-one could agree, and as a result the whole project was shelved despite its overall merits.
I learnt an important lesson from that experience. When a collective decision is required, detail is your enemy. Most projects will have – or at least may be perceived to have – some negative impacts on some people, even though overall they benefit everyone. Maybe someone loses autonomy in some area, or needs to loan some staff. Maybe there is some overlap with a pet project of their own. Whatever the reason, providing detail at the outset makes those losses visible, and can lead to opposition based on self-interest (even if that is well-concealed) which kills the whole project. As we all know, you can’t negotiate with a committee.
So what is the answer? The approach I have found works best is to start by seeking agreement for general principles with which the implementation must be consistent. The absence of detail means that the eventual impacts on individual colleagues are uncertain, and consequently the discussion is more likely to stay focused on the bigger picture. Ideally you are given authority to implement within the approved principles. But even if you have to go back with a detailed plan, once the committee has approved the outcome and the principles to be followed it is much harder for them to reject a solution that sticks to those, let alone to kill the project.
Looking at the wider world, perhaps the Ten Commandments of the Bible provide a good example of this approach. For a more business-relevant example, see my earlier posts on the principles behind good internal governance.
More generally, defining top-level principles is also the key to delegating decision-making to local managers. It means that they can make decisions which take proper account of local conditions, while ensuring that decisions made by different managers in different areas all have an underlying consistency.
I once worked for a young organisation with big ambitions. The managers were all highly experienced, but had only recently come together as a team. They decided to contract with a long-established and very stable international firm to help with operations.
I don’t think anybody was expecting what happened next. The partner firm arrived, and immediately started to call the shots. Needless to say, hackles rose amongst my colleagues – we were the customer, after all: isn’t the customer always right? It took some considerable (and uncomfortable) time to make the relationships work.
What happened? This was all about organisational maturity. The partner organisation had well-established ways of doing things and strong internal relationships. Everyone knew what they were there to do, and how it related to everyone else. They knew that their colleagues could be trusted to do what they expected, and to back them up when necessary. That organisational maturity gave them a high degree of confidence.
My organisation, on the other hand, had none of that. Although individuals (as individuals) were highly competent and confident, there had not been time for strong relationships to develop between us. Although there would be an expectation of support from others, without having been there before certainty about its strength, timeliness and content was lacking. In those circumstances, collective confidence cannot be high. Eventually our differences were sorted out, but it might have been quicker and easier if the relative lack of organisational maturity and its consequences had been recognised at the start.
Confidence comes not just from the confidence of individuals. It is also about the strength of teamwork, and a team has to work together for some time to develop that trust and mutual confidence. When two organisations interact, expect their relative maturities to affect the outcome.
Many years ago I used to make pottery as a hobby. After a few years I got to be good enough that friends sometimes asked me to make pots for them. Of course, that is when things start to get a bit difficult – what to charge them? I could have said “I’m a hobby potter – if I cover my costs, that will be fine.” But then, if a friend asked me to make something (in principle at least) it was instead of buying from someone who was trying (and mostly struggling) to make a living out of potting. For someone like me to undercut them seemed wrong. I always charged about what I thought they would have had to pay a ‘real’ potter for something similar. That way I felt that they were choosing my work just because they liked what I made. When I explained, everyone thought that was fair.
Over the years, I have learnt just how important it is to value yourself appropriately. I once took a job at a rather lower salary than I had been used to, rather than continue the uncertainty of searching until I found a better one. I discovered that because I had accepted that valuation of myself, understandably everyone else did too. The job didn’t challenge me, so I got bored, but it seemed to be impossible to persuade anyone within the organisation that I could be adding more value if only they would ask me to work on some more difficult problems – of which there were plenty. The job I was doing needed to be done. Before long, I left to go to a job at a more appropriate level.
This can be a difficult balance for an interim manager. Price is only an imperfect proxy for the value of the job, but what a customer expects to pay is usually a good indication of how they see it. We all need to pay the bills, but accepting a disparity in price perceptions is not usually a good basis for a satisfying relationship in any kind of transaction.