Design & Florals
David Beahm: Collaboration Is Part of the Design
David Beahm's real subject is collaboration, and it isn't polite agreement. It's everyone naming the constraint they know best before it gets expensive.
David Beahm is known for transformative event environments and inventive floral work, but the part of his process I find most useful is the collaboration underneath it.
His studio describes bringing together craftspeople across disciplines to build events specific to the host. Major industry profiles make the same point repeatedly: the client isn’t a blank check for a designer signature, and the creative team isn’t a row of unrelated vendors waiting around for instructions.
Collaboration is not a courtesy meeting
That matches how I think about events generally: they are one knot of connected decisions, and pulling on any strand moves the others. A floral decision can affect lighting. A stage can change sightlines. A caterer can need the exact corridor a scenic team already planned to fill with branches. The sooner those facts meet each other, the better the design gets.
Good collaboration isn’t everyone politely agreeing. It’s everyone exposing the constraint they actually know best before that constraint gets expensive.
A florist knows when a material will wilt. A lighting designer knows when a palette will die under the chosen fixtures. A rental team knows what won’t fit through the door. Those are design facts, not obstacles to design.
The client still needs to stay visible in all of it
Beahm’s emphasis on client expression matters just as much. Collaboration can produce generic polish fast, once a team gets more interested in demonstrating its own competence than understanding the actual event.
The host’s priorities have to keep acting as the filter. Which emotional moment matters most? What should guests understand without being told? Where is spectacle genuinely welcome, and where would it feel false?
Make collaboration visible in the plan
Bring the key disciplines into the concept earlier. Don’t finish the visual plan and then ask production whether reality is willing to cooperate. Let the constraints improve the idea while there’s still time to actually enjoy them.
See the work: David Beahm Experiences
Read more: Harper’s Bazaar’s profile of leading event designers
Meet the 20 designers shaping this field guide · Beyond the Centerpiece · Why Production Is Part of Event Design
Atmosphere OS · Theme Atelier
A palette is not yet a decision.
Atmosphere OS holds the color, the material, the light and the room in one object, so moving any of them shows you what it does to the rest. Costs come back as indicative bands and never as quotes, which is the difference between planning and pretending.
Free to use, local-first in your browser, and there is no account until you ask for one.
Field notes and corrections
When a number here turns out to be wrong, you hear about it.
Three things arrive and nothing else. The new field note — bar rates, cover widths, service clearances, the arithmetic worked through on one real evening. A line when a World opens, because a night only goes up once it can actually be thrown. And a correction whenever a rule in the published rulebook changes, or a number the tools rely on turns out to have been wrong. There is no weekly slot, because there is nothing weekly to put in it.
One email per field note or opening, plus corrections when a published figure moves. Unsubscribe from any of them.
Continue through the system
Pretty is still not a plan.
A party gets planned in roughly this order. Pick the chapter where your next problem lives.
What you have to decide next
One decision constrains the next. This is the order they actually happen in.
More in this chapter
See the complete five-chapter Event Design Intelligence map →