Category: Project Management

Are optimists, pessimists, or realists the most successful leaders?

Posted on by The Information Badger in Information Technology, IT Project Management, Leadership, Leadership & Management, Project Management, Psychology, Risk

The Badger was asked many times during his career to engage with delivery and business leaders encountering serious problems delivering a contracted project to requirement, time, and budget. These requests were often initiated by the company’s Chief Executive who simply asked the Badger to ‘chat with those responsible and see if you can help’. They knew the Badger would interpret the request as ‘get stuck in and get the  problems on this contract resolved’. Being aware of the personal traits of the people you deal with, especially those in senior positions, is crucial to interpreting what they really mean when they ask you to do something!

One such ‘how can I help’ conversation with a business leader proved memorable because it spawned a hypothesis that the Badger feels has been validated over the years. Although we knew each other in passing, it was the first time we had met for any substantive conversation. After some initial chit-chat, the business leader quickly focused on describing the delivery, financial, and contractual difficulties of their project. They had, apparently, already spoken to a couple of experienced staff about helping to resolve the difficulties, but neither was, in their eyes, suited to the task. They described one as a cheery but superficial, glass-half-full optimist, and the other as a pedantic, too laid-back, glass-half-empty pessimist. The Badger remembers wondering how he would measure up!

After an hour’s discussion, the business leader asked the Badger to help resolve the project’s problems, adding that ‘you are a realist and you don’t care whether the glass is half full or half empty, only that the glass is a receptacle to be filled with as much liquid as possible’. Their comment spawned a hypothesis in the Badger’s mind, namely that the delivery and business leaders who have the most success, and also the longest careers, are realists. Engagements with many diverse business and delivery leaders over the years have tended to reinforce the hypothesis.

Being a realist means having a personality with a propensity to take measured risks and take measured decisions. It doesn’t mean never demonstrating optimism or pessimism. Those with an optimistic, glass-half-full, leaning tend to be less risk-conscious, while those with a pessimistic, glass-half-empty, leaning tend to have little appetite for risk at all! During COVID-19, for example, glass-half-full characters might have seen themselves as less at risk and taken less precautions, whereas those with a glass-half-empty outlook might never have left their house at all. Realists, on the other hand, would have taken measured risks based on knowing that the virus’s impact mainly depended on age and underlying health.

The Badger’s seen glass-half-full, and glass-half-empty leaders be successful, but it’s the realists who’ve been the most successful and had the longest careers. Is the Badger’s hypothesis sound scientifically? Don’t know, but he’ll stand by it until a proper people expert shoots it down in flames!

Being moved to a new system shouldn’t mean the services in a customer’s account go backwards…

Posted on by The Information Badger in Energy and Energy Markets, Information Technology, Online Services, Project Management, Transformation

Two emails from the Badger’s energy provider made him cogitate on his account being moved over a year ago to a new billing system. The move has resulted in less functionality in his online account than with the old one. If companies want customers to engage with them using online accounts and smartphone apps, then surely a transition to a system that provides customers less online functionality when logged into their accounts indicates that something’s awry behind the scenes?

The first email notified the Badger that his energy bill was available in his online account. The second, entitled ‘We need your help’, was a request to answer a few questions related to customer satisfaction and customer service. The Badger logged into his account to look at his bill. He sighed, just as he has on each login since February 2022 when his provider moved his account to their new system. The Badger’s been with this provider for some years, and it used to be easy to track energy usage and cost trends, payments, and to see local comparative information in a useful customer-friendly way. Given the climate crisis, the need to reduce fossil fuel usage, and the pandemic, these facilities were particularly useful. Sadly, being moved to the new billing system meant these facilities, which require access to historic data on the old system, were no longer available. Prior energy data was not migrated to the new system. The move effectively meant becoming a new customer on a new system providing only rudimentary online services for meter readings, bills and payments.

There’s been no change in the rudimentary facilities in the Badger’s online account since being moved to the new system. Instincts honed from decades in the IT industry have driven the Badger to think that the energy provider’s move to a new billing system has proved more problematic behind the scenes than expected. If this is the case, they will never admit it! Moving from older systems to new ones is always a challenge for any company. It’s always difficult to effect the transitions that a company needs to make for its own purposes without upsetting some customers, but if customer online account services go backwards and stay that way for a year or more, then either the change hasn’t gone as planned or the company is disdainful of its customers – or both.

After logging in this time, the Badger decided that his days as a customer with this provider are numbered. He answered their ‘We need your help’ email with some clear points, but it will make no difference. Why? Because as one of the big six energy suppliers to UK customers, their perpetually mediocre customer service scores imply that customers are not really a high priority. So, who’s the Badger’s provider? Look here and see if you can guess…

Problematic underperformers – the dog must wag the tail!

Posted on by The Information Badger in Business, IT Project Management, Leadership & Management, Project Management, Risk

As the first day of a conference broke up, attendees moved to the venue’s bar to network, gossip, and share thoughts about the day’s sessions. A young project manager, however, sat alone in the venue’s lounge looking as if the world rested on their shoulders. The youngster smiled weakly and raised a hand in recognition as the Badger walked by. ‘Why so glum?’ the Badger asked before sitting down in an adjacent chair. ‘An underperformer is proving to be a problem that’s jeopardising the success of my project’ came the morose response.

The youngster explained that a person on a team on the critical path of the project was seriously underperforming, proving impossible to manage, and putting at risk the timely completion of contractual deliverables. The person had apparently been troublesome from the outset, but their team colleagues were now vocally grumbling because this individual was always late for work, always left on time at the end of the day with their work unfinished, and always blamed others for their poor productivity and low quality output. The individual also complained about everything! Performance management processes were in progress, but the person was using every nuance, ambiguity, and avenue for defence in the system to frustrate their execution. The young project manager asked if the Badger had any thoughts.  

The Badger stated that a rule of thumb which had stood him in good stead throughout his career was that ~10% of individuals on a project were underperformers.  Most were good people who were either in a role unsuited to their talents, or juggling with challenging personal or family situations, or both. Most did not poison a team’s spirit or damage overall output. A small proportion of underperformers, however, were truly work-shy individuals, with poor capability and often obtuse personalities, and somehow they had slipped through in the company recruitment processes. These individuals often distracted management, poisoned morale, and destroyed team spirit and the productivity needed for a team and project to succeed. The Badger said that he’d learned that these individuals must be dealt with by those in leadership positions in line with formal processes, but swiftly and decisively if positive project dynamics were to be preserved.

The youngster whined that diversity, harassment, and anti-discrimination policies made their ability to take swift, decisive, action more difficult. The Badger shook his head and simply reinforced two points, namely that a) their primary responsibility was to deliver to their client on time, to budget, and in line with their contract, and b) that allowing a poison apple to infect the fruit in the whole barrel was a leadership failure!

Later that evening the youngster bought the Badger a drink in the bar and said they’d made some phone calls and removed the problematic individual from the project. ‘I’ve learned’, they said, ‘that leadership involves decisions, judgements, and the dog wagging the tail, not vice-versa!’  Quite!

Walking out of a meeting with a client…

Posted on by The Information Badger in Business, Delivery, Information Technology, IT Project Management, Leadership & Management, Learning, Project Management

‘Meetings, meetings, meetings!’, a delivery leader exclaimed irritably after a session with a client who had given them the verbal hair-dryer treatment about an imminent milestone and its associated payment. ‘They don’t want to pay, even though we’ll have met the milestone in full’, the leader grumbled before berating themselves for not having walked out of the meeting. The Badger smiled. Memories of his own difficult meetings with clients came flooding back.

Notwithstanding the comprehensive training in meetings and negotiations that companies provide, it’s real experience in difficult client meetings that hones your  approach to getting the right outcome. The Badger’s approach developed over the years to have essentially three things at its core. The first was that the client is not always right, and that being in command of irrefutable facts, and using them calmly, consistently, and assertively rather than petulantly and confrontationally, is crucial to getting the desired outcome. The second was mental resilience, to have as much background to the client’s position as possible, and to decide tactics that are unwaveringly focused on the desired outcome, before the start of the meeting. The third was to always have a walking out option in the kitbag as a weapon of last resort, but not for use to assuage personal ego or frustration.

Had the Badger ever walked out of a client meeting, the delivery leader asked? Yes, but rarely. One occasion was some months after a system with a fractious delivery history had become operational with a client’s end-users. The meeting was to a) formalise that the delivery contract’s deliverables had all been delivered, and b) that the client would make the final payment due and close the contract. It should have been a formality, because the client’s staff had already confirmed everything had been delivered to contract and to their satisfaction. Item (a) was indeed confirmed at the meeting, but the client refused, without giving any reason, to pay the outstanding money.

During a break, the Badger and his team agreed we were wasting our time because the client had no intention of paying. After the break, the Badger asked the client to confirm that although no contractual deliverables remained, they would not pay the money due. They confirmed this, and the Badger got up and left followed by his team. The shock on the client’s team faces was palpable. It was not something they’d anticipated!  Payment was received three days later after the Badger’s CEO phoned the chairman of the client’s Board of Directors to complain and threaten litigation if users continued to use the system.  

With a twinkle in their eye, the delivery leader looked at the Badger, grinned broadly, and said ‘I was wise not to have walked out. If I had, the client might have thought I was a petulant, over-sensitive, snowflake with no backbone’.  The Badger laughed aloud…

‘Why haven’t we learned lessons from other problematic projects?’

Posted on by The Information Badger in Delivery, Information Technology, Learning, Processes and Practices, Project Management

Early in the Badger’s career, when he was part of a team sorting out a large software and systems project with serious problems, the CEO of the time angrily asked the line manager responsible for the project ‘Why has this happened? Why haven’t we learned the lessons from other problematic projects?’. The line manager’s answers were ill-considered waffle and only served to ratchet up the pressure from, and antagonise, their boss.  

At that time, projects involving anything IT related were notorious for serious timescale and cost overruns. IT was a young, rapidly growing industry, and software development was seen as black magic performed by very clever people. Disciplined software engineering processes were rudimentary, and most programmers were graduates from enormously diverse STEM-subject, rather than computing, backgrounds. The Badger’s first software team leader, for example, had a Civil Engineering degree and a master’s degree in Water (sewage) Treatment!

In the decades since,  IT companies have improved and evolved their management and  engineering policies and processes – their ‘company manuals’ – because it was necessary to stay in business. Today, a continuous improvement ethos that feeds lessons learned into policies, processes, and practices is a norm, and software and systems engineering is more standardised and rigorous. Companies still have troublesome projects, but there are fewer of them, and they are detected earlier and addressed faster.

And so, the Badger’s interest was piqued recently when he heard a CEO calmly ask a line manager the same questions as above. The line manager answered with three points that struck a chord with the Badger’s own experience. The first was that in recent years annual staff turnover of between 12 to 15% had diluted the continuity of knowledge because nearly half the workforce had changed. The second was that clients want the capabilities of evolving innovative technology much faster and cheaper, which means that projects can encounter more skill and experience issues than envisaged at contract signature. The third was that feeding lessons learned into management and engineering policies, processes, and practices and embedding awareness in the workforce needed a greater company willingness for those who had lived the project experience to spend more time as ‘overheads’ rather than revenue earners.

The CEO calmly agreed, and then said something which also aligned with the Badger’s experience, namely ‘Our company’s policies, processes, and practices will never be perfect. If we want fewer project difficulties, then we must get project people to just talk more to each other and willingly share their experience’.  And there you have it. The fastest way to learn lessons is for people to just talk to each other. Projects depend on people, and people have different personalities, motivations, strengths, and weaknesses, and never do quite what you expect! That’s why troublesome projects will never be eradicated completely and continuous improvement is always a challenge.  

Upset your client and spoil your career…

Posted on by The Information Badger in Delivery, IT Project Management, Project Management

What’s the saddest thing you’ve see happen o someone you’ve been working with? Bereavement is excluded; the answer must be something the person has inflicted on themselves. A youngster, chatting to the Badger socially, asked this very question the other day. Surprised, the Badger played for time and asked what had prompted the question. They shrugged their shoulders, and simply said that a couple of their project team lacked common sense and sadly seemed oblivious that this was spoiling their career prospects. The conversation was interrupted by someone else, and so the Badger didn’t get to answer their question, but if he had, it would have been along the following lines.

One instance of the saddest thing someone inflicted on themselves comes to mind because it illustrates what can happen when a personality with embedded behaviours gained at one company, proves to be mismatched at another company in a different sector.  The circumstances were as follows. A senior delivery leader was recruited by the Badger’s IT sector employer from a large international defence company to run a major, fixed-price, high-profile IT contract of strategic importance to the client. The printed contract documentation filled numerous lever arch files and the person recruited, who joined the company before contract signature to lead mobilisation and then delivery, insisted on having an A5-size printed copy for their briefcase.  

Grumblings soon emerged as delivery got underway and the individual became the focal point with the client. Tensions within the individual’s team, due to their self-important, patronising, ‘I know best’ personality and an approach to delivery ingrained at their previous employer, also quickly became evident. The team started disengaging from their leader because of their arrogance, failure to listen, and inept people skills. Ever louder grumblings from the client came because the individual reached into their briefcase at the start of every client meeting, theatrically put the A5 copy of the contract on the table, and then referenced or checked it as part of every conversation. Client requests, and those from company executives when the client escalated, not to do this were ignored. A contract is never an irrelevant document, of course, but there’s a time and place for waving it about and it’s not in every meeting! Eventually the client refused to have any dealing with the individual.

Seeing the individual damage their career by failing to recognise that their modus operandi was upsetting the client and damaging the effectiveness of their own team was very sad. They were moved, never ran a delivery again, and never accepted that the spoiling of their career was self-inflicted.  There are always exceptions, of course, but upsetting your client and your team by letting arrogance and self-importance dominate your modus operandi, is almost certainly going to spoil your career. Keep this in mind if you don’t want to spoil your career and be someone else’s saddest thing anecdote…

Wisdom for a first-time Project Manager…

Posted on by The Information Badger in Delivery, Information Technology, IT Project Management, Leadership & Management, Project Management

A book called ‘There’s a New Sheriff in Town: The Project Manager’s proven guide to successfully taking over ongoing projects and getting the work done’ was published recently, and the Badger, whose career centred on the many aspects of delivery in the IT business, is currently reading it. The book’s lengthy title, as it happens, also reminds the Badger of his very first assignment as a project manager, many, many years ago!

After working as an analyst-programmer and design authority on a number of sizeable software development projects, the Badger’s line manager took him to one side to say that his next assignment was to take over as project manager on a software and systems development project that was completely off the rails. The young Badger had no project management experience and expressed his surprise!  The line manager cited two reasons for why they had no doubt that the Badger was the right person for the job. The first was that the Badger’s character, experience, and latent capabilities were highly suited to sorting out the poor engineering and technical matters at the heart of the project’s problems, and the second was that most aspects of project management were always best learned on the job! Being thrown in at the deep end, they added, was nothing to be fear.  

Somewhat daunted, the Badger chatted to an experienced and consistently successful manager of difficult software intensive projects who gave three pieces of advice.  The first was ‘ You will fail if you fall into the trap of believing project management is about administering the processes in a project management handbook. It’s really about leadership, and showing the character, resilience, vision, drive, and professionalism to get the job done’. The second was ‘Most project management books are not written by people with a software or IT, so most are a distraction and won’t help get the job done or make you real project manager’. Things have moved on significantly since the time when there was a paucity of books about managing projects in the IT world, but the inherent not being overly distracted reading books still has some validity. The third point was ‘If you are replacing a current project manager who has lost the confidence of line management then remember that if you do what they did, you’ll get what they got!’  This was their way of saying be different, be focused, and be aware that you can be replaced too!

So, if you find yourself being appointed as the new sheriff in town on an ailing IT project, and it’s your first role as a project manager, don’t be fazed. Be a leader not just an administrator of process, be motivated to listen and learn, be focused, and know that these days there are books like the one above that can help by providing many nuggets of wisdom gleaned from experience…  

Troublesome projects…and Bertrand Russell

Posted on by The Information Badger in Business, Delivery, Information Technology, Project Management

Line managers always get pressure from senior executives to take swift action when a project they’re responsible for experiences serious difficulty. Line managers, especially inexperienced ones, often assuage this pressure by quickly changing the Project Manager. This often-knee-jerk response doesn’t always fix the problem because although the new appointee may be conveniently available, they may not have the breadth of personal, commercial, delivery and technical characteristics needed, or be properly empowered. One of the Badger’s experiences of being appointed as ‘the new project manager’ by a panicking line manager proved not only to be reminder of the strength and diversity of character needed to turnaround a troubled project, but also a memorable introduction to Bertrand Russell.

The project in question was not meeting its contract with an international prime contractor who was delivering a huge strategic programme for their end customer. The Badger’s remit from the line manager was ‘fix everything’ because the finances are perilous, and litigation is looming. Senior executives from all the organisations involved had met in a last ditch bid to avoid an expensive, embarrassing, catastrophe for all concerned. They had agreed to leadership changes and so the Badger found himself appointed at the same time as a new opposite number in the prime contractor.

Our first engagement shortly after being appointed was at a meeting involving both of our respective incumbent team leads, ostensibly as an opportunity for them to air their thoughts and feelings about the contract’s difficulties. The two teams were polarised, divergent, defensive, inconsistent, and in blame mode from the outset! After a particularly fractious exchange, the Badger’s new prime opposite number called a halt for a coffee break and took the Badger to one side. The badger was asked if he was familiar with Bertrand Russell and two of his famous quotes, namely:   

  • The fundamental cause of trouble is that in the modern world the stupid are cocksure while the intelligent are full of doubt.
  • Collective fear stimulates herd instinct and tends to produce ferocity toward those who are not regarded as members of the herd.

The Badger said no. His counterpart then used these quotes to make the point that if we could both see the problems and resolutions but were full of doubt and worry about being different to our incumbent teams, then nothing would change, and litigation beckoned. We agreed that we were not stupid, not members of the herd, only focused on finding solutions, unmotivated by personal kudos, and that we expected to take  unpopular decisions. Following this conversation, we both did difficult things with our teams and the turnaround started.

So, remember this. To fix a troublesome project needs a focused and resilient character, intelligence and a breadth of skills, and some awareness of Bertrand Russell’s wisdom!Anyone full of self-doubt or worried about being an outsider is unlikely to succeed.

Setting the bar too high…

Posted on by The Information Badger in Business, Delivery, Education, Information Technology, Leadership, Learning, Project Management

In his school days, the Badger was in the school field athletics team because he was good at javelin, long jump, and – rather surprisingly for someone of average height – the high jump. It was, according to the team coach, the Badger’s natural technique rather than any specific physicality that underpinned why he was good at these events. The coach, a resolute athlete who demanded the same dedication from others, had two favourite phrases to encourage team members to train hard and do better. The first was ‘technique is the difference between reliable success and reliable failure’. The second, used especially for the high jumpers, was ‘you don’t jump high unless you set the bar high’. Little did the schoolboy Badger know that he would regularly hear leaders and managers utter this one throughout his working life!

The Badger’s often heard executives say ‘you don’t jump high unless you set the bar high’ when setting an expected, imperative outcome that is challenging, and when trying to persuade their audience that the challenge is tough, but the outcome is within reach. These last few words, however, are crucial because if an audience don’t sense that the outcome is within reach then they will nod sagely, consider argument futile, and only work half-heartedly towards the objective. If that happens then the road ahead will almost certainly be full of disappointment, blame, low morale, problems, and financial under-performance.

For many leaders and senior staff in sizeable organisations, attending an annual gathering at which executives set out the key priorities and targets for the coming year is routine. The Badger’s attended many such events over the years, and whilst fundamentally there’s nothing wrong in using ‘you don’t jump high unless you set the bar high’ to set ambitious targets, two observations crystallise from the experience. The first is that if the audience sense the challenging target is reachable then they will embrace it, fully align their support and activities, and executives will hold onto their jobs. The second is that if the audience feels the bar has been set so high that you need binoculars to see it, then they will pay lip-service to the challenge, gossip about the credibility of executives, worry about the enterprise’s viability, and speculate about whose heads will roll when outcomes are not met.

The point is simply this. If you are the leader in a company, project, programme, or service, then don’t lose touch with reality or your people. If  you set the bar way too high, then you will have an unhappy workforce, people will leave, output and quality will decline, financial forecasts will not be met, and your credibility as a leader will be damaged. The best leaders stay grounded in reality, make good judgements that balance competing soft and hard priorities, set the bar within reach, and communicate honestly and inspiringly. Those that don’t ultimately suffer the consequences.

Describe the dynamics of today’s digital world in one word…

Posted on by The Information Badger in Business, Change, Climate & Environment, Delivery, Education, IT Project Management, Life, Online Services, Press & Media, Privacy and Surveillance, Project Management, social media, Technology

Would you find it easy or hard to describe the dynamics of our modern digital world in one word? Would one word immediately come to mind, or would you need time to think before deciding? Rather than decide yourself, would you prefer to converge on a word via a group discussion? What would your word be? An ex senior civil servant, in their eighties with a razor-sharp mind, asked these questions in a recent conversation. The Badger took the easy option, answered ‘don’t know’, and we moved on to other things. The questions, however, have bugged the Badger ever since, and so as Storm Eunice buffeted the windows, he settled in his study listening to a playlist of favourite music to decide his answers.

The answer for the first question was ‘it’s hard’. In fact, it took much longer than expected to decide on one word to answer the last question. The answers to the second and third questions came quick and were straightforward. They were, respectively, time to think rather than spontaneity, and deciding for himself rather than potentially succumbing to  ‘groupthink’. The word the Badger ultimately converged on as the answer to the last question was ‘Creep’.

The word has enormous breadth. In materials technology, ‘creep’ is the movement and permanent deformation of a solid under persistent load ultimately leading to failure. Glaciers and lead on church roofs are simple illustrations of the phenomenon. ‘Scope creep’, when requirements drift away from agreed baselines due to client pressure and poor controls, is well-known to those running businesses, projects, programmes, or service delivery. This kind of ‘creep’ often leads to financial problems, commercial disputes, and serious delays. And then, of course, ‘creep’ is sometimes used to describe people who are unpleasant, untrustworthy, insincere, or are just plain odd in their habits, interests, and behaviours.

‘Creep’ seems a more realistic descriptor for the dynamics of our modern digital world than the word ‘change’. For example, our insatiable demand for resources and fossil fuels is producing creep deformation of aspects of our planet to the point of crisis and questions about our sustainability on it. Additionally, digital innovation and fast technological advancement represents a persistent stress on businesses, governments, and the public producing the erosive creep of personal privacy to the point where societal rupture is a risk. Similarly, the need for social media platforms to keep people engaged and active is causing the creep of fact, news, and sensible debate into just disinformation, misinformation, abuse, and entertainment fuelling growing distrust and antipathy. ‘Creep’, of course, can still be used to describe some people, and it seems particularly apt today for politicians and so-called elites!

Oh, and ‘Creep’, by the way, is a great song by Radiohead! What would your one word to describe the dynamics of today’s world be?