Listening to a Hines Managing Director Explain How a $3B Project Actually Moves

Some talks give you information. Others change the way you picture a whole profession.

This one felt like the second type.

One thing I’ve been enjoying lately is seeing how different a topic feels once you hear it explained by someone who’s actually living inside the work — it’s a world away from just reading theory or textbooks.

I joined a conversation from UC San Diego’s Real Estate Planning and Development course, which focuses on how projects move from inception to completion — from planning, feasibility, financing, and design to entitlements, construction, leasing, and asset management.

And this guest conversation really stayed with me.

Not because it made development sound easier. Honestly, it did the opposite.

But it made the work feel more real.

Hearing a Managing Director from Hines, Eric Hepfer, talk through a project like Riverwalk made me realize that large-scale development is not just about architecture or land use maps. It’s about timing, negotiation, trust, capital, politics, compromise, patience, and an unusual ability to keep something alive for years while everything around it keeps changing.

That’s what I want to share here: what stayed in my head after sitting there and listening.

This made development feel less abstract to me

Before this, I already knew the broad outline of development: find a site, underwrite it, entitle it, finance it, build it, lease or sell it.

But listening to someone walk through an actual project made it feel very different.

It stopped sounding like a linear process and started sounding like a long chain of decisions that has to survive reality.

Not just once, but over and over again.

That was probably my first big takeaway: a major development project is not one breakthrough moment. It’s years of keeping momentum through uncertainty.

Hines sounded global, but the work still felt hyper-local

One thing I found interesting is how Hines was described.

Yes, it’s a massive global real estate firm with huge assets under management and major projects across markets. But the actual work still sounded intensely local.

That part really stood out to me.

Even with a global platform, success still seemed to come down to understanding: • a specific city, • a specific neighborhood, • a specific site, • a specific community, • and a specific local political environment.

That felt like a good reminder that real estate is still deeply place-based, even at the highest level.

The Riverwalk story made reputation feel very real

First impression, Riverwalk story.

The first pitch didn’t work.

And honestly, I liked hearing that.

Because it made the story feel human. It wasn’t presented like some perfect heroic arc. It was more like: we didn’t understand the other side well enough, we led with the wrong framing, and we didn’t win.

But what mattered is that the relationship didn’t disappear.

Years later, when the first selected developer couldn’t perform because the site was so complicated, Hines got called back.

That part really stayed with me because it says a lot about how this industry works.

Sometimes you don’t win immediately. But if people still trust your capability, the door might not actually be closed.

Riverwalk feels more like building a piece of city than doing one project

The more I listened, the less Riverwalk sounded like a normal development and the more it sounded like building an entire urban district.

It's a huge site in central San Diego, right next to Fashion Valley, with the San Diego River running through it, trolley access nearby, freeway visibility, and all the complexity that comes with trying to turn that into something mixed-use and walkable.

The vision itself is ambitious: • 4,300 residential units • 430 affordable units • around 1 million square feet of office / life science • around 150,000 square feet of retail • roughly 97 acres of parks and open space

That is not just “adding buildings.” That is trying to shape how people live, move, gather, and experience a part of the city.

That’s why the project felt so interesting to me. It wasn’t just large. It was trying to create a different kind of place.

The site itself is doing a lot of the storytelling

Another thing I found useful was hearing how the site constraints shape the land use plan.

The project isn’t happening on a blank sheet of paper.

The river, the floodway, the trolley alignment, the neighboring communities, and the freeway edges all seem to push the project into a very particular arrangement.

That makes the final plan feel less arbitrary and more like an answer to a complicated site puzzle.

I liked that because it reminded me that good planning is rarely about forcing a concept onto land. It’s more about reading what the land and context are already demanding.

Community outreach sounded structural, not cosmetic

One of the strongest parts of the conversation was the community process.

This didn’t sound like outreach as a box to check at the end. It sounded like outreach as part of the actual project-making process.

The numbers alone made that clear: • 3+ years of community outreach • 30+ community meetings and workshops • 100+ meetings with various stakeholders

And what made it even more interesting is that the feedback actually changed the design.

From the screenshot and the discussion, some of the changes in response to neighbors’ concerns included: • building height limits • generous setbacks • balanced density • more careful treatment of Friars Road • revised pedestrian connections • added private drive access • clarified maximum development intensity • permanent maintenance of landscaped medians

That part really stood out to me.

It made the process feel less like “sell the public on a finished idea” and more like “shape the idea until it can actually live with the people around it.”

The developer sounded like the center of a giant coordination system

Another clear takeaway for me is that the developer’s job seems much broader than what most people picture.

It’s not just finance. It’s not just design. It’s not just approvals.

It’s coordination at scale.

The in-house team might be relatively small, but the external network becomes enormous: architects, engineers, traffic specialists, rail consultants, media people, community engagement specialists, government relations teams, legal advisors, and more.

That made the role feel much closer to “business manager + dealmaker + integrator” than the simpler image people usually have.

Mixed-use sounds trendy until someone explains what it takes to make it real

I also liked hearing the project framed as trying to create a truly walkable, mixed-use, transit-oriented village.

That phrase gets used a lot, but listening to this made it feel much more demanding.

It means retail that actually belongs on the ground floor. Housing that actually works above it. Transit that people can actually use. A place that feels connected enough that daily life can happen there without everything depending on a car.

That felt important because a lot of places use urban language. Much fewer actually build the full system needed to support it.

The capital discussion made leverage feel very concrete

One of the parts I definitely wanted to keep was the way Eric Hepfer talked about the spread between equity and debt.

He shared that the target investor return is often around 16% to 18% on a levered basis, while development loans at that time could be something like Libor plus 200 to 300 basis points.

That creates a massive spread between the cost of equity and the cost of debt.

And that spread is a huge part of why leverage matters so much.

I liked this part because it made leverage feel less like a textbook concept and more like a very practical engine behind how developers can actually make projects work and pursue multiple deals at once.

At the same time, it was also framed as a balance. More leverage can improve returns, but only if the project is strong enough to carry that structure.

The green-light decision sounded surprisingly simple — and very serious

Another thing I found useful was the way project selection was described.

Not as a mystical instinct, but as a framework: • Can we win? • How much time will this take? • Is the profit high enough? • Is the risk proportionate to the reward?

That felt refreshingly honest.

A project can be exciting and still not deserve a yes.

That feels like a really important habit in development: not just imagining upside, but deciding whether the deal deserves your years.

Infrastructure is where vision and feasibility start negotiating with each other

One of the more grounded parts of the discussion was around infrastructure.

Everyone wants more from a major project: • transit improvements, • roads, • bridges, • public access, • better connections, • more public benefit.

And fair enough. A project this large should contribute something meaningful.

But the reality is that every requirement costs money, and those costs have to fit inside a working pro forma.

That tension felt very real to me.

Good development doesn’t mean promising yes to everything. It means finding the version of yes that the project can actually afford to deliver.

Networking sounded practical, not performative

I also didn’t want to miss the networking piece, because it sounded very direct and real.

The message wasn’t some vague “network more.”

It felt more like: reach out, connect, keep relationships alive, and understand that this field runs heavily on trust and remembered competence.

Even the simple advice to connect on LinkedIn felt meaningful in context.

And honestly, the speaker’s own path reflected that too. Relationships from past environments can open doors later — not instead of being capable, but because capability plus trust is what often moves opportunities.

That felt especially relevant in real estate, where projects last years and people keep running into each other across deals, cities, and capital relationships.

What stayed with me most: this work seems to require disciplined optimism

If I had to name the mindset that kept showing up underneath everything, it would probably be this:

disciplined optimism

Not blind optimism. Not cynicism either.

Just a strong enough belief to keep moving a difficult project forward, paired with enough realism to constantly re-check risk, feasibility, timing, and stakeholder alignment.

That balance might be one of the hardest parts of the profession.

Too little optimism, and nothing ambitious ever gets built. Too little discipline, and the ambition becomes dangerous.

A few practical lessons I’m taking away

If I had to reduce everything here into a few grounded takeaways, it would be these: • Large development projects are really long-duration coordination systems. • Reputation matters because second chances often come from credibility. • Community outreach can genuinely strengthen a project. • A site’s physical constraints often shape the best land use answer. • The developer’s job is deeply cross-functional. • True mixed-use is harder to make real than it sounds. • Leverage matters because the spread between equity cost and debt cost can be enormous. • Infrastructure demands and feasibility are always negotiating with each other. • Networking matters because trust compounds over time. • And the mindset that seems most valuable here is disciplined optimism.

That last one is probably the part I’ll remember most.

Because after listening to this conversation, development didn’t sound easy at all.

But it did sound meaningful — especially when the goal is not just to finish a building, but to shape how a city might actually live.