|
|
Posted by Estela Kennen Oct 23, 2006 |
Nonprofits often work from the supposition that something is missing in their community (whether that be a town, nation, or world). It might be obvious to you and your staff that things need to change—after all, you are education and impassioned about the subject. But the people around you – from your potential clientele to city staff to potential funders – might not see the need for change, must less want it.
Resistance to change is a pretty common phenomenon, and even if most of the population around you is in rousing favor of your project, there will be some nay-sayers. There may even be plenty of people who like the idea in theory, but find it less than appealing when it will be occurring next door (NIMBY, anyone?)
Instead of ignoring the resistance, one useful technique may be to co-opt those resistant to change early in the process. That way, you can understand and be prepared for objections that may arise later on, and hopefully find compromises along the way.
Has your nonprofit met with resistance in implementing a project? How did you resolve it—or why do you think things didn’t work out?