Featured on this episode:

• Join The Designers Edge waitlist here
• Grab Your Free Script Guide here
• Access the full video interview with Elana Steele of Steele Appliance here

What you will learn from this episode:

• Why the best projects happen when both perspectives are fully respected
• The biggest mistakes designers make in architect relationships
• Why role clarity early on prevents friction, fee issues, and project delays

---

There’s a misconception in this industry that quietly creates a lot of unnecessary friction.

That one professional is somehow “leading” the project while the other supports it. And in my experience, that’s not how the best projects work.

Interior designers and architects are equal collaborators. Different expertise, different scope, but equal value to the outcome of the project.

Now, depending on how the team was assembled, the practical dynamic may look different. Sometimes the architect brings the designer in. Sometimes the designer assembles the team. Sometimes the client hires both independently.

Those distinctions matter operationally.

But what matters even more is understanding which room you’re in before the project starts—and then showing up clearly inside your role.

Because the projects that feel collaborative, calm, and genuinely exceptional usually start with two professionals who respect each other’s expertise early, communicate directly, and understand that neither perspective works as well without the other.

Architects often approach a project from the outside in.
Designers approach it from the inside out.

And when both perspectives are fully brought to the table, the result is a home that not only looks beautiful—but actually works for the people living there.

That’s what I want to talk about today.

---

The Three Ways Designers and Architects End Up Working Together

There are essentially three ways this relationship starts.

First, the architect brings the designer in. The client hires the architect, and the architect recommends or requests an interior designer for the project.

Second, the designer assembles the team. The client hires you first, and then you bring in the architect for the architectural scope.

And third—and honestly this happens more often than people realize—the client hires both of you independently.

None of these scenarios is better than another. All of them can produce exceptional work. But they each require a different practical approach at the beginning of the project.

If you walk into a project behaving like you assembled the team when you didn’t, you’ll create friction quickly. The reverse is true too. If you brought the architect in but behave passively or apologetically, the project suffers in a different way.

You need to know which room you’re in.

Then you show up as the equal professional you are.

---

When the Architect Brings You In

This is where I see designers get themselves into trouble most often.

When an architect brings you into a project, they’re extending trust. They’re telling the client, “I know someone who will handle the interiors well and collaborate professionally.”

That matters.

And how you show up from there will determine whether that architect ever calls you again.

Now, honoring that relationship does not mean making yourself small. It does not mean deferring on every decision or acting like a guest in the room.

It means being clear about your scope, communicating directly with the architect, and respecting the structure of the team that already exists.

What doesn’t work is immediately repositioning yourself as the client’s primary point of contact or challenging architectural decisions in front of the client.

That damages trust quickly.

But here’s the part I really want designers to hear:

Architects are not looking for designers who simply agree with them. They’re looking for designers who make the project better.

Designers who catch things.
Designers who think deeply about how the home will function.
Designers who elevate the interior experience in ways that strengthen the entire project.

That is what generates referrals long term.

---

When You Bring the Architect In

If the client hired you first and you assembled the team, you likely have more operational authority. But that does not make the relationship less collaborative.

In fact, it makes your setup conversations even more important.

Before the project starts, the architect needs to understand your role clearly: that you are not a passive observer to the architectural process, and that you will be involved in decisions affecting the interior experience of the home.

This is also where the drawing conversation becomes critical. Because who handles drawing production directly affects your fee structure.

If the architect’s office is producing all drawings and you’re providing sketches or markups, your hours are lower. Your fee should reflect that.

If your team is producing interior drawing sets independently, that’s a completely different level of time commitment.

This needs to be established before the scope of work is finalized—not halfway through the project when everyone realizes assumptions were different.

Ambiguity here creates problems fast:

• billing issues
• timeline issues
• resentment
• scope creep

Clear expectations prevent all of it.

---

Most Designers Skip the Conversation That Matters Most

The strongest architect collaborations I’ve experienced all started the same way.

With a direct conversation.

Not a dramatic one. Not a formal one. Just a clear one.

Here’s what I do.
Here’s what you do.
Here’s where our scopes overlap.
And here’s how we’ll handle it when we see things differently.

Most designers skip this conversation because they assume the relationship will naturally work itself out once the project starts.

It usually doesn’t.

Or at least not as well as it could have if someone had named the structure early.

And honestly? I want that someone to be you.

---

Why Weekly Meetings Matter So Much

A real working relationship between a designer and architect is built over time.

Not through email. Not through forwarded PDFs. It’s built by being in the room together consistently.

Weekly site meetings matter because they create rhythm. You begin understanding how the architect thinks. They begin understanding how you think. You develop shorthand. You catch things for each other before they become problems.

And from my experience, architects genuinely appreciate designers who are curious about the architectural side of the project.

Ask questions.
Understand the constraints.
Learn why certain decisions were made.

That curiosity strengthens the collaboration tremendously.

Because the designers who are enjoyable to work with—the ones who are engaged, thoughtful, and solution-oriented—are the ones who get called for the next project.

And pleasure matters more in this industry than people like to admit.

---

Outside-In vs. Inside-Out Thinking

This is probably the clearest way I can explain why this relationship matters so much.

Architects generally approach a project from the outside in.

They begin with the structure, the envelope, the site, the program requirements. Their job is to create a building that works architecturally, structurally, and functionally.

That is an extraordinary skill set.

Interior designers approach the project from the inside out.

We think about how people actually live inside the home.

How mornings function.
How families move through spaces.
How kitchens operate during real life—not during a photoshoot.

We notice the practical details that deeply affect quality of life: where bags land, how someone cooks, where the dog leash goes, how traffic flows between rooms, which spouse wakes up first.

That perspective matters enormously.

And when outside-in thinking meets inside-out thinking successfully, the result is a home that feels effortless to live in.

Clients often can’t articulate why it works so well.

They just know it does.

---

How to Handle Disagreements Professionally

Disagreements will happen on every real project.

That’s normal.

What matters is how you handle them. And if there’s one thing I want designers to stop doing immediately, it’s challenging architects in front of the client. The moment team members openly disagree in front of the client, confidence in the entire team drops.

If you have a concern, address it directly with the architect privately.

And frame it around the project—not your personal preference.

There’s a big difference between: “I don’t think this works.”

And: “I’m wondering if this creates a challenge for the furniture plan we’ve been developing. Can we look at that together?”

One invites collaboration.
The other invites defensiveness.

That distinction matters.

---

Architects Can Become One of Your Best Referral Sources

This part is deeply underappreciated.

Architects can become some of the strongest referral relationships in your business.

When they trust your process, enjoy collaborating with you, and see the quality of your work consistently, they remember you.

They recommend you.
They bring you into future projects.
They mention your name to contractors and clients.

And those relationships compound over time.

But they’re built through professionalism, communication, consistency, and respect for the collaboration itself.

Not ego.

---

The Best Projects Happen When Both Perspectives Are Fully Valued

The architect relationship is not a threat to your authority.

It’s an opportunity to create work neither of you could have produced alone.

But it requires:

• understanding the project dynamic early
• defining roles clearly
• communicating consistently
• respecting the overlap between disciplines
• and keeping every disagreement focused on what serves the project best

At the end of the day, we need each other.

Architects create the structure that holds the home together.
Designers shape how life actually unfolds inside it.

And when both perspectives are fully respected, the work becomes something neither profession could have achieved independently.

That’s the goal.

And honestly? That’s when this work becomes really fun.

---

Like this Episode?

Be sure to check out Episode #294: The One Hour a Week That Keeps a Construction Project From Falling Apart

Be sure to check out Episode #283: Why Interior Designers Shrink on Jobsites (And How to Stop)

Be sure to check out Episode #158: How to Build a Supportive Network in Construction Management