Munich 1972: What Otl Aicher's Olympic Design Still Teaches Events
Pictograms, color and one design system that made the Games read as a single event. The wayfinding lesson every organizer should know.
Otl Aicher designed the Munich 1972 Olympics as one visual language, from the stadium to the staff uniform. This essay shows how his grid, his single typeface and his color code worked together. It ends with a one-page design manual and a sign test you can use at your own event.
Most event identities are a logo, a color and a template. The signs get made up on site in the last week. Otl Aicher designed Munich 1972 as something else. He built one visual language that ran from the stadium to the ticket to the staff uniform.
The Games read as a single place. That is still the wayfinding lesson for anyone who moves thousands of people through a venue.
A language, not a logo
The Munich Games are also remembered for the attack on the Israeli team. Eleven of its members were killed. That loss belongs first in any account of 1972. This essay is about the design, which was planned years earlier for a different hope.
A logo tells guests whose event it is. A language tells them where they are, where to go and who can help. Aicher designed the second.
Every sign, color and uniform followed the same rules. A visitor who learned the system at the station could use it in the stadium.
Otl Aicher's brief for Munich 1972
Aicher co-founded the Ulm School of Design in 1953. He was made lead designer for the Games in 1966.
The organizers wanted open, cheerful Games. They knew the world would read them against the memory of Berlin 1936. The Olympic Park by Behnisch & Partner, under Frei Otto's tensile roofs, shared that lightness.
The Olympic design had to carry the same message at every scale. That meant posters, tickets, maps, signs and clothing. It also had to work across a park, a city and many venues, for visitors who shared no common language.
Aicher's answer was to fix the rules first. Then every designer on the team worked inside them.
Grid, type and color
The Munich 1972 pictograms were drawn on a strict grid. Arms and legs ran only at right angles and at 45 degrees.
Smithsonian Magazine counts 166 of them. Most gave practical facts such as stairs, restrooms and transit. One typeface, Univers, ran through everything.
The colors came from the Bavarian countryside. They were light blue, green, silver and orange.
Red and gold were left out, because they were colors of power and of the 1936 Games. Staff uniforms were color-coded by department. Visitors could tell from a distance who did what.
The rules were written down in a manual, Guidelines and Standards for the Visual Design. It was finished in 1967. Niggli reissued it in facsimile in 2019. The manual came before the signs.
Precedents and legacy
Munich stands in a line. Tokyo 1964, under Masaru Katsumie and Yoshiro Yamashita, introduced Olympic sports pictograms. Mexico 1968, with Lance Wyman's identity, carried the Games' graphics into the city.
The Ulm school worked in the Bauhaus tradition. There, Herbert Bayer had already designed exhibitions around the visitor's field of vision.
After Munich, the US Department of Transportation made its own symbol set in 1974. Pictograms of this kind became standard in airports and stations around the world. A clear system works without words.
What organizers can use from Otl Aicher
Write the manual before production. Agree the typeface, colors, pictograms, sign types and sign positions before anything is printed. Use one typeface. Two weights cover every sign from the website to the wristband.
Make color mean something. Use it for zones, staff roles or access levels, never as decoration. A color that means nothing teaches guests to ignore color. Test it on site, because a color changes with the light and colors around it.
Dress staff in the color code. Munich's uniforms told visitors who did what. At a conference, give each role one color on shirts and lanyards. Then a lost guest can find the right person from across a foyer.
Use pictograms that work without language. International guests and guests with access needs read a clear symbol faster than a sentence. Stay consistent, so the restroom sign follows the same rules as the keynote screen.
Event wayfinding starts with the plan, not the sign. Signs confirm a plan that is easy to read. They cannot rescue one that is not.
Kevin Lynch showed why guests get lost when paths, edges and landmarks are unclear. No amount of signage fixes a plan that hides its own exits.
A one-page event design manual
- Typeface. Rule to write down: One family, at most two weights, a minimum size per viewing distance. Example: One sans serif for every sign and screen.
- Color code. Rule to write down: One meaning per color, listed. Example: Blue for registration, green for sessions.
- Pictogram set. Rule to write down: One grid, one line weight, tested without words. Example: Restrooms, exits, cloakroom, first aid, food.
- Sign types. Rule to write down: Directional, identification, information, regulatory. Example: An arrow at a junction; a room name at a door.
- Sign positions. Rule to write down: Where each type goes and at what height. Example: A directional sign at every decision point.
- Materials. Rule to write down: Approved substrates and print methods. Example: Fabric for reuse, rigid board for doors.
- Approval. Rule to write down: Who signs off and by when. Example: Design lead, then production manager.
Test the signs before you print
- Mark every sign on the plan at each decision point. That means entrances, junctions, stairs, elevators and doors.
- Walk the route from arrival to every destination with someone who does not read the event's language.
- Note every point where they stop, turn back or ask.
- Fix the plan first, then the sign.
- Walk it again.
Rules first, signs second
Write the manual before you design a single sign. If a stranger could extend it without asking you, the system is strict enough.
Aicher's lesson is that a sign can only confirm a plan that already reads well. Monet starts from the plan, drawing to-scale layouts on the real venue and re-checking exits and crowd flow after every change, so the routes are clear before the first sign is printed.