Is your forecast counting on an unfinished decision?

Two professionals examine a continuous plan above disconnected operating paths, with a crimson junction marking the unresolved handoff.

Today's Executive Briefing

The decision your forecast is counting on

A decision can be in the forecast and still not be made.

When a firm's leadership group agrees that renewals will move to the new rate card, finance does what finance does. The margin goes into the plan, the plan goes to the investors, and the meeting goes into the record as the day the firm raised its rates. Two weeks later, the first renewals go out at the old rates, and every practice lead has a reason.

Your first instinct is enforcement, and it may be correct. If the new rates were properly authorized, everyone left with the same understanding, and a practice lead has simply decided otherwise, that is a performance conversation, and you should have it.

That conversation assumes the meeting produced one decision. It may have produced several, because a yes in a leadership meeting can mean different things. It can mean this is right. It can mean I'll do it whether it's right or not. It can mean this is yours to decide and I won't fight you. It can mean we are forty minutes over and I have a client at two. All four sound identical, and the minutes record one word.

If one practice lead heard "new engagements" and you heard "every renewal by year-end," you gave the same answer at the same table, and neither of you lied. Then a renewal letter needs a number, and each of you fills in what the meeting left blank, you in the forecast and the practice lead in the letter. Each of you now believes the other has drifted from the decision.

You know this distinction from every audit you've sat through. In June, NASA's inspector general issued six recommendations on the Commercial Crew Program, and management concurred with all six. The report marks them resolved, and they close only on completion and verification of the corrective actions (NASA Office of Inspector General, 2026). That is one federal audit, and it still keeps apart two words a leadership meeting tends to merge. Agreement gets a decision to resolved. A forecast built on that agreement is treating it as closed.

Enforcement is aimed at one version of the decision, so it can improve the report before it improves the money. Tell the practice leads the rate card is mandatory, and the one who believes existing clients were carved out can bill the new rate and give the difference back as a write-off at invoice. The rate report looks right, realization stays where it was, and the variance reaches the investors attached to a decision no one finished.

For decisions made in pieces by different groups, as pricing is, clearly defined roles, accountability, or decision rights alone were not enough to reach the top group in a self-reported McKinsey executive survey (Aminov et al., 2019). Accountability also needs one decision, in one form, that both parties can point to.

The gap may sit somewhere else. The group may have wanted higher rates without deciding which clients it would accept losing, which is unfinished strategy. The practice leads may agree completely and lack the hours to reopen those contracts. A slow renewal won't tell you which.

What you can find out this week, before anyone is told to try harder, is whether the decision your forecast depends on exists in a form another person could act on.

Decision Path Check

Time: 10–15 minutes

Choose one consequential cross-functional decision from the past fourteen days that appeared settled and is now delayed, disputed, or being interpreted differently. Complete one record from the available decision documents and the people responsible.

  1. Authorization. Who could authorize this decision, and what evidence shows that authorization occurred?
  2. Verdict. What exactly was decided? Record any condition that made the decision provisional.
  3. Rationale. Which reasons, assumptions, and tradeoffs may another function use when applying the verdict?
  4. Implementation. Who must act, and what authority, information, and resources does that person have?
  5. Dissent. Which objection or tradeoff remains unresolved, and who can settle it?
  6. Reopening evidence. What new fact or threshold would justify reconsideration, and who decides whether it has been met?
  7. Exception route. Where does an exception go, and who can authorize the response?
  8. Next action. What happens next, by when, and what customer, financial, control, or operating consequence follows if it does not?

Finding

Record the state supported by the comparison:

  • No path discrepancy established. The required decision information is available, and the relevant people give compatible accounts.
  • Path discrepancy observed. A specific element is missing or disputed. Record the element, the evidenc,e and where action becomes uncertain.
  • Unresolved. The available records or accounts cannot establish what was authorized or what the receiving function can do.

Next investigation

Identify the first disputed or missing element. Ask its authorized owner for the evidence or clarification required to resolve it.

If no discrepancy is established, investigate capacity, communication, execution, resistance, or an unresolved strategic choice. Record any authorized adaptation separately from unauthorized departure from the verdict.

Scope limit: This check describes one decision under current conditions. A missing entry does not establish the cause of delay, and a complete record does not prove that implementation will succeed.

© 2026 Lauren Carter. This instrument is proprietary. For individual diagnostic use only. Reproduction, adaptation, or redistribution in any form requires prior written permission from Lauren Carter.

Lauren

If this is the conversation someone in your network has been needing, forward it. They'll know.

Lauren Carter

A twice-weekly diagnostic on the structural conditions underneath how organizations actually perform. Each issue names a mechanism most strategy conversations skip, then gives you a tool to test it in your own operation. Built for executives, founders, and operators who already suspect the problem is architectural.