change management
 |
Think through System Changes to Anticipate Quality Issues When you replace or significantly modify components of a larger system, too frequently we focus on whether the code we are building functions correctly. This is important, but it’s also short-sighted. It’s easy to introduce errors because we are changing interactions. Coding bugs are only one quality problem. |
|
 |
Something to Remember When Managing Change at Work Grieving is usually associated with the loss of a loved one, but it’s equally relevant to loss triggered by changes in the workplace. If you are introducing or overseeing a change, it’s a mistake to belittle people’s reaction to the loss or excessively tout the benefits of the new way. Be sensitive to those affected. |
|
 |
Managing the Turbulence of Organizational Change In times of major change, particularly organizational change, it's normal for people involved to experience turbulence, including anxiety, anger, or uncertainty. If you’re overseeing a change, how you communicate with those affected can significantly decrease—or increase—the duration and intensity of that turbulence. |
|
 |
The Software World Is Changing—Are You Willing to Change with It? The software landscape is changing. Processes are becoming quicker and leaner, but instead of re-evaluating some of our traditional practices, we sometimes try to make them fit where they don't belong. This holds back continuous improvement. If you want change, you first need to be willing to change. |
|
 |
Managing Resistance to Organizational Change Change can be difficult, and some people's reaction is to shut it all down. If they think their concerns aren’t being heard, they get defensive, and your project is on a trajectory for disaster. Don't fire off an email while tempers are running high. Managing expectations thoughtfully is essential to project success. |
|
 |
The Importance of Timing when Implementing Change Too many changes at once can prolong upheaval and delay people's adjustment to the new norm. If you are planning to start a complex project, introduce a new tool, or undertake any other major initiative, and employees are still reeling from other changes, it may be wise to delay the planned change if you can. |
|
 |
Shake Up Your Software Processes: The Intermediate Disturbance Hypothesis Organizations that refuse to change will get left behind. But at the other end of the spectrum, too much change is also harmful. Revamping everything you do at once creates stress and can lead to your efforts failing. The right balance is shaking things up just often enough to experiment with new ideas. |
|
 |
How Do We Sell the “Test Early” Principle? Many companies are striving to test earlier. But goals and principles are always easier to articulate than they are to implement. Often, this is less of a technical issue and much more an organizational, change management challenge. Michael Sowers talks about the steps to take to make things happen. |
