The 90-day test measures consulting project value by checking, three months after the consultants leave, whether recommendations are adopted, business results are moving, and your team can run the new way of working without outside help. It gives you a practical checkpoint before a consulting engagement becomes another polished report with no lasting change.
Three months is long enough for the launch energy to fade and daily habits to show the truth. This article explains what to measure, what warning signs to watch, and how to build the test into the project before the first workshop begins. Use it to judge value with evidence instead of goodwill, memory, or the quality of the final presentation.
What Is The 90-Day Test, And Why 90 Days?
The 90-day test is a post-engagement review that asks one direct question: did the consulting work create value that your organization can sustain without the consultant? It looks at adoption, measurable outcomes, and internal capability after the project has had time to meet real operating pressure.
The timing matters. During the project, people behave differently because the consultant is still present, leadership attention is high, and status meetings keep everyone alert. Right after the final presentation, the project can still look successful because the slides are clean, the steering committee is satisfied, and the team is relieved to have an answer. At 90 days, the protective bubble is gone.
That’s when you see whether the recommendations moved into the operating rhythm. Are managers using the new process in weekly reviews? Are teams making decisions with the new data? Are the promised Key Performance Indicators(KPIs) improving, flat, or quietly ignored? A useful consulting review starts there, not with how professional the engagement felt.
This timing also protects you from waiting too long. Bain & Company has reported that only a small share of companies fully sustain major change program results beyond 12 months, so a 90-day check gives you a chance to correct course before drift becomes normal. It’s early enough to fix adoption gaps, clarify ownership, and tighten measurement.
How Does The 90-Day Test Prove Consulting Project Value?
The test proves consulting project value by comparing what was promised with what your business is actually doing and achieving. A project passes when the recommendations are in use, the KPIs are moving in the intended direction, and your people can maintain the new practices without outside support.
Start with the original business case. If the project promised cost reduction, revenue lift, faster cycle times, better customer retention, fewer errors, or improved management reporting, those outcomes need named measures. Vague benefit statements don’t help at day 90. You need a baseline, a target, an owner, and a reporting cadence.
Then separate activity from impact. A team can complete training, attend workshops, and publish new process documents without changing behavior. The 90-day review should ask whether the new way of working appears in actual decisions. If the sales team still forecasts the old way, the finance team still reconciles manually, or operations still bypasses the new approval process, the project hasn’t landed.
Return on Investment(ROI) should be judged with care. Some consulting benefits take longer than three months to show up in financial statements, especially when they involve pricing discipline, operating model changes, or management capability. Still, by day 90 you should see leading indicators. If there are no early signals, no ownership, and no adoption, the value claim is weak.
Why Do Consulting Projects Often Look Successful At First?
Consulting projects often look successful early because energy, attention, and presentation quality can mask weak adoption. The project may feel productive long before it changes how work gets done.
The first reason is visibility. Senior leaders attend kickoff meetings, teams respond quickly to consultant requests, and project updates create a sense of motion. That motion can be useful, but it can also create false comfort. A full calendar is not the same as a changed operating model.
The second reason is the final deliverable. A good consulting deck can clarify decisions and make complex problems easier to discuss. The danger comes when leaders treat the deliverable as the outcome. A strategy document, operating model design, savings roadmap, or technology recommendation has value only when it changes priorities, behaviors, and measurable results.
McKinsey & Company has reported that many large-scale transformation efforts fail to achieve their objectives. That pattern shows why early satisfaction is not enough. A project can be well-run and still fail to stick if accountability, implementation discipline, and knowledge transfer are weak.
What Should You Measure At Day 90?
At day 90, measure three things: recommendation adoption, KPI movement, and internal capability. Those three measures tell you whether the consulting project created working value or only planning value.
Recommendation adoption is the first test. Don’t ask whether the recommendations were “accepted.” Ask whether they were implemented in the form agreed during the project. A recommendation is adopted when the relevant team uses it in normal work, leaders review it in business routines, and exceptions are visible rather than hidden.
KPI movement is the second test. A cost program may track savings captured, run-rate savings, invoice accuracy, purchasing compliance, or cycle time. A revenue program may track conversion rate, average deal size, sales velocity, retention, or margin quality. Choose measures tied to the original business case so the review doesn’t become a debate about new definitions.
Internal capability is the third test, and it’s the one many teams underrate. Deloitte Consulting has identified insufficient knowledge transfer from consultants to internal teams as a common reason projects underperform after consultants leave. Your review should test whether the team can explain the new process, train new users, troubleshoot issues, and improve the work without calling the consultant back for basic guidance.
What Are The Warning Signs A Consulting Project Failed The Test?
A consulting project fails the 90-day test when the organization reverts to old habits, KPIs don’t move, ownership is unclear, or the team still depends on the consultant. These warning signs usually appear before leaders admit the project is in trouble.
The first warning sign is shelfware. The recommendations exist, the documents are stored, and the project is considered closed, but day-to-day work looks the same. People may refer to the report during planning sessions, yet they don’t use it to make trade-offs. That gap tells you the project produced content, not operating change.
The second warning sign is unclear ownership. If every missed action has three partial owners and no decision rights, momentum will fade. A passing 90-day review should show named owners for each major change, clear deadlines, and routine review points. Without that structure, even good recommendations drift.
The third warning sign is KPI ambiguity. If the team can’t agree which numbers prove success, the original business case was likely too loose. The fourth warning sign is consultant dependency. If your managers still need outside help to run the process, interpret the dashboard, or make routine decisions, the project did not transfer enough capability.
How Should You Build The 90-Day Test Into The Contract?
Build the 90-day test into the contract by defining success measures, ownership, knowledge transfer, and a post-engagement review before the project starts. Don’t wait until the end to decide what value means.
The statement of work should name the business outcomes the project is expected to influence. That does not mean every benefit must be guaranteed, since market conditions, leadership decisions, and internal execution matter. It does mean the consultant and client should agree on the measurable indicators that will be reviewed. If no one can define value at the start, they won’t measure it cleanly later.
The contract should also specify adoption requirements. That can include process rollout, stakeholder training, governance routines, dashboard use, decision rights, and handover materials. Documentation alone is not enough. You need working sessions where internal owners practice the new process and receive feedback before the consultant exits.
Add a 90-day review meeting to the project plan. It should include the sponsor, operating owners, finance or performance management support, and the consultant if that was agreed upfront. The agenda should compare planned benefits with actual signals, identify adoption gaps, and assign corrective actions. This keeps the review factual instead of political.
How Can You Tell If Your Team Can Sustain The Change?
Your team can sustain the change when it can run, measure, and improve the new way of working without the consultant. The strongest signal is not confidence; it’s repeated execution under normal business pressure.
Look for ownership in meetings. If managers bring the new KPIs to their regular reviews, ask better questions, and make decisions using the new process, the change is becoming part of the business. If the new tools appear only during special project updates, adoption is still fragile. The 90-day test should examine normal meetings, not staged demonstrations.
Check whether knowledge has moved from the consultant to internal people. A trained team should be able to explain why the change was made, how the process works, what data is required, and what to do when exceptions appear. If only one project manager understands the method, the organization has a single point of failure. That’s not sustainable.
Resistance also needs direct review. Some pushback is practical: the tool is slow, the process has too many approvals, or the KPI creates the wrong behavior. Other pushback comes from habit or loss of control. A good 90-day review separates those causes so you can fix design flaws and address behavior gaps without treating every objection the same way.
What Should A Practical Post-Implementation Review Include?
A practical post-implementation review should include the business case, adoption evidence, KPI results, capability checks, and a decision on corrective action. It should be short enough to run, but disciplined enough to expose weak value claims.
Start with the original objectives. Compare planned deliverables with the actual operating changes made by day 90. Then review KPIs against the baseline and target ranges. If the numbers are early indicators rather than final financial outcomes, label them that way so expectations stay realistic.
Then examine adoption evidence. Use system data, process compliance, meeting routines, decision logs, training completion, manager feedback, and customer or employee signals where relevant. Don’t rely only on self-reported status. Teams under pressure often say a change is live when it is only partially used.
End with a decision. A project can pass, pass with fixes, or fail the test. Passing with fixes is common and useful when the gaps are specific. Failing is harder to accept, but it saves money if it prevents further spending on work that the business can’t or won’t use.
How Do You Keep Measuring Value After The 90-Day Test?
Keep measuring value by turning the 90-day review into a recurring value audit tied to operating reviews. The goal is to make consulting project value part of management discipline, not a one-time scorecard.
After the first review, set a smaller set of ongoing measures. You don’t need to keep every project metric alive forever. Choose the few that show whether the change is still working: cost captured, cycle time, compliance, revenue quality, customer retention, error reduction, adoption rate, or capability depth. The right measures depend on the project’s original purpose.
Assign ownership to the business, not the former project team. Value lives in operations, sales, finance, customer service, technology, or human resources after the engagement ends. If measurement stays with a temporary project office, it may disappear when the team disbands. Put the measures where decisions are made.
Use the audit to improve future consulting decisions. Track which types of projects created durable value, which firms transferred knowledge well, and which internal conditions helped or hurt adoption. Over time, you’ll get better at buying consulting support, scoping projects, and rejecting proposals that sound attractive but lack measurable follow-through.
How Does A 90-Day Test Work?
- Track adoption of agreed recommendations.
- Compare real KPIs with the business case.
- Check if the team runs the process alone.
- Confirm knowledge moved into daily work.
Make The Project Prove Its Value After The Slides Are Gone
A consulting engagement earns its place when the work survives normal business pressure. The 90-day test gives you a clean way to judge adoption, performance movement, and internal capability without relying on enthusiasm or presentation quality. It also improves how you buy consulting services because value is defined before the work begins. If you want stronger consulting project value, start the test on day one, not three months after the final meeting. The best projects don’t just end well; they keep working when the room is quieter and the consultant is gone.
Brian C Jensen is the CEO of Legacy Global Consulting, Inc., a management consulting firm. With 10+ years of experience, he advises organizations on digital transformation, risk management, and growth strategy—helping clients anticipate market shifts and scale sustainably.