Company: Vertex Technologies (fictitious), a mid-sized technology services firm with 1,800 employees, delivering software development, infrastructure management and digital transformation services to enterprise clients across banking, retail and manufacturing.
Background
For just over a year, the client delivery team at Vertex Technologies had made remote work function.
Deadlines were met. Client satisfaction scores held steady. The fourteen-member team had settled into a rhythm that worked, and leadership had largely left them to it.
Then came the quarterly business review with National Finance Bank, one of Vertex’s largest and most strategically important clients. Eight people from Vertex. Six from the client. The kind of meeting where how the team presents itself matters almost as much as what it presents.
One employee, Rohan Desai, joined the call from his car.
His camera switched on briefly, revealing a moving road in the background. Noise disrupted the audio at a critical point in the presentation. Then, while attempting to share the correct window,
Rohan accidentally shared a screen showing an online video game he had been playing before the meeting.
The client noticed.
So did the Vertex account manager.
The meeting recovered, but the embarrassment did not disappear with the call.
Two hours later, HR sent a message to the entire client delivery team. Effective the following Monday, all fourteen members would be required to return to the office five days a week. The stated reasons were professionalism, accountability and the need to protect client relationships.
No individual action against Rohan was announced. Nobody spoke to the team before the decision was communicated.
Within 48 hours, three employees had complained to HR. Two others had begun quietly exploring opportunities elsewhere.
The mandate has been announced. The client incident cannot be undone. HR now has to decide whether reversing the decision would demonstrate better judgement or simply make management look indecisive.
The dilemma
Should Vertex stand by the return-to-office mandate, arguing that a visible failure in front of a strategically important client justifies tighter controls over how client-facing work is conducted?
Or should HR reverse the blanket decision, hold Rohan individually accountable and preserve the flexibility the other thirteen employees have earned through a year of consistent delivery?
And if reversing course immediately risks undermining management credibility, is there a third path: retain the mandate temporarily, acknowledge that the response was made in haste, and create a clear route back to flexibility once proper client-facing standards are established?
What’s really at stake
This is a question about what accountability looks like when one person’s mistake creates a problem larger than the individual.
Rohan’s conduct was unacceptable. Joining a high-stakes client meeting from a moving vehicle, disrupting the presentation and exposing a gaming screen reflects poor judgement about what the moment required. National Finance Bank is one of Vertex’s largest clients. Leadership cannot simply dismiss the incident as an employee making an embarrassing mistake on a video call.
The question is whether bringing fourteen people back to the office actually addresses that risk.
For more than a year, the team had met deadlines and maintained client satisfaction while working remotely. Thirteen employees did not join the meeting from a car. They did not disrupt the presentation. They did not have a game open on their screens. Yet the immediate consequence of Rohan’s behaviour fell primarily on them.
There is nevertheless a management argument worth considering. Client relationships operate on confidence as much as delivery. After an incident that visibly calls professionalism into question, leadership may feel compelled to demonstrate that it has taken control. A return-to-office mandate is tangible, immediate and easy to communicate. Reversing it days later could create another perception problem: that management reacts first and retreats when employees object.
But decisiveness and effectiveness are not necessarily the same thing.
Physical presence would not, by itself, have prevented poor judgement. Nor does an office guarantee professionalism. What Vertex lacked was not necessarily supervision, but governance.
For a team that had operated remotely for more than a year, there appear to have been no sufficiently explicit standards around where employees could join critical client meetings from, connectivity, confidentiality, camera etiquette or screen sharing.
Rohan’s mistake exposed that gap.
The team’s response exposes another. Three complaints and two employees exploring exits within 48 hours suggest that the mandate has already begun creating a people problem alongside the client problem it was intended to solve.
Vertex therefore has two relationships to repair. One is with National Finance Bank, which needs confidence that the incident will not recur. The other is with a team whose year-long track record has effectively been overridden by one colleague’s mistake.
How HR responds will determine whether employees see flexibility as something earned through performance or something that can disappear whenever another person exercises poor judgement.
The deeper question is harder to avoid: when trust is breached by one employee, should accountability follow the person who breached it or the system that allowed it?
We asked three HR leaders how they would approach this dilemma.
What HR leaders said
Nitin Khindria, CHRO, Omega Group
“The Vertex case is not really about remote work. It is about how leaders behave when trust is disrupted.
Rohan’s conduct was clearly unacceptable. Joining a critical client meeting from a moving car, creating avoidable disruption and accidentally exposing a video game on screen reflects poor judgement and a failure to understand the importance of the moment. There should be accountability.
But there is another leadership failure in this case, and it sits with management. Moving fourteen people back to the office five days a week within two hours of one employee’s mistake is a disproportionate response. It treats an individual failure as an organisational failure. Worse, it assumes that physical presence will automatically create professionalism, accountability and client trust. It will not. An office can provide proximity. It cannot manufacture judgement.
That distinction matters in today’s workplace. Organisations operate across geographies, time zones and increasingly distributed teams. The question is no longer whether people can be seen working. The question is whether they can be trusted to deliver, exercise judgement and take ownership when nobody is watching.
I would address Rohan’s behaviour directly, understand why the incident occurred, reinforce clear protocols for high-stakes client interactions and make the consequences of non-compliance explicit. At the same time, I would protect the flexibility earned by the rest of the team through consistent performance.
Trust cannot operate on a collective punishment model. Flexibility is not an employee benefit. It is a leadership contract. The organisation provides autonomy. The employee returns it with responsibility. When that contract is breached, the response should be precise, fair and proportionate.
The real question for Vertex is not whether everyone should come back to the office. It is whether the organisation is mature enough to distinguish one person’s mistake from fourteen people’s performance and lead accordingly.”
Garima Kochar, CHRO, KEC Asian Cables
“One employee’s poor judgement should not become an organisation-wide policy. I would hold Rohan accountable, but I would not take away flexibility from the entire team.
Rohan’s conduct was clearly unacceptable, particularly in a critical client meeting. Joining from a moving car, causing disruption and inadvertently sharing a gaming screen reflects poor professional judgement. I would address this directly with him, understand the circumstances and take proportionate action based on the facts. I would also expect the manager to ensure that expectations for important client interactions are clearly understood going forward.
However, I would not convert an individual failure into a team-wide policy change. The team had successfully operated remotely for over a year, with deadlines and client satisfaction remaining stable. There is nothing in this case to suggest that remote working itself caused the problem.
The issue was not flexibility. It was the irresponsible use of flexibility by one individual.
I would strengthen the guardrails for client-facing work: clear expectations on where employees can join critical meetings from, connectivity, confidentiality, professional conduct and screen sharing. Rather than remove flexibility for everyone, I would make the standards explicit and enforceable.
I would also take the team’s reaction seriously. Complaints and early signs of attrition are important signals. A blanket reversal can create a larger people problem by damaging trust, engagement and retention, without necessarily addressing the underlying issue.
This case is ultimately about proportionality and leadership judgement. Flexibility and accountability should go hand in hand. Hold the individual accountable, strengthen the system, but do not penalise the entire team for one person’s poor judgement.”
Sheethal Preethi, GM, HRBP Operations, Vodafone Idea
“Before assigning blame, I would ask two questions: has Vertex actually adopted remote work as a deliberate operating model, and how has productivity held up under it? The facts here answer the second question already. The client delivery team met its deadlines and kept client satisfaction scores steady for over a year. That is evidence remote working was functioning well for this team, not a system quietly failing.
If Vertex has chosen remote work as how this team operates, then the company owes that arrangement strong policies and governance, not a reactive decision triggered by one incident. You cannot run a working model on goodwill for a year and then govern it by exception the first time something goes wrong on camera.
Vertex actually has a strong story to tell: a year of steady delivery and satisfied clients. The client had been comfortable with remote engagement, and that comfort is now at risk of being undone by a single incident. Rather than react with a blanket policy change, Vertex would do better to build clear governance into its client-facing standards: what is expected and what is not in remote client engagements, so both organisations operate on a shared framework going forward.
That said, Rohan’s lapse still needs individual consequence. He should be told plainly that this is not how one conducts themselves in a client-facing setting, and that accountability does not disappear because the team’s model survives.
Equally important is how this decision was made. Management can change rules, but announcing a return-to-office mandate within two hours, with no prior conversation with the team, does not reflect a healthy work culture. It is not surprising that complaints and attrition risk followed almost immediately. A team discussion, asking people directly what compliance measures would work, often produces better outcomes. Employees will frequently suggest sensible governance mechanisms themselves, and standards that emerge from those conversations tend to hold better than policies imposed from above.”
If you were the CHRO at Vertex Technologies
The mandate has been announced. The team is unhappy. Three complaints are on your desk.
Rohan has still not been addressed individually.
What would you do?
- Stand by the return-to-office mandate, accepting that protecting the client relationship now matters more than reversing course?
- Reverse the blanket decision, hold Rohan accountable and restore remote work with clear client-facing protocols?
- Keep the mandate temporarily, acknowledge the team’s concerns and establish a defined route back to flexibility?
Or is the bigger question this:
When one employee breaks the trust that flexibility depends on, who should actually pay the price?
Share your perspective in the comments or on LinkedIn using #HRKathaCaseInPoint.