Category: Project Management

A first-time Project Manager and scrutiny…

Posted on by The Information Badger in Delivery, Information Technology, IT Project Management, Leadership & Management, Processes and Practices, Project Management, Risk, Training

In times or yore, a young Badger was appointed to lead a new project developing software for an important client. It was his first time as a Project Manager! After six months, however, the Badger seriously doubted his suitability for the role. The initial enthusiasm, excitement, personal glow and motivation from knowing that your boss believes you have what it takes to be a Project Manager had been replaced by gloomy self-doubt. The project was on track, the team members was working well, and the client was happy, so what was the problem? Put simply, the Badger felt bogged-down with – in his view – unnecessary company bureaucracy and intrusion that encroached more and more on the time to lead the project.

In those days, all company employees had ‘a counsellor’, an experienced person outside the employee’s immediate chain of command, who acted as both a mentor and an independent performance appraiser. Employees met their counsellor formally twice a year, and one such meeting happened to be around six months after the start of the Badger’s project. At this meeting, the Badger shared his bureaucracy and intrusion misgivings and whether he was suited to a Project Management career path. His counsellor chuckled and said ‘Everyone initially struggles with scrutiny in their first leadership role because no one likes to be scrutinised. First-time project managers often underestimate the scrutiny that goes with the job!’ The counsellor was right. What the Badger labelled as unnecessary company bureaucracy and intrusion was largely the scrutiny that‘s part of good corporate governance and operational control.

The counsellor emphasised that embracing scrutiny was important because it builds trust and provides assurance that nothing is being hidden, whereas resisting it creates suspicion, distrust, and even more scrutiny! As an aside, they observed that the level of company scrutiny experienced can be a qualitative indicator of a company’s health, because the absence of it implies anarchy and ultimately company failure. Overbearing scrutiny of everything all of the time, on the other hand, suggests organisational constipation, risk aversion, stifled creativity, and likely underperformance compared with rivals in the market. The counsellor concluded with ‘As a Project Manager, you are actively managing your client and your team, but you must also actively manage your company scrutineers and their agendas’. Over subsequent years as a Project Manager that is exactly what the Badger did!

The Badger’s IT delivery career eventually took him into a senior, company-wide, delivery and business role that included being a scrutineer! Most of the first-time Project Managers he encountered as a scrutineer were better trained and supported and embraced scrutiny positively. Experiencing them trying to influence and manage the Badger was always fun, because when you’ve been in delivery for decades you know all the Project Manager’s angles and how not to be defected from your agenda!

Are Management Consultants useful and good value?

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

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.

Public inconvenience – A tale of a project gone wrong…

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

In 2021, the Badger’s local Town Council proposed a project to build new public toilets at a leafy recreation and community space close to a busy shopping area. The proposed facilities would be modern, environment-friendly, free to use, and aesthetically pleasing to blend in with the area. The need was undeniable, there was community support, funds were sourced from budgets, and the council applied for planning permission from the Borough Council. This was granted in November 2022, and the Town Council gleefully announced that a contract had been awarded to complete the project in February 2023, in good time for the facilities to be used during local celebrations of King Charles’ Coronation in May 2023. What could possibly go wrong?

The contractor completed the foundations, but an inspection found they had been laid in completely the wrong place! They had to be dug up and re-laid in the correct place, which didn’t happen quickly. The Town Council blamed the delays in rectification on the contractor, who in turn blamed difficulties sourcing materials and labour for the work. Eventually the new foundations were ready, and the Town Council announced that the building itself (being prefabricated in a factory 100 miles away) would soon be assembled on site and still be operational in time for the Coronation celebrations. Guess what, the building’s arrival and assembly on site was delayed. The council, pithily noting that they were fed up with being frequently let down by the contractor, was forced to announce the facility would not be operational in time for the Coronation.

When the building eventually arrived in the summer, there was a public outcry because it was very different aesthetically to that originally proposed and expected. The assembled building sat fenced off in its untidy site plot for a long time with no work taking place. In September, under pressure from the community, the Town Council committed to publishing a weekly update on what was happening to get the facility operational. Only three updates were issued, the last of which mentioned that permissions to a) connect the building to public utilities and drains, and b) for the contractor to do the associated groundworks, were still awaited. Since early October there’s been no updates from the council, and no work undertaken on the site. The community has lost confidence that there is a deliverable plan to complete the project and get the facility operational. The Town Council’s credibility is in shreds, rumours abound about the contractor’s track record with other councils, and the local community – the end users – are complaining loudly about management failings and incompetence!

Why tell this tale? Because it highlights that it isn’t just big public sector projects that go wrong, that the root causes of problem projects are fundamentally the same regardless of scale, and that ultimately, it’s always the end users who suffer and are inconvenienced…

Expect the unexpected; when the unexpected happens, respond rather than react…

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

The very first Project Management training course the Badger attended early in his IT industry career seemed of questionable merit. It was a residential course for Project Managers drawn from across all the business sectors in which his company  operated. Attendees arrived on a Sunday afternoon and ultimately departed mid-afternoon on the following Wednesday. At the time, it was common for people to be actively performing a Project Manager role before attending any associated training course, and so everyone on the course was already actively managing software and systems projects under a variety of contractual arrangements.

Most of the course sessions focused on the process and practice of managing a delivery/development lifecycle, risk, finances, and the basics of contracts and change control.  The format was rather dry but provided some useful reminders. At the end of the course, however, most attendees questioned whether being away from their projects had been a useful use of their time. There were, however, two overwhelmingly positive points of feedback, namely a) the usefulness of meeting peers and sharing experiences, and b) the closing, hour-long, Q&A session during which a senior business leader answered wide ranging questions from attendees.

Whilst the Badger came away rather ambivalent about this course, it had provided a useful reminder that Project Management is as much about people, as it is about structure, lifecycles, processes and practices. In fact, the primary thing that has stayed with the Badger from the course ever since are the wise words of the senior business leader in the closing Q&A session. When asked to give one piece of advice that everyone present should take on board, they said ‘Expect the unexpected, and when the unexpected happens, respond rather than react’. They explained that no one can avoid the unexpected, that some people are better at dealing with it than others, and that some people react emotionally, feel anger, panic and fear, become agitated, and initiate  knee-jerk moves to action that compound matters and alienate others.  Others respond rather than react. They stay calm, focus on the facts and what they can control, assess the options before progressing a plan of action, and unify and encourage those around them.  The business leader told the audience to remember to respond rather than react.

Throughout his career, the Badger encountered many leaders and managers who had to deal with the completely unexpected. Many reacted rather than responded ! This was a constant reminder that everyone is different, and that being a leader or manager doesn’t provide immunity to the core traits of your personality. Perhaps that first Project Management course was of more value than seemed at the time, because it sowed the seed of awareness that to be a truly successful leader or manager, then you must learn how to respond rather than react to the unexpected…

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…