In managing complex development projects, the difficulty is rarely the building itself. It is everything that surrounds it. You are dealing with multiple stakeholders, competing priorities, and institutional constraints that all need to be reconciled for the project to move forward.

What ultimately determines the success of a project is how well a diverse group can align around a shared goal and move forward as one team.

On large projects, that group is broad. The client, contractors, sub-contractors, city personnel, advisors, and other stakeholders are all operating with different assumptions and accountable to different pressures. If that dynamic is not managed well, the project will reflect it. Decisions slow down, issues circulate without resolution, and the work begins to fragment.

I have occasionally described the role of managing these development projects as that of a glorified bus driver. It is a simple analogy, but it reflects how I approach the work. The responsibility is to assemble the right group, understand what each person brings, position them to contribute effectively, and guide the team toward a shared outcome in a way that stays coordinated and productive.

Getting the Right People in the Right Seats

On our projects, capability is rarely the limiting factor. The difference comes down to how the team is assembled and how it is structured once the work begins.

Each project introduces a mix of stakeholders with different priorities, communication styles, and constraints. They are often operating within their own frameworks, with limited visibility into how others are approaching the same set of issues. Without a deliberate effort to organize that group, even highly capable teams can struggle to function effectively.

That work starts early. It involves understanding who needs to be involved, when they need to be involved, and how their contributions connect to the broader effort. It also requires recognizing how individuals operate. Some people take ownership naturally and move issues forward. Others are more effective in roles that support and stabilize the work. The goal is not to impose a structure, but to build one that reflects the strengths of the people involved.

When that is done well, the team does not just function. It begins to operate with a level of clarity and momentum that is difficult to create later if it is not established from the outset.

Leadership as a Practical Responsibility

In this environment, leadership is less about direction and more about responsibility. The role is not to control the work, but to ensure that it is structured in a way that allows progress to happen consistently.

That often comes down to a few core actions. Providing clarity when the problem is not well defined. Creating the right setting for decisions to be made, with the right people involved. And stepping in when something is slowing the work down, even if the issue is not immediately visible.

What makes this more complex is that the work extends beyond a single team. Clients, advisors, and external stakeholders all influence the trajectory of the project, and each brings their own internal dynamics. In many cases, the real challenge is not the work itself, but how those groups interact with one another.

A project rarely breaks down because people are incapable. It breaks down because the structure around them does not allow them to be effective.

Alignment Requires Deliberate Effort

Alignment is often assumed at the outset of a project, but in practice it is one of the more difficult conditions to establish and maintain. Even small differences in expectations or assumptions can introduce friction that compounds over time if it is not addressed directly.

It is not uncommon for projects to appear to be progressing, with meetings occurring and milestones being met, while underlying misalignment remains unresolved. When those gaps surface later, they tend to affect both the pace of decision-making and the quality of the outcome.

For that reason, a meaningful portion of the work involves making alignment explicit. That means bringing the right people into the same conversations, structuring those conversations so they are productive, and ensuring that key assumptions are surfaced, discussed, and tested. When that process is working, decisions tend to become clearer and more consistent. When it is not, the work becomes more reactive and more difficult to manage.

Creating Space for Better Thinking

The quality of the outcome is directly tied to the quality of the thinking behind it. That thinking does not come from a single perspective. It comes from how effectively different perspectives are brought together.

That requires an environment where ideas can be evaluated on their merits, not on where they come from. In practice, that is not always easy. Differences in authority, experience, and communication style can limit who participates and how.

Some of the most important insights on a project do not come from the most vocal participants. They come from individuals who are paying attention, seeing issues early, and deciding whether or not to raise them. If those perspectives are not actively brought into the conversation, they are often lost.

Part of the role is recognizing that dynamic and creating the conditions where those contributions are more likely to surface. The work improves when the full range of thinking is actually engaged.

Why Being in the Room Still Matters

While much of today’s work can be done remotely, there are critical moments in every project where bringing people together in the same room has a measurable impact. On more challenging efforts, we have found value in establishing a regular cadence of in-person working sessions focused on decision-making.

The benefit is not just efficiency, although issues are often resolved more quickly in that setting. It is also the quality of interaction. When people are working through issues together in real time, there is less room for misinterpretation, and a greater sense of shared responsibility for the outcome.

Even the informal aspects of those interactions matter. Time spent outside of structured meetings, including something as simple as sharing a meal, contributes to how the group functions. Familiarity builds trust, and over time that trust improves communication and coordination. These elements may seem secondary, but they often have a direct impact on how effectively the team operates.

From Coordination to Performance

There is a noticeable shift that occurs when a group moves from being organized to operating at a high level. It is not something that is formally announced, but it becomes evident in how the team works.

Conversations become more focused, and issues are identified earlier in the process. Individuals begin to anticipate what is needed rather than reacting to what has already occurred. The standard of work rises, not because it is being enforced, but because the group has developed a shared expectation around the outcome.

That shift is typically the result of clarity, trust, and a sense of shared ownership. When people understand their role and feel accountable for the outcome, they tend to engage more fully. Over time, that engagement compounds and strengthens the overall performance of the team.

Judgment Over Control

Even with a strong structure in place, projects require ongoing judgment. Not every issue carries the same level of importance, and not every decision needs to be addressed immediately.

Part of the role is understanding where to focus attention, when to intervene, and when to allow the team to work through an issue independently. That balance is not static. It shifts over the life of the project as different phases introduce different types of challenges.

Early stages often require more coordination and alignment, while later stages depend more heavily on execution. The approach evolves, but the responsibility remains consistent: understanding what the team needs at a given moment and responding in a way that supports progress.

What This Approach Makes Possible

When these elements come together, the effect is tangible. Teams operate with greater clarity, decisions are made more efficiently, and stakeholder groups remain aligned over longer periods of time.

Complexity does not disappear, and challenges are still part of the process. However, when the team is structured effectively and operates with a shared understanding of the work, those challenges become more manageable and less disruptive to the overall trajectory of the project.

Coming Back to the Role

Across projects, the specific details change, but the underlying responsibility remains consistent. Someone has to bring the right people together, create a structure that allows them to work effectively, and guide the group toward a shared outcome.

That is what the bus driver analogy is intended to convey. It is not about control in the traditional sense, but about coordination, awareness, and direction. It reflects the responsibility of ensuring that a complex group of individuals and organizations can move forward together in a way that is aligned and productive.

Because when that is done well, the project has a much stronger foundation for delivering the outcome it was intended to achieve.