Filter facts from stories in difficult emails before sending
Before sending difficult emails or presenting challenging conclusions, run your draft through fact-story filtering by asking which statements would survive if you had to prove them with timestamps, screenshots, or measurements, because this prevents narrative from masquerading as evidence.
When This Fires
- Drafting an email that delivers bad news, raises a concern, or makes a difficult request
- Preparing a presentation with conclusions that stakeholders may resist
- Writing a post-mortem, incident report, or performance review
- Any written communication where your credibility depends on the accuracy of your claims
Common Failure Mode
Leaving stories in because they feel true. "The process is broken" feels like an obvious fact when you're frustrated. But it's a conclusion — your interpretation of specific events that may support other interpretations. The recipient who disagrees can dismiss "the process is broken" in one sentence. They cannot dismiss "three of the last five deployments required hotfixes within 24 hours" — that's a fact that demands engagement regardless of interpretation.
The Protocol
Before sending a difficult email or presenting challenging conclusions: (1) Read each sentence and ask: "Could I prove this with a timestamp, screenshot, or measurement?" (2) Mark sentences as FACT (provable) or STORY (interpretation). (3) For each story, either replace it with the underlying facts or explicitly label it as your interpretation: "My reading of this is..." (4) Facts go first; interpretations go after, clearly framed as such. This structure is harder to dismiss and more likely to produce productive conversation.