Part 3 of 13 in How to Get Your Team to Work Well from Home← Part 2Part 4 →
This chapter addresses common objections Indian companies raise about remote work, including trust, culture, unreliable infrastructure and customer confidence. It helps managers design work around clear outcomes, written communication and practical backup plans.
- Clear outcomes are more useful than monitoring online presence or office attendance.
- Culture and mentorship can grow through written feedback, recorded videos, one-on-ones and deliberate recognition.
- Asynchronous work, documentation and backup options can reduce disruption from internet and power outages.
- Customers usually care more about responsiveness, quality and reliability than where the team works.
- A small office-based core team can support client visits while the wider organisation works remotely.
“How Will I Know They Are Working?”
This is the most common objection in Indian companies. The hierarchical culture makes managers feel responsible for watching people. Fried and Hansson’s answer remains the best: if you do not trust people to work without being watched, you have hired the wrong people or you are managing the wrong way. Presence is a poor proxy for productivity. An employee can sit in the office for ten hours and accomplish little, or work six focused hours from home and ship something valuable.
The practical response is to define clear outcomes. Instead of “be online from 10 to 7,” define “ship the feature by Friday with these acceptance criteria” or “close three customer conversations this week and document the learnings.” When outcomes are clear, the need to watch people decreases. Managers who still feel anxious can review progress in shared documents rather than by walking around.
A useful exercise is to list every recurring meeting and ask: what decision or information transfer happens here that could not happen in writing? Most of the time the honest answer is “very little.” Cancel or shorten those meetings and replace them with written updates. The anxiety about “knowing they are working” usually drops once progress becomes visible in documents rather than in desks.
“What About Culture and Mentorship?”
Culture does not require a common floor. It requires shared standards, regular communication and deliberate moments of connection. Many Indian companies already run on WhatsApp groups and late-night calls; remote work simply makes the asynchronous parts more intentional. Mentorship can happen through recorded videos, written design reviews and scheduled one-on-ones rather than corridor conversations.
Young employees in particular benefit from written feedback they can re-read. An AI tool can help a manager turn a rough voice note into a clear, structured feedback message that the junior can study later. This is often more useful than a hurried verbal comment in a noisy office.
Culture is also transmitted through the stories a company tells about what it values. When a remote team publicly recognises someone for helping a colleague solve a problem asynchronously, or for writing an exceptionally clear document, those behaviours spread. The office does not create culture; deliberate reinforcement does.
“Internet and Power Are Unreliable”
This is a real Indian constraint, not a theoretical one. The solution is not to pretend the problem does not exist. It is to design the work so that temporary outages do not stop progress. Prefer asynchronous tools over live video. Maintain clear written documentation so that someone else can pick up work. Encourage employees in smaller towns to have a backup plan—mobile data, a nearby co-working space or an inverter.
Companies can also offer a small stipend for reliable internet and power backup; the cost is far lower than an office seat. Many Indian remote workers already solve this. They work from home when the power is stable and shift to a café or co-working space when it is not. The key is to measure output, not continuous online presence.
“Customers Will Not Take Us Seriously”
Some founders worry that clients, especially traditional Indian enterprises, will not respect a remote team. In practice most customers care about responsiveness, quality and reliability. A well-documented, responsive remote team often outperforms a local team that is constantly in meetings. When necessary, a small core team can remain in an office for client visits while the rest of the organisation works remotely.
Many Indian SaaS companies already sell successfully to global customers without large local sales offices. The product and the responsiveness matter more than the address on the business card.
Frequently asked questions
How can managers know remote employees are working?
Define clear outcomes and acceptance criteria instead of requiring employees to be online for set hours. Review progress in shared documents rather than relying on office presence.
Can remote teams maintain culture and mentorship?
Yes. Shared standards, regular communication, written design reviews, recorded videos and scheduled one-on-ones can support culture and mentorship.
How can Indian companies handle unreliable internet and power?
Use asynchronous tools and clear documentation, and encourage backup options such as mobile data, co-working spaces or an inverter. Companies can also offer a small stipend for reliable internet and power backup.
Will customers take a remote Indian team seriously?
Customers generally care about responsiveness, quality and reliability. A small core team can remain in an office for client visits while the rest of the organisation works remotely.