Design as communication and evidence

Start with a communication problem

Graphic design organizes visible information so a particular audience can understand or do something. A beautiful poster that hides its event date is unsuccessful communication. Begin every task by writing the audience, the situation, the required message, and the intended action. These four items become a brief against which you can evaluate choices. Personal taste still matters, but it is one input rather than the only test.

Distinguish a business objective from a design objective. A training center may want more enrollments; its poster can help people identify the course, understand eligibility, and find registration instructions. The poster cannot guarantee enrollment because price, timing, trust, and teaching quality also influence that result. Describe the contribution you can plausibly test: readers should locate the start date within a short viewing period and understand the registration route without asking the designer.

How people notice information

Visual attention is selective. Strong differences in size, weight, position, shape, and contrast attract attention. Similar-looking elements are often understood as belonging together. Closely spaced labels and values appear related. An isolated element may become a focal point. These tendencies are useful, but their effect depends on context, reading direction, familiarity, and the task. They are design hypotheses, not guaranteed rules about every person.

Build hierarchy by deciding an order of importance before choosing fonts or colors. A simple three-level hierarchy has a primary message, supporting information, and practical details. Repetition establishes a pattern; a deliberate interruption can highlight an exception. If every element interrupts the pattern, nothing feels exceptional. White space is active structure because it distinguishes groups and gives important information room to be noticed.

Worked example: a community workshop

Imagine an A4 notice for a fictional bicycle-repair workshop. The initial copy is: Saturday 18 October, Mtoni Community Hall, bring a bicycle, practical beginner workshop, 09:00–12:00, registration at the reception desk, maximum twelve participants. First identify the reader's question: what is this and can I attend? Use “Repair your bicycle” as the primary message, “Beginner workshop” as its supporting description, and group date, time, and place together.

A first draft might use a large headline at the top, a bicycle illustration in the center, and tiny event details at the bottom. The image has taken space from essential information. A revised draft keeps a modest illustration, enlarges the date and place, and places “Register at reception” near the information that makes the action meaningful. The design now expresses a sequence: recognize, evaluate, act.

Do not invent a testimonial or claim that attendance improves income. The example has only the facts supplied. When information is missing, record a question for the organizer rather than silently filling the gap. Content accuracy is a design responsibility because wrong information can be perfectly typeset.

Studio exercise

1. Choose a fictional event and write a brief containing audience, setting, message, and action.
2. Write all required copy as plain text. Rank each item as primary, supporting, or practical.
3. Make three small black-and-white sketches. Change grouping and emphasis, not merely decoration.
4. Show each sketch for five seconds to a consenting peer. Ask what they remember and what they would do next.
5. Record their actual words, select a direction, and explain one revision using evidence.

Expected outcome and self-check

Your deliverable is a one-page brief, three sketches, and a short decision record. If a viewer remembers the illustration but cannot identify the event, the hierarchy needs revision. If the action is registration but the design only says “Learn more,” the instruction is underspecified. A strong answer identifies both what the design communicates and what remains unknown.

Common mistake

Beginners often open software immediately and judge the first attractive arrangement as finished. Separate the problem definition, exploration, and evaluation stages. This makes revision less personal: you are improving a communication system, not defending a favorite arrangement. Keep rejected sketches because they reveal which assumptions changed and provide useful evidence in a later portfolio.