Separating the men from the boys

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.

Getting very wet

[caption id="" align="alignright" width="300"]team leadership Frigate Type M silhouette (Photo credit: Wikipedia)[/caption] When I was at school I was in the cadets. One of the exciting consequences was that we would sometimes be taken off for a weekend to do training exercises at a Naval base, and one exercise we did taught me important lessons about team leadership which stick firmly in my memory to this day. The exercise was to practice damage control on a warship. Not a real ship, of course, but a mocked-up ship’s compartment on the shore. At least there was no danger of sinking! About a dozen of us were shut in the compartment with all the tools and materials we needed to stop the leaks. Then they turned the taps on. No ordinary taps - the water level in the compartment was rising inches every minute. What happened next amazed me. Out of all the boys in there, just three of us immediately started to do what was needed to fix the leaks. Everyone else just tried to keep out of the way. And of the three, none were the normal leaders in the group – not the best sportsmen, nor the oldest, probably not the most self-confident.

Team leadership

So what happened? The situation was one which demanded just getting stuck in and doing what was necessary, regardless of ‘position’. Those who were used to being asked to lead found themselves bypassed – there was no time for asking, even if it had occurred to anyone to do so. Team leadership arose instinctively, and was not authoritarian but part of a team effort. The team assembled within seconds with no discussion, did what it needed to do – and then vanished. What does that story tell you about leadership? First, that leadership is not the same thing as authority that is granted, does not depend on it, and may not be found in the same places. Second, that circumstances may create leaders. And finally, perhaps most importantly but also perhaps confusingly, that to lead well it helps to see yourself as part of the team you are leading. Not all managers are also leaders.

Celebrate Failure!

[caption id="" align="alignright" width="300"]celebrate failure English: neck of bottle of champagne (Photo credit: Wikipedia)[/caption] What? Don’t you mean success? Well, no – although that is worth celebrating too. I came across the idea that you should celebrate failure recently in “Co-active Coaching”[1], and it makes a lot of sense. People rarely fail at things because they didn’t really try – or at least not at things that matter. First they had to find the courage to attempt something which they knew might to expose them to failure. Then, wanting to avoid failure, they tried hard, probably attempting things they had never done before. Finally they had to admit they had failed - even though in the process they had probably achieved more than they ever thought possible. All of those things are difficult, and worthy of celebration in themselves. But there is more to it than that. Failure is an excellent teacher! When you fail, you have to face up to things you tried which did not work. Often you will want to understand why they did not work, and this may lead to more success next time. There is also a less obvious reason. When we are criticised, blamed and shamed for failing, it usually has the desired effect of making us very keen to avoid failing again. Unfortunately, the consequences of that very understandable urge are not necessarily to make us try harder. We are very likely to learn to avoid taking the risky option in the first place, or to limit the options we consider only to the ones which appear ‘safe’. You can’t stop failure hurting, but instead of adding to the hurt, celebrate failure – the courage, the effort, the learning involved – and at the same time create a culture in which even risky options can be seriously considered.

[1] “Co-Active Coaching” By Henry and Karen Kimsey-House, Phillip Sandahl and Laura Whitworth