Recognizing the Need for Change
Recognizing the Need for Change
I love the quiet of August. It’s in-between-ness. The heat hasn't broken, the morning light comes in a little later, and the rush toward the year-end hasn't started. That in-between space is a great opportunity to take stock and, hopefully, stay ahead of the need to change. This piece is for leaders who don't want to wait until it hurts to know something needs to change.
When something needs to change, recognizing it is the first step. It is not the whole of leading it, however. What strikes you is a signal; a pattern of friction, a repeated complaint, a stalled initiative, evidence that something in the system is asking for attention before it has clarified exactly what. The step that follows recognition is being honest about where that signal is coming from, because its origin shapes whether the organization can actually metabolize the change or whether it gets endured instead.
One axis is relational: listen across the board, the leadership team, the working team, and the constituents you serve, because a signal can originate in any one of these seats without ever showing up in the others. The second axis is the change itself: where something different is needed; a person, a process, the shape of the work, or a specific deliverable. Identifying the wrong one leads to solving a problem you don't actually have. Diagnosis draws on both axes at once; read only relationally and you'll know something's off without knowing what to do about it, read only the change type and you'll design the right fix for the wrong thing.
The origin of the signal
The relational axis casts a wide net. Signals arrive from the board, from constituents, from a team member's aside that wasn't meant to be a data point, from a leader's own read of the room. Volume matters; when independent voices across the system converge on the same concern without coordinating, that convergence is itself information. But volume can also be manufactured rather than arrived at; the same convergence that signals a real problem can just as easily be the sound of groupthink, or of people falling in line behind whoever raised their voice first. The relevant question is not how many signals are arriving. It's whether they carry directional consistency.
Earned Change. The organization outgrew its own structure through success. What worked at one scale creates friction at the next; the shift is not a failure to anticipate, it is evidence that something worked. The risk here is not resistance. It is under-crediting the moment as a real decision point and drifting into the next phase without intention.
Ambition Change. The signal originates inside the team, not from outside pressure; the work wants to broaden because the people doing it see more of what is possible. This is the change most easily mistaken for scope creep, particularly by leadership sitting above the team generating the signal. The diagnostic question is not whether the ambition is legitimate. It is whether the organization has the structure to hold a larger mandate before it builds one.
Reactive Change. The environment moved and the organization is responding; a funding cut, a political shift, a partner's exit. The signal is loud and undeniable, which is precisely why it gets treated as crisis management instead of change requiring real diagnosis. Reactive does not mean unplanned. It means the timeline was set by something outside the organization.
Anticipatory Change. The environment has not moved yet, but the signals are visible to anyone paying attention. This is the hardest case to build internal support for, because there is no crisis to point to; leadership has to choose to see the signal before it is forced on them, and choosing to see it early carries a cost. Someone still has to do the work of getting ahead of it, and that person is rarely given new capacity to do so; they are pulled off their existing deliverables to lead the proactive change while still carrying them. Organizations rarely fail anticipatory change because they missed the signal. They fail because acting early requires spending time nobody is required to spend, and capacity nobody has budgeted for.
Imposed Change. The change was not chosen by the people living inside it. It arrived by mandate, restructuring, or decree, and the organization was never asked whether it agreed. This is the least recognized of the five, because what was never chosen does not get processed as legitimate change. It gets endured. Endurance without recognition is where horizontal violence starts; the energy that should have gone toward the actual source of the change goes sideways instead.
The maxim about the pain of staying the same vs the pain of change; that's true for two of the five origins. It says nothing useful about the other three, which exist precisely to act before pain is the reason.
Deep listening as the diagnostic tool
None of the five origin types announce themselves cleanly. Ambition Change and Earned Change can look identical from the outside; both show up as a team asking for more. Reactive and Anticipatory Change can share the same underlying signal, arriving at different points on the timeline; the difference is only visible to someone paying attention before the crisis, not after it. Imposed Change is often the easiest to name and the hardest to creatively engage with, because the inorganic nature of the signal means you have to re-establish the bounds of acceptability.
This is why recognizing the need for change cannot be a single conversation or a single data point. It requires deep listening across the full relationship system; board, leader, team, constituents; for signals about the person, the process, the shape, or the deliverable while you manage a million other things. Deep listening is not the same as gathering feedback. Feedback answers the question you asked. Deep listening surfaces the question you did not know to ask, and it is the only way to correctly identify which of the five origins is actually generating the signal, rather than defaulting to the explanation that is easiest to act on.
Correct recognition is not a guarantee of success in a change management moment. In one organization, senior leadership knew precisely what needed to change: years of undercommunicated value and loose governance had left the function exposed. They were right. What they built to fix it was a horizontal team of individual contributors with no strategic mandate and no real ownership of the outcome, tasked with solving a problem nobody had actually defined. The effort produced no result. The organization absorbed a major hit in a company-wide layoff not long after, and three years later it still hasn't recovered its footing. Nothing about that outcome traces back to a failure of recognition. It traces back to what recognition alone cannot do.
The failure mode on the other end of deep listening is easier to spot in hindsight than in the moment: change driven by conviction rather than signal. One version of this looks like a leader who decides on their own read of the landscape, a new strategy developed in a silo, a new team brought in without context. The vision may be genuinely held. It is not the same as a recognized signal, and a change built on conviction instead of listening rarely survives contact with the structural, organic support it never had.
The alternative is not always cleaner in the moment, but it tends to hold. In one post-crisis planning process, leadership expected a fairly contained conversation about program strategy and instead ran into a team who expected a genuine organic process to consider a wider world of possibility. It was not efficient. It did not need to be. What made it feel inefficient was leadership's own expectation of an efficient, affirming process; a mismatch between what they had planned for and what deep listening actually required. Staying with the wider conversation is what allowed it to resolve into a strategy neither side had walked in with.
The prioritization problem
Recognizing a real signal does not mean the organization can act on it immediately. Most organizations are not tracking one change signal at a time. They are holding several at once, at different origins, at different points on the board/leader/team/constituent map, each competing for the same finite leadership attention and organizational capacity.
This is where recognition has to hand off to two further questions, each substantial enough to require its own treatment: how deep does this particular change need to go, and how much change can this organization actually carry right now without breaking something else in the process. Getting the origin right is necessary. It is not sufficient. An organization that correctly identifies five legitimate signals and tries to act on all five at once will fail differently, but just as completely, as one that never recognized any of them.