The post-COVID WFH backlash
A significant number of Indian companies pushed aggressive return-to-office mandates in 2023 and 2024. Their reasoning, when stated plainly: "We tried WFH during COVID. It did not work. We are not doing that again." Now, with PM Modi's WFH appeal in May 2026 reigniting the conversation, those same companies are hearing from employees who disagree with that conclusion.
Both sides have a point. WFH during COVID often did not work well. But the diagnosis of why it failed is almost universally wrong. The failure was not about working from home. It was about the absence of systems that make remote work functional. Fix the systems and the outcome is different.
What actually failed — the honest post-mortem
Failure 1: No outcome clarity
When offices closed in March 2020, most Indian companies had no documented outcome frameworks for individual roles. Managers managed by presence — seeing who was at their desk was the primary accountability signal. Suddenly removed from that signal, they had no alternative. Employees did not know what good looked like. Managers did not know how to verify it. The result was anxiety on both sides that never fully resolved.
The fix: Before any WFH arrangement, every role needs written, measurable outcomes for each time period. Not tasks — outcomes. Not "work on the module" — "deliver a tested, reviewed feature by Friday."
Failure 2: No work verification system
Without office presence, managers had no visibility into whether work was happening. The response was typically one of two extremes: blind trust (which eroded confidence when deadlines slipped) or excessive check-ins and status update requests (which fragmented everyone's day and bred resentment). Neither gave managers the accurate picture they needed.
The fix: Passive work tracking tools that capture session activity, application usage, and work timelines automatically — without requiring manual timesheets or constant check-ins. The data is there when needed; it does not interrupt the workday.
Failure 3: Communication norms collapsed
In offices, communication norms are ambient. You know when someone is in a meeting. You know when to interrupt and when not to. At home, those norms disappeared and were not replaced. The result was either constant Slack interruptions (destroying focus) or silent disconnection (destroying coordination).
The fix: Explicit async-first communication protocols. Defined core hours for synchronous availability. Meeting-free focus blocks protected by team agreement. These are policies, not technologies, and they require active management to enforce.
Failure 4: Junior employees were left to drift
The COVID WFH experience was dramatically worse for junior employees than for senior ones. Senior professionals had established networks, clear context, and self-directed work habits. Junior employees learning their roles depended on proximity — watching senior colleagues work, asking quick questions, receiving informal feedback. Remote work removed all of that without replacement.
The fix: Structured mentorship programs with scheduled pairing sessions, deliberate knowledge transfer documentation, and anchor office days specifically designed around junior employee development.
Failure 5: Mental health and isolation were ignored
COVID WFH happened during a global crisis, under lockdown conditions, with no social outlets. Many employees experienced genuine isolation, burnout, and anxiety that would have happened regardless of their work location. Companies attributed the mental health impact to WFH when it was actually a response to pandemic conditions.
The fix: Separate the COVID WFH experience from the WFH question itself. Structured WFH in normal conditions — with social connection opportunities, clear work boundaries, and management support — looks very different from pandemic remote work.
The systems checklist for WFH done right
- Outcome contracts for every role. Written, measurable, and reviewed weekly. Not job descriptions — live deliverable agreements.
- Passive work tracking with employee access. Session records, application context, and proof-of-work timelines visible to both managers and employees.
- Async communication protocols. Core hours defined, meeting culture redesigned, focus blocks protected.
- Structured mentorship for junior staff. Scheduled pairing, documentation culture, and anchor office days.
- Manager training on remote leadership. Output management is a different skill from presence management and requires deliberate development.
- Clear WFH policy in writing. Who is eligible, under what conditions, how performance is assessed, and what the review timeline is.
- India DPDP compliance for any monitoring tools. Employee notice, consent, dashboard access, and documented retention limits.
The honest question to ask before deciding
Before your organisation decides its WFH policy in response to the current moment, ask one honest question: "Do we have outcome clarity, work verification, and communication norms in place?" If the answer is no — and for most Indian companies it still is — the solution is not to ban WFH. The solution is to build those systems. With them, WFH works. Without them, even RTO does not solve the underlying management problem.
The bottom line
WFH did not fail in India. Poorly designed remote work systems failed in India. The two are not the same thing. The companies that recognise this distinction — and invest in building the systems that make remote work accountable — will have access to the full Indian talent pool regardless of geography. The ones that conflate the experience with the concept will keep fighting a war over desk presence while their best people explore employers who have figured it out.