Challenge India Part 2: How to handle specifications?

This article is a follow up to: Challenge India (for western cultures) Part1, section “specifications”

Work packages for external service providers are set down in specifications. A specification document is created by subject matter experts in the client company and passed to the service provider. After implementation the service provider hands over the deliverable to the client, expecting his acceptance.

Unfortunately that’s the way western companies handle their business relation with Indian vendors and even believe it really works this way. Eventually the companies realize that the deliverables are far from what was expected. If the specification was written on abstract level, the service provider team doesn’t know exactly what to do. But without demanding further information they start to work according their own interpretation; needless to say that the deliverable won’t match your expectation.

If the specification is written on a very detailed level, the service provider team follows each instruction without reconsidering if things make sense or not. In most cases the deliverable also won’t match your expectation. So how to write the “perfect” specification?

1) Let the service provider write the specification.
Give a rough guideline of the specification contents and the expected deliverables. Let the service provider write the specification in their own words with their understanding. Accompany the creation of the specification, ask for drafts on regular basis and clarify different views immediately.

2) Use an incremental approach.
If it takes 10 months to implement a deliverable, insist to get provisional results presented on regular basis, e.g. every 4-8 weeks. This ensures that misunderstandings are identified as soon as possible and corrective actions can be taken on the spot. Include the approach of iterative delivery cycles already in the specification document, i.e. what is presented when. Not at any time accept an approach with a single final deliverable only.

For sure, both points take more time in setting up the specification and lead to higher costs in the very beginning. But this additional effort will definitively save costs in subsequent project phases.

Challenge India (for western cultures) Part1

No doubt, the evaluation of outsourcing and offshoring locations brings you in touch with India. Mumbai, Chennai, or Bangalore are emerging cities offering services for any kind of business processes. Low labour costs, strong technical expertise, and good English skills are the pulling factors making India an attractive place. However, dealing with the Indian subcontinent can be a challenging task especially for people from a western culture. Here are the 3 most challenging issues when doing projects with Indian contractors:

Feedback
In India weaknesses and failures are not admitted in public; it might result in losing face. So before someone admits a failure he tries to cloud it with vague statements. Therefore the client can’t expect an early warning if a milestone is not achieved. Western cultures treat a deadline as given, so 5th of September means 5th of September and not 6th, 7th or 15th. From Indian perspective time is stretchable; they see a few days delay still as delivery in time. Together with the Indian "optimistic" style of planning this brings projects into trouble.

Specifications
Projects start with user requirements usually written down in a specification document. If the specification is written on abstract level, people don't know exactly what to do. Without demanding further information they start to work according their own interpretation. If it's written too detailed, people follow each instruction without reconsidering if things make sense or not. The first presentation of an interim deliverable (and I hope you have interim deliverables in your project) ends up with an unpleasant surprise for the client.

Contracts and agreements
In western cultures contracts are final after signed by both parties. An agreed fixed price is a fixed price. In India a fixed price is often treated as guideline, a point of reference. It is considered normal to renegotiate or to charge extra cost during the contract period of validity. The major issue is that during contract negotiation, the Indian party fully agrees to the fixed terms without mentioning the possibility of extra charges. On the other hand, the western counterpart does not even think on upcoming extra charges after signing; they take the approval of the Indian counterpart as fixed agreement. And as soon the Indian party starts the first attempt to renegotiate the price, the clash is inevitable.

Feedback, specifications, and contracts; 3 Indian challenges. In the next “Challenge India” articles I will advise how to deal with these challenges and make projects with Indian contractors a success story.