Tag: public good

“No” – the project manager’s best friend?

I remember my first change request: “We need the center to host 150 people, 50 more than initially planned, which means building one extra wing.” That would have increased the budget by 30%. It was unrealistic, given the budget cycle. I had to ask another colleague from the regional coordination to say “No”. Then I came across Peter Taylor’s book ““The project manager who smiled” where I read:  “The most valuable and least used word in a project manager’s vocabulary is ‘No’.

Project managers get often requests like: “We want these new features to the product. And by the way, why doesn’t the software have these new reporting tools we just adopted?!” or  “We liked the study visit. We would like to go on one more by the end of the year.”

These are not Christmas letters to Santa. Yet, it is pretty close. In the course of project implementation, beneficiaries tend to try to get more than initially planned. And it’s normal for them to try, for different reasons. I usually do not questions their motives. Not my job. My project manager’s job is to give them what we agreed, when we agreed and for the budget we agreed, without jeopardising the expected quality.

Because the project manager is not Santa, it’s ok to say “No”. There are a number of ways to say “No” by considering the repercussions on the project and ultimately the beneficiary. The most important part is to have the beneficiary understand why the project manager says “No”. Reference to facts or similar past experience may support the understanding of pragmatic beneficiaries. One approach is to show what would happen if “yes” would be the answer.

Let’s take one of the wishes from the above list. “Yes” to an extra wing would mean delayed opening of the temporary detention centre (due to reopening of the construction authorisation procedure etc.) and increased risks of revolt at the current facilities, which hold 100 people in less than acceptable conditions. Data shows that over the last three years the number of incomers is stable and the documents processing rates have improved. Therefore, the centre’s capacity is aligned with the demand. It worked in a project I managed years ago with a data-adept beneficiary.

When the beneficiary is guided by emotional or more personal motives, he/she may not hear /want to hear a reasoned “No”. The costs of “No” can be also high. For example, it asks to choose a certain consultant/service provider. A “No”, even if demonstrated by strictly adhered to procurement procedures and open competition rules, can have the beneficiary complain to the project sponsor and/or lead to the rejection to work with the chosen consultant/service provider. Each project is different and each beneficiary’s powers are context specific, so careful consideration is warranted. What I found important in such situations is to be as open and transparent about these kind of requests with all concerned. It cost me once a friendship, but then it was not perhaps the kind of friendship I would keep.

A “No” does not need to be brutal and cutting-off. One soft way of saying “No” is to help the beneficiary find another project who can accommodate the request. It will bring value added through networking to the relationship with the beneficiary, in addition to the opportunity for a good collaboration with another project/partner.

 

 

Networking in projects

As a preschooler, I was best friends with our teacher’s son, Andrei. It was particularly helpful at disciplining times. “If you do not listen to me, you’ll be sent to the babies’ class” was the harshest penalty on earth for us. At the slightest sign of the “penalty” approaching, I was quick to announce “Me and Andrei were listening and did nothing of (whatever was it that caused the teacher’s discontent). “Ok, you two go back to class. The rest – off you go”. This relationship brought to both of us many perks in those pre-school years.

As we find out in adulthood, networking does not come that easy, at least not to all of us. “Why on earth?” “How? How do I start the conversation?”. “What if they will think I am too pushy?” etc are the usual introverts’ inner talks at networking events. I’ve been there. Done that. In time, I learned that the initial contact struggle was the easiest part. Maintaining and nourishing the network is the hardest part. It takes time and effort.

It is self-explanatory that projects do not exist in a vacuum and networking is part of the project manager’s job. “How good are you at networking?” is a question I got on almost all job interviews.

Networks help in projects. Knowing the right person in the right place at the right time helps solve and/or prevent lots of issues. Networks also contribute to the change the project works for.

To make a network work it needs not to be self-serving. The perks of networking need to bring mutual advantages and lasting benefits to those involved and the professional community at large. And it needs to be clean of any allegations of inappropriate actions.

A story:

Mary was managing a multi-million project whose success depended on a vast network of Government officials. She knew some of them through previous professional contacts. The majority though were totally new both in their jobs and to the project.

She did her homework and found out whom from her network she could approach to help her gain access to the rest. Her first strategy of meetings over coffee and introductions at official receptions was successful. She moved to the next step and asked the most influential project partner to convene a meeting with all, to make it official through a charter signed by all. It was an important milestone for setting the common goals and demonstrating the benefits of the network and the project.

As the project progressed, some inevitable hurdles emerged and the network kept changing as the commitment of some of its members to common goals changed due to Government reshuffles. Mary kept true to the charter and continued to pro-actively engage the members of the network at levels which worked: one-to-one, smaller groups, entire network. In the end, keeping the network consistently functioning for the entire duration of the project paid dividends, as its members demonstrated a sufficient degree of maturity for a more advanced phase of the project.


“Corruption in public projects and megaprojects: There is an elephant in the room!” – re-post

As announcements of unprecedented economic responses rolled on, public procurements worked in an emergency regime. Economic relief plans opened the door to opportunities. Opportunities put to test both the business integrity and the integrity of public institutions. International organisations – such as Council of Europe, OECD – started publishing warnings of corruption risks across industries.

I have not managed investments and/or big infrastructure projects yet, although many years ago I was in charge of overseeing a portfolio, which included a number of infrastructure projects. I remember the complexity of those projects and, in consequence, how high maintenance they were. There was no corruption involved, as reported later by auditors. Yet, my state of alert was constantly high. And understandably so. Seven digit invoices, delays, explanations and justifications, demands for additional budget were some of the red flags. Plus, rubber boots and dusty construction sites came in a package.

The article “Corruption in public projects and megaprojects: There is an elephant in the room!” by Giorgio Locatelli, Giacomo Mariani, Tristano Sainati, Marco Greco equips project managers with a number of valuable insights, both at the planning and at the implementation phase. As the executive summary of the article states: “This paper leverages the institutional theory to introduce the concept of “corrupt project context” and, using the case study of Italian high-speed railways, shows “the impact of a corrupt context on megaprojects.”

In addition to that, the article analyses the salient facets of corruption and characteristics of projects which make them more or less prone to corruption. One can use them as red flags. Authors raise an important number of issues, which are to be paid attention to, in particular as the topic of corruption can still appear as highly controversial in some project management contexts, in particular in times of emergencies.

“Corruption in public projects and megaprojects: There is an elephant in the room!” by Giorgio Locatelli, Giacomo Mariani, Tristano Sainati, Marco Greco, published in the International Journal of Project Management, volume 35, Issue 3, April 2017, pages 252-268, available here: https://www.sciencedirect.com/science/article/pii/S0263786316301090

The story of a book which saw the light in lockdown

On a bright April day, as I was casually browsing Linkedin for updates, I noticed a post by Peter Taylor:

A month into full lockdown, my brain jump at it with delight. “A legacy-book to be published in 21 days? Phew! Why so long?!” I thought to myself. So, I responded to the challenge and so did 55 other project managers across industries from around the world.

“The Projectless Manager: Inspirational Thoughts from a World of Project Managers” is now on Amazon, both in paperback and for Kindle.

It is dedicated to “A global community of health carers and key workers. Its proceeds go to NHS. The book is, as Peter puts it, “unique ‘in the moment’ and ‘of the moment’ book.”

It was such a by-the-book project by itself: on time, within budget and objective – achieved, all this with members of a tribe who basically only know each other by Linkedin profiles.

I have to mention kids here. Those who know me, know that I am a full-time kids’ advocate. The cover is a result of a challenge for 9 year olds. So, it is also an inter-generational act of contribution and sharing. Kudos to kids!

Managing the “No”

Learning to say “No” can be a vital skill for a project manager. Learning to deal with “No” on the receiver’s end is equally important.

There are many “No”s a project managers finds him/herself obliged to deal with. It could be a “No” to additional funds, or to budget revisions, or to deadline extensions. Or a “No” from a service provider to a request to speed up the delivery. Or a “No” from a team member.

How do you deal with “No” on the receiving end? Is it “I do not take “No” for an answer? Or “How could you, after all I’ve done for you?” Or “Wait until your boss learns about it!” Or a blanc staring, Scarlett’s style?

With experience, you’ll learn to anticipate “No”s coming your way and you’ll deal proactively with it.

Here is a story:

The project sponsor asked for a project on three sites in three different countries. Each had a resident rep of the sponsor. As we started work, the representative of the sponsor on one of the sites changed and with him – the expectations.

We re-entered into negotiations, with some heavy weights on our side. During an intense exchange, it became clear that we are moving nowhere. They said “No” to all our proposals. We dropped that site. We still kept the two other project sites with plenty of opportunities to do good. It also freed some of our resources, thanks to which we launched a regional platform.

We kept the loyalty of our clients from the dropped site. And to compensate the local stakeholders for the lost opportunities, we invited them to the other sites to benefit from the products we delivered.

Couple of years later I met the sponsor’s rep and it gave me great pleasure to share all the good things we did on the other two project’s sites and the regional spin off.

Top five most frequent questions in time of crisis

These past two weeks, I have been contacted for advice on what to do with projects in these new and unexpected circumstances. Crisis management, here we come.

While my advice and tips matched the variety of situations the projects were in, I noticed several common take aways:

1. Damage control and remaining in control are strongly interdependent. Analyse what you can control and acknowledge that you cannot control the pandemic and its extent. Unless you are a project manager in a hospital in an epicenter.

2. Analyse your project’s work plan/charts and be honest about what can be done in the period announced by the authorities if your country is in a confinement/quarantine. Have a plan B and be ready to change it, as things evolve. Communicate it well to all concerned: sponsor, stakeholders, providers, consultants.

3. Check all your contracts, the obligations part in particular, both yours and the other parties’. Now it’s the time for forgotten or overlooked things to come to light. Get the help of your organisation’s lawyers, if needed. Check the clauses on causes for suspension and delays for payments. Notify the other party, if required so. For new contracts, check what you can agree on and sign electronically.

4. Now it’s the time to move online if you have not done it yet. There is a variety to choose from, from Trello, Monday, Basecamp to Zoom and clouds. Make the technology work for you.

5. Teams will watch you for cues. So, control yourself, by distinguishing your fears from facts. Acknowledge team members’ fears. Offer a mirror of calm. Help when you can. Summon all your empathy and compassion.

The seven habits of mentally strong project managers

Over the last two decades, I worked with numerous project managers from different industries and the ones who are rock strong share a number of things in common. Now more than ever these habits will be tested and new ones will be developed. I’ll leave these ones below for now:

1. Mentally strong project managers practice self-awareness. They know that mental strength is their choice which requires commitment and a big sense of humour. They prefer self-irony to ego.

2. As they are building on self-awareness, they remain pro-active. They will pick up the phone first. They own the mistakes and failure. They act responsibly towards the team, the client and the sponsor.

3. They practice humility. They are humble enough to acknowledge that there are things they cannot control. They will however take seriously damage control. They refocus their attention on the things they can control and take the team through this. They care about what the team and the client thinks. The rest is a facebook thread to them.

4. They say “Hello, gorgeous!” to the unexpected, and projects by definition are plentiful of those. They know that even with the best of planning skills, there is a great deal of unchartered waters. Mentally strong project managers are as flexible as a willow and turn adversity into opportunity to bring return on investment.

5. They are best pals with risk management. They will ponder, calculate, analyse, involve others. They will put people first and thus sleep well at night.

6. They put relationships first. They know that reports, deliveries and milestones will become past. Relationships last.

7. They keep things in perspective and share it with others. They will respond to a colleague’s call for help and give the best of advice they can.

“On Leadership. Practical Wisdom from the People Who Know” by Allan Leighton with Teena Lyons

Yet another of my favorite books I often pick up from the shelf. We all know how important is the leadership in project management. We all struggle from time to time with the “How to” become and remain a leader. This book is like a treasure chest. Every time you need a gem, you open a chapter:

Getting Started,

Coping with Success,

Dealing with Disaster,

The Art of Communication,

Getting the right team,

The Customer is King,

Talking to the Media,

Business vs Politics,

Looking to the Future.

As project managers we find ourselves dealing with many if not all of the above. Hence the value of the book for project managers.

The book is written with wit and wisdom. Each chapter feels like going into the offices of the best executives Leighton talked to for this book. Each was generous with insights and advice you would get from very few academic or professional training programmes. It is also highly entertaining and will glue you to learning with fun and motivation to become the best at what you do.