Where the friction actually comes from
Communication & FeedbackThe question asked was not the question answered
A manager asks "can you have this by Friday?" and hears yes. Friday arrives and the work is not there. Two different things happened at once. A yes-or-no question was asked in a setting where declining a manager outright is neither comfortable nor useful, and it was answered as agreement with the intent rather than as a forecast of the date. Nobody lied and nobody was careless. The question could only be answered one way. A US manager asking about a date is asking for a forecast, not for agreement, and will treat your number as the commitment. Giving a date later than the one asked for is heard as information, not as refusal. Saying "Friday is possible if the test data arrives Tuesday, otherwise Monday" reads as competence in that frame, where a plain yes followed by a slip does not.
Decisions & AgreementThe meeting is not doing the same job for both sides
In the US default, the meeting is where the decision gets shaped: people arrive with positions, argue them live, and silence reads as agreement. In the Indian default, alignment is built beforehand in one-to-one conversations with the people who matter, and the meeting confirms a direction that already exists. Both produce alignment. They put the work in different places, and each looks like an absence of the work to the other. In a US meeting, a position raised afterwards in private is often heard as having been withheld, and a decision taken in the room is treated as settled. The pre-work you would normally do one-to-one still helps, but the position needs saying again, out loud, while everyone is there. Silence will be counted as a yes.
Accountability & OwnershipNaming an owner does two things, and only one is wanted
US practice puts one name against every significant task, and credit and blame both follow that name. Indian teams more often absorb both collectively, and naming an individual in public for a miss carries a cost that is not visible from the other side. The clarity of named ownership and the exposure of public naming arrive together, which is why one side sees a basic management hygiene step and the other sees an unnecessary risk. In a US setting, saying "I own this" out loud is read as confidence rather than as self-promotion, and not saying it is read as the work having no owner. Claiming a result you delivered is expected. The collective framing that is generous in one frame reads as vagueness about who did what in the other.
Relationship & TrustTrust is being built on different timetables
The US default extends provisional trust on arrival and lets delivery confirm it. The Indian default builds it through the relationship first and then extends it broadly. In practice the first weeks of a new engagement feel slower to one side and rushed to the other, and the check-in at the top of a call is doing real work for one party while reading as delay to the other. A US colleague moving straight to the agenda is not being cold; getting to the point quickly is itself a form of respect for your time. You can build the relationship alongside the work rather than before it, and small delivered commitments early will do more for trust in that frame than any amount of rapport.