The Functional Art Summary: Design Graphics People Can Use

Key Ideas

1. Define the tool’s job before selecting its shape

Cairo’s author interview describes function as a constraint on possible visual forms. The practical implication is that a familiar template should not decide what readers are allowed to learn. Begin with a task expressed as an action: compare, locate, trace or inspect. Two displays of the same dataset may be appropriate for different actions, so disagreement about layout can conceal disagreement about purpose.

In the library case, the communications officer first writes three reader questions. Which branches offer access after work? Which open on Sunday? How does my nearest branch compare with alternatives? A map may help with location, while an aligned weekly schedule may make evening availability easier to inspect. One oversized total cannot carry all three jobs. The team chooses a small location reference beside a schedule, with the branch names shared between them.

Apply this by asking a colleague to complete the sentence: someone will use this graphic to decide or understand what? Then name the operation the graphic must support. Sketch two plausible forms before opening a design application. Compare how readily each one answers the question, including what it makes difficult to see.

This matters because a visually impressive display can still obstruct the audience’s actual work. Keep the task narrow enough to evaluate. A communication does not have to answer every possible question, but it should support the questions it invites. Record the intended use beside the draft so later styling decisions remain connected to it.

2. Make the important comparison visible and interpretable

Cairo’s focus on perception encourages designers to consider the effort a reader must make. A comparison that requires someone to remember several disconnected values is different from one that can be inspected together. In this guide’s application, the design team treats that effort as a question to investigate rather than assuming that visual novelty creates clarity.

The library’s first draft gives each branch a differently sized illustrated building. Residents have to estimate the relative shapes and then consult a legend for opening hours. The revised schedule puts the same days and times in aligned positions for every branch. Labels explain whether an interval represents staffed access or another kind of availability. A small note distinguishes a recurring schedule from temporary holiday exceptions.

The change is useful because the reader no longer has to infer whether differently sized pictures encode floor space, opening time or importance. The schedule still needs context: a closed interval says nothing by itself about demand, staffing resources or the quality of service. Clearer comparison is not permission to claim an explanation that the data do not provide.

Try identifying the one relationship your reader most needs to inspect. Put its elements near one another, use consistent units and label them directly where practical. Ask someone to show the comparison with a finger and explain what it means. If they cannot, investigate the structure before adding another color. Also ask what conclusion the display cannot support. That second question protects a useful comparison from becoming an exaggerated claim.

3. Offer a clear entry point while retaining meaningful depth

In the book’s discussion of depth, Cairo resists equating clear communication with removing all complexity. The reader needs access to the subject, but may also need enough detail to examine it. A simple-looking page can conceal an important distinction; a detailed page can remain usable when its information has a sensible structure.

The library team initially plans to publish a single citywide average. That average would be easy to repeat, yet it would not tell a resident whether a particular visit is possible. The revised report begins with a short explanation of what the schedule shows, then provides branch-level information. It defines the reporting week and identifies seasonal exceptions in a separate note. Readers who only need the overall subject can stop early; readers planning a visit can continue.

This is an editorial choice about useful depth, not an instruction to add every available field. Staff names, historic renovation costs and unrelated usage figures would distract from the access question. Missing data should remain identifiable rather than silently becoming zeros. A branch with unconfirmed hours should not look like one confirmed closed.

For your own draft, list what a hurried reader needs first and what a more interested reader needs next. Preserve detail that can change an interpretation or practical action. Move unrelated material elsewhere. This matters because a concise statement is useful only when its omissions do not distort the task. Judge clarity by the route into the information, not solely by the number of marks left on the page.

4. Balance guidance with the reader’s freedom to explore

Cairo’s layering discussion describes an entry level followed by logically organized detail. The communication challenge is to guide attention without making the designer’s preferred conclusion the only available reading. Exploration can happen on paper as well as through an interactive interface. It depends on what comparisons the information permits.

For the library report, the opening sentence identifies the topic as access across a typical week. Residents can then scan all branches or follow their own branch through the schedule. If an interactive version permits filtering by evening or weekend access, its default view remains clear and a reset control restores the full comparison. A printable version retains the main schedule rather than hiding essential detail inside hover behavior.

These choices make the report more useful to people with different purposes. A parent looking for Saturday hours and a shift worker looking for late access can inspect the same underlying information. Neither needs to accept a communications team’s claim that the overall pattern is convenient. The display supports those judgments without pretending that every resident has the same needs.

Apply this by asking what a reader can do after noticing the headline. Can they find a relevant case, compare it with another and return to the overview? Keep controls, ordering and labels consistent across those actions. If exploration is not appropriate for a small announcement, provide a direct route to the fuller source. The aim is a usable balance between an understandable introduction and a meaningful opportunity to inspect further.

5. Treat appearance as part of a testable communication

The publisher describes design elements such as color and typography as resources for effective graphics. In this guide’s application, the test is whether those elements help a person perform the intended task. The choice is not between an attractive page and an informative one. It is between decisions that support use and decisions whose contribution remains unclear.

The library team uses one restrained emphasis for evening hours and keeps branch names easy to scan. It also checks a monochrome printout, because residents may receive a photocopied schedule. Important distinctions have labels as well as color. Before publication, two people unfamiliar with the draft try to plan specific visits. The team watches where they hesitate rather than first asking whether they like the design.

That session can reveal a confusing legend, an ambiguous date or an unreadable footnote. It cannot validate the library’s data collection or prove that every resident will understand the report. The team must separately confirm the source schedule and the process for correcting changes. A useful graphic remains dependent on accurate and maintained information.

Choose a realistic question, let a reader attempt it without coaching and ask them to explain the answer. Record the point where they had to guess. Revise that point and try again with another task. This matters because design intent is not the same as reader experience. A small, observed difficulty offers a more specific revision target than broad feedback that the page feels busy or needs more impact.