Them: Yes
Me: Ok, and would you be able to blah blah blah?
Them: Yes
Me: Great, and do you think that will be ready by blah blah?
Them: Yes
Me: Fantastic. What approach do you intend to use?
Them: Yes
Me: mutes phone, curses, unmutes phone, goes back to start
I've occasionally worked with some excellent individuals, but the aggregate has been poor.
My most recent experience with a team of this type repeatedly involved requests for documentation at a level of detail where automating the task would be less effort.
The biggest problems are cultural, but the perception is going to be hard to overcome.
I'll let one of our Indian colleagues suggest the best alternative here, as I'm sure they know more about the relevant Indian cultural points than I.
But even something like "Tell me how you will accomplish X?" or "Do you have any worries about doing Y?" tend to produce better India-US communication.
Another factor is that most of my encounters with such groups has been while working for organisations looking for a cheap option. I strongly suspect that this is common and results in hiring low quality groups with mediocre people - again tainting popular perception.
Usually the consultants/people-who-pitch at such dollar-hungry Indian firms won't tell you 'NO' because they fear they might lose you. People in-charge of saying 'YES' aren't often aware of the abilities of their team.
And, surprisingly, sometimes, the 'YES' comes out of plain politeness. In some occasions, they don't want to disappoint the clients who've exhibited a lot of trust on these folks.
So, when an Indian says 'YES', they correctly understand the liabilities & responsibilities that are implied, but they might not have what it takes to deliver on the commitments they made.
1. Saying yes to everything. Questions, estimates, analysis: everything was answered in the positive even when the facts were negative. I makes project control very hard. 2. Deferring to management every 10 minutes. On every call, meeting etc. Engineers were very much not able to make decisions by themselves.
Having said that, all men and women I worked with from these companies we're really friendly and certainly tried their best.
It's rather an untold rule across the industry to channel all decisions & difficulties via their manager.
I'll give an example - We once asked our offshore-engineer (contractor) to share their personal email ID for a github invite for we knew that he had one readily at his disposal. Using gmail for work is a big deal for IT offshoring companies. The guy, instead of sharing his concerns about his directives & security guidelines directly with us, called his manager who replied to our email asking us to stick to Enterprise email IDs.
Other experience, estimates are wrong, filling in more hours than actually worked and they always say yes. But what they mean is we can't or don't understand what your mean and we will stall the project.