How I Document Impact Without Exposing Sensitive Internals

I use five rules:

1. State scope with concrete units

Use numbers that define scale, such as data volume, traffic envelope, or timeline.

2. Explain the mechanism

A credible claim should include the design or operational mechanism that caused the result.

3. Report before/after outcomes

Percentages are stronger when anchored to real baseline and final values.

4. Add proof links whenever possible

For closed-source work, proof can include public launch links, OSS contributions in the same domain, talks, and recommendations.

5. Mark what is intentionally sanitized

A short note that details are abstracted for confidentiality improves trust and sets expectations.