Design the Conditions, Don't Deliver the Content

You design the conditions, you don't deliver the content This is the sentence I keep coming back to. It's the closest thing I have to a professional creed, and I've arrived at it from so many directions that I can't tell anymore which one was first. In the ICU, the principle looks like this: you don't heal the patient. You create the conditions under which healing can occur. You manage the environment — temperature, medication, monitoring, positioning, hygiene, timing. You observe continuously and intervene precisely. But the recovery is the body's work, not yours. The best nurse is the one whose patients improve without being able to point to a single dramatic moment of intervention. The drama is a failure of conditions. The absence of drama means the conditions are right. I didn't understand this as a design principle at the time. I understood it as nursing. But the structure is identical to everything I've done since. At URW, the shopping centers I helped design were conditions. Not destinations — conditions. The spatial arrangement, the sightlines, the furniture placement, the lighting, the transition between zones. All of it was designed to produce a particular kind of behavior: lingering, browsing, discovering, spending. But the behavior itself belonged to the visitor. The best spatial design is the design that people don't notice — they just find themselves doing what the space was shaped to support. When someone sits down, it should feel like their choice. The bench's position made it inevitable, but the experience is freedom. At Grau, the feedback infrastructure I built was conditions. The journey maps, the reporting structures, the communication channels, the training programs — none of these delivered customer satisfaction directly. They created the conditions under which the organization could hear its customers, respond appropriately, and improve continuously. The NPS moved from 58 to 82 not because I improved customer satisfaction. I built the system that enabled the people who actually talk to customers to do their work better. The improvement was theirs. The conditions were mine. In facilitation — which has become central to my practice — the principle is at its most explicit. A good facilitator does not deliver insight. A good facilitator designs a process, arranges a room, sequences a set of activities, manages energy and time and group dynamics — and then gets out of the way. The insight comes from the participants. The decision comes from the team. The alignment comes from the conversation. All the facilitator provides is the container. And the quality of the container determines the quality of what happens inside it. I've watched facilitators who don't understand this. They prepare brilliant exercises, deliver sharp provocations, guide the room toward the conclusion they arrived at before anyone else entered. The workshop looks successful. The energy is high. The post-its are organized. And three weeks later, nothing has changed — because the room didn't own the outcome. The facilitator delivered it. And delivered outcomes don't stick. Only discovered outcomes stick. This is also why I cook the way I cook. The meal is the conditions. The evening is the content. I can control the ingredients, the timing, the sequence, the spatial arrangement of the table. I cannot control — and should not try to control — what people talk about, how long they stay, what they remember afterward. The evening that surprises me is the evening I designed well. The evening that goes exactly as planned is the evening where I held on too tightly. Hassenzahl taught me the theoretical foundation for this: experience cannot be designed directly. You can only design for experience. The product, the service, the environment, the workshop — these are all conditions. The experience is what happens when a person encounters those conditions, and it's shaped by everything they bring with them: their mood, their history, their expectations, their attention. The designer's job is to create conditions robust enough to support a range of experiences and precise enough to make certain experiences more likely than others. But the experience itself is always co-created. Always. This principle resolves what looks like a contradiction in my career. How can someone be simultaneously a systems thinker and a human-centered designer? How can you care about infrastructure and still care about the individual experience? The answer is that infrastructure is care. The feedback system that surfaces a dealer's frustration to leadership is an act of care — for the dealer, for the organization, for the relationship between them. The workshop structure that gives every voice in the room equal weight is an act of care — for the participants, for the quality of the decision, for the organization's future. Designing conditions is not cold. It's the warmest thing I know how to do. It just doesn't look warm from the outside because the craft is invisible when it's working. The systems I'm proudest of are the ones where my contribution is hardest to see. The Grau infrastructure that runs without me. The workshop where participants say "we figured this out" without registering that the process was designed to help them figure it out. The dinner where friends remember the conversation, not the food. In each case, the conditions did their work and then disappeared. This is the standard I hold myself to: design the conditions so well that the people inside them experience freedom. Not control. Not guidance. Not the gentle hand of a well-meaning facilitator steering them toward the right answer. Freedom — the genuine experience of arriving at their own insight, in their own time, through their own effort. The fact that the conditions made that arrival more likely is the designer's knowledge. It doesn't need to be the participant's. The ICU nurse creates the conditions for healing and the patient heals. The spatial designer creates the conditions for gathering and people gather. The CX infrastructure builder creates the conditions for organizational learning and the organization learns. The facilitator creates the conditions for insight and the room discovers something. You design the conditions. You don't deliver the content. The content was always theirs.