top of page
Search

Trust

  • crystalhopwood
  • Nov 15
  • 2 min read

Updated: Nov 16

Recently we have been thinking about trust.


We have been reflecting on the role of trust in our professional lives. How it shows up, how it shapes relationships, and what is possible when it is prioritized.


Watching a tech business implement a 32 hour work week has been a reminder that trust isn't just a "nice to have", it's the engine that powers healthier, more sustainable ways of working. It requires believing that your team will show up, contribute meaningfully, and care deeply without needing to be constantly monitored.


We have felt the same thing on a project using Integrated Project Delivery (IPD) principles. When the client, architect, consultants, and contractor all trust one another, when we can speak openly, share responsibility, and make decisions collaboratively it creates space for better outcomes AND a better process.


Too often in architecture, trust is missing. We hold on tight to old systems, rigid schedules, and hierarchical relationships because we are afraid of what will happen if we loosen our grip. But in our experience, when we build cultures of trust, we unlock creativity, flexibility and genuine collaboration.


Trust isn't about being naive. It's about setting the stage for people to do their best work. And believing that they will.


When the approach to a project is built on openness and shared responsibility it only works if everyone is willing to trust each other. To be transparent. To speak up. To listen. To ask questions. To show up with kindness, even when things get hard.


And I think that's what's often missing in the traditional way we practice architecture. So many firms are afraid to offer flexibility or let go of control because they don't trust their employees.


Trust doesn't just feel good, it leads to better work, stronger teams, and more thoughtful outcomes for everyone involved.


 
 
 

Recent Posts

See All
Collaboration

One of the most over-used, yet undefined terms. Here is our first attempt to articulate what 'collaboration' means to us. We don’t see architecture as a solitary act. While design might begin with an

 
 
 
Why do this?

Why leave the (relative) stability of employment and venture out on our own? There are a few reasons, some practical, others more personal: Flexibility Our most focused, productive hours rarely fall w

 
 
 

Comments


bottom of page