FIELD NOTES / STUDIO PERSPECTIVE

The Experience of Being Designed For

4 November 2026

Kellie Patry

Why the process of design deserves as much intention as the spaces we create

At KPHD, we want to create places that amaze and lift the spirit.

That ambition is about more than appearance. It is about what happens when someone enters a room, how the room changes their mood, what they notice, what they remember, and whether the experience feels unexpectedly right.

A successful hospitality space must also work. Staff need to move naturally. Service needs to flow. The physical environment needs to support the business without sacrificing the character that makes it worth visiting.

There is a tension between the practical and the emotional, and much of our design work takes place within it.

Recently, I have been thinking about another experience that deserves the same attention: what it feels like to be the client while that space is being designed.

Black-and-white photograph of a round table and chairs in sunlight at Equator Coffees in Culver City, seen through glass.

Equator Coffees, Culver City. Photograph by Antonio Diaz, 2024. Project gallery.

The finished environment is the visible result of design judgments, operational needs, and coordination.

The experience before the experience

For a restaurant or café operator, commissioning a new space can be one of the most consequential undertakings in the life of the business.

There are ambitions, uncertainties, competing priorities, and significant financial decisions. There are also dozens of people and processes that may be unfamiliar to someone whose expertise lies in hospitality rather than construction.

The work changes as it develops.

An initial idea becomes a space plan. A space plan changes when equipment is coordinated. A material selection affects detailing, availability, and cost. A drawing that made sense during design may need reconsideration when an existing condition is uncovered on site.

None of this is unusual. It is the nature of designing something that will eventually be built and occupied.

But what does the client experience?

Do they understand why a decision changed? Can they recognize which choices need their involvement? Is the information arriving at the moment when it becomes useful?

Or are they expected to reconstruct the history of their own project from meetings, drawings, email threads, and conversations?

We have been examining these questions as part of how our studio works.

Clarity is part of the design

A client should not need to understand every technical complexity of a project to participate meaningfully in its development.

That does not mean withholding information. It means designing how information is encountered.

The distinction is important.

There are things we need a client to decide. There are things they need to understand but do not need to resolve themselves. And there are technical details that must be preserved and available without dominating every conversation.

We have begun thinking about communication in those three layers.

The first makes participation possible. The second builds understanding and confidence. The third maintains the professional record.

This is an information-design problem, but it is also a relationship problem.

A good presentation should clarify the argument behind a design, not simply demonstrate how much work has been produced. A useful project update should explain what has changed and what happens next, rather than reproduce the complexity of the studio’s internal operations.

When we ask a client to make a decision, we should make that decision as understandable as the circumstances allow.

What a project remembers

In another working paper, What your project record is not telling you, I examined the information systems behind a small design practice.

One finding was revealing: the practice could record the status of its projects far more easily than it could explain the relationships between the decisions that shaped them.

A design decision might exist in a meeting transcript. Its consequences might appear months later in a revised drawing. The reason for the revision might survive in someone’s memory, but not in the relationship between those records.

We began experimenting with a connected project record—a graph that links projects, phases, decisions, people, and supporting evidence.

The intention was not to create more administrative work. It was to make the information we already produce more useful.

We are now extending that thinking to the client experience.

Imagine a client asking why the service counter has changed since schematic design.

The useful answer is not merely that the latest drawing shows a different arrangement.

The useful answer connects the original intention, the operational constraint that emerged, the alternatives considered, the decision that followed, and the effect on the rest of the project.

Ideally, that explanation should not depend on which person happens to remember the conversation.

That is the kind of continuity we are trying to build.

Technology in service of judgment

We use connected records and AI-assisted tools to explore how a small studio might preserve more of this reasoning without requiring a large administrative team.

But there is an important boundary.

A recorded meeting does not necessarily mean a client agreed to something. An email sent is not the same as an email understood. A drawing issued is not automatically a drawing accepted.

Our systems need to preserve these distinctions.

We are building connections between existing project records and a map of the client journey, from early discovery through design, documentation, construction, and the period after opening.

Some of those connections are already useful internally. Others require better evidence, clearer attribution, and testing through actual client relationships.

We do not yet know how much this will improve the client experience. That is what future work must establish.

What we do know is that better technology cannot replace professional responsibility, design judgment, or the trust established through conversation.

It should support them.

Two experiences, one intention

There are two experiences we are designing simultaneously.

The first belongs to the people who will eventually enter the space: the guest who encounters something unexpected, the employee whose work feels more natural, and the operator who sees the character of the business made physical.

The second belongs to the people bringing that space into existence.

They are navigating uncertainty, making choices, committing resources, and trusting us to carry an idea through a process they may only experience once.

We want the finished place to amaze and lift the spirit.

Perhaps the process of arriving there should offer something of that same feeling—not through spectacle, but through understanding, confidence, discovery, and the pleasure of seeing a good idea become real.

That is a design challenge in its own right.

And it suggests a useful measure for the systems we are building:

If a better project record does not ultimately create a better human experience, we have only made the administration more sophisticated.

This is an evolving practice study, not a claim of demonstrated improvement. KPHD is developing and testing the connections between its project records, design decisions, and client journey. The aim is to make the process more coherent and understandable while preserving the evidence and professional judgment behind the work.

Sources & editorial note

The ideas are mine — lived, read, and noticed first. AI writing assistance helps me get them onto the page. — Kellie Patry