There's a question I've started asking prospective clients that tends to catch them off guard: what was your last development experience like? Not the building that came out of it, not whether it met the budget or schedule, but the actual experience of going through the process. What was it like to be in all of those meetings? How did it feel?

The most common answer I hear is some version of: it was painful. Long meetings. Adversarial dynamics. People throwing problems across the table. A constant feeling of being behind or out of the loop. And at the end, even when the building turned out well, the overwhelming sentiment is relief that it's over, not pride in what the process produced.

I've never accepted that this is just how development has to work. These projects take years. For many of our clients, this will be one of the most significant investments their institution ever makes. The people responsible for shepherding it through, the facilities directors, the capital planners, the project managers, will spend a substantial portion of their professional lives inside this process. Why should that experience be something they have to endure rather than something they genuinely value?

Two Customers, One Project

One of the things I've come to understand over the years is that on every project, we're really serving two different customers with two very different sets of needs.

The first customer is the decision maker: the university president, the city manager, the county executive, the board. Their focus is on the outcome. Did we get the building we needed? Was it on time? Was it on budget? Does it serve the mission? Those are the questions they're going to be asked, and those are the metrics they'll be measured by.

The second customer is the person who lives inside the process every day: the head of facilities, the capital planning director, the project manager on the client's side. For them, the project outcomes matter, but the experience of getting there is equally important. This is their daily life for the duration of the project. How the team communicates, how problems are raised and resolved, whether they feel informed and respected and like they have a genuine partner rather than just a vendor, all of that shapes not just the project but their professional life for years.

Most development teams focus almost entirely on the first customer. They optimize for the outcome and treat the process as a necessary means to get there. I think that's a mistake, because the experience of the process and the quality of the outcome are not separate things. They're directly connected. When the people inside the process feel supported, informed, and genuinely engaged, they make better decisions. They raise issues earlier. They contribute more creatively. And the project benefits from all of it.

Setting the Table

So how do you actually make this work in practice? It starts with what I think of as setting the table.

Before any of the visible work begins, we invest time in making sure the right people are aligned around the right goals, that everyone understands how the process will work, and that the team we've put together is the right fit for this particular project. It sounds straightforward, but it's the step that most often gets rushed, and when it does, you feel the effects for years.

When that foundation is solid, the whole dynamic changes. Problems still come up, they always do, but they get raised earlier and worked through more productively. Decisions move faster because the trust is already there. And the overall experience starts to feel less like something people are getting through and more like something they're genuinely part of.

I use the word "frictionless" a lot, and I realize that might sound unrealistic for this kind of work. What I mean by it is practical: we try to remove every unnecessary obstacle from the process so that the people involved can focus on the things that actually matter. It's not about avoiding hard conversations. It's about making sure the hard conversations are about the substance of the project, not about a team that isn't working well together or a process that nobody trusts.

Beyond Delivery

The experience we're talking about doesn't end when construction is complete. If anything, that's when it matters most, because that's when the people who will use the building every day start to find out whether the promises made during development actually hold up.

At Fuse at Mason Square, our team is on the ground every day, and their job isn't property management in the traditional sense. It's making sure the experience inside the building is as intentional and well-crafted as the process that created it. They know every tenant by name, not the company name, the actual people. They make introductions. They create reasons for people to connect who otherwise wouldn't. One of our team members buys tenants coffee once a month as long as they bring a discussion topic about what's happening in the building. Small gestures like that are what turn a finished building into a living community.

That continuity, from the first conversation with a client all the way through to the daily experience of the people inside the building, is what we mean when we say the ride matters. It's not just about the years of development. It's about creating something that keeps delivering a great experience long after the construction team has gone home.

Why This Matters Now

I spend a lot of time thinking about where this industry is heading, and I keep coming back to the same conclusion: the developers who will win in the next decade won't be the ones who can deliver the lowest price or the fastest schedule. Those things matter, and they always will. But they're becoming table stakes. What will increasingly differentiate one team from another is the quality of the experience they create, both during the development process and in the life of the building after it opens.

A lot of our clients will only do something like this once. One project, one shot to get it right, and they'll live with the outcome for decades. They deserve a process that doesn't just produce a great building but that leaves them feeling proud of how they got there. And the people who show up to work inside that building every day deserve a space that was thoughtfully designed and is being actively cared for with them in mind.

I always call it the ride. And the ride should matter just as much as the destination. When the process is one that people look back on and say that was a genuinely great experience, and the building keeps earning that same response from the people inside it year after year, that's when you know you got it right.