When the Advice Works, Can You Explain Why?

Suppose a company raises prices and profit increases by $80,000.

Six months later, the only record anyone can find says:

Raised prices. Profit increased by $80,000.

The result looks good. The lesson is almost gone.

No one can see why prices changed, which products or customers were affected, what increase was approved, when it took effect, what the advisor expected, what the company actually implemented, or what else changed during the same period.

The company may have improved because of pricing. It may also have sold a different mix, reduced overtime, lost a low-margin customer, negotiated a supplier discount, or benefited from unusual demand. The number alone cannot settle that question.

This is the problem Milan’s Fourth Law of Financial Improvement addresses:

Connect the decision to the result, or lose the lesson.

A completed task is not a completed advisory episode

Many advisory systems are built to mark work complete.

The analysis is delivered, the recommendation is accepted, the task is assigned, and eventually someone checks it off.

That may close the workflow, but it does not finish the advisory work. The advisor still needs to know what the client actually did and how the result compared with the expectation stated before implementation.

For the price-change example, a usable record would preserve:

• the margin pressure that started the conversation;
• the evidence available when the decision was made;
• the customers, products, or services included in the change;
• the approved price adjustment;
• the expected effect on volume, margin, and cash;
• the implementation date;
• customer exceptions or discounts granted after approval;
• the actual operating and financial result;
• outside factors that may have influenced the outcome;
• the next decision.

That record does not prove causation. It gives the advisor enough context to interpret the episode honestly.

Traceability protects against hindsight

Once the result is known, almost every decision starts to look more obvious than it felt at the time.

If the result is good, people may remember the explanation as more certain than it was. If the result is poor, they may remember the warning as clearer than it was. In both cases, hindsight rewrites the meeting.

A traceable record keeps the uncertainty that existed at the time from disappearing later.

The advisor might have believed that poor margin was partly caused by pricing but also noted uncertainty about sales mix and labor efficiency. The agreed intervention may have been a five-percent increase for one service category, not a company-wide change. The client may have delayed implementation by three weeks or approved exceptions that weakened the expected effect.

Those details separate a weak recommendation from weak execution. They also separate a good decision from a lucky outcome.

A good decision can produce a poor result because conditions changed. A poor decision can produce a good result because something else went right. Advisors need to be able to discuss both without turning every review meeting into a defense of the original recommendation.

A practical review conversation

At the review date, return to the record before looking for a new recommendation.

Ask:

1. What did we recommend?
2. What did the client agree to do?
3. What was actually implemented?
4. What did we expect to change first?
5. What financial response did we expect?
6. What happened?
7. What outside conditions changed?
8. Is the original explanation supported, partially supported, not supported, or still inconclusive?
9. What should change about the next decision?

The purpose is not to prove the advisor right. The purpose is to make the next decision better informed.

Where the advisory trail usually breaks

The trail can fail in several places.

The recommendation may live in a presentation while the assigned work lives in an email. The expected result may exist only in the advisor’s notes. The client may implement a modified version without recording the change. The review meeting may focus on the newest problem instead of returning to the original decision.

Over time, the firm may accumulate reports and completed tasks without preserving much evidence that can guide the next similar decision.

This is expensive. The advisor has to reconstruct the client history before each meeting. New team members cannot see why earlier decisions were made. Similar situations are treated as if the firm has never seen them before.

How Clear Path To Cash supports traceability

Clear Path To Cash can preserve the question, observation, candidate explanation, intervention, expectation, owner, due date, actual execution, result, and next decision in one connected record.

The app does not turn stored information into truth. It does not prove that one action caused the outcome. It keeps the evidence recoverable so the advisor can compare what was expected with what actually happened.

That is the operating purpose behind the Advisory Evidence Record. Reports show the result. The record keeps the decision and its assumptions attached to it.

Practice the review, not only the recommendation

The November Advisor App Bootcamp includes the part most training skips: returning to the decision after the action has been chosen.

Participants will work through a company case, rotate through advisor, client, and observer roles, and practice narrowing a complicated situation to a useful next move. They will also connect the recommendation to an owner, expectation, guardrail, and review plan inside the Advisor App.

The core program runs November 20-21, 2026, in San Antonio with live virtual attendance available.

See what advisors will practice at the November Bootcamp

Good advice remains useful after the meeting only if the decision, assumptions, execution, and result stay connected.