Resolving Stakeholder Conflict in High-Stakes Government Project
In a government project several years ago, I was tasked by the CEO to address a critical internal conflict that was jeopardizing the progress of an important initiative.
The situation involved a misalignment between key internal stakeholders, including the Project Team, the Architect, and a particularly difficult Manager—whom I’ll refer to as Mr. D, who was overseeing the site in question. The root of the issue stemmed from a significant misunderstanding: Mr. D believed he was receiving a new facility, when in reality, the funding allocation was only sufficient for a renovation.
My typical approach in such cases is to first hold a pre-meeting with all key decision-makers. This serves as a strategic session where we review potential risks, clarify positions, and ensure alignment on the negotiables and non-negotiables. For this project, key points included that Mr. D would not receive additional funding in the current or next fiscal year, and that a more feasible design solution would be proposed.
However, when it came time to brief our Planning Director, he declined to attend the pre-meeting, claiming he was already well-versed in the mandate and didn’t need further briefing. This decision was concerning, as it suggested a lack of preparation for what was sure to be a tense and complex conversation.
The meeting itself began with a lengthy back-and-forth about who had said what, with the Planning Director misinterpreting key details and referring to elements that appeared to relate to a different site altogether. It was an uncomfortable situation, as we had to step in and tactfully correct him.
Then came the real shock: Mr. D raised a concern, and the Project Manager was ready with a well-prepared response, only for the Planning Director to unexpectedly announce, “Mr. D, we’ll be able to accommodate your vision of a new facility in the next budget.”
The room fell silent. It was a moment of disbelief, none of us had anticipated such a statement, particularly from our own Director.
With the conversation spiraling, I, along with a senior colleague from another division, attempted to steer the dialogue back on track. However, the Planning Director continued to assert his authority, saying, “I’m the Planning Director, and I know what we can and can’t do.”
As John C. Maxwell wisely puts it, “If you have to tell people you’re the leader of the pack, you’re not.”
At that point, I had to take control of the situation and, unfortunately, shut down the conversation to prevent any further damage. I ended the meeting with a promise to follow up and resolve the issues. The Planning Director, however, was incensed and even threatened my position.
After the meeting, he continued to argue his case by making disparaging comments about both the CEO—his direct superior—and the GM, who had not been present. Incredibly, I received numerous calls from colleagues demanding his removal from the project. Even Mr. D himself called to voice his displeasure.
Despite his technical brilliance, the Planning Director lacked essential people management skills. He couldn’t read the room, failed to understand basic project details, and worst of all, operated with a sense of superiority that was both disrespectful and untenable.
Within 48 hours, I convened another meeting with Mr. D, our CEO, and the Project Manager—the true subject matter expert—to resolve the outstanding issues and bring the project back on track. This time, we reached a mutually beneficial solution that salvaged Mr. D’s reputation and restored momentum to the project.
As for the Planning Director? He was ultimately removed from his role, permanently.
This experience reinforced an essential leadership principle: while a title may open doors and offer initial credibility, true influence and success in leadership are built on respect, clear communication, and the ability to engage with others constructively. If you fail to do that, your title won’t keep you in the room for long.
