Connect with us
+91 9999818480
A product lead at a health tech company in Gurgaon has seven people reporting to her. Four engineers work from Gurgaon and Pune, a QA analyst is in Hyderabad, and two implementation specialists spend most of the week at client hospitals. She sees them all together perhaps once a quarter. When a hospital go-live slips for the second time, she has no way of knowing whether the client changed requirements, someone was stuck for days without saying so, or something is going wrong at home. She also isn’t sure how to ask without it sounding like an accusation.
The same problem looks a little different elsewhere. A sales manager at a medical devices startup has reps covering hospitals across four territories. A customer support lead at a SaaS company runs a team working in shifts she barely overlaps with. Each of them has to decide whether to trust people whose work they mostly can’t watch. (All three are composites rather than real people.)
Why this is a business question
Most HR leaders don’t need convincing that managers matter, but two recent numbers are worth having on hand. In Korn Ferry’s Workforce 2025 survey of more than 15,000 professionals across ten markets, India among them, 80% of workers said they would stay in a job because they had a manager they trusted. Gallup’s 2026 State of the Global Workplace report found that manager engagement fell from 31% in 2022 to 22% in 2025, and that this was the main reason overall engagement declined. Gallup has long attributed about 70% of the variance in team engagement to the manager.
So a manager who can’t build trust with people they rarely see has more than a morale problem. It shows up in regretted attrition first. Later it shows up in the leadership bench, because good people don’t stay long enough to be developed.
Checking more doesn’t fix it
When managers can’t see the work, the natural response is to try to see more of it: a daily call, another report, a WhatsApp message at 6 p.m. asking for the day’s numbers. Each step is reasonable on its own. Taken together, they tell the team the manager is worried about them.
Microsoft’s Work Trend Index put a number on this gap back in 2022, when hybrid work was still new for most companies: 85% of leaders said it was hard to be confident their people were productive, while 87% of employees said they were. People respond to extra checking by working to look busy. The manager gets more updates and no more confidence.
Trust is decided in a few moments
The standard advice on remote trust is sound, and most managers already agree with it. Be clear about outcomes, keep your commitments, explain your decisions, don’t micromanage. Agreement isn’t the problem. Trust tends to be won or lost in a small number of tense moments, and in those moments managers fall back on whatever they have practiced, which is often the opposite of what they believe.
Three of these moments come up again and again.
When bad news arrives
An implementation specialist messages on Thursday evening to say Monday’s go-live won’t happen, because the integration with the hospital’s lab system is still failing. The first thing many managers say is: “Why am I only hearing about this now?”
It’s an understandable reaction. It is also the sentence that teaches a team to stop raising problems early. The team member hears an accusation, and next time they will wait until the problem can’t be hidden. A manager who wants early warnings has to make the first one feel worth it: “Thanks for flagging it before the weekend. What’s blocking it, and what do you need from me?” The words are simple. Saying them while the client is waiting and your own manager wants an update is much harder.
Picture an implementation manager whose team kept missing go-live dates with almost no warning. Problems surfaced at the Friday review or the night before launch, never earlier. Looking back, she realized she had opened nearly every one of those conversations with some version of “Why didn’t anyone flag this sooner?” She decided to change one thing. Whenever someone raised a risk before a deadline, her first sentence would be a thank-you and her second a question about what they needed. She rehearsed it with a peer beforehand, because under pressure her old line kept coming out first. The early warnings were small and hesitant at first. Within a couple of months, risks were coming up midweek, while there was still time to act on them. Nothing else about the team had changed.
She is a composite too, but most managers who have tried this will recognize how it goes.
When you’re about to break your own commitment
A manager promises to join a client call, sign off a release or review a test plan by Thursday, and Thursday is going to slip. The usual response is silence, followed by an apology afterward. Distributed teams notice. Every quietly missed promise tells them deadlines are negotiable, and they start applying the same rule to their own. Telling people on Tuesday and resetting the date costs almost nothing, but it only becomes a habit if managers learn to see the slip coming.
When something difficult has to be said at a distance
Feedback on a rough client demo, a disagreement about a target, a conversation about attitude. The temptation is to send a message, because it’s quicker and avoids an awkward call. But text strips out tone, and people tend to read the harshest version into it. These conversations belong on a call, ideally on video, followed by a short written note of what was agreed.
Practice, not more reading
None of these moments is fixed by reading an article, this one included. Managers need to say the better sentence out loud, under some pressure, enough times that it comes out first when the real moment arrives.
That matters for how organizations develop managers of distributed teams. A session on trust that ends with agreement and an action plan rarely changes what happens on the next Thursday evening call. What helps is rehearsing the specific conversations: the early warning, the reset commitment, the difficult feedback over video. That might be structured role-play with peers, a coach listening in on real calls, or a few minutes spent saying the opening line out loud before a conversation you know will be hard. Any of these works, as long as it happens more than once.
What you could measure
If you are investing in manager development for distributed teams, a few signals are worth tracking, and most can come from data you already hold:
- How often problems are flagged before a deadline rather than after it is missed
- Regretted attrition in each manager’s team, before and after development
- Whether one-on-ones actually happen, and how much of that time goes on the person rather than the numbers
- Internal moves and promotions out of each manager’s team over a year
Four questions to ask yourself this week
- Could each person on your team say what “done” looks like for their most important target or task this month?
- What did you promise your team last week, and did you deliver it or reset it in time?
- When did someone last bring you bad news early, and what was the first sentence you said?
- In your last one-on-one, how much of the time went on the numbers and how much on the person?
If any of these is hard to answer, that is a better place to start than a new report.