Case 01
I endorsed anonymity before testing what the report could reveal
In 2021, while director of people operations, I supported an anonymity promise for an employee survey. The proposed manager report omitted names. I accepted that feature too readily as evidence that the promise was sound, without examining how the available filters would work together in a small shop or a distinctive role. The assurance was part of a people process for which I held responsibility.
The pre-release review combined store, role and tenure. Fourteen resulting cells contained one person. A recipient who knew the team could potentially infer who a response described even without a name field. We held the report before manager release. This fictional account does not claim that a respondent identity was published, that a particular inference occurred or that a legal breach was established. The finding was sufficient to challenge the promise before we relied on it.
I took the issue back through the CHRO and supported ₹24 lakh for report redesign, permissions and explanation. Qualified privacy review was necessary alongside the people-function work. The correction concerned the report's context and use, not merely the removal of another column. Managers also needed to understand why some apparently useful breakdowns could not be offered on the original terms.
The outcome was a held release and a funded correction. I do not claim universal anonymity from a revised design or a measurable increase in trust. My error remains the early endorsement of an assurance without adequate examination of the recipient's perspective. The case changed the question I ask before signing off a people promise: what can someone infer from the whole view, including what they already know about the people behind it?