How to Challenge Assumptions Politely in Finance Meetings

Finance meetings often require disagreement. The professional skill is to challenge the assumption rather than attack the person. In English, this usually means asking focused questions and separating facts from interpretation.

Ask for the basis of an assumption

• “What is that assumption based on?”
• “Could you talk us through the evidence behind the growth forecast?”
• “What gives us confidence that margins will recover at that pace?”
• “How was the downside case calibrated?”

Signal concern without rejecting the whole analysis

• “I’m comfortable with the overall direction, but I have a question about the revenue assumption.”
• “I agree with the conclusion in principle, although I’m less comfortable with the pace of recovery.”
• “The base case looks reasonable, but the downside may be too mild.”

Test an alternative scenario

• “Could we test that against a more conservative scenario?”
• “What happens if revenue is 10% below plan?”
• “How sensitive is the result to a one-percentage-point margin decline?”
• “Would the recommendation change if the refinancing were delayed?”

Challenge causation carefully

• “Do we know that the improvement was driven by pricing, or could volume also be contributing?”
• “Is it possible that some of the cash improvement is timing-related?”
• “I’m not sure the data yet supports that conclusion.”

Correct a factual point

• “I may be reading the numbers differently, but I have net debt at $48 million rather than $42 million.”
• “Just to clarify, the covenant is tested quarterly rather than annually.”
• “I think we may be using two different definitions of EBITDA.”

Phrases such as I may be reading this differently help maintain a constructive tone while still correcting the record.

Disagree more directly when necessary

• “I don’t think the current forecast adequately reflects the downside risk.”
• “I would be cautious about relying on that assumption.”
• “I’m not convinced that the mitigant fully addresses the risk.”
• “I would prefer to see additional evidence before we support that conclusion.”

A useful challenge structure

• Acknowledge: “I understand the logic behind the base case.”
• Identify: “My concern is the assumption on customer retention.”
• Test: “What happens if retention falls by five percentage points?”
• Next step: “Could we run that sensitivity before final approval?”

Avoid weak or unnecessarily aggressive language

• Too weak: “Maybe this is perhaps a little optimistic?”
• Clearer: “I think the revenue assumption is optimistic relative to the historical trend.”
• Too aggressive: “This forecast makes no sense.”
• Professional: “I’m struggling to reconcile this forecast with the recent run rate.”

Good challenge language is specific. Identify the assumption, explain why it matters and ask for the evidence or sensitivity needed to test it.