dcsimg
June 19, 2018
Hot Topics:

Why Are Developers So Resistant to Change?

  • January 24, 2013
  • By Developer.com Staff

Over the years, developers have developed a reputation for being resistant to change. In this article, Datamation's Eric Spiegel offers five reasons why developers may be reluctant to try new processes and development tools:

  1. Shame—When developers get caught doing shoddy work they may be embarrassed and resist efforts to make changes designed to avoid the same problems in the future.
  2. Bad timing—if a proposed change might delay project delivery, developers understandably resist.
  3. Fear—like many people, developers sometimes fear changes that are unfamiliar or that they don't understand.
  4. Mistrust—developers who have had bad experiences with mandated changes in the past may not be very willing to give additional changes a fair hearing.
  5. Just becasue—some developers just have personalities that are naturally resistant to change.

Spiegel tells managers, "If your best efforts to avoid the other change resistance factors are not sinking in, don’t waste too much time on these folks. Instead, focus on winning over the majority of the staff. Then consider it a victory and move on."

View article






Comment and Contribute

 


(Maximum characters: 1200). You have characters left.

 

 


Enterprise Development Update

Don't miss an article. Subscribe to our newsletter below.

By submitting your information, you agree that developer.com may send you developer offers via email, phone and text message, as well as email offers about other products and services that developer believes may be of interest to you. developer will process your information in accordance with the Quinstreet Privacy Policy.

Sitemap

×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date