When people look at large development projects from the outside, the conversation tends to center on what’s easiest to see: the building itself. The design, the construction process, and the milestones along the way naturally become the focus, because they’re the most tangible parts of the work.

Over time, however, working across a range of complex projects, I’ve found that those visible elements rarely tell you whether a project will actually succeed. The more consequential work tends to happen much earlier, and it is typically less tangible. It involves understanding why the project exists in the first place, what it is intended to accomplish, and how it fits into a broader set of institutional or community objectives that extend well beyond the physical structure itself.

In my experience, no one builds a building simply to build a building. There is always a larger purpose behind the effort, whether it is helping an institution evolve, strengthening a community, or enabling a group of people to do something they were not previously able to do. The building ultimately becomes the physical expression of that purpose, but it is not the purpose itself.

Understanding What the Project Is Really About

One of the more consistent challenges on large-scale development projects is that the underlying purpose is not always clearly defined at the outset, or it is defined in a way that is too broad to guide meaningful decision-making. When that happens, teams can make steady progress in a technical sense while gradually drifting away from what the project was actually intended to achieve. The work continues to move forward and milestones are reached, but over time the outcome can end up far removed from the original intent.

For that reason, one of the most important questions to establish early, and to revisit throughout the life of the project, is a relatively simple one: what is this actually meant to do? Not just in functional terms, but in terms of impact, role, and long-term value. It is a question that tends to surface gaps in understanding very quickly, particularly when different stakeholders are working from slightly different assumptions about what success looks like.

It is a straightforward question, but arriving at a clear and shared answer is often more difficult than it appears. Most projects involve a wide range of stakeholders, each bringing their own priorities, constraints, and perspectives. Without a consistent understanding of purpose across that group, it becomes much more difficult to evaluate trade-offs, prioritize decisions, and maintain a clear direction as the project evolves.

When the Project Becomes Something More

One project that illustrates this dynamic particularly well was a business school development at the University of Nevada, which included a new academic building and hotel. From a purely functional standpoint, it could have been described as a set of facilities designed to accommodate classrooms, faculty offices, program space, and hospitality uses.

However, once we spent time with the university leadership and began to understand the broader context, it became clear that the ambition behind the project extended well beyond those immediate needs. The university was working to redefine its relationship with the surrounding city — strengthening its identity and creating a more cohesive connection between campus and community. The goal was to become more integrated and visible, generating energy, activity, and economic vitality across the area.

At the time, that portion of the campus did not reflect that ambition. It lacked a sense of arrival, did little to encourage interaction, and failed to reinforce the role the university was trying to play within the broader urban environment. As the conversations evolved, it became clear the project needed to do more than deliver additional space. It began to take on a different level of significance — less about buildings, and more about creating a gateway that could physically and symbolically connect the university to the city.

Once that intent was clearly defined, it began to influence the work in tangible ways. Conversations became more focused, decisions were evaluated through a different lens, and the team’s level of engagement shifted, because the work was no longer just about the buildings.

Alignment Changes How Teams Perform

That shift in understanding has a direct impact on how teams perform. When people recognize they are contributing to something that carries broader meaning, they approach the work with a different level of care and accountability. They are more willing to challenge assumptions, revisit decisions, and take ownership of outcomes beyond their immediate responsibilities.

Over time, the difference becomes clear between a team that is simply executing tasks and one that is genuinely invested in the result. It is not always easy to quantify, but it shows up in the quality of conversations, the consistency of the work, and the way the team interacts. When alignment is present, a different level of engagement emerges, and it tends to carry through the life of the project.

Creating and maintaining that alignment is not automatic. It requires deliberate effort to involve the right people, structure conversations in a way that allows meaningful participation, and build a shared understanding of what the project is trying to achieve. Without that foundation, even highly capable teams can struggle to perform at the level the project requires.

The Role of Leadership in Complex Projects

In many ways, the role on projects like these is less about directing the work and more about enabling it. With multiple stakeholder groups, layered decision-making structures, and a level of complexity that makes centralized control unrealistic, leadership becomes less about authority and more about coordination.

I have occasionally described my role as that of a “glorified bus driver.” The responsibility is to ensure the right people are on the bus, that they are positioned to contribute effectively, and that the group is moving toward a shared destination.

That requires a combination of coordination, communication, and judgment. It means creating an environment where people feel comfortable contributing, where ideas are encouraged and evaluated on their merits, and where the team can move forward with clarity. The objective is not to have all the answers, but to create the conditions where the best ideas can emerge, regardless of where they come from.

Why a Standardized Approach Doesn’t Fit

Many teams approach this kind of work with a standardized model, designed to create efficiency, move quickly, and bring consistency across projects.

The reality is that the types of projects we are involved in rarely fit neatly into a predefined model. They come with unique constraints, stakeholder dynamics, and objectives that require a more thoughtful response. Applying a generic approach may create the appearance of efficiency, but in our experience it often produces outcomes that fall short of what the project actually demands.

I’ve often described the work we do as being closer to that of a tailor. “We continue to be the bespoke tailor for the person whose suit size is not on the rack already.” There are clients and situations where an off-the-rack solution simply isn’t going to fit the way it needs to. What’s required instead is something shaped around their specific needs, constraints, and objectives. And like any well-tailored suit, the difference is rarely defined by a single dramatic change. It comes from a series of smaller, more deliberate adjustments made over time — refinements that bring everything into alignment. When that level of care is applied, the result is something that fits in a way a standardized approach never could.

That mindset shapes how we approach each engagement. We are not trying to move as quickly as possible to a predefined solution or apply a repeatable formula. The goal is to understand the situation well enough to develop an approach that truly fits, and to stay with the work until the outcome reflects that level of alignment.

When that happens, the difference is clear. Decisions come with greater clarity, teams operate with stronger alignment, and the work becomes more effective because it is grounded in the specific needs of the project.

Rethinking What Success Means

Over time, I’ve come to think about success differently than I did earlier in my career. Delivering a project on time and on budget will always matter, but those metrics alone do not fully capture whether a project has achieved what it set out to do.

The more meaningful measure of success reveals itself after the project is complete, when the building is in use and the long-term effects of earlier decisions begin to take shape. It shows up in how the space functions, how it supports the people who rely on it, and whether it continues to serve its intended purpose years after opening.

Viewed through that lens, the building becomes one component of a broader outcome. What ultimately matters is whether the project delivers on its intended purpose and continues to create value over time. That perspective reinforces the importance of maintaining clarity of purpose throughout the process, rather than focusing solely on delivery.

Coming Back to the Same Question

Across different projects, clients, and contexts, the same question tends to surface again and again: what is this really about?

It is a simple question, but it becomes an anchor for navigating complexity. When it is answered clearly and shared across the team, it helps guide decisions, align priorities, and maintain focus on what matters most. When it is not, the project can still move forward, but it becomes much harder to ensure that the outcome reflects the original intent.

In the end, while the building is what people see, it is rarely what defines success. The more lasting impact is found in how well the project serves its purpose, how effectively it supports the people and institutions it was created for, and how it contributes to the broader context in which it exists.

And for that reason, it is worth returning to that question throughout the life of any project.

Because it is never just about the building.