‘A crisis’ – the name for a group of dysfunctional experts.

Many years ago, the Badger took a late morning phone call from his boss asking him to pop into his office for a chat. A reason for the chat wasn’t mentioned, and so it was with a little trepidation that the Badger took the lift to the floor where his boss’s office was located. On approaching, the Badger saw his boss through the open door with elbows on the desk, head in hands, looking morose. Sensing the Badger’s arrival, his boss sat back, smiled, asked for the door to be closed and waved the Badger to a seat.

‘What’s the collective noun for a bunch of experts responsible for designing a huge software intensive system on a fixed-price contract?’ the Badger was asked in a relaxed manner. His boss didn’t wait for an answer. ‘A crisis’, they said with irritation and a flourish of colourful language that would cause apoplexy today. They explained that this answer derived from problems on a multi-tens of million pounds, fixed-price IT development project with a dysfunctional Design Authority (DA) team. This team, apparently, was full of acknowledged experts who seemed incapable of agreeing or deciding anything that was crucial to the progress of the overall project team’s software developers. At the start of the project line management had apparently insisted on staffing the DA team with experts who’d been between assignments and non-revenue earning for some time. The Badger’s boss admitted that, in hindsight, it hadn’t been wise to allow this to trump an individual’s technical and personal suitability for the project.

The Badger was then asked to sort this out and get the project back on track! He joined the project with an open mind and quickly assessed the situation. There were some leadership and management dynamics to adjust, but the DA team was indeed the key problem. Its members were all respected experts with specialist knowledge, but each was focused on expanding and protecting their expertise rather than the big picture and the project’s fixed price delivery. Teamwork, within the Design Authority itself and with the rest of the project, was poor. Experts can add enormous value to any team if used correctly, and so the Badger carefully considered how to rectify the situation. He repopulated the Design Authority with good people drawn from other parts of the project. The experts were released to their home units to be used a couple of days a month for consultancy if required by the new DA team. The experts and their line managers grumbled, but the project went forward to success.

The point of this tale? Simply to highlight that experts who keep their egos in check, never lose sight of the big picture, and have both specialist knowledge and the personal characteristics for teamwork, are valuable assets on tough delivery projects. Those that don’t have all of these attributes are more suited to short term specialist consultancy…

Are Management Consultants useful and good value?

A recent item about Management Consultants made the Badger chuckle. It’s  worth a quick read to see if anything resonates and makes you chuckle too. The Badger giggled because the narrative struck a chord and made him remember one particular encounter with a ‘management consultant’ while he was leading the delivery of a very large, fixed-price, IT systems and service development contract for his company. This delivery was a key part of an overall public sector programme transforming the workings of an entire industry. Inevitably, this overall programme was mired in politics, resistance from some quarters of the industry, and commercial gamesmanship by some of the parties involved to ensure they avoided blame for any difficulties the overall programme might encounter.

In private, every party believed the overall programme would be delayed. Their public stance, however, was different because the commercial ramifications of being blamed for delay were punitive. Most expected the key, critical path, IT delivery from the Badger’s team to be late. His magnificent team, however, delivered a system of quality on time, and in doing so exposed unreadiness and delay in other key parts of the overall programme. The overall programme’s stakeholders appointed management consultants from a well-known company to review and advise on the situation, and the Badger, in due course, spent an afternoon being interviewed by one of them. He didn’t come away from the session with much respect for management consultants.

As soon as initial pleasantries were complete, the Badger wondered how the expensive, brash, sharply suited, intelligent but over-confident, youngster in front of him could be a ‘management consultant’ when they were just a few years out of university and simply executing a process with a long list of associated questions. They had no real business, project, programme, or leadership experience, but they had clearly read many books, and drafted many reports and PowerPoint presentations. There was no discussion, just questions with the Badger supplying increasingly curt answers. The interviewer’s brash confidence and superficial real experience was irritating, and their credibility as a consultant providing value dissipated with every question. Two weeks later, the programme’s stakeholders received the management consultants’ overall report and supporting presentation. Both were stylish and well-written, but contained little that stakeholders didn’t already know. It didn’t seem like value for money!

You might think from this that the Badger has a low opinion of management consultants? In fact, he has engaged with many over the years and developed great respect for those who have become management consultants after years of important roles in business, industry, or project delivery. They are useful and provide significant value. Those, however, who call themselves management consultants, have expensive fee rates, but do not have such underlying experience are not great value for money. You may, of course, feel differently…especially if you are a management consultant.