See What I Mean

From: A List Apart: The Full Feed

Comics are a unique way to communicate, using both image and text to effectively demonstrate time, function, and emotion. Just as vividly as they convey the feats of superheroes, comics tell stories of your users and your products.

Comics can provide your organization with an exciting and effective alternative to slogging through requirements documents and long reports. So let’s see how you can start using comics to communicate in your work.



<img src="" alt=""><a href="">Keep reading the comic</a>

Imagination: A key property of comics

In the book Understanding Comics, Scott McCloud discusses the idea of abstraction. He describes how in comics, you can abstract details in characters so as to allow the reader to bring his own imagination into the story. To illustrate this, I’m going to borrow an example from Scott’s book.

I’ve drawn three versions of myself in Figure 2.5 with differing levels of detail. At one end, the simple stick-figure rendition could be interpreted as not resembling me at all or possibly resembling anyone. The lack of detail makes it look like nobody and everybody. On the far right, the drawing is much more detailed and leaves little room for interpretation as to who is being represented.


<img src="" alt="">Figure 2.5: Varying details of Kevin.

By reducing the amount of detail in a drawing, you can encourage your reader to relate personally to what’s being presented. The more detailed and specific a drawing, the more concretely defined it is. You can draw a bridge that looks like a bridge, or you can make it very plainly the Golden Gate Bridge. When it’s just a bridge, the reader might associate a bridge they’re familiar with in their mind and thus create a more personal connection to your comic.

The lack of detail can be accomplished in the art by using fewer lines. But you can also remove details by being symbolic instead of literal. For example, you could use animals instead of people—like a talking rabbit or a hapless coyote.

When we watch cartoons like Bugs Bunny and Road Runner, we feel a certain connection to the characters. We laugh at the plight of Wile E. Coyote, but also sympathize with him. These characters are drawn simply and don’t try to photo-realistically portray rabbits and coyotes; we would have a lot of trouble connecting with that! In addition to being simplified drawings, though, they’re also abstracted by not being human characters. They’re not old or young, black or white. They are simply characters. For Road Runner and Wile E. Coyote, the characters are abstracted even further by having no voice. Without a voice, you can’t presume anything based on their accents.

The viewer isn’t consciously thinking, “I’m just like Wile E. Coyote. I can never seem to get things right,” or “Road Runner is just like my friend Peter!” Nevertheless, they’re likely to feel a deeper connection to the characters because subconsciously they can apply their own experiences to fill in the abstractions.

You don’t have to use the same level of detail across the whole comic, either. By varying the detail of various elements, you can call attention to particular aspects and help guide the reader’s imagination.

A common practice in manga is to draw a very detailed background with fairly simplistic characters. The effect is twofold. First, the characters pop out of the detailed background, creating an effective contrast that guides the reader’s focus to the characters. Second, the detailed background makes the setting very clear while the character remains abstract, allowing for better reader-to-character immersion, as shown in Figure 2.6. Scott McCloud eloquently calls this “one to see, one to be.”


<img src="" alt="">Figure 2.6: A detailed background leaves no room for interpretation, but the character stands out with its lack of detail.

The practice of reducing detail isn’t just restricted to the art. We can also be deliberately vague when conveying user interfaces or processes in our comics.

We learned this when we were creating our comics at Yahoo! Local. In one particular panel, we wanted to illustrate that our character, Dana, was searching through Yahoo! Local (see Figure 2.7). How the search was performed was unimportant; we simply wanted to convey how Dana got to the subsequent page.


<img src="" alt="">Figure 2.7: Yahoo! Local comic where Dana is searching for restaurants.

Because the search results page already existed, we thought it would be easier to use a screenshot. In hindsight, the outcome should have been quite predictable. Readers focused on the design and content of the search results page more than the story itself.

Once we discovered this problem, we reduced the level of detail so the reader saw only what was necessary to understand context. We included the site’s logo, a search box, and the location in large print. The fact that the screenshot wasn’t entirely accurate wasn’t an issue—just as the fact that a face is only a caricature wasn’t an issue.

Then we took the idea of simplification even further by removing the view of the screen entirely, as shown in Figure 2.8.


<img src="" alt="">Figure 2.8: Showing interface options without showing the screen.

In both of these versions, we can’t see the screen that the character is viewing, but we reveal just the right amount of interface to communicate the pertinent elements. In the second iteration, the interface elements are handdrawn, making the elements informal and even more concise. Keeping the interface within the same artistic style as the rest of the comic also made it less jarring for the reader.

Recognizing how much to abstract away requires some amount of experimentation and practice. For the moment, simply remember the power that abstraction in comics gives you.