Tag: research

Stakeholders analysis or who else is in the sandbox?

Projects are not stand-alone “enterprises”. They usually need to co-exist and be implanted in already “populated” areas by those who have /can have a stake in a project.

A project’s needs assessment or design phase shall include the stakeholders analysis. I am sometimes asked “Why do a stakeholders analysis?” This analysis enables an up-to-date picture of stakeholders’ roles and interests in the project. These can range from ministries, parliaments, local authorities, institutions and organisations, both public and private, professional and non-professional groups, to people and groups of people.

I sometimes, make an analogy with the sandbox and start my analysis by looking around who else is in the “sandbox” and what they do. Who builds a castle (ambitious ones), who destroys it (opposition), who digs ditches (planners), who is well equipped with buckets and shovels (the doers), who sits on the edges (the expectants) …Sandbox-Pic

In development management projects, I find the following classification of stakeholders useful for the analysis of their impact/potential impact on the project:

  1. Resource Providers: those who provide funds.
  2. Target Group: are directly affected by the project and directly benefiting from the work of the project
  3. Beneficiaries: those who directly/indirectly benefit, in the longer term, from the improved capacity (skills, knowledge, etc.) and quality of services and products of the target groups
  4. Project partners/supporters: provide support for the implementation of the project. Although not in B and C categories above, their co-operation is vital for the successful implementation of the project (e.g. ministries, other governmental agencies, NGOs)
  5. Potentially affected/threatened: are/could be adversely affected by the implementation of the project
  6. Opposers: are/could be opposed to the implementation of the project
  7. Undecided: stakeholders with unclear role.

These categories are not static and stakeholders might switch roles throughout project implementation. It is thus important to regularly monitor their roles and stance.

Feel free to download and use this template PROJECTS STAKEHOLDERS ANALYSIS TEMPLATE_web

 

Thought of the week: context matters

-Thank you and your team for the flexibility.

– Oh, no. We are not flexible. We understand context.

-Thank you even more.

The above was a dialogue I had some time ago. All good project managers know that context is important – he/she will not rely on a “one-size–fits-all” approach.

I am personally allergic to copy-paste, in projects and beyond. It makes me want to cry when I see the name of the country changed through “find and replace” in development project documents.

Do yourself and your client a favour – research the context, do a proper needs assessment and/or diagnosis and bring what’s needed in that context.

origami by Sofia, 2017

 

Conflict. Bring it on?

– Conflict is good, my junior colleague said to me on our way to an important meeting. He just read an article in HBR.

I wondered if he meant conflict in the team or with the client. It could have been on either fronts. Or even on both.

I did not pursue that conversation back then. I knew he was going through a tough period in his personal life and was looking for an excuse to vent his spleen. “Not on my watch”, I thought back then. Bringing personal conflict into professional life is a no win-win. Same is valid the other way around.

Let’s look at origin of the word: “conflict” com “with, together” (see con-) + fligere “to strike” (see afflict). Think about it.

Conflict happens quite often in projects. Some time it is avoidable. Sometimes, it is unavoidable. When it happens, there are things to do or abstain from. It depends on a series of factors, among which I would consider the following:

1. The origin of conflict

Different priorities, incompatible communication styles, unclear roles or a lack of trust are often at the root of conflict between team members. Unmet expectations, exceeded budget, unmet objectives or deadlines can generate conflicts with the project sponsor or contractors.

2. The parties to conflict

Conflicts happen between team members, with the project’s sponsor or contractors.

3. The objective of the conflict or what are the parties after.

Some just love to live in a perpetual conflictual state with no positive objective in mind. Some want to bring to the surface things, which are not seen as positive or beneficial for the project or a party concerned.

Depending on the answers to the above, a conflict management strategy has to be put in place. It has to be managed, otherwise it will manage the project right into failure or difficulties.

There is plenty of literature on approaches to manage conflict. Here are top three steps I applied and observed as a project manager over years:

1. Start with checking your assumptions about the origin of the conflict and the purpose of parties concerned. Do not be mislead and do not mislead.

2. Look for common ground. For example, the project sponsor wants more visibility and threatens to cut funds. At the same time, the project team is reluctant to go “public” and feels unappreciated. A common ground could be to present the visibility requirement of the sponsor as an opportunity to do justice to the project team’s work.

3. Keep your head and stay neutral, the same way Switzerland does it. Avoid at all costs taking sides, unless there is blatant injustice to any of the parties concerned. For example, a team assistant blaming the driver for a failure of the translation equipment and putting at risk the entire event. A good conflict management strategy in this case is to talk to all concerned and find out what happened exactly and ask both of them to read again their respective job descriptions. Designing a standard operating event management procedure and/or an event preparation check list helps to prevent potential future conflicts.

Integrity in projects: Receiving gifts

integrity image

“Oxana, the boxes of chocolate and tea are more for you”, read the email I received from the big boss of the organisation I worked for. It was after a meeting between top management and the project team. One of the consultants on the team offered to the chair of the meeting the famous chocolate.

“Thank you very much. I’ll pick them up and open the boxes for everyone to enjoy in the office’s coffee room” was my immediate response. I knew the ethics rules this Organisation had. And I was committed to apply them.

It was also an example for other team members who were puzzled at the meeting and watchful of management reaction.

A box of chocolate is a small thing, right? the temptation jumps in. Better check your client’s and your organization’s policies on Receiving gifts. If you are a free-lancer, check your professional quarters’ guidelines. PMI for example, https://www.pmi.org/about/ethics/code

Some guidelines are more gifts-tolerant and set a maximum value for gifts which can be accepted. They range from USD 30 or equivalent (UNDP) to 100 Euro of equivalent (Council of Europe). More important than the value are the intention and or perception of influence that gifts may carry. Some Organisations are outright intolerant to gifts, regardless of the value and source, in particular for staff involved in procurement. As project managers, we are involved in procurement.

I’ve seen guidelines which contain a permission to accept gifts, which otherwise would be insulting to the offerer, for cultural or local customs reasons. In such a case, the gift shall be immediately disclosed and transferred for a decision to management.

Once in Ukraine, at a dinner paid by the project at the end of the project, I was offered two traditional cakes by the client. I declined politely. “We know it is below the value of gifts you can accept. We checked.”, they insisted. “I will pass it to my colleagues in the local office, to enjoy, as a token of your appreciation”, was my response. And so I did the next morning.

If I cannot refuse the gift, I make sure that offerer understands that I act in accordance with the gifts receiving policies I abide by and that I accept it on behalf of the team. And I share it with the team: be it a box of chocolate, traditional sweets, a bottle of spirits, an invitation to a cultural event, a tour, etc. I know it is given to me only because I am on this project and I am already paid for doing my job.

Some Guidelines prohibit gifts from certain sources: Government, for example, or vendors, as these carry the risk of being seen as a “down payment” for a future favour on behalf of the organisation/company you work for. Money gifts are a No in literally all professional conduct guidelines I saw. No explanation as to why is necessary.

“What about gifts post-project?” you may ask. I can only congratulate you for having succeeded to transform a business relation into a friendship. Nevertheless, I would be watchful over how much time elapsed after the project, if you are not in a new project design phase and if no strings are attached from either side.

Keep it professional and maintain your integrity watchful!

From the series “Integrity in project management”. To be continued.

Thought of the week

“Strength lies in differences, not in similarities” Stephen R. Covey.

I fully subscribe to this. It might sound strange coming from a project manager who loves standard operating procedures and streamlining. Some recent and not so recent manifestations showed me why.

Gender mainstreaming in projects: a case study

Project A was designed to respond to institutional strengthening needs of an association of professionals – let’s call it Stars Alliance – and to contribute to improving the quality of the profession. Gender mainstreaming was included in the Project’s Work plan as a cross-cutting theme, yet its practical implication remained to be investigated and followed-up. The Project indicators were not gender-disaggregated at the start of the Project.

During its inception phase, the Project team used the stakeholders’ analysis to understand their roles, needs and situation. At the start of the Project, 30% of the Stars Alliance members were women. Yet, there were no women on its board and there were less than 10% of them in other internal management committees. Women have organised themselves into an association, let’s call it WLA.

WLA was established in March 2015 by 8 women lawyers. It was a young and small association with high aspirations to promote gender equality both within Stars Alliance and on the legal services market. The WLA was marginalised within the Alliance and its voice was weak. None of its initiatives, including gaining equal treatment of women professionals within social security, were supported by the Alliance.

The Project’s Stakeholders Analysis increased the understanding that for the gender mainstreaming to be successful, the WLA voice had to be heard and its capacity had to be strengthened. Moreover, including WLA in the Project meant that it would have the same effects and impact on men and women, both at the level of capacity and skills. A number of gender sensitive indicators were introduced, for example the number of women in the Bar pool of trainers; the number of women candidates to management positions and the number of women elected/selected in management committees.

Thus, the Project team pursued a pro-active role in involving WLA in the Project. The Project insisted on including WLA in all consultations organised to prepare the Stars Alliance Management Road Map, draft it organisational Strategy for 2017-2022 and its Communication Strategy. The Project also included consistently WLA representatives in all Project workshops, conference and seminars, breaking down little by little the isolation previously experienced. WLA was also included in the Project’s Steering Committee enabling the organization to make contributions and participate in decision making.

In addition to that, the Project implemented a number of activities designed specifically to strengthen WLA capacity as an organization.  As a result of these, WLA prepared its own Strategy for 2018-2023, started to collaborate with a similar organisation at the European level, organised its general assembly on a regular basis, multiplied by ten the number of its members, gained space on the Alliance website (where it can regularly publish its news and make itself visible and heard); presented an alternative report on women rights situation in the country at the UN Committee for Social, Economic and Cultural rights in Geneva.

All of the above contributed to making the WLA voice heard within the Alliance and externally, empowering it to take gender mainstreaming forward to the benefit of the  profession.

The Project’s approach to increase the capacity of WLA brought two lessons learned:

a. the Project had to be ready to mitigate risks of occasional disengagement from the Alliance management in Project activities, when WLA lead-activities were perceived as challenging to the institutional culture that existed since its establishment.

b. helping WLA to form partnerships – e.g. with the European women professional associations – was an important part of the sustainability of the action, as it anchored it in a network of organisations, which share similar challenges and aspirations.

“Heart Coherence 365: A guide to long lasting heart coherence” by Dr David O’Hare

My reflexologist introduced me to this book. Its title sounded like a book on project management so it resonated with my thinking framework and my need at that moment. I needed to emotionally realign myself in a period of turbulence. And times of turbulences are not rare in project managers lives.

Moments of anger, disappointment and pressure are part of life in project management. Your heart accelerates, your breath is short, you can’t think straight, your self-esteem might have been hurt… If you have a good self-awareness and you are not too tired, you know what to do and how to get back to the safe and sound harbour. If you are looking for help, this guide can offer it. Hence, I am sharing it here for any fellow colleague to refer to in times of need.

I read it in one go. The author kept his promise to keep it simple and understandable for a non-professional audience. 365 means 3 times a day, 6 times a minute, 5 minutes. All you need is your breath and mindfulness. And a quiet space. The guide offers detailed explanations on how to reach 365. The 365 is the foundation I was looking for in my modest yoga and meditation practice.

If you are curious to learn more, visit http://www.coherence.info.

Stay healthy. Breath.

The Controlled Breathing app can be of help as well.