Friday, February 29, 2008

Blamegame goes on...where the pesticide got into the dumplings?

A big war of word is ongoing between China, who claims that there is no possibility whatsoever that the pesticide found in the doomed dumplings was in there where they are in China's turf, and Japan, who has said that as far as the investigation goes, a very low possibility of the poison was put in where the dumplings arrived in Japan, one of the evidence Tokyo police presented to the Chinese is that the use of the type of pesticide has been long discontinued in Japan. Not only the police of the two sides, now even Tokyo governor Shintaro Ishihara steps in, who has expressed displeasure towards the Chinese attitude.

Who should to blame?

Let's take a step back here, since the both sides have expressed a desire for a quick solution, and everyone realizes that as the issue drags on, more people will stop using more products from China, Made in China reputation goes down the drainage, and Japanese government, who has been facing a mounting inflation headache, suffers along with the consumers.

It takes two to dance, the solution should be a two step dance--one is to get into the bottom and identify the source of problems by presenting evidence clearly, exchange information on any clues, and take between door, intensive and collaborative works between all related parties from both sides. No questions are harder to ask, no suspects are left at large. Only through detailed hard work. Words are cheap and usually serve no good for no one.

Second step is to take a quick measure to ensure a complete root out of the problematic areas. Wherever it is, responsibility has to be taken. In today's globalized world, a local protectionism is simply not working, more protection invites more rotten wounds, to have a health back to the system, the affected area has to be taken away promptly.

A blame game is easy to play, however, a solution takes patience, hard working and more importantly, cooperation, are China and Japan ready to play along?

No comments:

 
Share |