Company: TechEdge Solutions (fictitious), a mid-sized software development firm with 1,200 employees specialising in enterprise SaaS products for banking and logistics clients.
Background
A Vice President – Engineering role has been open for three months. It is among the company’s most senior technical positions, overseeing four product teams, 180 employees, and a delivery roadmap worth Rs 120 crore.
Two internal candidates underwent a formal evaluation process involving structured interviews, leadership assessments, and a panel review by the CTO and business heads.
The decision was finalised on Friday.
The announcement was scheduled for Monday morning.
It did not make it to Monday.
The situation
By Saturday afternoon, the news had already started circulating internally.
By Sunday evening, Deepa Krishnamurthy, one of the two candidates, had received multiple messages congratulating her peer, Sanjay Mehta, on his promotion.
Deepa has spent seven years at TechEdge. She built the company’s core payments integration platform and believed she was ready for the role.
She discovered she had not been selected through a WhatsApp forward.
On Monday morning, before the official announcement, she walked into HR.
“I’m not questioning the decision,” she said. “I’m questioning how I found out. If the decision was already made, I deserved to hear it from you, not from a colleague’s message. This is humiliating.”
Leadership is divided.
The CHRO wants to investigate the leak before moving ahead. The CTO wants to proceed immediately, arguing that the announcement has already been delayed and Sanjay has been left in limbo through no fault of his own.
HR now faces a difficult choice.
The dilemma
Should HR pause the announcement, investigate the leak, and acknowledge that the process failed Deepa?
Or should it proceed immediately, accepting that the damage is already done and focusing instead on a direct, honest conversation with her?
What’s really at stake
This is not just about confidentiality. It is about trust in organisational process.
Deepa’s grievance is not about losing the role. It is about losing dignity in the way the decision was communicated.
Every employee watching this situation is asking the same question: if I go through a serious internal process and don’t get selected, will I at least be treated with respect?
If TechEdge pauses the announcement, it risks prolonging uncertainty for Sanjay and appearing indecisive. If it does not, it risks signalling that confidentiality and candidate care matter only until the decision is made.
The deeper question is difficult to ignore: when organisations fail to control sensitive decisions, who is actually accountable for the damage that follows?
We asked three HR leaders how they would approach this dilemma.
What HR leaders said
Viekas K Khokha, CHRO, Sharda Motor Industries
“I see this primarily as an integrity issue. If someone knowingly disclosed the information, that needs to be addressed. If the leak happened accidentally, then the process itself requires correction.”
However, I do not believe the promotion decision should be delayed because of the leak. The outcome was already finalised through an objective process.
The announcement should proceed immediately. At the same time, HR must have a direct and honest conversation with Deepa. Not a consoling discussion, but a meaningful one –explaining the decision clearly and the specific areas she needs to strengthen.
What should not happen is any confusion around the finality of the decision. Once organisations begin appearing inconsistent because someone is disappointed, confidence in the entire process weakens for everyone who comes after.
The leak must be investigated, but the promotion must move forward. Protecting process integrity and restoring Deepa’s dignity are not competing priorities – both must be addressed, and neither can be used as a reason to avoid the other.
Praveen Purohit, CHRO, Vedanta Aluminium, Power, Port & Mines
“Incidents like this usually indicate governance gaps rather than isolated mistakes.”
Whenever confidential information leaks in organisations, it points to weak systems, unclear ownership, or poor process discipline. And every time that happens, someone’s dignity is affected.
I always look at the basics first. Who had access to the information? Was communication sequencing clearly defined? Were there controls around sensitive discussions?
Confidentiality depends as much on systems as on individual ethics.
I would not delay the promotion announcement. But I would absolutely conduct a rigorous post-mortem to identify exactly where the breakdown occurred and close it permanently.
Deepa also deserves a serious conversation. She participated in a structured process and has every right to understand clearly why the decision went against her.
Promotion leaks are rarely one-off incidents – they are symptoms of governance that has not kept pace with the seriousness of the decisions being made. The announcement can proceed, but the organisation cannot treat the breach as a minor administrative lapse and move on.
Anil Mohanty, Group CHRO, Falcon Marine
“Leaks like this often happen unintentionally. Information travels informally through conversations, assumptions, and forwarded messages long before formal communication catches up.
But what matters here is the nature of the process itself.
In Deepa’s case, this was a formal internal competition. She applied, prepared, and went through assessment. In such situations, candidates absolutely deserve a direct conversation before the outcome becomes public knowledge.
The larger issue is that organisations often invest enormous rigour in selection processes but very little rigour in communicating outcomes. The evaluation receives structure. The aftermath becomes informal. That imbalance damages credibility far more than the leak itself.
If organisations expect employees to treat internal processes seriously, they must treat the communication of outcomes with equal seriousness. The process does not end when the decision is made — it ends when every candidate has been spoken to with honesty and respect.”
If you were the CHRO at TechEdge
You have been asked to recommend a course of action to the leadership team.
Do you:
- Proceed with the announcement and speak directly with Deepa, acknowledging the communication lapse and committing to a structured development conversation?
- Pause briefly to investigate the source of the leak before announcing the decision, accepting the short-term uncertainty that creates for Sanjay?
- Acknowledge the communication failure formally in writing to Deepa whilst moving ahead with the promotion, separating the two issues explicitly?
Or is the real issue this:
The moment employees learn outcomes through WhatsApp forwards instead of leadership conversations, has the process already failed – regardless of what happens next?
Share your perspective in the comments or on LinkedIn using #HRKathaCaseInPoint