Sunday 30 December 2012

Handling power, dominance and submission in modern workplace:

The most timid one feels to be extremely powerful the moment he/she gets himself/herself associated to the dominant class of people. That’s what leads commoners to take part in gruesome offence during all the crusades and community wars in history and also during gang-rapes and even teasing (both eve and adam).

This is something what we need to keep in mind while leading a big group of people/ team in the organisation, even if it is a team of translators. Technical understanding of couple of languages may not cause increasing rationality among people. It may not be possible for the HR people to concentrate on each and every individual’s behavior in the project teams, especially if the number of team members are many. Finally, responsibility rests on the project manager.

According to Melbourne-based psychologist and career-change specialist Meredith Fuller, bad workplace behavior falls into three categories and the second in the list is:
“Insidious cruelty to others: nasty comments or behavior that undermines or causes stress so that a person is afraid to go to work”.

We often find some new joiners in the company having habit of passing nasty comments on some people they find awkward – obviously as per the cultural standard of the place/social strata/community where he/she has been brought up in. In newcomer’s case, target can be any one of the same group or seniors. We may ignore comments for some time and in most of the cases, bad habits subside with increasing workload or absence of co-workers interested in the same topic. Individuals having bad habits can be successfully treated with appropriate behavioral training programs as well.

It turns into a matter of concern when we pick up a group of new joiners having the same habit for the same project or a couple of new joiners (friends) are influential enough to form a group in the office. Being a group, they are often good performers at workplace which make them indispensable in the project, especially when the project manager has to show profit in a very short term. Often these become active participants in all cultural/social activities in the organisation making their presence felt and needed everywhere. Well, now there is a chance of these becoming the dominant group having the power of practically ‘recruiting’, ‘promoting’ and ‘firing’ co-workers according to their choice in a very short span of time. Showcasing power attracts apparently ‘timid’ colleagues join their group while they anticipate this is the only option for their survival.

Verbal teasing (rarely physical) and fiery gossiping becomes this group’s main weapon to irritate the person they don’t want to see and finally drive him/her away. Being ‘good performer’, obviously they have enough influence on the project manager’s decision making process. Sometimes project managers wrongfully appreciate these people for having very good “interpersonal skill”as their secret of success.  In course of time, if the authority is not cautious, this becomes the most dominant pressure group within the project team, practically having the power to ruin the project.  Well, my experience says dominating groups offer every person outside the group the scope to become an obedient member. And they take extreme step only in case of the ‘disobedient’ one.

Effect: presence of dominant pressure group may not have any direct effect in the profit making process - sometimes it works excellent if we think of revenue generation in short term. But this indirectly affects a company's bottom line – the moral backbone, the result of which may start showing up after a long time. Employees outside the dominant group, however efficient they are, feel uncomfortable at work, absenteeism may rise, finally resignation of sensibly serious employees  is common. Many times the organisation keeps on losing hardworking and serious human resource only because of not being able to handle dominant groups in the projects – impact is again on sustainability.

Fuller says smart organisations know that human capital is their most important resource and they ensure that HR as well as project teams have adequate staffing, authority and procedures to address such troubles and well as treat the troublemakers. For those that don't, there could be trouble down the track. But how can a project manager in an organisation evolve ‘smartness’?

  1.     Work on perception – the process by which we perceive meaning of any event. Manager should come out of bias (we know it’s difficult but it’s a must) – please forget your own cast, community, race, religion etc when you are supposed to manage people.
  2.      Develop a habit of observing people’s body language, i.e. eyes and gesture as well as keep an ear open to know what they are talking about – please don’t participate in gossips – onus is on you.
  3.      Don’t let any two people mocking at the third person – at least at your presence. People are always looking for your support, even for wrong practices.
  4.      Stop using dominant groups to fulfil your objectives - bad or good. They will gradually become weaker if importance is not given.
  5.      Be a part of the team, not part of the dominant group.
  6.      Use the ‘taught’, ‘thought’ and ‘felt’ concept of life rationally – don’t become dependent on any one of these.
  7.      Try to know your people as much as possible – background, education, social class, families 
  8.      Have a little courage at heart when you are supposed to ‘lead’/’manage’ a group – you may loss your job  if the pressure group is very strong in the organisation – no need to be scared – you will find another!
  9.      Don’t complement or criticise your people irrationally and depending on information collected from the dominant group – this may be misleading.
  10.      Leave the organisation which favours blame game and is not interested to sort out the issue.


We don’t have industrial unions is modern day service industries, unattended dominant groups have the potential to take the role of industrial unions of THOSE days!


Saturday 15 December 2012

Estimation in translation – Some challenges


Estimation in translation – some of the challenges

Every translator/language consultant needs to estimate the effort as any software consultant/programmer does.
In both the cases, difference can be too wide between the estimation provided by the group manager/delivery manager and that provided by the consultant.
But this difference is often shockingly high between the estimation done by the language consultants and the one by the delivery manager, if the translator is working with some software project/ manufacturing unit/ heavy industries unit:

Why it is so?
Let’s understand the difference between the parameters considered by the very honest translator and the very honest delivery manager – say for a text containing 50 words with two screenshots, the word count of which cannot be taken (the process is all manual without the scope of using any CAT tool).
What goes in the back of the minds in case of techie manager and the linguist translator while estimating?:

Parameters considered by a manager
Time needed
Parameters considered by translator
Time needed
1.
I see only 50 words to be translated and I know how much time it takes to type 50 words. Translator’s job means typing 50 words for 50 words.
5 mins
I see a text containing 50 words having relevance to finance\mechanical and heavy engineering for which I need good research and then I will be able express this effectively in 40 words in target language.
15/20 min
2.
I know what typing speed a good typist should have and the translator needs to type at that speed.
5/7 mins.
Time for starting the computer, create the development (read translation) environment and getting the right source. Company does not provide me a single dictionary or tool – and I have to find out all online dictionaries relevant for this task. So I need time to ‘build’, ‘check in’ and ‘fix’.
20/25 min
3
It’s just a minor work – the translator may have to copy and paste the text to google translator and then copy and paste it back to the document; then change a couple of words here and there to claim it to be his/her translation!    
3 mins
The first reading shows it’s quite rare to find exactly the right information on the first try. Even if it is found, I may need to go through some business documents of this kind available in the library to verify the correctness of my translation. That needs another 30 mins which am not even adding!
45 mins
4
Document format – what the hell that matters to the translator? –well will be happy if I get the translation of the 3 included screen shot too. Well, that cannot be done through google – I understand- let the translator take ten mins more.
15 mins
I see the source document is in non-editable PDF - I need to copy and paste the text to a document – then screenshots separately and make table for the screenshots while these are not non-editable as well. Seems screenshots contain another 50 words.
15 mins extra (making total time 45 mins)
5.
I cannot understand which word means what in the screenshot if translator does not write the original in the table. Request to write original too.
5 mins extra  (total 20 mins)
Typing original means I have to type some special characters in the source language – I cannot use even shortcut keys in the laptop provided…so copy + paste from the symbol button is only option!
Another 15 mins extra (making total time 60 mins)
6.
Review? Why? Does not a translator see what he is writing while working on system?
20 mins
In any case I HAVE TO REVIEW THE TRANSLATED DOCUMENT to ensure everything important mentioned in the source is mentioned in the target too. Well – let’s not mention extra time which can make the manager go mad – will do it at home, or cutting time for my breakfast of something.
60 mins
7.
Advice the translator to be honest which may work as a warning so that he/she does not try to make me a fool – last time we received a translation from another translator in 10 mins for a similar text.
20 mins maximum (final)
How to explain the manager that translation is not googling – I can’t even invite the person to sit with me while working and follow the process! – the document he mentions is of different domain  - and yes, the target document shows that the previous translator only googled! – let me discuss the topic “language quality’ with him.
60 mins (final)
8.
Language quality? – I can never imagine the word ‘quality’ to be associated with a low level subject called ‘language’….it’s not engineering after all!

Quality is something a translator has to stick to. I see very well from company’s old project documents how incorrect translation spoiled some projects and our  superiors couldn’t even  determine it due to lack of language skill. I should take care of this.

9.
Unfortunately company has picked up a stubborn person as translator who does not even understand how urgent the task is – or does not even able to type 10 words/min.

The manager knew since last one month that some documents in this pack need translation - wonder why he/she didn’t inform long back (I was sitting almost idle for a week a fortnight back!)


 And finally it’s a standstill, often leading to resignation of the annoyed translator or indirect firing and it’s time to search for an obedient translator.

The biggest challenge here is, none but a bi-lingual person knows “hab mal gehört dass ein SAP Wörterbuch Deutsch-Englisch als Transaktion existiert. Weiss einer, wie die Transaktion heisst?” Does not mean “SAP've heard that a German-English dictionary exists as a transaction. White one, as the transaction is called?”

Or “Materialien, die als Schüttgut gehalten sind und Serialisierung Profil 12, ausgeschlossen sind, während durch die Transaktion verbunden ZSD602” does not mean anything in Deutsch while the source English was “Materials, which are maintained as bulk material and have serialisation profile 12, are excluded while connected through the transaction ZSD602”.

And it’s almost impossible to argue about the correctness when a ready machine translation is always available. Bi-lingual experts are rarely found in the companies who can examine the facts and provide a solution. Anyway, clients anyway await the quickest solution/set up and never bother how the service providing manager is to get a project done in 30 days which would need a translation effort of 10000 words a day. The sales management teams are rarely aware of any word called ‘translation effort’ which should be included in contract, while service/ consultancy/infrastructure is being provided to Ukrain or similar non-English speaking countries. Anyway all the superiors of the client company speak English very well! Translation is  not even considered as ‘deliverable’ in many cases.

And the story goes on................