Were you recently taken by surprise in what was considered a routine standup meeting to be asked to change the course of what you were working on?
Were you asked to do something that you felt was not so easy to do, not good for the long term outcome of the product or something you would definitely need more time to get done (even if it was a good idea)?
How did you handle that situation?
Could you respond? Did you stay silent?
We work with many offshore teams, especially teams in India who work with US clients. Many of those we work with speak English as a Second Language, have 5-15 years experience in the field, but may not always know the cultural context to “push back” or how to build the relationship to handle these not-so-easy conversations.
Those we work with, like you, are technically brilliant. If you ask me about your work, I’d say for sure you have a lot to teach me that I do not know!! But, while one excels in the technical aspects of their job, gets tongue tied when having to be in front of the client. It becomes more complicated when maybe you are the only one handling the meeting because of the new work from home dynamics, your senior moved on and you suddenly took his or her place, or your manager was not available for the meeting that day.
So, how can you handle these conversations in a tactful way?
In working with many startups in India, it was clear that processes from sales, to contracting, to intake, to change requests, project planning, documentation, meeting notes, and off boarding (among others), were either not all in place, not up to date, or done haphazardly. In working with US citizens, many do rely on the written word, take more stock in it. The written word typically builds trust as compared to the spoken word. The more that can be put in writing and managed in an organized way, the more trust one may tend to build. Also, when it is in writing, it can be filed and easily retrieved (hopefully). So, that when a request comes through that you need to push back on, it should be easy to find that document, email or contract (sow- statement of work) snippet that refers to what the clients wants changed to be able to use that as “evidence” that it was earlier discussed and decided on. Of course, it’s still important to listen to the “why” of the client’s request. In some cases, a conversation may open more doors to understanding possibly if what the client is asking is already being done (but, as they are not technical, they did not understand that part, so talking in conversational English about technical topics may be required), may be being done in a slightly different way than anticipated, the code or technology that’s being used doesn’t support that change request, or any other valid reason.
Some related responses that may relate to this are:
For more information on the important of processes, see How do you push back against a client?
Author, Jennifer Kumar, coaches virtual team members working with US Americans to bridge the cultural divide. We can work on small talk with US Americans, managing meetings, building your developers into consultants, and presentations over virtual mediums, and preparing your teams to come to the US among other business building skills.
Updated May 2019
Find your ideal program in just a few clicks.
Select Industry > Learning Level > Skill, to see 1-3 suggested programs.