There's an assumption in our industry that the development process is going to be painful. Not just complex, which is expected, but genuinely unpleasant. Long contentious meetings, adversarial dynamics, and a general acceptance that this is just how it works. I've never understood that. These projects take years and they involve real consequences for the communities they serve. We've found that when the process works well, when people feel respected and genuinely involved, the outcome is always better. That's not just a nicer way to work. It's a more effective one.

A Different Kind of Meeting

The City of Falls Church, Virginia needed a new middle school. The community was growing, classrooms were overcrowded, and there was no available land within the city to build on. We found a way to make it work on land the city already owned, saving them millions of dollars and years of process, and delivered the project two years ahead of schedule and $10 million under budget. It remains one of the most beloved community facilities in Falls Church over twenty years later.

But what stayed with our team most from that project had nothing to do with the budget or the timeline. At the dedication ceremony, the superintendent of the school system said something that has stuck with us ever since. She said that throughout her career, she had built a lot of facilities and had always dreaded the weekly contractor meetings. They were never enjoyable. She would sit for two hours while people threw problems at her.

On our project, she said she came to look forward to the meetings. Not because there weren't problems, but because when problems came up, solutions were offered right alongside them. All she had to do was make a decision.

That is what we work to create on every project. Our job is to do the heavy lifting, think through the options, and help our clients navigate toward the best decision for their community. When problems arise, and they always do, our team has already thought through the options before we walk into the room. The client should never have to carry the burden of the process. That's what they hired us for.

When Losing the Project Wasn't the Worst Part

We spent three years working with a university in Texas on a major new campus expansion. It was a great team, a great project, and we had built real momentum together. We were within hours of getting the green light to move to the next phase when the university's leadership changed. New chancellor, new direction, and the project was terminated.

Three years of work, gone in a moment. But what the client's team told us afterward has stayed with us longer than almost any win. They said they were most sorry not about the project ending, but about not getting to work with our people anymore. To us, that meant a lot, and it reinforced something we've always believed: that the relationships and trust built during a project can be just as valuable as the project itself. Sometimes even more so.

There's a Reason People Call Us Back

I've been told that one of the things people notice about us is that we're nicer than the average developer. I take that as a compliment, and I think it matters more than people realize. It changes the tone of meetings. It puts people at ease. And it creates the kind of environment where honest, collaborative problem-solving can actually happen.

But being nice and easy to work with is not the same as being soft. We hold ourselves to a very high standard, and we expect the same from our partners. The difference is how we pursue that standard. We do it through commitment, not confrontation. Through personal accountability, not finger-pointing. Everyone on our projects knows what's expected because we're upfront about it from day one, and we hold ourselves to it before we ask it of anyone else.

And we stay. The people who start a project are the people who finish it. I started working with one of our clients in Long Beach in 2009 and I can still pick up the phone and call her today. Our partners have been here for years, some for decades. In an industry where firms often send their best people to win the work and then hand it off to someone else, we think that kind of consistency matters. Our clients seem to agree.

It's Supposed to Be Fun

I tell people all the time, don't let my boss know, but I actually love what I do. 

Every project is different, every client has a unique set of challenges, and finding creative solutions to those challenges, the ones that are better than what anyone expected, is something we take a lot of pride in.

I think that attitude comes through in the work. When our team is enjoying what they're doing, it shows. When our clients can feel that energy and commitment, they respond to it. And when everyone involved in a project actually wants to be there, doing the work, solving the problems, pushing for something better, the results speak for themselves.

The best projects we've been part of were the ones where everyone involved, our team and the client's, looked back and said that was a great experience. Not just a great building, but a great experience.

That's the standard we hold ourselves to.