Skip to main content

Tag: Stakeholder

PMTimes_Sep25_2024

Skillful Efforting to Achieve Leadership Success

Written by George Pitagorsky on . Posted in Articles.

Create a realistic work-life balance in the context of leadership and project management to achieve optimal performance and success. Apply it to your own life and influence those who work for and with you.

Leadership boils down to the ability to cultivate a positive mindset, relate well with others, and make effective decisions. To sustain a dynamic work-life balance requires all three.

What is the mindset that promotes optimal balance?

In a recent article, Jerry Seinfeld is quoted:

“It’s a very Zen Buddhist concept: Pursue mastery. That will fulfill your life. You will feel good.

The problem is, that developing a skill takes time and effort. Mastering a skill takes considerable time and effort, not all of it — or even most of it — enjoyable. ”

He recommends that you “Make ‘Did I get my work in?‘ your favorite question to ask yourself, and while you may not achieve every goal you set out to accomplish, you will definitely accomplish a lot more.” 1

The mindset here is 1) to expect to make an effort to get what you want and 2) that the way you make the effort makes a great difference in the way you and others feel and the outcome of your work.

 

Working Hard

In Working Hard but Not Too Hard  I wrote

“Working hard is applying a high level of effort, being consistently focused, productive, and effective, and applying emotional, physical, and intellectual energy. Working hard is rewarding, it leads to personal and organizational success.”2 https://www.projecttimes.com/articles/working-hard-but-not-too-hard/

As wise individuals in our roles as performers, leaders, and managers, we recognize that hard work is necessary to develop skills and accomplish goals. Of course, working smart is highly valued, but it is not a replacement for working hard.

 

Overdoing It

We also recognize that we can overdo it. We can become so obsessed with succeeding that we forget our personal wellness and the wellness of those who are affected by our behavior. We work too hard.

If we work too hard, we get tired, disengaged, and less effective. If we miss the signs that we or our team is working too hard, stress levels increase, quality suffers, and we enter a spiral that does not end well.

 

Self and Other Awareness

This is where self-awareness and awareness of others come into play.

“Self-awareness is the ability to “step back” and observe yourself objectively to know your behavior, motivations, feelings, values, and desires.  It is knowing your personality and the way you display it in your life.” 3 https://www.projecttimes.com/articles/self-awareness-a-critical-capability-for-project-managers-d23/

An effective leader is aware of how others –  for example, your team members, clients, boss, significant others, and peers – are doing. Are they excited, motivated, and in the best shape to get the mission accomplished? Are they slowing down, or getting tired? Or are they past that stage and exhibiting the symptoms of over-work?

 

The Symptoms

The symptoms of overwork are easy to spot – more arguments and emotionality, an increase in errors, absenteeism, and lower productivity are the most common.

The quicker you see the symptoms, in yourself and others, the better. Catching overwork early gives you the ability to apply the least amount of effort to remedy it. Avoiding it is best.

 

Skillful Effort

The way you make the effort makes a great difference in the way you and others feel and the outcome of your work.

Ideally, the effort is effortless. As in Flow where skills and experience come together to perform optimally as if there was no one doing it. When that is not the case, be aware of tendencies to over or under-effort. The Buddha compared skillful effort to tuning a stringed instrument. Too loose, poor sound quality. Too tight, a broken string.

 

Advertisement
[widget id=”custom_html-68″]

 

Avoiding Overwork

Avoiding and remedying overwork begins with recognizing and acknowledging it. It can be avoided by consciously addressing it as an issue when planning and scheduling.

The more people are aware of the issue of overwork, the better. Make work-life balance a topic in team building. Acknowledge the degree to which there is an expectation of 24-7 availability. Will there be tight deadlines that lead to overtime? What are expectations about weekend work, and vacations?

Also acknowledge the influences of poor planning, cultural norms, personality issues like workaholism and perfectionism, and fear to push back against unrealistic demands.

When expectations are explicitly stated people can be better prepared and more accepting of what happens. Expecting a 9 to 5 arrangement and having 24-7 demands come as a surprise is likely to result in disruption at home and work.

If your project is going to require working intensively, build in practices that enable that kind of work – stress management techniques, breaks, meals, comfortable working conditions, a sense of camaraderie and adventure, and recognition when it is time for a rest.

If one intense project is followed quickly by another, beware of burnout. Take a lesson from extreme sports teams, there is an off-season for R and R, and the players get massaged and conditioned during the season.

Schedule realistically. You can add optimism to your mindset but consider it an aspiration. Hope for the best, plan for the most likely, and be ready for the worst.

 

Remedying

If you have not avoided it, and you, your team, or other stakeholders are suffering the symptoms of overwork, acknowledge it and treat it as you would a physical injury or sickness. Acknowledge it, seek its causes, relieve the symptoms, and remove the causes. And most importantly, take good care of the patients.

As we have said, poor planning, cultural norms, personality issues like workaholism and perfectionism, and fear of pushing back against unrealistic demands may be the causes. Each situation is different. There may be no options to eliminate causes, so all you can do is minimize the impact of the symptoms. Sometimes the options are severe, like changing jobs.

What can you do to reduce the symptoms and maintain the kind of motivation that will fuel success? The minimum remedy to explicitly acknowledge what is going on. That alone will reduce stress and discord.

Then find ways to institute the same practices you might have planned for to avoid the situation.  Implement breaks, meals, comfortable working conditions, morale building, and recognition when it is time for a rest. Negotiate schedule changes, additional (or fewer) resources, and other means fir reducing pressure.

 

Action

If efforting – doing the work – is an issue that needs to be addressed, bring it to the surface. Correct imbalances among expectations and realities with self-reflection and candid communication.

Implement practices to avoid over-efforting and make hard work as effective as possible while sustaining wellness. Avoid the expectation that you can get what you want without hard work.

Recognize the real-world nature of your situation. If intensive effort is a fact of life, make it known so that people can make decisions to join the fun or opt for a less intense environment. Assess all the factors (family, physical and psychological health, career, finance, etc.) from multiple perspectives, considering short, medium, and long-term impacts.

Then decide what to do, when, and how to do it.

 

 

1.https://www.inc.com/jeff-haden/jerry-seinfeld-says-achievement-success-comes-down-to-repeatedly-asking-yourself-this-6-word-question.html?utm_medium=flipdigest.ad.20240910&utm_source=email&utm_content=article&utm_campaign=campaign
PMTimes_Sep04_2024

The Role of Emotional Intelligence in Agile Leadership and Program Management

Written by KC Lakshminarasimham on . Posted in Articles.

The success of agile projects increasingly relies on the emotional intelligence (EI) of leaders. Agile methodologies focus on teamwork, flexibility, and ongoing improvement—all of which are significantly influenced by a leader’s emotional awareness and ability to manage interpersonal relationships. This article explores how emotional intelligence is integral to agile leadership and program management, showing how it can be a driving force for project success and the development of a motivated, resilient team.

 

Understanding Emotional Intelligence

Emotional intelligence, a concept brought to prominence by psychologist Daniel Goleman in the early 1990s, refers to the ability to recognize and manage one’s own emotions while also understanding and responding to the emotions of others. The five key components of emotional intelligence include:

  • Self-Awareness: Recognizing emotions as they occur and understanding their impact on behavior and thoughts.
  • Self-Regulation: Effectively managing emotions, controlling impulses, and adapting to change.
  • Motivation: Maintaining a strong drive to achieve goals, often setting high personal standards.
  • Empathy: Understanding and sharing the feelings of others, which is vital for building trust and strong relationships.
  • Social Skills: Successfully managing relationships, influencing others, and fostering effective teamwork.

For agile leaders, these elements are essential in navigating complex team dynamics, creating a positive work environment, aligning with company strategy and maintaining high performance in demanding situations.

 

The Intersection of EI and Agile Leadership

Agile leadership goes beyond simply guiding teams through sprints and meeting deadlines. It involves a deep understanding of team dynamics, individual motivations, and how change affects both morale and productivity. Leaders with strong emotional intelligence can apply their skills in several key areas:

Building Trust and Encouraging Collaboration

Trust is foundational for any agile team. Leaders who demonstrate empathy and strong social skills can create an environment where team members feel valued and confident in sharing their ideas. This trust fosters open communication, allowing for more effective collaboration and innovation without fear of failure. By addressing the emotional needs of the team, emotionally intelligent leaders can remove barriers to teamwork and ensure the group operates cohesively.

Improving Communication

Clear communication is critical in agile methodologies, whether during daily stand-ups, retrospectives, or sprint reviews. Leaders with high emotional intelligence excel at interpreting nonverbal cues and understanding the emotional dynamics within the team. They can adjust their communication style to fit the situation, ensuring that their messages are well-received and constructive. In parts, they have the ability to contextualize to the larger, strategic goal.  This nuanced approach to communication helps prevent misunderstandings and keeps everyone aligned on project objectives.

Handling Conflict Proactively

Conflict is inevitable in any team, especially in high-pressure agile environments. Leaders with strong emotional intelligence can identify early signs of conflict and address them before they escalate. By approaching disagreements with empathy and a focus on resolution, these leaders can transform potential disruptions into opportunities for growth. Empathy develops over experience and leaders bring in more empathy with their experience. They encourage open dialogue and help team members resolve issues in a way that strengthens relationships rather than damaging them.

Motivating and Engaging the Team

Understanding what motivates different team members is key to driving performance. Leaders with high emotional intelligence recognize that individuals are motivated by various factors—whether it’s the challenge of the work, the desire for recognition, or the opportunity for personal growth. By aligning tasks with team members’ strengths and interests, emotionally intelligent leaders can boost engagement and productivity. They are well aware of balancing motivations and handling conflicts that may arise. Additionally, they maintain a positive team atmosphere by acknowledging efforts and celebrating achievements, keeping morale high even during challenging times.

 

Advertisement
[widget id=”custom_html-68″]

 

Program Management and Emotional Intelligence

In the broader realm of program management, where leaders oversee multiple agile projects and teams, the role of emotional intelligence gains significance. Program managers must not only guide their teams but also ensure alignment across different projects, stakeholders, and organizational goals. Here’s how emotional intelligence is crucial in program management:

Managing Stakeholder Relationships

Navigating the interests of diverse stakeholders is one of the most challenging aspects of program management. A high level of empathy and social awareness is needed to understand and address their concerns while keeping the program on track. Emotionally intelligent program managers handle these relationships with care, ensuring that stakeholder expectations are managed effectively and that their support is maintained throughout the program’s lifecycle. This skill is particularly vital in agile environments, where requirements and stakeholder needs can change rapidly.

 

Facilitating Change

Agile projects often involve significant changes, whether in processes, team structures, or project goals. Such changes can be met with resistance, especially if they disrupt established routines. Program managers with strong emotional intelligence can anticipate these reactions and manage them effectively. By clearly communicating the benefits of change and supporting their teams through transitions, they can reduce resistance and help their teams adapt more quickly, ensuring continued productivity.

 

Making Informed Decisions

In program management, decisions can have wide-ranging impacts across multiple teams and projects. Emotionally intelligent program managers consider not only the technical aspects of their decisions but also the emotional and relational consequences. They understand that the way a decision is communicated can be just as important as the decision itself. By involving the right people, considering emotional impacts, and communicating transparently, these leaders ensure that their decisions are well-received and supported by those affected.

 

Building Resilient Teams

The ability to build resilient teams is another area where emotional intelligence is invaluable. Agile projects, by their nature, involve iteration, and setbacks are inevitable. Program managers with high EI can help their teams recover from these setbacks by fostering a culture of learning and continuous improvement. They encourage reflection on failures, facilitate discussions on how to improve, and provide the emotional support necessary to keep the team focused and motivated for the next challenge.

 

Conclusion

Emotional intelligence is not just an optional trait for agile leaders and program managers—it is essential for their success. By developing their EI skills, leaders can improve team collaboration, resolve conflicts more effectively, and drive motivation and engagement. These abilities are crucial for the success of agile projects. As organizations continue to adopt agile methodologies, the demand for emotionally intelligent leaders will grow. Developing and leveraging these skills will be key to thriving in the complex, dynamic world of modern project management.

 

References

Goleman, D. (2005). Emotional Intelligence: Why It Can Matter More Than IQ. Bantam Books.

Druskat, V. U., & Wolff, S. B. (2001). Building the Emotional Intelligence of Groups. Harvard Business Review.

Bradberry, T., & Greaves, J. (2009). Emotional Intelligence 2.0. TalentSmart.

Mayer, J. D., Salovey, P., & Caruso, D. R. (2009). Emotional Intelligence: Theory, Findings, and Implications. Psychological Inquiry.

Dulewicz, V., & Higgs, M. (2005). Assessing Leadership Styles and Organizational Context. Journal of Managerial Psychology.

Boyatzis, R. E., & Sala, F. (2004). The Emotional Competence Inventory. Hay Group.

PMTimes_Jun1_2024

The Value of a Project Charter

Written by Lauren Zinsmeister on . Posted in Articles.

If you’re familiar with the Project Management Book of Knowledge, or PMBOK for short, you know all about the Project Charter and its criticality to the success of a project. The PMBOK says that the project cannot start until the Project Sponsor formally signs off on the Charter.

 

Having worked at midsize companies for nearly 15 years, I learned that actual Project Charters with formal sign-off are more of a “big company” thing. To date, I haven’t once been required to write a Charter or get one approved to begin a project. Let me tell you why I insist on a Charter and have more than just the Project Sponsor sign off before I kick off a project. Come with me on this thought journey.

 

If I had to pick a single area of knowledge from the PMBOK as the most critical, I would pick Stakeholder Management. You can have the best plan and the best tools, but a tumultuous stakeholder situation can completely derail a project. On the flip side, you can have a scrappy team with few processes and subpar tools, but with committed people working well together, a project can succeed in spite of other project elements being challenging.

 

If I had to pick an area of knowledge to be second most critical, it would be Time Management. This encompasses your ability to scope the project, break it down into tasks, understand dependencies, build a project schedule, and keep the team aligned with each other as well as the schedule. In a sense, it’s a superset of a few other areas and captures the core of your project plan.

 

Enter the Project Charter, which I would argue is the most critical project artifact. Below are the basic elements of a good Project Charter:

  1. Problem statement
  2. Business case
  3. Goal statement
  4. Timeline
  5. Scope
  6. Team members

 

Diving into these 6 elements, we see 1, 2, 3, and 6 align to Stakeholder Management and 4 and 5 align to Time Management.

 

Advertisement
[widget id=”custom_html-68″]

 

Let’s start by looking at the Stakeholder Management elements.

  • Problem statement – Having this clearly written in the Charter ensures that key stakeholders agree a problem exists. They are agreeing on what that problem is. Finally, they are agreeing that this project is the right approach to solving the problem.
  • Business case – Here is where stakeholders are agreeing that this project is worth the resources. It’s possible to have everyone agree that a problem exists and needs to be solved, but it’s something entirely different to agree on its priority and resourcing.
  • Goal statement – Different people can look at the same problem and come to a different conclusion about how to solve it. Articulating the goal in writing will avoid assumptions and make it clear to stakeholders what everyone is working toward. Without stakeholder alignment on the project goal, the project is doomed to become tumultuous when the project team inevitably encounters a fork in the road.
  • Team members – We’ve agreed we have a problem to solve, we’ve agreed it’s worth investing in, and we’ve agreed on what the ultimate goal looks like. This section gets specific about whose time will need to be invested, what the commitment is, and what their responsibilities will be. Key stakeholders reviewing the Charter will be able to think through the impact on their teams and make sure they are able to commit the team members required. They will also be able to identify other team members who may not be listed, helping to complete the project team.

 

Our remaining two elements are tied to Time Management, though agreement on these is also inextricably tied to Stakeholder Management.

  • Timeline – To be able to write this section of the Charter, you will have had to do some high level project scoping and establish your project structure. Do you have phases? Stagger starts? Is your execution stage planned to be managed using Agile methodology, so the timeline needs to be flexible? All of those considerations and more are required for a timeline estimate. Putting this estimate in front of key stakeholders in the Charter ensures they understand the high level of time commitment. This provides an opportunity for discussion if some stakeholders think it needs to be completed faster or someone says they can’t commit the required resources for the deadline, so the project needs to be extended.
  • Scope – They say the devil is in the details, and this is where those details live. Clarity on scope allows for work estimates, project scheduling, and work coordination among team members. Clarity on out-of-scope work is just as important, because that enables you to define “done,” wrap up the project when in-scope deliverables are complete, and hand off deliverables and/or processes to business-as-usual owners for long-term ownership. The clearer you can be about your scope in the Charter, the fewer struggles you’ll have with scope creep later.

 

I personally expand on these base elements with a couple of my own tried-and-true tools. Seizing the opportunity to get stakeholder alignment, I also include the below:

  • Communication plan – I use this section to detail what information will be shared with which stakeholders as well as the method I will use. This is especially important if some team members or stakeholders are in different time zones, and even more important if there are people from multiple cultures. Communication norms vary in different cultures, so I like to ensure everyone knows what to expect and has an opportunity to raise a hand if they need something different from what I had originally planned.
  • Project change management – What are the criteria for something to be considered a project change? What process does it go through to be approved? Who has the authority to approve a change? Stakeholder alignment up front will save time and struggle when someone wants to add a deliverable to the project or expand the project to include related work that is discovered during project execution.

 

The Project Charter provides the best opportunity for you to detail critical components of your project and get stakeholder alignment. You can’t possibly list every detail, but you can align on your plans, processes, and expectations so everyone is working in the same way when questions and challenges inevitably arise.

PMTimes_Oct04_2023

A Self-study about the Impact of AI on Project Stakeholder Management

Written by Anju Aggarwal on . Posted in Articles.

I want to know the exact details of how AI can help project managers.

Not much concrete work is done in this area, so it is hard to find scientific papers or case studies about the impact of AI on project management. 

In this situation, I had to rely on the most powerful and trustworthy method, i.e., Self-help.

To understand the influence of AI, I picked one specific knowledge area: Project stakeholder management.

I will try to find out the benefit of using an AI tool or system on the four processes that comes under this knowledge area.

 

These days, I am reading loads of articles related to “AI in Project Management”. Being a PM, I always look for such articles with great curiosity and expectations. I want to understand how AI will impact project management.

 

To my dismay and frustration, most of such articles turn out to be fluff. I can categorize most of these articles into the following three brackets:

  • Some start with an explanation of AI and then get into details about different forms of AI like NLP (Natural Language Processing), ML (Machine Learning), Generative AI, etc.
  • A few articles mention various tools that use AI. Unfortunately, these tools had no relevance whatsoever to project management.
  • Many articles talk about the benefits of using AI in project management, such as automation, cost reductions, time savings, and better decision-making. In my opinion, all these benefits look like a general statement that goes for every other innovation too.

 

First, a refresher on what is project stakeholder management: 

Stakeholder management is the process of managing the expectations of anyone who has an interest in a project or will be affected by it.

 

The four process groups identified in project Stakeholder management are as follows:

  • Identify Stakeholders
  • Plan Stakeholder Management
  • Manage Stakeholder Engagement
  • Control Stakeholder Engagement

 

I will examine these processes and try to inject AI into their ITTO (Inputs, Tools, Techniques & Outputs) to the best of my knowledge.

I am not an expert in AI, so please correct me wherever you think there could be better usage of AI in that specific process.

 

Identify Stakeholders: Identify everyone, be it groups or individuals, affected positively or adversely by the project’s outcomes.

In this process, we check the existing project documents to identify all the stakeholders. These documents can be project charter, project proposal, or any contract created at the project beginning.

I do not think AI will be of any use in this process. Generally, a Project manager checks all these documents and lists all the stakeholders. PMs should also connect with project sponsors and other subject matter experts for their input in the stakeholders list.

 

Every project is unique in nature with its own enterprise environmental factors (EEF). In such a case, it is not possible to develop a ML model that provides predictions for unique projects.

Stakeholder analysis is one of the techniques used in this process. The primary goal of stakeholder analysis is to gather information about these stakeholders and use it to make informed decisions, manage relationships, and mitigate potential conflicts.

Can we use AI here? Can we Develop an ML model to categorize the stakeholders according to their power and influence automatically?

 

A few questions to ask: Is it worth the effort? What could be the maximum number of stakeholders in a project? Let us assume that the project is big and complex, so we have many stakeholders identified. Can we create a machine learning model by mapping different attributes like stakeholder’s interests, concerns, and influence and then classify them based on their level of interest and power or influence? The input data would vary a lot for each project. In such cases, the models would need a large amount of data for training to identify patterns for predictions.

 

Let’s assume we can create an ML model that can define stakeholders’ engagement strategy depending on their power/influence/interest. Will this model add much value to the organization’s productivity?

I feel a project manager could do the stakeholder analysis more quickly and accurately.

The output of this process is a stakeholder register.

 

Advertisement
[widget id=”custom_html-68″]

 

 

Plan Stakeholder Management: comes up with the management strategies required to engage stakeholders effectively.

This process also requires the PM to check project-related documents.

Mind mapping is one of the techniques used in this process. It is a visual tool.

 

Can AI be useful in this technique? We could automatically create a Mind map using the stakeholder register constructed in the previous process. PMs can then develop an engagement strategy or prioritize the engagement efforts based on the mind maps. This automated process saves time and effort for the Project managers.

Is this a good AI use case? No, according to me. The mind mapping tools might already have the feature to import a risk register as an Excel or doc file. So, I don’t think it is justified usage of ML for developing mind maps from Stakeholder risk register.

The output of this process is the Stakeholder Engagement Plan.

 

Manage Stakeholder Engagement: This process outputs effective communication with stakeholders and works with them to meet their needs through meaningful and appropriate involvement in project activities.

This is primarily an execution phase where documents are updated on a need basis. An ML model cannot predict this day-to-day process. So, an AI chatbot cannot replace a project manager here. A PM needs to have active interactions with stakeholders. PM needs to listen to what the stakeholder is saying and try to infer what the stakeholder is not saying.

The tools & Techniques in this process talk about interpersonal and communication skills, which are tough to emulate via an AI chatbot. I feel if a stakeholder gets to know that a bot is doing communication instead of a human PM, they might view it as a communication breach. I cannot imagine a stakeholders’ meeting where an AI bot is giving a status update report, and all the stakeholders are nodding their heads, feeling proud and in awe about this technology feat.

 

Control Stakeholder Engagement: This is the process of monitoring overall project stakeholder relationships and adjusting the strategies and plans for engaging stakeholders accordingly.

One of the techniques in this process is decision-making – Multicriteria decision analysis (MCDA)

MCDA is a structured approach for evaluating and comparing multiple criteria or factors when making decisions. It also requires data collection, assessment, monitoring, and readjustments.

We can use some software for decision-making that uses custom-trained ML models. I feel the attributes to train the models would be humongous and human centric. It would not be useful to create custom models for stakeholder engagement.

 

I have covered all four processes involved in the Project Stakeholder Engagement knowledge area.

In this exercise, I tried to put an unbiased perspective where I wanted to incorporate AI consciously in the Project Stakeholder Management knowledge area.

 

My concluding thoughts on how AI would impact Project Management:

The Project management stream requires more behavioral skills than technical skills. It requires human eyes, ears, brain, and heart. It cannot be completely replaced by Artificial Intelligence generated robots or systems.

 

As mentioned earlier, I am a project manager, not an AI expert. I would look forward to constructive input from other AI experts. But for the AI bots generated comments, please stay away!

 

PMTimes_Sep27_2023

Manage Your Opinions for Optimal Decisions

Written by George Pitagorsky on . Posted in Articles.

If you are ready to improve your team decision making “Do not search for the truth; only cease to cherish opinions.”[1]

When you cease to cherish opinions you avoid unnecessary conflict and achieve optimal decisions by allowing the “truth” to reveal itself through analysis, intuition, and dialog.

There is nothing wrong with opinions. Just don’t cherish them. To cherish them is to be attached to and identified with your opinions. Avoid this because it gets in the way of finding optimal decisions and it fuels unnecessary conflict and division.

 

What are opinions?

Everyone has opinions. They are the result of our experience, beliefs, knowledge, and training. They express our intelligence. They can be useful, and they can also get in the way.

Opinions are beliefs, points of view, assumptions, or judgements. They are not conclusive, not facts.

Often, we do not have the luxury of making fact-based decisions. Our issues may be too complex. Data may not be available. We may act on an opinion and gut feel, but if we do, it is best to do it with objectivity and self-awareness.

 

Objectivity and Self-awareness

Objectivity knows the difference between fact, certainty, and opinion. It values facts and realizes that subjectivity is also valuable. Self-awareness tells you when your attachment to your opinion is causing emotions to surface and you to resist questioning your opinion.

Together these two, objectivity and self-awareness, are key to effective relationships. And effective relationships are critical success factors. They are displayed in decision making, conflict management, planning, problem solving, change management – just about every aspect of project work or any kind of collaborative effort.

 

Managing Opinions

We are living in a time when beliefs and opinions are confused with facts and reality. People have lost the distinction between objectivity and subjectivity.

Are you willing to question and validate your beliefs and assumptions?

 

“When you see …, how belief, prejudice, conclusions, and ideals divide people and therefore breed conflict, you see that such activity is obviously not intelligence.

  Will you drop all your prejudices, all your opinions … so that you have a free, uncluttered mind?

If you say it is impossible, you will never find out for yourself what it is to be intelligent.” — J. Krishnamurti Excerpt from Can Conflict End?

 

Opinions Drive Action

Manage opinions well because they drive action. We hold opinions about team values, what vendor to use, how best to perform some tasks, who to hire, promote, or fire, and more. Opinions directly affect performance because they influence decisions.

Clearly, we want to make sure we understand the need to put opinions under the microscope and see their source and why we have them. Our approach is to balance opinions and fact-based analysis to make decisions that consider opinions and seek optimal results.

 

Attached

Being attached to and identified with opinions gets in the way. What does it mean to be attached to and identified with your opinions?

It means that you are so convinced that your opinion is “right” that you reject or suppress alternative opinions and refuse to question and validate your own. You are cherishing your opinion as if it were a part of your body. When you see it as an idea, a concept, you can value your opinion without being attached to it. This allows you to be open and respectful of other opinions.

Valuing is different than cherishing. You value your opinion because you think it is well founded on a strong belief, experience, data, theory, etc. You value it enough to state it and argue for it. And you also value the learning you get from exploring and validating your opinion.

 

Learning

Learning may strengthen your conviction that your opinion is worthy of being acted upon. Or it may show you that your opinion is not worth holding onto.

Learning comes out of dialog with opinions being shared and supported by the reasoning behind them. Be open to changing opinions to reach win-win outcomes and the actionable decisions that resolve issues most effectively.

 

Advertisement
[widget id=”custom_html-68″]

 

Beliefs

When opinions are based on strong beliefs, for example the belief that agile project management is always better than alternatives, there is a need to explore and question the underlying belief.

Fortunately, in project work we are less likely to find strong underlying beliefs driving decisions. When they do present themselves, we can justify confronting them because it is part of our best practices.

With beliefs regarding social and political issues it is not so easy. While these beliefs and the opinions that grow out of them is important, it is best to address them outside of business decision making.

 

Exploring Opinions

Should the sponsor of a project express her opinion, for example, “AI is too immature to waste our time looking at it”? Even if she isn’t convinced about her opinion, it will influence the team. As a leader, it is wise to hold back and open the space for opinions to be shared easily.

Other team members may have the opinion that there is something to be gained and that it won’t take much to explore how an available tool might be used to make the project go more smoothly with less effort and higher quality.

Wise leaders ask questions that lead the team (including the leader) to identify opinions and explore them to find the best outcome.

Are assertions backed by facts? For example, is AI not mature enough? Would it be too costly to explore? What biases are at work? What does ‘too costly’ mean?

 

Decision Making

Managing opinions is one part of decision making — the process that settles conflicts, underpins planning, vendor selection, and every aspect of team performance. It is a mission critical capability, no matter what the mission.

 

In the following articles I have explored decision-making from different perspectives:

 

[1] Seng-ts’an The Third Zen Patriarch,  Hsin Hsin Ming (Verses on Faith in Mind).