We Don't Deliver a Report and Hand You the Keys

The report arrived on a Thursday. Four months of work distilled into thirty-two pages.

I had spent that time inside the institution, conducting interviews at every level of the organization, reviewing years of data, mapping the distance between what senior leadership believed was true about their culture and what the people closest to the work actually experienced. It was careful work. Evidence-based. Organized around the institution's own stated priorities.

The response was warm. The cabinet found it clarifying. The president thanked me in writing. The board chair called it exactly what they needed.

Six months later, I got a call. Nothing had changed.

The pattern is not unusual. I have watched it repeat across institutions, across sectors, across leadership structures that differ in almost every other way. A consultant is engaged to produce a diagnosis. The diagnosis is delivered and accepted. And then the organization, with its existing people, its existing culture, its existing pressures and competing priorities, is left to implement something it did not produce.

The implicit theory behind this model is that insight, delivered in sufficiently compelling form, translates naturally into action. It does not. The peer-reviewed literature on strategy implementation is consistent on this point: most strategic plans deliver a fraction of their intended results, and the gap compounds over time. This is not a failure of will or intelligence on the part of the institution. It is a misunderstanding of how organizational change actually works.

Institutions are not rational actors that update their behavior when they receive new information. They are social systems, organized around shared assumptions about what is real, what matters, and what is possible in this particular place. Those assumptions are not listed in any strategic plan. They are embedded in the language people use in meetings, in which questions get asked and which do not, in what happens to the person who names something that has not been named before.

A report can describe those assumptions accurately. The organization can read the report, agree with every word, and still not change. Because the assumptions are not changed by being named from the outside. They are changed by sustained engagement from inside the system, over time, with partners who have developed enough understanding of the organization to know where the real levers are.

This is the structural problem with the assess-report-depart model. It can describe the levers accurately and still leave no one in the room who knows how to pull them. The things a good report identifies often require the organization to do something it has never done, and there is rarely anyone present who has done it before, and there is no one still in the work helping them figure out how. The model is optimized for producing a diagnosis. It is not designed for what happens next.

I did not arrive at this view from the consultant's chair alone. In my own early leadership roles, I received the kind of plans I am now describing: careful, considered, and going little or nowhere, though no one had given up on them. In a later, more senior phase I tried the opposite move. I used the authority of my own role to animate consultant recommendations, to become myself the accountability mechanism the plan had assumed the institution would somehow become. That did not work either.

But it taught me something the first experience could not. It taught me that the engine of transformational change is not the plan, and it is not the final document, and it cannot be a transaction. It is the working partnership itself. And because the partnership is the engine, the measure of a consulting engagement is not whether the document was sound. It is whether, when the engagement ends, the institution can carry its own movement forward. That is the quiet test most fixed-scope engagements fail. A good report cannot make an organization self-sustaining. Only sustained partnership, over time, can do that.

When SPARC takes on a consulting engagement, we are not offering to produce a report. We are offering to work alongside an institution through the change process itself. The distinction has practical consequences.

It means we stay in the work long enough to see what the initial assessment could not predict. Every plan is brilliant until the end of the first week. That is when its blindspots, its load-bearing assumptions, its places of quiet weakness begin to surface, not because the plan was badly made, but because the organization is a living thing and the plan is a snapshot. A plan cannot adapt. A partnership can. The consulting engagement that ends with the final document is gone when those reveals arrive. The institution is left to navigate them alone.

It means we can keep asking why. "We tried that and it didn't work" is often the single most repeated sentence in a change process, and it is the sentence that forecloses most change before it begins. A long-term consulting partner can keep pressing on what lives underneath that sentence (why it didn't work, what was being protected, what the institution could not see about itself at the time) without exhausting the relationship. That sustained inquiry is what deepens an organization's awareness of itself. And that deepening awareness is where the real insight lives: insight into the particular conditions under which change, in this place, with these people, might actually take hold.

It means we can tell the truth over time. The hardest things to name in organizational life are not the things that show up in the data. They are the things the data cannot capture because no one felt safe putting them into a survey, or because the question that would have surfaced them was never asked. A trusted long-term partner, with enough relational history to have earned candor, can often surface what the initial assessment could not reach. In my experience, this is where the most consequential work happens.

And it means we have accountability to the work, not to the final document. The temptation in a fixed-scope engagement is to shape findings toward completion. The work is done when the report is written, so the pressure is on the report. In a long-term partnership, the work is done when the institution has actually changed, and that test is considerably harder to falsify.

I have sat in enough of those rooms to know the particular quality of frustration that lives in them. Not anger. Not blame, exactly. Something more like bewilderment. Or, after long enough, resignation. We had the right diagnosis. We agreed on the problem. We knew what needed to happen. And somehow, here we are.

What a partnership looks like in practice is different from what a plan looks like. In a plan, the consultant's job is to bound the work. Every discovery that does not fit the scope must be weeded out, defined away, or deferred, because the plan must arrive at a clear and compelling document and that document must be defended against anything that would pull it off course. In a relationship, the discoveries are the work. When something new surfaces (a capacity that wasn't visible before, a problem the assessment did not reach, a leader whose situation has changed) the partnership absorbs it rather than routing around it.

Absorbing discoveries is not the same as letting the engagement drift. A partnership still has goals that get set, reset, and retired as the institution earns the right to move on from them. There are clearly parsed periods of work together, with beginnings and ends. The difference is that the work is accountable to the institution's actual progress, not to the terminal date of the contract.

The fair concern to raise here is dependency. A long-term consulting relationship can, if the consultant is not disciplined about it, become a fixture in the institution's decision-making. The aim of our kind of partnership is the opposite: self-sustaining movement, with the partner's job defined precisely by the ability to step back. In my experience, stagnation is the far more common risk than dependency. The institutions that make durable change are almost never the ones who did it alone.

The institutions I have watched make genuine, durable change share a characteristic that does not show up in their strategic documents. They treated consulting not as the procurement of a document but as the beginning of a working relationship. They expected to be challenged over time. They expected that implementing what the assessment recommended would reveal things requiring further assessment. They expected the conversation to continue.

That expectation is not naive. It is a more accurate model of how change works.