Project Management

Please login or join to subscribe to this thread

Are We Too Quick to Call Stakeholders Resistant to Change?

linkedin twitter facebook   Governance   Organizational Culture   PMO  
avatar
Lissette Indhira Pimentel Sosa
Community Champion
Program Manager| HARPER SRL Santo Domingo / Distrito Nacional, Dominican Republic

What if the stakeholders labeled as resistant are actually the ones seeing problems the project team has overlooked?

When stakeholders question a transformation, delay adoption, or challenge a proposed solution, their behavior is often interpreted as resistance. Yet some objections come from operational experience, previous failed initiatives, or concerns that were never properly addressed. Dismissing those perspectives can cost projects valuable insight. How do you distinguish genuine resistance from legitimate concerns that deserve reconsideration?
avatar
Marie Wood United States
To distinguish genuine resistance from valid insight, evaluate substance over sentiment: legitimate concerns stem from operational reality, offering specific root causes, edge cases, or historical precedents that highlight actionable flaws in the project design. In contrast, pure resistance often manifests as vague pushback, moving goalposts, or refusal to engage even when solutions are provided. By shifting your approach from defending the plan to conducting structured root-cause interviews asking "What specific scenario breaks this?" you turn perceived opposition into valuable risk management.

Please login or join to reply

Content ID:

Sponsors

Newsletters

Oct 28: Leadership Isn't a Popularity Contest
Oct 21: Leadership Takes Courage
Oct 7: The Skill That Refuses to Be Automated

See all newsletters