The most successful projects aren’t always defined by their architecture. Sometimes, they’re defined by the relationships that made them possible.
Beyond the drawings, successful projects are shaped by the relationships behind them.
What makes an owner want to work with the same architect again?
Is it the quality of the drawings? The ability to deliver on schedule? The attention to detail, the design, or perhaps the final construction cost?
Of course, all these things matter. But after more than two decades working in architecture, I’ve come to believe that something far less tangible often determines whether a project is genuinely successful.
Trust.
Not the kind established through a signed agreement or a carefully worded scope of services, but the kind developed through conversations, difficult decisions, shared experiences, and the occasional mistake. The kind that allows people to challenge one another without damaging the relationship, and creates room for creativity because neither side feels the need to constantly defend its position.
And perhaps most importantly, the kind that makes everyone want to work together again.
The Relationship Behind the Project
Architecture is fundamentally a relationship-driven profession, yet we spend remarkably little time discussing the relationships themselves.
We talk about procurement, budgets, design development, construction documents, and schedules. We establish responsibilities, reporting structures, and communication protocols. Every phase has deliverables, and every deliverable has expectations.
But somewhere between the first client meeting and the final walkthrough, something else develops.
People begin to understand one another.
An architect learns how an owner approaches decisions, what matters most to their organization, and where they are willing to explore new ideas. The owner begins to understand the architect’s process, the reasons behind certain recommendations, and the complexities involved in turning an idea into a functioning building.
Over time, these conversations create a shared understanding that no project manual can fully capture.
I’ve been fortunate to experience this throughout my career, particularly working with school districts in British Columbia. Some of the strongest professional relationships I’ve developed began with a single project and continued through years of collaboration.
Those relationships weren’t built exclusively in meeting rooms.
They developed during long drives to project sites, over dinners after difficult meetings, through conversations that had very little to do with architecture, and while celebrating milestones that everyone had worked incredibly hard to achieve.
Some of the most important conversations happen outside the meeting room.
Eventually, the person across the table stops feeling like simply a client. They become a colleague, a mentor, and sometimes a friend.
And that changes how you approach the work.
Fair and Reasonable
One of the people who helped shape my understanding of these relationships was Mitch, whom I had the privilege of working with through the Kelowna School District.
Mitch had a particular way of approaching projects. He understood that construction was complicated, that challenges were inevitable, and that not every situation required a confrontation.
One of his guiding principles was remarkably simple: be fair and reasonable.
Those three words have stayed with me.
Being fair and reasonable doesn’t mean overlooking deficiencies, accepting unnecessary costs, or avoiding difficult conversations. It means understanding the circumstances, respecting the people involved, and approaching decisions with a sense of proportion.
Mitch understood the importance of establishing expectations early, particularly when dealing with changes during construction.
The first change on a project often establishes a precedent. How it is reviewed, negotiated, and resolved sends a message about how subsequent changes will be handled.
How the first change is handled can establish the tone for the entire project.
If expectations are unclear, or if one party feels the other is taking advantage, trust can deteriorate surprisingly quickly.
But when everyone understands that costs should be justified, decisions should be transparent, and nobody should be using the situation to unfairly benefit themselves, the relationship becomes much stronger.
That approach benefits everyone.
The owner receives fair value. The architect can provide professional advice without unnecessary pressure. The contractor understands that legitimate issues will be considered reasonably.
It creates an environment where people can focus on solving problems rather than protecting themselves from one another.
Mistakes Don’t Have to Define a Relationship
One of the most important things Mitch demonstrated was how to handle mistakes.
Because mistakes happen.
They happen in architecture, in construction, and in every profession where people are making decisions under pressure.
The question is not whether someone will eventually make a mistake. It’s what happens afterwards.
I remember Mitch’s approach being refreshingly straightforward. If something went wrong, he expected people to acknowledge it, take responsibility, and correct the issue.
And then came the lesson.
“Just don’t do it again.”
There was accountability, certainly. But there wasn’t a desire to hold the mistake over someone’s head indefinitely. Once the issue was addressed, the team moved forward.
I’ve always admired that.
Too often, professional relationships become strained because people are more concerned about assigning blame than understanding what happened.
An issue that could have been resolved through a straightforward conversation becomes an exchange of defensive correspondence. People begin copying additional parties on emails. Positions harden, and the actual problem becomes secondary.
Trust doesn’t eliminate accountability. It makes accountability possible without destroying the relationship.
An owner should be able to challenge an architect. An architect should be comfortable acknowledging an oversight. A contractor should be able to raise a concern without immediately being treated as an adversary.
When those conversations can happen openly, problems have a better chance of being addressed early, before they become significantly more complicated.
And when people know they will be treated fairly, they’re often more willing to bring forward difficult information in the first place.
Trust Creates Room for Better Architecture
There’s another side to the owner–architect relationship that I think deserves more attention.
Creativity.
An architect can develop a thoughtful design, explore innovative ideas, and challenge conventional approaches. But without an owner willing to participate in that process, many opportunities never move beyond the drawing board.
Trust creates the confidence to explore something different.
I remember working through school projects where elements such as learning stairs, serveries, and interior colour selections became opportunities for genuine collaboration.
These weren’t simply technical decisions about materials and dimensions. They were conversations about how students and staff would experience the building.
A learning stair could become more than a means of moving between levels. It could support gathering, interaction, and informal learning.
Trust gives design teams room to explore ideas that go beyond basic building requirements.
A servery could be approached as more than a functional food-service space. Its layout, connections, and relationship to adjacent areas could influence how the broader school community uses the building.
Even colour selections could become part of a larger conversation about identity and atmosphere.
What made those discussions valuable was the willingness to explore ideas together.
Mitch understood that the design team had expertise worth trusting. He wasn’t interested in controlling every decision simply because he represented the owner.
He established expectations, asked questions, and allowed the professionals around him to do their work.
That doesn’t mean every idea was accepted. Budgets, maintenance requirements, operational considerations, and practical constraints still mattered.
But the conversation began from a position of possibility rather than resistance.
That’s an important distinction.
When architects feel trusted, they’re more willing to bring forward ideas that might improve a project. When owners feel respected and informed, they’re more comfortable considering approaches that differ from what they initially imagined.
The relationship becomes a collaboration rather than a transaction.
And that’s often where better architecture begins.
The Value of Understanding Your Client
Strong relationships also create something that is difficult to measure but incredibly valuable: institutional knowledge.
Every organization has its own preferences, standards, processes, and expectations.
School districts are a good example.
One district may have particular requirements for finishes, hardware, maintenance access, or classroom layouts. Another may approach similar spaces quite differently.
Some organizations document these preferences through design guidelines, standard operating procedures, or established material standards. Others rely heavily on the experience of the people managing their capital projects.
Understanding those expectations is an important part of delivering successful work.
But understanding why those expectations exist is even more valuable.
A particular material specification may reflect years of maintenance experience. A standard detail may have evolved after previous projects revealed a recurring problem. A preference for one building system over another may be rooted in the operational realities of a district’s facilities team.
Behind many familiar project standards are years of experience and lessons learned.
When those lessons are carried from one project to the next, the entire process can become more efficient.
The architect doesn’t need to rediscover the same preferences. The owner doesn’t need to repeatedly explain decisions that were resolved years earlier.
More importantly, the team can distinguish between requirements that are essential and practices that might benefit from reconsideration.
This is where long-term relationships create opportunities for continuous improvement.
The knowledge gained from one project should inform the next. And the next.
Too often, valuable information disappears when a project closes, a team member changes roles, or an organization appoints a new consultant.
The relationship may continue, but the lessons don’t always follow.
That represents a missed opportunity, not only for project efficiency but also for the quality of the buildings we create.
More Than Another Project Number
One of the things I remember most about working with Mitch wasn’t a particular drawing, specification, or construction issue.
It was the conversations.
There was even a familiar association with fish and chips that became part of the experience of working together.
The conversations that stay with us aren’t always about architecture. AI-assisted conceptual illustration, not a historical depiction.
These are the small details that rarely make their way into project records, yet they’re often the things we remember years later.
The long drives. The meals. The stories shared after a difficult day. The satisfaction of walking through a completed school and seeing the result of everyone’s work.
Architecture can be an incredibly demanding profession. Projects stretch over years, responsibilities are significant, and decisions can carry substantial financial consequences.
It’s easy to become consumed by the next deadline, the next meeting, or the next issue requiring attention.
But buildings aren’t delivered by drawings alone.
They’re delivered by people.
And those people spend a considerable portion of their professional lives working together.
I think that’s worth remembering.
The relationships we develop shouldn’t be viewed simply as a means of securing another commission or improving client retention.
They have value in their own right.
Some of my most meaningful professional experiences have come from the people I’ve met along the way. People who challenged me, trusted me, taught me something, or simply made the difficult days a little easier.
Mitch was one of those people.
He taught me that you could be firm without being unreasonable, hold someone accountable without damaging their confidence, and maintain high expectations while still treating everyone with respect.
Those lessons extend far beyond architecture.
Building Relationships That Last
As our industry becomes increasingly digital, we have more tools than ever to organize information, manage projects, document decisions, and communicate across teams.
These tools are valuable, and I believe they have an important role in improving how architectural practices operate.
But technology cannot replace the foundation of a strong professional relationship.
It can help preserve institutional knowledge, maintain continuity between projects, and make important information easier to access. It can support clearer communication and reduce the frustration of repeatedly searching for decisions that have already been made.
What it cannot do is make people trust one another.
That still comes from experience.
From following through on commitments. From being honest when something goes wrong. From respecting another person’s expertise and recognizing that everyone involved is working toward a common outcome.
It’s also about remembering that the relationship shouldn’t end when the keys are handed over.
Celebrate the completed building. Reflect on what worked and what could be improved. Carry those lessons into the next opportunity.
And occasionally, make time for the conversations that have nothing to do with the project at all.
Because years later, when the drawings have been archived and the construction meetings are a distant memory, those relationships may be what remain.
Mitch’s influence continues to shape how I think about working with owners, architects, and the people responsible for delivering buildings.
Be fair. Be reasonable. Take responsibility. Trust the people around you.
Simple principles, perhaps, but powerful ones.
And they leave us with a question worth considering before the next project begins.
Are we building relationships that merely deliver what was requested, or relationships that make something better possible?
Project Arc is built around a simple idea: the knowledge and decisions behind a building shouldn’t disappear as the project moves forward. Explore how we’re connecting the work behind project delivery.
