What are the Differences Between Technical Illustration, Information Design, and Editorial Illustration?
© 2010 Ugur Akinci
Thanks to a number of responses to an earlier post about Technical Illustration, I had the opportunity to think more about the topic.
I now realize that I have not clarified the various niches that exist within the catch-all category of graphic arts that we call “technical illustration.” Here I’d like to point out to a few of them.
The first distinction I’d like to make is that of “technical illustration” (TI) versus “information design” (ID).
The traditional TI is a passive format. Its main purpose is to support and illustrate the accompanying text.
The technical illustrator is not trying to make a statement through her art but help the text by making it more accessible, intelligible, and understandable.
Here is a good TI site: http://TechnicalIllustrators.org
ID, on the other hand, does make a statement. Actually, that’s the whole point to ID. An ID product that does not make a statement is like a public speaker who does not say a single word. It’s a contradiction in terms.
Here is a fantastic ID site that I visit daily: http://flowingdata.com
A technical illustrator does not need to understand the data at hand or how the system or hardware in question works. DEPICTION is the main goal in TI. IDENTIFYING THE PARTS and how they fit together to make the whole work, is the principal goal in creating a TI.
An information designer, on the other hand, takes in the raw data, regroups it in a visual way, shifts and moves it around, and coaxes a generalization or statement out of it that did not exist before, or at least was not that readily apparent. There is a DEBUNKING process going on here, just like in any “data mining” operation.
A good ID product creates that classic “a-ha!” moment of illumination and recognition. It’s a revelation in a way that TI is not. In TI the a-ha moment is delivered through the accompanying text.
One is passive (TI); the other is active (ID).
And somewhere in between is the “editorial illustration” (EI). This is an interesting format that speaks with its mouth closed. We hear a statement is being made but the voice is not clear; it’s muted and the message is semi-clear. The CREATIVE and ARTISTIC LICENSE taken by the artist prevents us from hearing the message in an obvious pattern, as is the case with ID. Instead we have to work on it and come up with our own INTERPRETATION of what the message means.
A good example of this form is represented by Harry Campbell: http://www.drawger.com/hwc/
I believe the first two types of illustration fall well within he scope of Technical Communication whereas the EI rather belongs to the domain of creative fine arts. But all these three forms of illustration overlap and create enough in-between forms to welcome technical illustrators from all kinds of backgrounds.
Technical illustration in general is a field rich with possibilities, especially in this day and age of globalization where more technical project managers than before are relying on visual products to hold down the cost of text translation, on the one hand, and appeal easily to a cross-cultural audience, on the other.
What do you think about this post? Does it explain the differences between these different types of illustrations adequately? What’s your take on this topic? Please feel free to share. Thank you.
Ugur, thanks for tackling this topic. I hadn’t thought much about the distinction between technical illustration and information design, but I agree with the way you’ve defined it.
By the way, you seem to be interested in graphic design and information design. Can you share more about the reasons why? I’m currently developing a series of posts on information design/visualization on my blog. Our conversation today spurred me to move forward with it.
Tom, thanks for the comment. First off, I love tech illustrations because I love to draw and always had a keen interest in fine arts (my mother is a painter). As a writer I was always fascinated in visual expression of data and relationships. I studied the works of information design masters like Edward Tufte and Richard Saul Wurman with great interest. So it was very natural for me to find myself learning how to use programs like Illustrator and starting to create technical illustrations just for my own pleasure, initially. Soon my humble efforts were recognized, welcomed and encouraged by my colleagues and managers as well. Today where I work I not only do regular tech writing but tech illustrations as a part of my job and I love every minute of it.
Another reason why I’m very interested in tech illustrations is the obvious need for it in this day and age of globalization and localization. It’s an obvious big feather in your cap as a tech writer if you know how to draw and create illustrations. It’s definitely a competitive edge, and here is why:
Project managers are increasingly looking forward to documentation with less words and more pictures in order to minimize translation costs. The adage “a picture is worth a thousand words” has never been more literally true than today. I was glad, for example, that I could contribute more to the last international product-launch project in my company through the fully-illustrated installation guides that I’ve personally designed and drawn than through my writing. It was a pleasant and rewarding experience that convinced me how important tech illustration will be in the future as a part of every technical communication project.
We are living truly in an era where “communicating” means a lot more than just “writing.” So that’s why I’ve made it a central mission of this web site to help my fellow communicators develop not only their writing but illustration and drawing skills as well. I’d be happy to collaborate with you further on this topic.