How to Work With a Consultant—and Get Lasting Value

I am going to make an argument against my own interests here: a consultant cannot make an engagement successful on their own. The variables that most determine whether the work produces lasting change sit on the client side, and most of them are set before the contract is signed.

Organizations that get real value from consulting tend to do the same handful of things. Organizations that end up with an expensive document usually skipped them.

Define the problem, not the deliverable

The most common way an engagement goes wrong is starting from an output. "We need a strategic plan." "We need a dashboard." Sometimes that is exactly right. Often the stated deliverable is a proxy for something else, and building it will not address the underlying issue.

Before you scope anything, write down what is actually happening. What decision cannot be made? What keeps recurring? What does failure look like if nothing changes in eighteen months? A good consultant will push on this in the first conversation, and you should be wary of one who does not.

Write the scope down, including what is excluded

A scope should name the specific deliverables, the phases, who is involved in each, what you are responsible for providing, the timeline, and how changes to scope get handled.

The exclusions matter as much as the inclusions. Most scope disputes are not disagreements about what was promised. They are two parties who each assumed something that was never discussed. Writing down what is not included feels pedantic and saves real friction later.

Agree how change control works before you need it. Scope will shift, because discovery reveals things nobody knew. That is normal. What should not be normal is shifting scope without a corresponding conversation about timeline and cost.

Name an internal owner with actual authority

Every engagement needs one person inside the organization who owns it. Not a committee. That person coordinates access, chases documents, convenes the right people, and can escalate when something stalls.

They also need enough authority to make day-to-day calls, or the engagement waits on them waiting on someone else. And their time needs to be genuinely protected. Adding an engagement to an already full plate is the most common cause of a project that slips a month at a time.

Prepare your information before kickoff

Engagements stall on document access more than on anything else. You can eliminate weeks of delay by assembling the standard materials before day one.

• Governing documents, current bylaws, and the board roster
• The last two or three years of financial statements, audits, and the current budget
• Any prior strategic plan, assessment, or consultant report, including the ones you did not act on
• Program descriptions, logic models, and whatever outcome data exists
• Organizational chart and current job descriptions
• Grant agreements and reporting requirements
• A list of stakeholders you want consulted, with contact information and any sensitivities

Include the unflattering material. Consultants are not shocked by weak documentation or a failed initiative, and withholding it only means the recommendations get built on an incomplete picture. The prior report you did not implement is often the most informative document in the set.

Be available, and be candid

The most valuable thing a client provides is timely access to decision-makers. When leadership availability is the constraint, the engagement extends and quality suffers, because the consultant ends up inferring what they should have been told.

Candor matters as much as availability. If there is a board member who will block a recommendation, a program that leadership has privately decided to end, or a funding relationship that is less secure than it appears, say so early. A consultant who does not know the real constraints will produce recommendations that cannot survive contact with them.

Make decisions when they are put in front of you

A consultant can analyze options, surface tradeoffs, and recommend. They cannot decide. Every engagement reaches points where leadership has to choose, and deferred decisions compound: each one delays everything downstream.

Agree in advance who makes which decisions and how quickly, and whether any require board approval. If a decision needs a board vote and the board meets quarterly, that has to be in the schedule from the beginning.

Build implementation into the engagement

This is the single biggest determinant of lasting value, and it is usually decided at the wrong time: at the end, when the budget is spent.

Ask at the outset what happens after the final deliverable. Who owns each recommendation? What is in the budget to execute them? What capability needs to be built internally so that the organization can sustain the work and, ideally, repeat it without external help next time?

A consultant should be actively transferring capability throughout: explaining the reasoning rather than only presenting conclusions, leaving behind usable tools and templates, and training the people who will maintain the work. If nobody internal can run what was built, you have bought a dependency.

Define what success looks like, in advance

Write down, before the work starts, what would make this engagement worth the investment. Not deliverables received. Changes achieved: a decision made, a capability established, a measure moved, a problem no longer recurring.

Then schedule a review three to six months after closeout to check against it. That review is uncomfortable and it is the most useful hour in the entire engagement, because it is the only point where anyone finds out whether the work actually changed anything.