GARBAGE LEADS TO MORE GARBAGE

Back when computers were the size of your garage, programmers often summarized a particular situation as “garbage in, garbage out.” It normally referred to either bad data or bad instructions that, when fed into a computer, led to worse results. For example, if the programmer’s client didn’t provide a precise description of the program’s objectives, the result might not be what was expected. Or, if the data being fed in was inaccurate, the results could be even worse.

 

The same comment applies to writing. No matter how much talent a writer may have, the results he or she will be able to produce are entirely dependent on the quality of information that’s available. If a client can’t express the objectives or parameters, there’s a good chance that what the writer does won’t meet expectations.

 

After all these years, it still baffles (and bemuses) me when a client takes me to task because a particular piece of copy doesn’t do X or include Y. And when I reply, “You didn’t tell me that you wanted it to do X” or “The information you gave me didn’t mention Y,” I get one of those looks that tells me I’m giving that person a headache.

 

If you want a writer … or a programmer … or a graphic designer … or anyone to give you a certain result, make sure they have the right information at the beginning of the process. If you hand them garbage, there’s a good chance you’ll see more of the same at the end.

, , ,

Comments are closed.