Five Human Challenges With Executing Project Development
And Resolution Strategies That Change Average Project Managers into Great Ones
In the previous Note, we explored how to translate a strong project concept into evidence-based deliverables that balance cost, speed, and quality.
We established that passing a strict “Go/No-Go” gateway at the Concept stage is a prerequisite before a project owner and project manager dedicate substantial financial resources to the detailed feasibility and structuring work in the remaining 4 stages of project development.
I also described how successful project development is scoped and executed to pass rigorous commercial, technical, environmental, and legal due diligence carried out by investors.
Let us assume you have done everything right up to this point.
The senior management has given an enthusiastic “Go” decision; they have even approved a budget for project development, the internal team is in place, and any external consultants have been selected to deliver a robust scope of work in line with quality expectations.
Yet, deadlines slip, conflicts arise, and team friction slows down efforts or even grinds them to a halt.
The uncomfortable truth is that while we manage tasks, budgets, and schedules, we must ultimately lead people.
Most reasons why large infrastructure projects fail to be completed on time and within budget are behavioural and organizational rather than purely quantitative.
Poor morale, poor human relations, and a lack of commitment from project participants can derail the most brilliantly scoped initiative.
Even the most competent teams can be slowed down by human inter-relational friction, shifting stakeholder expectations, and organizational politics.
To keep your infrastructure project moving well, a project manager must understand the complex interaction of organizational and behavioural variables to foster execution that delivers.
This note explores five common human challenges that slow down quality project development and provides actionable strategies and tips for addressing those challenges.
Challenge 1: Destructive Conflict and Lack of Psychological Safety
In a high-pressure project environment, conflicts are inevitable. While some conflict is beneficial—such as a healthy debate over a technical design versus its financial cost—it easily devolves into destructive interpersonal conflict.
When team members lack psychological safety, they become fearful of exposing mistakes, viewing bad news as a personal failure or damage to their reputation, or are afraid to challenge actions that may need to be challenged. For example, if an engineer discovers a fatal flaw in the geotechnical data but fears the wrath of a domineering project sponsor, they might hide the information, which leads to bigger issues and long-term impacts later.
This lack of transparency erodes quality development because the team spends more time playing internal politics and protecting their turf than openly discussing real issues and collaborating on solutions.
Strategies for Navigating Conflict:
Establish Clear “Rules of the Road”: At the project kickoff meeting, the project manager must establish operating rules for the team, detailing how disagreements will be handled and emphasizing that no single individual has a monopoly on the truth.
Adopt a Collaborating/Confronting Approach: Project managers must avoid withdrawing from or smoothing over serious conflicts. Instead, they should tackle the problem head-on through constructive problem-solving and confronting the issues. This involves engaging affected parties to identify the root cause of the conflict, focusing on facts rather than personalities.
Foster a Culture of Appreciative Inquiry: Shift the team’s mindset from a culture of blame to one of continuous learning. Focus attention on what the team is doing right and use those strengths to address the identified barriers. When team members feel their professional growth is supported, they are far more likely to engage in open, productive dialogue.
Objective Conflict Resolution: What worked for one conflict may not always work for another conflict; nevertheless, there must be fairness, reasonableness, and practicality in how issues are resolved. Showing favoritism with some and tolerating bad behavior must be avoided to maintain objectivity in conflict resolution.
Challenge 2: Internal Politics and the Erosion of Commitment
Infrastructure projects can take a considerable amount of time to progress from concept to financial close. During this time, it is common to experience “project fatigue.” Executive sponsors may leave the company, or corporate priorities shift, leaving the project underfunded or under-supported and the initial enthusiasm that fueled the “Go” decision naturally dissipates.
When internal politics take over, departments begin competing for the same human and financial resources, contaminating the project environment. If the project team feels they have lost the unwavering support of the C-Suite, morale plummets, and the pace of development crawls.
A competent team cannot function at a high level if it believes its project might be arbitrarily cancelled due to the personal whims of new management.
Strategies to Sustain Commitment and Support:
Continuous Internal Project Marketing: Project marketing is not just for external investors; it is a vital internal function. The project manager must continually “sell” the project’s strategic value, progress, and alignment with corporate goals to internal stakeholders and senior management. Keeping the project visible and relevant ensures ongoing resource allocation with regular, proactive status updates to the management teams. Regular, transparent briefings prevent executives from losing touch with the project’s complex realities.
Manage Transitions and Acknowledge Milestones: Recognize the transition phases in project preparation, where details from the previous step are crucial to complete the next, such as the handoff from Commercial feasibility to detailed design to CAPEX estimation. Manage these transitions well. Check if documents are sent or uploaded on time, in the acceptable format, and on time so that work can progress.
Then acknowledge and even celebrate these smaller milestones, so that the team can take into account the progress it makes against the project deliverables and take satisfaction from those wins while working toward the large one of financial close.
Communicate Cancellation Decisions With Empathy: One of the hardest things is communicating with empathy while managing your own disappointment. Yet if the management team has decided to scale down, delay, or stop a project that is already being developed, the project manager has the unenviable job of ensuring clear communication to the team and any other external stakeholder without using incendiary language that stokes discontent. They must also be ready, if necessary, to receive the first unfiltered outburst or emotional reaction of the parties receiving the news, without taking it personally or reacting badly and escalating the situation.
Challenge 3: Unmanaged Stakeholder Expectations and Optimism Bias
Infrastructure projects involve a vast web of stakeholders: local communities, government regulatory agencies, debt investors, equity partners, and internal senior executives. A massive relational challenge occurs when the expectations of these diverse groups are poorly managed or inherently conflicting.
Early in the project, sponsors and executives often exhibit “optimism bias,” pushing for aggressive timelines and low budgets to get the project approved. They view the project through rose-colored glasses, ignoring potential environmental bottlenecks or procurement delays. When the competent project team eventually uncovers the complex, expensive realities of the project during early-stage feasibility studies, it clashes with the unrealistic expectations set by senior management. This results in frustration, loss of morale, and executives feeling that the team is underperforming, when in truth, the initial expectations were impossible.
Strategies for Managing Expectations:
Deploy the IDEAS Framework: In this note This 12 Minute Read Could Save Your Project Months of Pain, I shared the IDEAS framework (Identify, Define, Engage, Align, Succeed) to proactively categorize stakeholders and understand their unique requirements against the project requirements and see where alignment could occur. Also very important to limit assumptions by asking questions and seeking clarity.
Communicate Bad News Early and Effectively: A project manager must possess the courage to present unpopular findings and recommendations to decision-makers, including the reality of schedule slippages. Educate senior management and the client on the detrimental consequences of unwarranted scope changes and negotiate mutually acceptable terms before the baseline is entirely shattered.
Implement 3 R&S Checks (Reality, Reasonableness, and Sanity): The project team must continuously subject executive assumptions and cost forecasts to independent, critical, and objective checks. By validating data against historical benchmarks and past project post-mortems, the project manager can ground executive expectations in reality.
Challenge 4: Silos and the Breakdown of 4Cs in the Project Team
The foundation of any successful project is what project development experts refer to as the 4Cs: Communication, Coordination, Cooperation, and Collaboration. Despite assembling a team of highly competent engineers, financial analysts, and legal counsel, a project will stall if these professionals operate in isolated silos.
A common challenge in scaling organizations is “over-the-fence” management, where one department completes its portion of the scope and simply “throws it over the fence” to the next department without proper communication or integrated planning. This leads to immense frustration. For instance, the engineering team might finalize a technical design without continuous input from the business analyst, only to discover weeks later that the design is too expensive to meet the forecasted demand.
Furthermore, poor communication quickly produces bottlenecks. When a situation of mistrust prevails between the project team and functional managers—or between the developer and external stakeholders—the project slows down as people begin writing “protection memos” to avoid blame, exponentially increasing unnecessary paperwork.
Strategies to Address A Breakdown in 4Cs:
Regular Update and Resolution Meetings: Eliminate silos by holding regular, well-structured project team status meetings that bring different functional experts into the same room. This cross-pollination ensures that legal, technical, and financial teams are moving in lockstep, recognizing their dependencies early.
Promote Active Listening and Empathy: Project managers must spend considerable time communicating with individual team members about their personal needs and concerns. Active listening—hearing the message without immediately judging or interrupting—builds the trust necessary for true cooperation.
Structured Fairness in Application of Rules: Communication should not be left to chance. Project managers must proactively manage the communication environment by defining what information is needed, who needs it, when it is needed, and how it will be delivered, ensuring a balance between those who need to know so they can act and those who are just updated, so they can provide other types of support later.
Challenge 5: The Authority Gap and Matrix Organization Conflicts
Infrastructure development teams usually operate within a matrix organizational structure. In this setup, the project manager is accountable for delivering the project but often lacks direct, formal authority over the functional team members (like engineers or procurement officers) who still report to their respective line managers.
This creates the “authority gap.” The project manager must motivate functional representatives to dedicate project support from their functions, while mindful that the functional managers control the performance reviews and salaries of these experts. If a line manager decides to pull their best piping engineer off your project to work on another priority, your project immediately stalls. Conflicts erupt over shifting priorities, competition for scarce resources, and overlapping responsibilities.
Strategies to Bridge the Authority Gap
Leverage Project Sponsorship: The project sponsor (usually a senior executive) must act as a referee when disagreements arise between the project manager and functional line managers. The project manager must keep the sponsor informed and leverage their executive authority to ensure line managers honour their resource commitments.
Rely on Interpersonal Influence: Because formal authority is limited, successful project managers rely on practical ways to build strong personal alliances and friendships in the organisation and with the team. By understanding the needs of the individuals over whom they have no direct authority, project managers can win loyalty and minimize resistance.
Define Clear Roles and Responsibilities: Implement a Responsibility Assignment Matrix (RACI), which clarifies exactly who is Responsible, Accountable, Consulted, and Informed for every major work package. This eliminates confusion and prevents functional managers from pulling resources without proper consultation.
Bringing it all home
As a project manager, with my own figurative battle scars, I can tell you from painful lessons that the project manager’s role extends far beyond managing spreadsheets, schedules, and deliverables.
Our role is to align the work of diverse human beings toward achieving a single goal.
The reality is that most infrastructure projects do not fail because the engineering was impossible or the financial model lacked mathematical precision. They fail because communication broke down, stakeholders felt ignored, and unmanaged conflicts evolved into toxic organizational politics.
The true test of your leadership as a project manager lies in the crucible of project execution, where the unpredictable nature of human dynamics constantly threatens to derail even the most meticulously crafted plans.
To keep your project moving forward, you must review and consider the strategies that help to resolve conflict, achieve effective communication, provide psychological safety, and maintain respect.
It requires human interrelation skills in addition to understanding the quality of deliverables required to pass investor due diligence.
This is the mastery that must be learned and applied intentionally to create, organize, and deliver work that attracts institutional investors. It is the difference that shifts an average project manager into a great one. The kind that can be trusted to navigate the inevitable storms of infrastructure development to create assets that attract investors and impact society.
Reviewed to complete this note:
Project Management: A Systems Approach to Planning, Scheduling, and Controlling by Harold Kerzner
Navigating Project Selection and Execution for Competitive Advantage by John E. Triantis
Project Finance for Business Development by John E. Triantis