Changes in priority, scope, or personnel can leave teams feeling unsettled. Knowing how to properly combat these shifts to improve performance and morale is a key skill when leading engineering teams.
“The only constant is change.” It’s an often-said, but not particularly helpful statement. Especially when you’re in the midst of a transition that’s proving to be distracting, overwhelming, and difficult to navigate. As a developer, working through change requires leadership and intentionality. But how does one lead through change?
Tackling scope changes
Most of us are familiar with changes in scope. Commonly, people dealing with an increase in scope are being asked to do more with less.