September 17, 2015 § 5 Comments
Some months ago the event technician approached me during a break and told me a story that made me think of a very important aspect of our practice that is rarely mentioned. He said that during the prior weekend he had worked a conference with two interpreters he did not know (something extraordinaire for this individual who has worked with just about everybody).
Apparently, the agency had brought them from out of town because they wanted to abate their costs, and from the information the technician gathered, they were court interpreters with very little conference experience. According to him, they were very quiet and not very helpful, and to the dismay of the technician, he even had to decide the location of the booth in the conference room because the interpreters did not make any suggestions or give any input. He also commented that the quality of the interpretation was poor.
Of course a story like this one frustrates me, as I see once again that there are many in this business with total devotion to the old mighty dollar and total contempt for the quality of the service; but it made me think about the importance of a good relationship with the tech staff. It is obvious that it does not matter how well-prepared we are for an event if at the time of the rendition we cannot hear the speaker because of a sound system that was not tested, we cannot see the presentation on the screen because of poor location of the booth, or the audience cannot hear a word of what we are saying because of an equipment malfunction. It is essential that we learn how to work with the technician, and this includes not just being nice to the individual, but also our ability to use the equipment, our opinion as to the location of the booth, our willingness to participate in the final run through so that all microphones and consoles are tested and all levels are adjusted.
It is also very helpful to have a communication strategy. Sometimes the technician is next to the booth, but there are times when they are very far away from the interpreters. For this reason, having agreed to some signs and gestures ahead of time will let the technician know that something is bleeding into the system, that a relay button is not working, and many other things.
I have been in situations where the event organizer refuses to pay for a dedicated technician throughout the event, and everybody can tell the difference: When something goes wrong and the technician is there, things get solved and the conference continues. Things can get ugly when there is no technician on the premises, and there are just so many coffee breaks the participants can have while a well-intentioned but unskilled individual tries to fix a problem.
We interpreters should always consider the technician as part of our team. We cannot work without them, so we should include their function when developing our master plan for an event. Besides, having the tech support staff on your side can get you additional benefits: They are often some of the first ones to know of an event, and many times they are asked by agencies and event organizers to suggest interpreters for conferences. We should recommend the good technicians and in turn they will put out a good word for you.
As you see, this conversation with my technician friend and colleague got me thinking of the importance of their job and how it impacts us professionally as interpreters. It made me pledge that I will never be like the interpreters he worked with the prior weekend who were quiet, had no opinions, and did not know how to work with the technician. I now invite you to share with the rest of us your comments and stories about your relationship with the technical staff.