When teams approach complex development projects, there is often a tendency to rely on familiar models. In many cases, that instinct is well placed. Standardized approaches exist for a reason. They create efficiency, provide structure, and allow teams to move with a level of consistency and predictability.

The types of projects we are typically involved in do not operate within those conditions. They bring together institutions, stakeholders, and constraints that are specific to a particular place and moment in time. The variables are not interchangeable, and the circumstances rarely repeat themselves in a way that allows a predefined model to truly fit. An approach that worked well on one project can become misaligned on another, not because the approach itself is flawed, but because the underlying conditions are different. Of course, experience with similar projects is highly valuable and often shapes how the work is approached, but even familiar projects carry their own distinct fingerprint that needs to be understood on its own terms.

There is a sense of responsibility that comes with choosing not to rely on a canned solution and instead taking the time at the outset to fully understand what a project is meant to accomplish. That upfront investment carries through the life of the project. Like a tailor working through a series of fittings, the process is defined by attention, adjustment, and a commitment to getting it right. On projects of large scale and complexity, there is very little room to recover from an approach that was not built for what the project actually demands.

Where Things Start to Go Wrong

In our line of work, failure does not usually come from a single decision or a visible breakdown in execution. More often, it begins with small differences in how key stakeholders understand the project, what it is meant to achieve and how. Those differences are not always dramatic, and they do not immediately interrupt progress, which is why they are easy to miss in real time.

As the project moves forward, decisions continue to be made, but they are no longer anchored to a shared understanding. Each group is interpreting priorities and tradeoffs through its own lens. In large institutions, this is compounded by a tendency to let procedure stand in for judgment. People follow the process because the process is what they know, and the question of whether it is producing the right outcome gets asked less frequently. The work continues to move, but the distance between what different groups believe they are building grows wider with each decision.

By the time the impact becomes clear, the work has already been shaped by those decisions, and the cost of correcting them is rarely proportional to how small they seemed when they were made.

Shaping the Process Around the Project

Recognizing this pattern is one thing. Building a process that accounts for it is another.

On the largest projects I have been involved with, including several of the largest buildings in the Mid-Atlantic region, we established a regular cadence of structured working sessions that brought all key stakeholders together, in person. On one project, that meant coordinating with seventeen different Pentagon agencies. On another, it meant aligning a university president, a provost, a CFO, and a facilities group, each operating with different priorities and different definitions of success. In each case, we configured dedicated conference space with presentation areas, breakout rooms, and collaboration zones, and brought people together on a weekly or biweekly basis to work through critical decisions in real time.

What happens in those sessions is more nuanced than it may appear. A meaningful part of the role is making sure that what one stakeholder group is asking for is being accurately communicated to the team responsible for addressing it, and that the response actually solves the problem. When that feedback loop is working, decisions happen quickly. Options are presented, debated, and resolved with the right people in the room. Projects that would normally take three to five years in their early phases can move through in a fraction of that time.

But speed is a byproduct, not the objective. The real value is alignment. And alignment depends on things that are easy to overlook. Eating lunch together may sound trivial, but it builds rapport. Rapport builds trust. Trust changes how people communicate and work together. Over time, these interactions create the kind of team dynamic where people begin raising the bar on their own, redoing work without being asked because they know it can be better. 

What Gets Left Unsaid

The other factor that is easy to underestimate is psychological safety. The quality of any solution is limited by whether people feel safe enough to contribute to it. In practice, junior team members often defer to senior ones, and consultants defer to the client. People hold back ideas they think might be seen as obvious or out of their lane. Over time, that hesitation narrows the range of thinking that actually reaches the table.

I pay close attention to who is not participating. If someone is unusually quiet in a meeting, or seems to be going along with a direction without fully agreeing, I will reach out to them one on one afterward. Not everyone is comfortable pushing back in a room full of people, but that does not mean they have nothing to say. More often than not, those are the people who have picked up on something the rest of the group has missed. Getting that perspective into the conversation early can change the trajectory of a decision that would otherwise go unchallenged.

There is no pride of authorship on these projects. The best idea wins, regardless of where it comes from.

A Standard Defined Over Time

Over time, we have come to measure success a little differently. It is not just about delivering a project, but about how well it continues to perform for the people it was built to serve. That perspective has shaped how we approach the work, and it is reflected in the consistency of outcomes across our projects. Over the past twenty five years, every project has been delivered on schedule and on budget, a track record we are proud of. More importantly, these buildings continue to serve their purpose well beyond delivery, often in ways that exceed what was originally expected.

No one builds a building to build a building. Behind every project is a bigger purpose driving it: a university trying to transform itself, a county seeking a judicial facility that can serve the growing needs of its court system, a defense agency building the infrastructure its mission demands. When the people involved in that work feel the weight of that purpose, they perform differently. They hold themselves to a higher standard. And the result is not just a project that was delivered well, but something that continues to serve long after the ribbon cutting.

That is the standard we hold ourselves to. Not just projects that are delivered well, but buildings that are still earning their place fifty years from now.