THE FIELD GUIDE · SITUATION
You Found a Problem. Now What?
You are doing the final content check on a customer case study scheduled to publish tomorrow.
You go back to the source notes.
The headline says
“Customer cuts processing time by 40%.”
The source notes say
The customer said the improvement was “around 40%, based on an internal estimate.”
The customer-approved version says
It does not use the number at all. It says the new process “significantly reduced processing time.”
You did not write the case study.
The page is not live yet.
You could change the headline to remove the number in about thirty seconds.
Your call
What would you do?
Commit before you keep reading.
Finding a problem does not automatically tell you how loud to make it
A typo in an internal draft and an unsupported number in a customer-facing headline are both “problems.” They are not the same problem.
Start with:
What changes because this problem exists?
If you leave it alone, who might rely on the bad information and what happens next? Can it still be corrected easily, or is it already working its way into somebody else’s decision? And are you looking at a confirmed problem, or at something suspicious that still needs checking?
Then there is the authority question. Some things really are yours to fix. Others change a claim, a commitment, an approval, or somebody else’s work enough that the owner needs to know.
In this case
I would surface it.
Not because every imperfect sentence requires a tiny emergency siren.
Because removing the number changes the headline, the evidence behind the claim, and potentially what the customer approved.
It is still easily correctable. Excellent. Fixing it before publication is precisely the goal.
But the material issue should not disappear silently with the edit.
Model language
“I found a support issue in the case study. The 40% figure appears in the interview notes as an internal estimate, but it isn’t in the customer-approved version. Because the number is also in the headline, I’d remove or qualify it before publication unless we have a source confirming the precise claim. I can update the page and social copy once we confirm which version we want to use.”
It gives the owner what they need without turning the situation into an accusation or a small theatrical emergency. Most importantly, it does not let a material problem vanish just because you happened to be able to fix the sentence.
A useful threshold
If the problem is small, reversible, clearly within your responsibility, and does not change what anyone else is relying on, fix it.
If it changes a claim, commitment, decision, approval, dependency, or meaningful consequence, make it visible to the people who need to know.
And if you are not yet sure it is actually wrong, verify before you turn suspicion into fact.
The goal is not to make every problem loud. It’s to avoid quietly making it somebody else’s surprise.
A small but important boundary
Even though I am your venerable Office Auntie, I do not outrank your incident-response policy. A pity, really.
If your workplace has a required process for security, safety, legal, compliance, financial-control, mandatory-reporting, or other reportable issues, use it.
A NOTE ON THE EVIDENCE
This scenario and decision aid are practical teaching translations, not a validated escalation protocol.
WHERE TO GO NEXT
Same hidden problem: The AI Answer Sounds Plausible. What Do You Verify?
Complication / boundary case: You Discover a Material Ambiguity Halfway Through the Work
Same judgment move: Should I Ask, or Can I Just Decide?