Good Enough or Grand? Gauging the Depth of Change
Gauging the Right Depth of Change
Recognizing a signal tells you something needs to change. It does not tell you how far the change needs to go. That is a separate question, and getting it wrong in either direction costs something: too shallow, and the organization is back here within the year, having spent real capacity to change nothing that actually mattered; too deep, and the organization pays for a rebuild it never needed, exhausting people and goodwill on a problem that would have resolved with a lighter hand.
How origin shapes the pull toward shallow or deep
The five origins from recognizing the need for change do not just explain where a signal comes from. Each one carries a natural pull toward a certain depth, and knowing the origin tells you which pull you are navigating — recognizing the right depth is one thing, building the space and resources to actually see it through is another, separate question. These are generalities. Exceptions exist in every organization, and any of these origins can show up regardless of whether the deciding voice is a single leader, a leadership team, a working team, or a board.
Earned Change pulls shallow, but the risk is not a temptation to rebuild. It is neglect by omission: the problems that accumulate during growth rarely get addressed while they are not yet slowing the growth itself, so they wait. When they finally do get attention, the organization is usually deep into planning for what's next, and what gets fixed gets fixed in patchwork; whatever is prioritized in the moment, addressed in isolation from everything else quietly falling behind. The result, left unchecked, is a Frankenstein's monster of swift, disconnected fixes that were each individually reasonable and collectively incoherent. What Earned Change actually needs is not reinvention. It is someone stepping back far enough to see the whole patchwork at once.
Ambition Change does not so much pull deep as it pulls large; the scale of what's being asked for can feel overwhelming before anyone has actually assessed whether it requires real depth or just looks that way from the outset. The diagnostic question is not whether the ambition is legitimate. It is whether the organization has, or can build, the actual capacity the ambition needs, separate from how big the ask initially feels.
Reactive Change pulls toward whichever squeaky wheel is loudest in the moment — the board member, funder, or constituent voicing the sharpest urgency — rather than toward the actual source of the problem. That chase for the squeakiest wheel usually produces the shallowest response the organization can get away with, since getting the noise to stop is prioritized over real diagnosis, and it is not always clear at the outset whether the triggering issue is temporary or lasting. The risk with Reactive Change is rarely going too deep. It is defaulting to a quick, noise-driven patch and calling it resolved.
Good enough or grand, asked three times
Once the direction of the pull is named, the actual depth decision comes down to one question, asked more than once: is this a moment for good enough, or a moment for grand.
Good enough is not second best. The humanitarian sector has operated on a version of this distinction for two decades, through a Good Enough Guide developed by a coalition of aid agencies including CARE and the International Rescue Committee. Its core premise: adopting a quick, practical solution is not a failure of ambition, it is an honest acknowledgment of what a moment allows, revisited as the situation changes. Organizational change deserves the same honesty. Good enough is the right call when momentum matters more than perfection, when a partial solution enables the next real step. Grand is the right call when a partial solution will calcify, when good enough today becomes the barnacle someone else has to scrape off during the next transition.
This question is not asked once and settled. It gets asked three times, and the honest answer can change between askings.
The first time is before depth is set, in the earliest read of the situation; a gut check against the pull the origin type is already exerting.
The second time is once depth has actually been chosen, as a check against habit. It is easy to decide good enough is the right call and then build grand anyway, out of institutional muscle memory, or to decide grand is warranted and quietly under-deliver toward good enough because grand is harder to sustain than it looked at the outset.
The third time is mid-process, and this is the one most leaders skip, because revisiting a depth decision mid-flight can look like indecision. It is not, when the revision is earned. Changing your mind on depth partway through is legitimate when it is tied to something you actually learned in the doing and connected to the outcome you are working toward. It is not legitimate when it is tied to fatigue, to a personal shift in appetite for the effort, or to a desire to simply be done. The difference is not whether you changed your mind. It is what the change in your mind is actually anchored to.
Three is a deliberate number, not a minimum. Revisiting scope constantly, past these three points, is not rigor. It is analysis paralysis wearing the costume of diligence, and it carries its own cost; a team that watches depth get renegotiated every week stops trusting that any decision will hold long enough to act on. The three checkpoints exist precisely to contain the practice: enough discipline to catch real learning, not so much that the question itself becomes the work.
Depth answered correctly is still only two-thirds of the equation. An organization can name the right origin, choose the right depth, and still fail; not because the diagnosis was wrong, but because it never asked whether it actually had the capacity to carry what it had just decided to build. That is a different question entirely, and it deserves its own answer.