Skip to main content

Author: George Pitagorsky

George Pitagorsky, integrates core disciplines and applies people centric systems and process thinking to achieve sustainable optimal performance. He is a coach, teacher and consultant. George authored The Zen Approach to Project Management, Managing Conflict and Managing Expectations and IIL’s PM Fundamentals™. He taught meditation at NY Insight Meditation Center for twenty-plus years and created the Conscious Living/Conscious Working and Wisdom in Relationships courses. Until recently, he worked as a CIO at the NYC Department of Education.

Practical Perfectionism and Continuous Improvement

“One of the basic rules of the universe is that nothing is perfect. Perfection simply doesn’t exist…..Without imperfection, neither you nor I would exist” ― Stephen Hawking

 

“Continuous improvement is better than delayed perfection.” Mark Twain

 

Practical perfectionists use the urge for perfection as fuel for achieving it, accepting that while things could be better, they may never be perfect.

Practical perfectionism is at the root of quality improvement. We set standards and try to meet them with the goal of optimal performance – performing as best we can. We recognize that optimal performance is perfection even though there may be flaws, errors, and omissions.

 

Perfect

Sometimes things are perfect as they are:

  • People are happy, effective, accepting, flexible and resilient
  • Change and problems are well managed
  • Communication and relationships are healthy
  • Performance quality is high, and
  • There is a continuous improvement process that asks “How can we do better?”

In that ideal scenario the stakeholders are aware that everything is in motion, continuously changing. They know that expecting to sustain a static perfect state is a pipe dream – an unattainable hope. They know that perfection is in the process and not the outcome.  They strive for the perfect outcome even though they know it may not be attainable.

 

The word perfect is an adjective and verb. We perfect our process to make it perfect. According to Merriam-Webster the meaning of perfect is:

“Being entirely without fault or defect flawless. a perfect diamond. : satisfying all requirements : accurate. : corresponding to an ideal standard or abstract concept. a perfect gentleman.”

 

Perfectionism

Perfectionism is a character trait that can be healthy, positive, and functional or unhealthy negative, and dysfunctional. It is a need to have oneself, others, or things in general to be perfect. There is an uncomfortable felt sense, a pressure from within, when things are not perfect. There is a belief that perfection is possible and necessary.

Perfectionists set standards that they use to judge their own behavior, and the behavior of others. They assume that others expect them to meet those self-set standards.

When perfectionism operates unconsciously it gets in the way of optimal performance. For example, it can manifest as procrastination because things are not perfectly ready. “I can’t get started until I am absolutely sure that I won’t be interrupted.” Some perfectionists procrastinate or avoid acting because they fear that their work will not be perfect.

 

Perfectionism may emerge as a negative self-image or image of others because they are not perfect.

For example, a project sponsor keeps putting off the funding of a project because the design team cannot find the perfect solution or the selection of a key product or system is held up because there are  no perfect options.

The expectation that a team’s or individual’s performance be perfect can motivate high performance or, if the expectations are impossible to meet, over-stress and demotivate.

 

Advertisement
[widget id=”custom_html-68″]

 

Striving and Concerns

Perfectionists strive to achieve personal standards that they set themselves and are concerned that they won’t measure up. The striving may be focused on both themselves and others.

They worry and fear that they will be punished or rejected if they fail to be perfect in the eyes of others – their boss, client, peers, etc. They tend to promote the impression of their own perfection and work to prevent others having a negative impression.

The striving and concerns, when they are unconsciously driven, waste energy and create stress, the enemies of optimal performance.

 

Non-perfectionists

Non-perfectionists tend not to have pre-stated standards or expectations about themselves or others. Non-perfectionists are OK with whatever happens. While this leaves them with less stress and may even be a sign of enlightenment, it does not promote continuous performance improvement.

Acceptance is a positive trait, but it can also lead to stagnation and the degradation of performance. Healthy acceptance accepts things are as they are in the moment, that they will change, and that with effort they can be made better into the future.

 

Practical Perfectionists

Practical perfectionism involves setting rational performance standards and expectations and generating the motivation to achieve them. It is an example of how we can use a character trait to its best advantage.

It begins with the acknowledgement that perfectionism is at work. This is an aspect of self-awareness, the sense of what is happening internally and how it is influencing behavior.

With that awareness, perfectionism can be used as a powerful force in optimizing performance and promoting personal growth, emotional intelligence, and wellness. Perfectionism is accepted and managed.

 

Practical perfectionists have ambitious standards and bring rational thinking to bear. They assess why they think their standards and expectations are realistic. They look at the costs and benefits of improvement and decide whether to improve radically or incrementally, or to leave well enough alone, making the best of the situation.

Perfectionism is a positive trait if it is moderated by acceptance of things as they are, self-awareness, rational thinking, and realistic understanding of

  • what ‘perfect’ means,
  • whether and how it can be achieved,
  • how much it costs,
  • how long it takes to achieve it, and
  • whether achieving it is worth the time and effort.

Practical perfectionism drives continuous improvement and optimal performance.

 

Overcoming Obstacles to Perfect Performance

It is hard to imagine why anyone would not embrace a practical perfectionist mindset. But the reality is that there is resistance to self-awareness and rational thinking.

Overcoming obstacles to applying practical perfectionism to continuous improvement begins with self-awareness and understanding among team members and leadership at all levels..

When individuals realize that they are being overly stressed by their own perfectionism or are overly stressing others by expecting the impossible, they can act to change.

 

In projects the change comes about when perfectionist managers or clients realize that their expectations are irrational and counterproductive. Then the process of defining goals, acceptance standards, value, costs, risks, and benefits will lead to expectations that can be met.

Practical perfectionism combines emotional intelligence and analytical process thinking to promote a perfect process.

Practical PM for Everyone

Project management is a process that, when done well, enables optimal performance. Why wouldn’t everyone want to know how to manage projects?

 

Everyone Has Projects

A project is an effort to create a result in a finite time. According to PMI, “a project is a temporary endeavor undertaken to create a unique product, service or result. A project is temporary in that it has a defined beginning and end in time, and therefore defined scope and resources.”

Everyone is part of projects. Some projects are long, large, and complex, like a lunar expedition or the implementation of a new system in an organization. Others are moderate and more personal – planning a party, buying a car, moving, painting your house. Others are quite simple, for example getting up and out of the house, packing for a vacation, grocery shopping, doing the dishes, cooking a meal. Even the individual activities of regular operations like answering emails or working to close a sale fit the definition of projects. we can consider them as mini-projects.

 

Therefore, everyone would do well to know the basic principles of project management and adapt them to the size and complexity of the projects at hand.

Professional PMs would add value by promoting wide-spread appreciation and knowledge of project management for all.

 

Agile Adaptability

Applying a complex project management process with forms, protocols, and reports to manage your at home cooking dinner project or a small project that is repeated many times is not skillful.

You might like to be formal and explicit because it makes you feel good but if there are others involved you might drive them crazy and waste lots of time and effort.

 

At the same time, doing any project without a plan, without writing things down (for example a shopping list), with ambiguous or inadequate communication, and without looking back to learn from the experience is equally unskillful. It is likely to lead to extra trips to the store to get missing ingredients, too much or too little food, misunderstandings of who will do what, and when.

Planning, performing, monitoring, controlling, and closing happen in every project, the way we do them varies widely depending on the situation. It was the intention of the earlier founders of the agile approach to point this out and promote the idea that the project team does best to adapt practices to the needs of their project, stakeholders, and setting, while being aware of the need for a degree of structure and discipline.

 

Advertisement
[widget id=”custom_html-68″]

 

The Agile Manifesto:

“We are uncovering better ways of developing software by doing it and helping others do it.

Through this work we have come to value:

Individuals and interactions     over     processes and tools

Working software                     over     comprehensive documentation

Customer collaboration            over     contract negotiation

Responding to change              over     following a plan.

That is, while there is value in the items on the right, we value the items on the left more.”

http://agilemanifesto.org

 

Communication and Collaboration

To enable an adaptive and agile approach make sure that all stakeholders have a sense of  the basic principles of project management.

The basics are what everyone should know about managing a project, even if they are not managing one. Knowing the process and principles stakeholders can assess how well the project is being managed. They will be able to connect a sense of the project’s health  accomplishment and progress.

 

The basics are:

  1. Plan, to create a clear sense of what is to be accomplished, how, where, by when, by whom, and for how much it will cost. Remember that plans are always subject to change. Planning is not over until the project is over.
  2. Let go into execution, the performance. It’s like dance or a play. You learn the steps and your role and surrender into performing them.
  3. Mindfully monitor and control to assess progress against the plan and to adjust. Make it part of the performance so it doesn’t get in the way.
  4. Close. Take a step back to assess performance. Tie up loose ends. Learn from the experience. Turn over the results.

So simple, if there is understanding, adaptability, effective communication and collaboration.

Without these the project management process becomes a burden. With them the probability of project success goes way up.

 

What gets in the Way?

You’d think that everyone would be eager to apply the basics and to understand, adapt, communicate, and collaborate. But it is not the case.  The principle things that get in the way are:

  • Lack of process thinking – Thinking all that is needed is to put heads down and do the work instead of recognizing that objectives are met by skillfully applying effort to perform a set of definable steps or tasks.
  • Too much process thinking – over formalizing project management, creating unnecessary bureaucracy and overhead.
  • Not recognizing the value – thinking that the effort to manage the project is not worthwhile.
  • Thinking that it is too hard to engage others in the work required – believing that changing stakeholder mindsets about project management is impossible.
  • Personality traits – for example, closed-mindedness, impatience, fear of being criticized and controlled, and over confidence block attempts to implement some degree of planning and control.

 

What to Do About It

Removing the obstacles to implementing the right kind of project management (PM) requires a learning process in which PM champions convince stakeholders that PM is a practical process that adds value by upgrading performance and promoting project success.

Breaking through resistance to PM requires mindset change and changing people’s minds is no easy task.

 

It is not just about getting people to take a PM course, though an appropriate one, with a skilled facilitator, is a good place to start. It is committing to a dialog that addresses resistance to applying PM principles coupled with a commitment to the agility to adapt the principles to fit the projects being performed and the people who manage and perform them.

It takes time and patience with an understanding that much of the resistance is reasonable given experience with dysfunctional PM and rigid project management professionals who don’t adapt the process to the situation at hand.

Psychology at Work to Improve Performance

Most of what gets in the way of optimal performance is rooted in psychological or emotional issues. That is why the most valued traits for a manager are communication, emotional and social intelligence, empathy, and adaptability.

 

Psychology

Psychology is the study of the way the mind functions and influences behavior. Individual psychology influences relationships and relationships are the key to effective performance, wellness, and optimal living. It follows that attention to psychology is a pillar of performance management.

Though, in many organizations, psychology has gotten a bad name.  It falls into the mental health realm. Attention to it is often avoided unless behavior gets so severe that it undeniably gets in the way of living and performing well.

 

Take for example a steering group of peers charged with making important decisions. One member is designated as chairperson. The chairperson takes the title to heart, does a lot of good work, but attempts to silence anyone who raises issues regarding the team’s process and performance.

One team member confronts the chairperson by raising uncomfortable issues. Over time the relationship between the two deteriorated. The chairperson has left the team member out of important meetings, does not respond to emails and has ignored  a direct outreach by the team member to meet and discuss their relationship in any way the chairperson chooses – one on one, mediated, in person, virtual, etc.

The refusal to engage in a dialog effects the degree to which the group can make effective decisions because it blocks the social interaction that is critical to team performance. The rest of the team “feels” the subtle disturbance. Hearts and minds close down. The free flow of discussion is blocked. Life goes on, but it is not pleasant.

 

Avoidance

One doesn’t need a PhD in psychology to know that there is a psychological process at work in this relationship, that effects performance. Causes may be fear of competition, over-aggressive perfectionism, aversion to conflict, or over-controlling. These are all related to the participants’ mindsets.

This is just one example. Performance is effected by issues that stem from anxiety, depression, need for excessive control, excessive competitiveness, obsessive and compulsive urges, and addiction expressed as anger, withdrawal, and the kind of behavior that disturbs relationships – angry outbursts, abuse, withdrawal, unnecessary and poorly managed conflict, discrimination, gossiping, absenteeism, and more.

But there is avoidance. Handling psychological or emotional issues remains difficult. Some people believe that personal psychology is  “too personal” to be addressed in “public”.  They want to separate the personal world from their work world, as if that was possible.

 

Some are not introspective and don’t acknowledge the internal processes that lead to external behavior or, if they do, they may not think they can influence the process with self-management.

Some just don’t care how their behavior affects others, thinking and saying “This is who I am, live with it.”

 

Advertisement
[widget id=”custom_html-68″]

 

Changing the Narrative

Interest in emotional intelligence with a focus on performance has  changed the narrative  by changing the terminology – people want to be more intelligent, they do not want to be lumped into a mental health category. However, to become more emotionally intelligent one must

  • Acknowledge that behavior results from internal psychological processes, the individual’s mindset, and setting.
  • Recognize the effect on others of their speech, actions, and even their “vibe.”
  • Care.
  • Accept that mindful self-awareness enables self-management.
  • Manage emotions to optimally perform.

It becomes obvious that the person who expresses anger overtly or as passive aggressive behavior impacts the team’s performance. One who views any criticism as an attack gets in the way of performance improvement. One who is afraid of speaking up robs the group of valuable insights and information.

 

Look to the Process

Promoting process thinking is the key to being able to manage psychological issues. Process thinking recognizes that everything is caused by something – a process.

In general, a group will operate more effectively if the members acknowledge and skillfully address both the visible processes and the processes operating below the line of consciousness, as needed, to optimize performance.

 

For example, to overcome aversion to criticism, cultivate awareness of both the process improvement process and the presence of internal psychological processes that lead individuals to be overly and unskillfully critical or unable to accept and value criticism.

Participants can work together when they realize that the problem of aversion to criticism gets in the way of effective performance. It involves a conflict between the idea that constructive criticism makes a positive contribution vs. the need to protect oneself or one’s position.

 

Overcome Resistance

Cognitively knowing that behavior is the result of a process is an important starting point for cultivating the capacity to avoid unskillful behavior. However intellectually knowing that mental habits like aggression or avoidance are not effective does not immediately translate into behavioral change.

Rational thought is lost to the emotions and to unhealthy beliefs and mental habits. Psychological issues are often deep and painful. Habits are hard to change.

 

So how do we get people who are stuck in neurotic patterns like resistance to criticism, shutting down communication, and yelling, to change their behavior?

There is no simple formula. The complexities include the degree to which organizations can require people to be self-aware and overcome the resistance to psychotherapy.

With the knowledge that organizational performance is the sum of team and individual performance, effectiveness becomes the measure of how well teams functions. Organizations are motivated to create a culture in which addressing emotional and psychological issues is part of performance management.

 

At the same time the workplace is not the forum for psychotherapy. At work, addressing these issues is about changing behavior. It is up to each individual to assess the causes of the their own disruptive behavior and adapt it to benefit the health of the team.

Stop focusing on labels like depression and anxiety. Instead, focus on the symptoms and their impact on performance, where performance includes the happiness and wellbeing of the people involved.

 

Going Forward

There is a simple, though not easy, process: raise consciousness, apply it, and adjust so that it there is neither too much nor too little attention to psychology and its effect.

Cultural change is set in motion by training to acknowledge the need for self-management, process-awareness, and self-awareness and how to apply them in teams.

Regularly (not too often) dialogue about the symptoms and impact of psychological issues on performance and what to do about them. When issues arise address them in the context of what the team has learned. Over time, assess your process and adjust.

 

With the right mindset, behavior that downgrades performance automatically motivates action. That mindset needs the team to be willing and able to cut through the psychological issues that get in the way.

Depending on the culture and individuals involved, readiness for this kind of change can be quick and self-supported, or can take months or even years with expert coaching and consulting.

Collaborative Relationships Between Project and Functional Managers

This article addresses the project manager/functional manager relationship with an emphasis on collaboration, reporting, expectations, and empathy.

 

One of the nice things about PM is that the principles don’t change much over the years. One of the disheartening things is that the problems also don’t seem to change. Collaboration remains a key to the wellbeing of organizations, particularly, the collaboration between project managers (PMs) and functional managers (FMs). It is still a challenge that hinges on clarity, communication, understanding, and empathy.

 

Over the years there has been continued interest in a paper I wrote 25 years ago, The Project Manager/Functional Manager Partnership[1]. The key point then as now is that there is a need for clarity regarding roles and responsibilities, priorities, and communication protocols regarding commitments and status.  Clarity leads to understanding, hopefully, resulting in empathy – a sense of feeling for others.

 

Roles and Responsibilities

The role of the project manager focuses on the accomplishment of project objectives – getting the work done on time, within budget to deliver a quality outcome.

The role of the functional manager, a manager of a department usually associated with a specific discipline,  is to ensure that properly trained and well motivated resources (people) are available for project work. Some FMs lead departments that perform the work as a service, while others provide resources to be directly managed by project managers.

For example, the manager of a project management office is responsible for making sure that project managers are available for assignment to projects. Those PMs report directly to a program manager or steering committee with regard to project related activities.

 

The manager of business analysts provides her department’s people for work on projects and programs. The BAs typically report to the project manager. A Quality Assurance manager provides testing services as well as quality management standards and procedures, and oversite in the form of audits. Testers typically report directly to the FM and not the PM. Other functional managers provide engineers, procurement experts, attorneys, and more.

The manager of a software development department may be responsible for providing programmers to work on projects and ongoing system maintenance activities. Or they may be responsible for managing the programmers for the delivery of software for projects.

 

Reporting To

Regardless of whether the task is to provide people or services, functional managers “report to” project managers in the same way that a contractor reports to a client.

The idea of what “reporting to” means is a point of conflict between FMs and PMs. Commonly the term means that there is a hierarchy in which the person reporting to the other is under the authority of the other.

 

In project work, the FM does not report to the PM in that way. The PM does not have the authority to tell the FM what to do and how to do it. But the FM does have the responsibility to tell the PM what is going on, to provide information regarding plans, estimates, projections, status, and changes to resource availability.

Part of the needed clarity is about how and when this reporting will be done. Perhaps the most critical part of this reporting process is notification of changes to commitments.

 

Advertisement
[widget id=”custom_html-68″]

 

In healthy organizations FMs take part in project planning. They provide estimates and resource availability information. Where there is a well-functioning project portfolio management process, there is clarity about which projects are to be initiated when. This clarity comes from the knowledge of functional resource availability as well as the priority of each project.

So the FM not only reports to the PMs that he/she/they  serves but also to the portfolio manager. Whenever there is a change to resource availability it will impact project performance.

 

PM as Client

I find the analogy between FM and contractor to be helpful. A contractor knows that satisfying the client is the most important part of the job. If the client is not satisfied the contractor will suffer. Rational and empathetic clients will understand the contractor’s situation, protect themselves by being realistic in their expectations, and creating agreements that include provisions for both penalties and flexibility.

The FMs that treat the PMs their departments serve as clients deserving quality service will add greater value to their organizations and will better serve their own staff.

 

The FM’s Situation

The FM and the savvy PM know that there are multiple “clients” vying for the same resources. The FM needs to satisfy them all. Just like some clients, some PMs try to ignore this reality, making themselves believe that they are the only one.

Just like some contracting firms, some FMs overpromise, often caving into unrealistic demands and putting themselves and their resources under unnecessary pressure.

This leads to unreasonable irrational expectations. And irrational expectations lead to conflict, overwork, stress, burnout and missed deadlines.

 

That is where understanding and empathy comes into play. Effective collaboration is based on the understanding of the other’s situation leading to the ability to maintain rational expectations. This doesn’t mean to be “soft” and allow oneself to be taken advantage of. It means being reasonable and rational.

The FM needs to understand the PMs situation. If the project is behind schedule because functional resources or services are not delivered as expected, the PM will be accountable.

The PM needs to understand the FMs situation. The FM is not in control if resources are out sick or leave, or if project priorities change causing resource shifts. The best the FM can do is to report the situation as it is to the PM and portfolio manager, and be open to having project variances clearly pinned to functional performance variances.

 

With reasonable and rational expectations set at planning time and made part of the overall organization’s project management and portfolio management process, there will be less conflict, less unnecessary strain on functional resources, and a greater probability of project success.

If there is chronic conflict between PMs and FMs an intervention that seeks the causes and works to resolve them.

 

[1] Pitagorsky, G. (1998). The project manager/functional manager partnership. Project Management Journal, 29(4), 7–16 (https://www.pmi.org/learning/library/collaborative-relationship-roles-well-being-organization-2062)

Goals are NOT Expectations: Change Mindsets to Avoid the Suffering of Disappointed Stakeholders

Goals are something to work toward or aspire to. Expectations are beliefs that something will occur in a certain way. Goals are not expectations. And knowing the difference can help to avoid unnecessary disappointment and conflict.

 

Last month I wrote about embracing imperfection to achieve ongoing performance improvement. The implication is that we must expect imperfection, though it is certainly not a goal. Over time imperfection (for example schedule overruns, defects, and unnecessary conflicts) is very highly probable. So, expecting it to occur is realistic. It is what risk management is all about.

We also expect to achieve our goals. That expectation may be more or less realistic, depending on the goal and the capacity of the people involved to achieve it.

 

The Problem and Symptoms

While it may be wise to have no expectations, they are a natural part of life. The expectation is not the problem. The problem is failing to remember that the expectation is a belief or desire subject to uncertainty and change.

Failing to remember is a problem because it leads to unnecessary stress in the form of anxiety, anger, blaming, and more. Symptoms are conflict, unmet objectives, and the disappointment and unease of unfulfilled expectations.

 

Case Example

Imagine this scenario. Senior stakeholders have set a goal. To accomplish it means initiating work in late March, to meet the need to use an expensive, elite contractor team, only available for three months. At the end of June, the resources are firmly committed elsewhere.

According the contractor’s detailed schedule and a guarantee, the work these resources will perform can be done in three months, with some time set aside as a buffer to account for delays related to the work itself, for example sick time, slippage, testing, etc. The contractor agreement stipulates that if work does not begin in March there will be no guarantee of completion by June. If the team has to leave without completing the work the entire project will be significantly delayed.

Project management and the steering group expect that in the two months beginning January 30th the negotiation of a contract and the receipt of permission to perform the work from a corporate controller will be completed so our elite team can begin their work on the planned March start date.

 

Advertisement
[widget id=”custom_html-68″]

 

Contract negotiations with the involvement of a legal department has commonly taken an unknowable amount of time owing to the availability of attorneys, their priorities, and the issues that come up in the negotiation. The time the controller department takes to review and sign off begins only after the contract is signed and is subject to committee schedules and the number and type of issues found.

Senior sponsors expect the PM to take care of everything and get the job done. The PM believes that the predecessor tasks will be done quickly, trusting in the attorneys and accountants to do their jobs on time.

What is the likelihood of slippage? When it happens will there be anger and blaming or acceptance and understanding? Who will pay the costs associated with the delays.

 

The Cause

Over confidently expecting goals to be met with certainty is the problem. But what is the cause?

The cause is ignoring the fact that expectations are beliefs and that there is uncertainty about them being met. People tend to ignore this reality because they are so attached to the expected outcome that they can’t bear the thought that it won’t be accomplished. we tend to like certainty, especially when it comes to accomplishing or acquiring what we want.

The root cause of suffering is ignorance which appears as attachment and aversion, according to Buddhist psychology. It seems true. We tend to cling to an impossible idea or belief until we are convinced it is impossible. For example, being certain that we will meet our schedule (“I’m sure the legal department will get back to us with time to spare”).

Ignorance is an interesting word. Many people are insulted by being informed that they are ignorant, they don’t like to admit they are ignorant of something. Others do not realize or care that they are ignorant of something, for example the demanding boss/client/sponsor/project manager who is not aware of the complexity of the work that has to be done and the risks involved, and who isn’t motivated to find out.

The good news is that since ignorance is not having knowledge or information, it is curable.

 

The Solution: Risk Management

There is a solution to the problem of over confident expectations. It is to cure ignorance by making it clear to every stakeholder that uncertainty must be accepted because uncertainty in project work is an undeniable reality. That is why risk management is part of the project management process.

The core of the solution is to change mindsets. The desired mindset is one that expects uncertainty and change.

Mindset change can occur as part of a formal training program. Or it can be in the form of content in conversations, proposals and plans that highlight where there is uncertainty, what the probability of negative and positive outcomes, and what impact they may have. Mindset change can be as simple as presenting ranges of cost and schedule expectations.

With a change in mindset, practice estimating and scheduling skills to integrate risks and buffers to assess multiple scenarios and get a practical sense of how likely it is under various conditions to achieve the goal. Then throughout project life report, reassess and adjust as needed to manage expectations.

 

Going Forward

Eliminating the pain triggered by mistaking goals for expectations is simple. Get rid of ignorance and the light goes on making everything better. Simple but not easy. changing mindsets takes intention, time, and skillful effort. It is a change management or transformation program.

The effort is easiest if there is an existing process improvement process and mindset is addressed as part of it. If that is not the case, then the effort is more difficult. If the most senior leadership is open-minded and aware of the situation, change is more likely to be successful.

If the cause is not recognized on the highest levels, then rely on subtle bottom up change in which there is firm push back and skillful communication to set rational expectations.

 

References:
Managing Expectations: A Mindful Approach to Achieving Success by George Pitagorsky
The Zen Approach to Project Management by George Pitagorsky