"And every time we met, they refused to take notes. I would say 'are you getting this' and I would get these head bobs, that looked like a yes, and they would say yes....but 4 months later when the product arrived my suspicious were confirmed: they couldn't remember everything I said"
Met with a friend from graduate school this week to enjoy lunch and the conversation turned to his last company where he served as a product manager working closely with an India development team. This PM was wildly confused by his inability to get this remote team to write anything he said down. After belaboring the requirements document in finite detail he would look around to see no pens, paper....only that infamous India yes. Guess what? The product was a complete failure. Requirements were not met deadline over deadline. Yes it will get done. Yes we understand. Yes we will be implementing that feature. Yes that feature requires what you have written on the document. Yes, Yes, YES.
How can my friend get to a real yes? Notes, notes and notes again. Demand that notes are taken by the Indian team and TAKE YOUR OWN NOTES. Implement protocol that notes are exchanged after each meet. Reconcile the notes from the opposite side with yours and create a finalized set of note. Get the remote team to sign off on the new adjusted reality of the meeting.
This situation with its seemingly easy resolution is in reality SO painful for US citizens to implement. Why? Because we all are trained to "believe" that we have individual styles for communicating and remembering information. We all have a different way to "get it done." When we enter into this new mixed nation relationship we take in this baggage and assume that all is the same. From my experience, its not. This is not to say that Indians don't have the same number of talents that you hold in your pocket. Rather, there is so much room for a communication failure in these situations that a formal method for communicating must be implemented. It seems stiff right--and wow I really don't want to spend the time doing that. Well, you can take the same road as my friend, and find yourself enjoying your boss's glare when the project fails under your watch.
Ironically what I hear from people that implement this strategy is that they realize how many things were missed by the remote team. They also realize that understandings are completely different. Of course, this lack of meeting of the minds would occur in any situation such as comparing notes in a grad school class. The degree of variance is the problem. When taking notes in class you may decide not to write something because its not "important" and you already know it. You know the teacher and what they will ask on the test so you construct your methodology on this basis. Unfortunately this is not a luxury you can afford with a remote team who has never met you, or perhaps has shared a mango lassie over a brief stay in country. They don't have the ability to decide on importance and you can't rely on them deciphering your communications without verification.
At the end of the day, whats on paper is what is on paper. Get it on paper. Review it on paper. Email it and get agreement. Your project will be better for it.
Recent Comments