Clients often arrive with what sounds like a solution. Move a wall. Add a room. Expand a garage. Build it here. These ideas are valuable starting points, but they don’t always reveal the deeper problem that needs to be solved.
Good architecture begins with listening, but it doesn’t end there. Through dialogue and careful questioning, architects begin to understand what a client’s request may really be responding to.
The real work begins when we start questioning the answers.
In this edition of Real Chats with AI, MODE4 founder and design principal Chris Tucker reflects on how listening, dialogue, and thoughtful questioning help architects explore what a client’s request is really pointing toward, and how those discoveries ultimately shape stronger architecture.
Q1
AI:
In your experience, what’s the difference between hearing a client’s request and truly understanding what they are asking for?
CT:
The difference begins with patience.
When I first meet with a client, I’m primarily listening. I’m not sketching yet. In fact, I’m usually not writing much down either. I’m trying to hear their story first. What brought them to this design table, how they came to own the property, and what they hope will change in their lives through the project.
Clients will often arrive with what sounds like a solution. They may suggest moving walls, building an addition, or converting a space to another use. When that happens, it’s usually a signal for me to pause and dig a little deeper; to better understand what it is they’re trying to solve.
Often what they’re presenting is a solution to a problem that hasn’t yet been fully articulated.
So, I start by listening and letting the conversation unfold. As the dialogue develops, I begin pulling out key phrases and observations. Sometimes repeating them back to the client to make sure I’ve understood correctly, and making quick notes.
I almost never begin sketching a design solution during that initial conversation. If I draw anything at all, it’s usually a quick diagram to clarify something the client has described; a visual way to confirm that we’re talking about the same idea.
The goal at that stage isn’t to design. The goal is to understand.
I’m trying to understand the client’s narrative. Where they grew up, how they came to the property, what they love about the site, their daily routines and hobbies, and the hinge points in their lives that are driving change.
Understanding that story allows me to see the project through a clear lens. From there, I can begin asking better questions and start to parse out the reasoning behind their requests.
Q2
AI:
Can you recall a time when a client initially asked for one thing, but deeper listening revealed a different problem that needed to be solved?
CT:
Yes. And interestingly, because we remained committed to the process, the situation eventually led to a national award-winning project.
The clients initially approached us with what seemed like a straightforward request: convert an existing garage into a dining room and construct a new garage with a possible art studio above.
The challenge was that their house was already a well-known, award-winning home. Adding to it required a thoughtful approach, because any new work had to respect and complement the architecture that was already there.
We went through several iterations. Beautiful ideas. Thoughtful models. And a number of promising design directions.
But something about the project still felt unresolved.
Through many conversations with the clients, the real issue slowly began to surface.
The problem wasn’t the garage.
The real challenge was arrival: how someone approached the house and moved from the driveway or upper parking area to the front door. The entry sequence was difficult to read, and the front door itself wasn’t clearly expressed.
Once that became obvious, the entire project shifted direction.
The design moved away from simply replacing a garage and toward reorganizing the arrival sequence and strengthening the experience of entering the home.
The solution ultimately created a sequence of spaces: wooden terraces leading from the upper parking area down to a bridge spanning a newly designed Japanese-inspired garden and arriving at the front door.
That moment of discovery changed everything.
Q3
AI:
How do you train yourself and your team to truly listen during design meetings, especially when ideas and solutions are being discussed?
CT:
Ironically, truly hearing what clients are saying begins with hearing my own thoughts.
To understand the direction of a conversation, I have to be present enough to notice when something isn’t fully clear. Sometimes that awareness shows up as a simple thought: I’m not sure I fully understand what they mean. Other times it’s more subtle: a hesitation in the room, a pause in the conversation, or a sense that something has been left unsaid.
That awareness requires mindfulness.
I encourage my team to approach meetings the same way. It’s a form of empathic listening; being fully present with the client and sensing where the conversation actually needs to go. Part of that also means leaving your ego at the door. I often remind younger designers that a sketch or concept is simply a communication tool. It helps move the discussion forward. If a client dismisses an idea, that isn’t failure. It’s progress. It means we’re one step closer to discovering the right solution.
Great design rarely starts with a preformed idea.
It emerges through listening.
The second part of this is what we call Outreaching at MODE4.
Outreaching requires courage as a conversationalist. It means leaning into difficult questions when necessary - questions about budget, priorities, usability, or even vanity. Sometimes a client’s request is driven by practical needs. Other times it reflects identity, pride, or celebration. Homes often carry those emotional layers.
When we sense that something deeper is shaping the conversation, it’s our responsibility to explore it - gently, and with respect.
Brené Brown often says, “Clear is kind; unclear is unkind.”
I believe that applies directly to the design process.
When uncertainty appears in a discussion, the most respectful thing we can do is help bring clarity to the conversation.
That’s really the purpose of these design meetings.
Clarity in direction.
Clarity in the solution.
Because once that clarity emerges, we can begin the design process with confidence - starting with the first diagrams that move the project forward.
Q4
AI:
Once that clarity emerges, how does it begin to shape the design process itself? When do you start translating those insights into diagrams or early design ideas?
CT:
Once we leave the meeting and review our notes, the translation begins.
We look carefully at the conversation and begin separating what we heard into categories: the client’s needs, their desires, and their priorities - what is essential, what would be nice to have, and what might fall into the category of dream items. At the same time we’re working to understand the realities of the project, particularly the program and the budget, because those factors will shape every decision that follows. All of these considerations begin influencing the first diagrams.
This leads into a concept that is central to my own design process. I often describe it as designing to the ideal.
We begin by asking a simple question: What does the site want to be?
And similarly: What does the program want to be?
We explore that condition in its most ideal form before filtering it through the specific constraints of the project. Gradually we introduce the realities: the program, the budget, and the client’s personal priorities. The elements that remain after that filtering process become the foundation of the design.
In other words, we explore the ideal first and then guide the design back toward the specific and personal needs of the client.
This idea has always reminded me of a book I read in graduate school, The Sacred and the Profane by Mircea Eliade. Eliade explores how people understand space through deeper layers of meaning and orientation. Our process isn’t exactly the same, but the idea of beginning with something universal before translating it into the lived and personal world has always resonated with me.
When we move from the meeting table to the design table - whether that’s a sketchbook, bumwad, or a computer screen - we’re translating conversation into visual thinking. Words begin to take shape as diagrams, sketches, and early study models.
Those drawings aren’t final solutions. They’re part of the ongoing conversation we bring back to the client as the project continues to evolve.
Q5
AI:
In your experience, what happens when the real problem behind a client’s request finally becomes clear? How does that moment change the direction of the project?
CT:
There is often a moment when the ideas crystallize, and the true problem becomes clear.
When that happens, the project suddenly becomes unstuck. Momentum returns, and we finally have something to work toward.
That moment rarely comes from a single conversation. It’s usually the result of many discussions, layers of thinking, and iterations - quite literally, layers of trace upon trace.
Eventually there is a moment when everyone involved sits back and realizes that something special has emerged. The problem has been solved, and the design direction feels both clear and inevitable. More importantly, the solution reflects not only the architecture, but the client.
I’ve always believed there is no great architecture without a great client.
Clients should choose an architect whose personality and communication style align with their own. That relationship matters, because the design process often unfolds over several years. When the partnership works well, the result is more than a successful project. It often leads to a lasting professional relationship - sometimes an architect becoming that client’s architect for life.
As a counterpoint, we’ve recently been exploring a small side effort where we act more as a developer, designing speculative homes ourselves.
And I’ll admit - it’s more difficult than I expected.
Because suddenly I’m the one trying to imagine the role of the client - their priorities, their decisions, their voice in the process.
It’s a good reminder of something important:
The client’s narrative is a critical part of the design process.
Without that voice, the work feels very different.
CLOSING NOTE
The design process rarely unfolds in a straight line. It develops through conversation, reflection, and discovery.
Clients bring ideas, goals, and instincts about how their homes should evolve. Through dialogue and careful listening, architects help interpret those ideas and translate them into spaces that respond not only to the site, but to the people who will live there.
At MODE4, this process is guided by the firm’s core values of mindfulness, outreach, design-driven thinking, and enthusiasm for architecture. When architect and client engage openly in that dialogue, the work moves beyond simply solving problems and begins to shape something more meaningful.
Because in the end, architecture is not just the result of design decisions.
It is the result of a shared conversation.
