A Pattern Language for Events

Christopher Alexander described the patterns of good places. Twelve of them, applied to events.

Christopher Alexander's A Pattern Language records good answers to problems that keep coming back in buildings and towns. This essay picks twelve of its 253 patterns that fit events, from the entrance to the lighting. It ends with a twelve-question checklist to run over any event floor plan.

Event layouts are drawn from scratch or from last year's file. The same problems return each time. There is the empty foyer, the dead corner and the meeting no one can hear.

Christopher Alexander and his colleagues wrote A Pattern Language for problems that repeat. Twelve of its 253 patterns carry straight into events. Together they make a checklist for any event layout.

Problems that repeat

The venue changes every year. The problems do not.

Guests cluster at the door and leave the far end of the room empty. A networking area sits beside the loudspeakers. The breakout room is a corridor with chairs.

These are not failures of talent. They are known problems, solved again from nothing. A pattern language suits events because it records a solution once. The next designer can then adapt it.

What a pattern is in A Pattern Language

A Pattern Language came out from Oxford University Press in New York in 1977, subtitled Towns, Buildings, Construction. Its authors were Christopher Alexander, Sara Ishikawa and Murray Silverstein, with Max Jacobson, Ingrid Fiksdahl-King and Shlomo Angel. They worked at the Center for Environmental Structure.

The book holds 253 patterns, from regions and towns down to building details. Each one states a problem, the reasoning behind it and a solution. Each one also links to larger and smaller patterns.

The solution is a core to adapt, never a drawing to copy. The book later shaped software design too, but its home is the built world.

Arriving

53 Main Gateways. Mark the threshold so guests know they have arrived. At an event, that means one clear entrance, not three doors of equal weight.

112 Entrance Transition. Give guests a change between the street and the event. It can be a change of light, of level or of view. A short lobby with lower light does more than a banner.

149 Reception Welcomes You. Make the first thing guests meet a welcome, not a queue. Move registration back from the door. Put a person, not a desk, at the threshold.

Moving and gathering

120 Paths and Goals. Give every path a goal guests can see, such as the bar, the stage or a lit wall. People walk toward what they can see.

123 Pedestrian Density. Size public areas to the crowd. For a lively square, Alexander proposes 150 to 300 square feet per person. Do not copy that figure. Test any figure against the venue's licensed capacity, since indoor events run at very different densities.

124 Activity Pockets. Line open spaces with small, partly closed pockets at the edges. People then have somewhere to settle without leaving the action.

126 Something Roughly in the Middle. Give a large space a focus. It need not be a stage. A bar, a sculpture or a lit installation works too. Without one, a foyer feels empty at any density.

Talking

127 Intimacy Gradient. Arrange spaces from public to private. Start with the foyer, then the session rooms, then the meeting rooms. Guests should never cross a private space to reach a public one.

151 Small Meeting Rooms. Provide small rooms for real conversations. Big rooms suit announcements. Small rooms suit talk.

185 Sitting Circle. Where people must talk, set seats in rough circles away from passing traffic, not in rows.

251 Different Chairs. Mix chair types. People choose the seat that suits their body and their conversation. A mix tells them the space is for staying. William Whyte found the same wish for choice in movable chairs, as the social life of event spaces sets out.

Pools of Light

Pattern 252 overturns the usual lighting brief. Uniform illumination is "the sweetheart of the lighting engineers," Alexander's problem statement says. Yet it "serves no useful purpose whatsoever," he wrote. He argued that it destroys the social nature of a space.

His answer is to place the lights low and apart. Each pool of light should then "encompass chairs and tables like bubbles," as he put it. In his view, this makes the social character of each space stronger.

At a reception, a lounge or a dinner, light the groups, not the room. Low pendants or table lamps over each cluster give guests a place to stand together. Light also changes how colors look, as Josef Albers showed.

A pattern language checklist for events

• 53. Pattern: Main Gateways. Event problem: Guests unsure where the event starts. Question for the plan: Is there one clear entrance?
• 112. Pattern: Entrance Transition. Event problem: Street noise and light run into the room. Question for the plan: What changes between street and event?
• 149. Pattern: Reception Welcomes You. Event problem: The first thing met is a queue. Question for the plan: Who greets guests at the threshold?
• 120. Pattern: Paths and Goals. Event problem: Aimless circulation. Question for the plan: Does every path end at something visible?
• 123. Pattern: Pedestrian Density. Event problem: A foyer too big or too small for the crowd. Question for the plan: Is the area sized to the crowd and the licensed capacity?
• 124. Pattern: Activity Pockets. Event problem: Open floor with nowhere to settle. Question for the plan: Are there partly enclosed pockets at the edges?
• 126. Pattern: Something Roughly in the Middle. Event problem: A space with no focus. Question for the plan: What sits roughly in the middle?
• 127. Pattern: Intimacy Gradient. Event problem: Private meetings in public paths. Question for the plan: Do spaces run from public to private?
• 151. Pattern: Small Meeting Rooms. Event problem: Nowhere to talk in confidence. Question for the plan: Where do small groups meet?
• 185. Pattern: Sitting Circle. Event problem: Rows where people need to talk. Question for the plan: Are conversation seats in rough circles?
• 251. Pattern: Different Chairs. Event problem: One chair type everywhere. Question for the plan: Is there a mix of seats?
• 252. Pattern: Pools of Light. Event problem: Flat, uniform lighting. Question for the plan: Are the groups lit, not the room?

Run the twelve questions over a to-scale event floor plan. For a conference, start the density question from space planning for conferences.

Your own language

Patterns form a language because they combine. Keep the ones that work, and add your own. Choosing them stays the designer's job.

Alexander's patterns only prove themselves on a real plan at real size. Monet makes to-scale layouts from a venue plan and a brief, then re-runs crowd-flow, noise and spatial-occupancy checks after every change, so you can test each pattern in the room before the event.