Tag: recovery

What to expect: when taking over a project run by a colleague-friend

I have to say that I was never in such a situation. I witnessed a few such cases though in different work environments. Each case was pretty  specific, yet some general patterns were there. Here is Rosalia’s case: a young professional who was given responsibility beyond her experience, with the “bonus” of her work friendship at test.

Rosalia was booming when, upon return from a long vacation, she took over the project’s files.  She found out that she will be given this project two months ago.  Her best friend and colleague, Michael, left for another job in another country. Rosalia was very enthusiastic at first. She idealised her friend and everything he did so her usually active critical sense was put to sleep. Two months later she paid dearly with her health. Her joy soon turned into a depression fueled by a stream of difficulties. A surprise kept popping up after another. A consultant was paid for a product of unacceptable quality. A statutory evaluation was skipped with no explanations in the file. There were no contacts established with the project donor and the project was at its final stage. Large amounts of budget remained unpaid and the budget lines were guarded rigidly by the sponsor.

Could at least some of these have been prevented by knowing what to expect and preparing to act? A proper hand-over, to start with, would have given Rosalia a clear status quo. She did not  want to ask her friend any questions of fear to be perceived as challenging his authority. If you find yourself in such a situation, there a few strategies which you could try.

First, ask for a tri-lateral meeting with the departing project manager and your supervisor. It can be over coffee or another less formal set-up.  Follow-up the meeting with a note and send it to both to get confirmation on what you were told. It will give you a baseline and your friend will not feel as reporting to you.

Time permitting, organise a joint introductory meeting / a conference call (in case of teams located in different places), where both you and the departing project manager could participate. Follow the meeting with minutes circulated to all concerned.

Agree with your departing predecessor for how long and on what you estimate to still be needing to get back to him/her with questions you might have.

While friendships come in different forms and many complexities might arise, some of the above might allow to set the boundaries between personal and professional relations so that you can continue your friendship unaffected, to the extent you can. Sometimes you’ll have to choose. Sometimes you’ll have to compromise. It’s important not to compromise your professionalism though. A true friend will not ask you this.

„Fail-Safe Management: Five Rules to Avoid Project Failure” by Jody Zall Kusek and Marelize Goergens Prestidge

New to the job, I had a silent prayer in my head: “Please don’t let me fail”. This fear of failure was almost paralyzing. I only conquered it when I learned to learn from failures. It took a number of failures to get there. Then I learned that I am not alone thanks to a number of books, among which a World Bank publication I would like to share with you.

Fail safe mngt

The book gives insights into five rules the authors advise to follow for a fail-safe project management:

Rule 1. Make it about how.

Rule 2. Keep your champions close and your critics closer.

Rule 3. Informal networks matter – use them.

Rule 4. Unclog the pipes.

Rule 5. Build the ship as it sails.

This book is both a good acquisition and an inspiration. It might not be eye-opening on all accounts (as it depends on your level and extent of project management experience) but it still contains a number of important lessons to take away for mindful managers. Here are a couple of mine:

A. In many cases failure is „baked into” the project almost from the start by managers and team members who simply fail to be mindful of the details and who focus on avoiding the obvious problem spots that any project will face as it goes along.

B. „Build the ship as it sails” suggests to start on a smaller scale and pilot whenever possible. Keep learning.

C. The definition of success will vary, depending on who assesses it. Making a difference to people on the ground is a mark for projects making progress in development.

D. Regardless of whether the stakeholder is a champion or a critic, these relationships must be managed to avoid project failure (the book includes a tool to manage stakeholders relations).

***

From time to time failures occur or we let them happen. For a variety of reasons. I once drafted the project’s work plan based on an overly estimated partner’s commitment. An unexpected management change in the partner organisation demanded a serious rethinking of the implementation approach through resource- consuming  alliance building and bottom-up approaches. I have on my desk a brochure with the nice pic of the previous management of the partner to remind me not to let my overly optimistic outlook to take over pragmatism in project planning.

Failures are the learner’s best friends in projects and in time I learned to identify and address them. Reasons for failures in projects are multiple and the approaches to deal with them differ. They therefore deserve a separate post, to which I’ll return. In the meantime, a fail-safe and learning rich project management!

“The project manager who smiled” by Peter Taylor

– What are you reading now, Oxana?project manager who smiled

– “The Project Manager who smiled”.

– Did you write the book? asked my good friend Frank.

– I wish. It’s Peter Taylor’s book, I smiled in response.

– See, it could be easily about you.

I do smile. Indeed, a lot more than at the beginning of my project manager’s path.

I believe now in the value of fun in project management. Walt Disney’s saying “It’s kind of fun to do the impossible” resonates with my believes as project management is often about making the impossible possible.

I discovered the book 3 years ago. I wish I discovered it at the beginning of my project management path.

It is one of my favourite books so far on project management.

The book is about having fun and being productive. In its Foreword, it brings the evidence of linkages between fun, good mood and healthy atmosphere and, ultimately, productivity.

Some personal notes I made:
It is unorthodox in a tools-templates-square–linear thinking project management world. Nevertheless, the book talks to you on pragmatic levels, from project manager to project manager, regardless of the size or location of your project.

It relies on a wealth of other project managers experience for things tried and workable approaches.

It puts a smile on the reader’s face and makes sure it stays there till the end.

The author is brave enough to give personal examples and stories, showing that there are gains in vulnerability. For example, in a moment of despair, Peter recalls a case when he walked out of a room full of team members, closed the door and pretended to be a boss firing him in a very loud voice.

You’ll not often find “expectations management” tackled in project management books. It has its place in this book. The book gives workable approaches to the management of expectations through e.g. constant feedback mechanisms.

It gives reassurance that creativity has its place and role in project management, making it thus appealing to more creative spirits who want to do project management.

Each chapter on Fun Inspiration, Fun Jokes, Fun Motivation, Fun Status, Fun Ideas, Fun Theme Tunes, Fun Team is followed by a PM Celebrity Gossip, sharing reputable project managers’ experience and projects’ successful fun stories. You can really relate or have an aha! moment in these gossips.

I warmly recommend it! It works both in project management and in overcoming storms at home. My kid will certainly respond with a smile when, in a moment of unhappiness, I’ll point a finger at her with ”don’t you dare smile, do not even think about smiling”. Enjoy the book!