Related Content
16 Questions to Assess Your Response to Major Change If your responsibilities include guiding others through major change, you might find it instructive to assess your own behaviors and response to change. The sixteen questions here can help you do just that. You can also use these questions to facilitate a discussion with your team about a current or upcoming change. |
||
A Checklist for Managing Go-Live Decisions and Risks If you have to replace a complex existing data system in production, decisions about when and whether to go live should be treated with gravity and care. One process that can help keep you honest is developing checklists that describe very clearly what is expected to be accomplished and verified at each milestone. |
||
Dealing with a Change-Resistant Manager With almost any change, whether a trivial adjustment in procedures or a large-scale organizational change, people will vary in their receptiveness to it. But if you and your teammates have some good ideas to improve processes and your manager keeps shutting them down, you may be dealing with a change-resistant manager. |
||
How Do We Land This Thing? Planning for Go-Live and Beyond Some project managers have little experience bringing a project in for a landing, so they can be dismayed or just blindsided by organizational change needs and stakeholders’ expectations at delivery. Here is a checklist of some commonly forgotten items to address when a project goes live, so be sure to plan for them. |
||
Handling the Emotional Turmoil of Organizational Change Chaos, confusion, and emotional turmoil are not unusual during major organizational change. Nevertheless, even people at the top sometimes minimize the impact of the change on employees—and on themselves. Worse, they sometimes do so dismissively. It's important not to underestimate the challenge of managing change. |
||
During Times of Major Change, Keep People Informed During times of major change, readily available information can help reduce the fears of those affected about what it means for them. If you’re involved in implementing change, it’s wise to keep people informed—not just about the change itself, but also about its impact on processes, responsibilities, and expectations. |
||
An Agile Approach to Change Management Many organizations are reluctant to introduce new tools or technologies, or even to update existing ones. The reason is often framed in terms of risk management, but agile teams already have the tools to manage the risk of change: testing and experiments. These approaches together eliminate gaps in risk identification. |
||
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. |