Confidentiality Is a Workflow, Not a Promise

A confidential file is attached to a routine message. The sender selects a familiar address, presses send and discovers that people outside the authorised group can now see information they were never meant to receive. A recall is attempted. Recipients are asked to delete the file. Leaders restate the importance of confidentiality and the organisation returns to work.

The immediate response may be necessary, but the incident began before the final click. Someone decided which information belonged in one document. A system determined who could open it. A workflow allowed the same communication channel to carry both an ordinary update and a sensitive attachment. Time pressure, auto-complete, naming conventions, permissions and review practices shaped the act that is later described simply as human error.

Confidentiality is a workflow, not a promise. Values-based leadership does not remove personal responsibility, but neither does it place the whole burden on memory and caution. It designs the complete information journey so that purpose is clear, access is proportionate, unusual disclosure meets friction, mistakes can be reported without concealment, and every incident improves the system that made it possible.

Reuters reported at 13:40 UTC on 24 September 2026 that a senior Morgan Stanley banker covering financial sponsors in Asia mistakenly attached the group's deal pipeline to a weekly client email. According to six people familiar with the matter, the list…