Deciding Whether to Speak Up
Mia reviews pilot data suggesting that David’s new client rollout is creating avoidable compliance risks. She weighs the consequences of staying silent against the need to raise the issue with evidence rather than speculation.
Dialogue11

Jack, could I get your read on the pilot data? I’m seeing a pattern that concerns me, but I want to separate what we can substantiate from what I’m inferring.
Sure. What are you seeing? If there’s a real issue, better to catch it before the rollout gets any bigger.
In the first two cohorts, several client files moved to activation without a complete record of who approved the exceptions. That’s confirmed; whether the approvals happened elsewhere is still unclear.
How many files are we talking about? And do we know whether those exceptions actually breached policy, or just weren’t documented in the system?
Seven out of forty-two. I haven’t found evidence that anyone bypassed a required review, so I wouldn’t call them violations. The gap is that we can’t reliably verify the review occurred.
That distinction matters. Still, raising it with David could be read as questioning a rollout he personally backed. What makes you think it’s worth that risk?
Because the next phase triples the volume, and the same approval path is planned. If the records stay incomplete, we’ll have a much larger exposure before we know whether the control is working.
What if you’re overreading a temporary handoff problem? The team may have the approvals in email, and a formal escalation could create noise without changing anything.
That’s possible, which is why I’d frame it as a verification gap, not misconduct or a definite compliance breach. But silence would leave a material uncertainty unexamined as we expand.
Then take the figures, the precise limitation, and a practical next step. You’re not asking David to reverse his decision; you’re asking him to make sure the control holds at scale.
That feels fair. I’ll document what we know, flag what still needs checking, and ask for a targeted review before the next phase. I’d rather raise a measured concern now than explain later why I didn’t.
Vocabulary8
- get your read on
To ask someone for their assessment or opinion. Here, Mia wants Jack’s perspective on the pilot data.
- substantiate
To support a claim with evidence. Mia uses it to distinguish confirmed facts from her own interpretation.
- verification gap
A lack of reliable evidence that something was checked or completed. It describes the recordkeeping problem without claiming that anyone broke a rule.
- read as
To be understood or interpreted in a particular way. Raising the issue might be read as questioning a decision David supported.
- overreading
Interpreting something as more significant than the evidence justifies. Jack raises the possibility that Mia may be drawing too strong a conclusion.
- material uncertainty
An unresolved question important enough to affect a decision. Mia says the uncertainty should be examined before the rollout expands.
- targeted review
A focused examination of a specific issue or process. Mia proposes one before the next phase rather than asking to reverse the rollout.
- holds at scale
Continues to work reliably as the volume or size of an operation grows. Jack frames the review as checking whether the control will remain effective.
Key Sentences8
- 1
I’m seeing a pattern that concerns me, but I want to separate what we can substantiate from what I’m inferring.
This is a careful way to raise a concern while showing respect for the limits of the evidence. Reuse it when you want to distinguish verified facts from your interpretation.
- 2
That’s confirmed; whether the approvals happened elsewhere is still unclear.
This sentence clearly separates what is known from what remains uncertain. Use the contrast to report evidence without overstating your conclusion.
- 3
I haven’t found evidence that anyone bypassed a required review, so I wouldn’t call them violations.
This phrasing avoids making an accusation when the evidence does not support one. You can adapt it to clarify what you have—and have not—established.
- 4
If the records stay incomplete, we’ll have a much larger exposure before we know whether the control is working.
This explains why an unresolved issue matters by connecting it to a future risk. Use a similar structure to show how growth or delay could increase exposure.
- 5
That’s possible, which is why I’d frame it as a verification gap, not misconduct or a definite compliance breach.
This acknowledges an alternative explanation while keeping the concern on the table. It is useful when you need to choose accurate, non-accusatory language.
- 6
But silence would leave a material uncertainty unexamined as we expand.
This makes a persuasive case for speaking up without claiming certainty about the cause. Reuse it to explain the risk of inaction.
- 7
You’re not asking David to reverse his decision; you’re asking him to make sure the control holds at scale.
This reframes feedback as a practical safeguard rather than a personal challenge. Use the contrast to make a request feel constructive and proportionate.
- 8
I’ll document what we know, flag what still needs checking, and ask for a targeted review before the next phase.
This gives a clear, measured plan that separates established facts from open questions. Adapt the three-part structure to outline responsible next steps.