When someone asks an engineer for some technical help, they usually say: “right now, really quick.” It is not unusual to take these “small technical favors” for granted; we often think they are very simple – until we take a closer look at them.
It all starts when one approaches the maintenance person and says, “Could you fix this problem right now, really quick? It was just a tiny little pipe that broke.” In fact, the “tiny, little pipe” broke because there was too much pressure on it, since there is another part that was bent. This was caused by yet another part that is way on the back, difficult to reach. When the technician takes a closer look at the whole structure, he find out that what was causing the problem was a set of interconnected parts, one causing the other to malfunction and all need replacement.
Although the situation may sound a bit fanciful, this is exactly what happens in most cases. The real problem is not what is right in front of your eyes, but rather something much more complex affecting the apparently obvious problem.
If the repair is to be done “right now, really quick,” the problem will persist — before you would expect. Not to mention that, as the service was done in a hurry, some details were overlooked and crucial aspects may have been ignored.
Can you clean up the sofa right now, really quick?
Just find some space for our guest to sit down…
This is what happens with almost every one: mechanics, electricians and computer technicians and… localization engineers!
A simple Word or PDF file can have way more details than it seems at first glance, especially when it comes to engineering procedures, which involve format conversions, file preparations or more complex tasks. At this stage, 80% of the potential problems that could affect the project appear—these are the worst and most complicated ones. This is when you realize that the automated task that would take five minutes is not working and doing it manually will require 25 hours!
To make matters worse, we often only receive the file at 6 p.m., on the day the client should be receiving it. After all, the procedure would take just five minutes, the client delayed the file handoff (which should be much smaller than the actual batch received), the translator forgot a tiny detail, and the reviewer was working on another small, but urgent project and so on… For all these minute details, the project was not received earlier. By now you have an idea of how big the problem is.
There are other situations when the client sends a Flash file, with audio, written in English with very small fonts to fit on the screen and says that the file is due in three days, “It’s only a few words. And we’re just going to translate to German, Arabic and Japanese.” When the client was supposed to receive the files, one finds a little problem that is going to delay the handback in just a couple of hours. But then another little problem arises. And another one… The actual delivery one happens three days after the due date.
This attitude makes it difficult for the team to devise potential problems, stresses the whole production group, reduces quality and frustrates the client. Next time, think twice before asking your colleague from the engineering department to complete a task “right now, really quick.”