You've had the assessment, but nothing changed.

Most advancement teams have been through at least one strategic plan or consulting engagement that promised lasting change. The work was thorough and the recommendations were sound, but within six months, the team was operating more or less the way it did before.

"I've done three assessments. This is the final one I'm going to do. This has to stick."

— A foundation CEO at a major university

Most assessments do their job. They identify the real issues: staffing gaps, unclear priorities, misaligned processes, donor pipeline risk. The strategic plans that follow are usually thoughtful. The consultants who deliver them are usually experienced. The problem is not the quality of the thinking.

The problem is what happens after the thinking gets handed over. The team receives a set of recommendations, and the consultant moves on. Meanwhile, the Vice President is left to implement the changes with the same team, the same bandwidth, and the same operating patterns that created the problem in the first place.

Change does not fail because the strategy is wrong. It fails because no one stays to help the team work differently.

Most consulting in this sector follows the same model: diagnose, recommend, deliver, depart. The deliverable is a document. The expectation is that the team will take the recommendations and translate them into new ways of working. But that translation is the hardest part. It requires changing how the team sets priorities, how work gets assigned and tracked, how decisions get made in a busy week, and how leadership reinforces new patterns over time. A document cannot do that. The recommendations sit in a binder or a shared drive. The team absorbs what it can. The rest quietly fades. Six months later, the VP is left wondering whether to try again or accept that this is just how it works.

Teams do not operate on strategy. They operate on habits.

How a team runs its week. The meetings it holds. The way priorities get set on Monday morning. The way trade-offs get made under pressure. These are habits, built over months and years. They do not change because someone presents a slide deck that says they should. A quarterly recommendation is working against daily gravity. Unless something changes about the team's actual operating rhythm, the old patterns will reassert themselves.

If the change did not stick, it was probably not a leadership failure.

Leaders in this position often take it personally. They wonder whether they did not push hard enough, communicate clearly enough, or follow through consistently enough. But the pattern is too widespread to be explained by individual effort. It happens at large research universities and small private institutions. It happens with experienced VPs and first-year Chief Development Officers (CDOs). It happens after expensive engagements and after lightweight reviews.

The common thread is not the leader. It is the model. Diagnosis without sustained support through implementation does not produce lasting change. It produces a moment of clarity followed by a slow return to the previous rhythm. This is not a firm's failure. It is what happens when the engagement model ends before the work of changing does.

If you find yourself explaining to a board chair or president why the last engagement did not hold, the honest answer is usually not about the team. It is about what the engagement was built to deliver, and what it was not.

The question is not whether outside help works. It is whether the help stays long enough to change how the team actually operates.

That is the only thing that determines whether the changes hold.