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

📝 Editor's note (May 2026): Independent reporting now puts Riverwalk's total project cost at $4 billion, not the $3B figure I heard cited at the talk (San Diego Business Journal). After a pause in May 2024 for capital-markets headwinds, Hines closed $380M in Phase 1 construction financing with Bank OZK and Related Fund Management in October 2025, and broke ground on 721 units (Commercial Observer). So the story below is mid-arc, not finished — the years of pitching and outreach I describe have just crossed into dirt-moving.

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

This one felt like the second type.

You probably know the Margot Robbie scene in The Big Short — the one where she explains mortgage bonds from a bubble bath, champagne in hand. Real estate development turns out to be the much slower version of that same scene. Same financial machinery. Much longer bath. About twelve years longer.

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 organized around 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.

One question kept echoing the whole time I sat there: how did Hines lose the original pitch for this same Mission Valley site in 2013 and still end up the developer of record by 2016? And what does that say about how a $4 billion project actually gets allocated — not in the textbook version, but in real life?

That’s what I want to share here: what stayed in my head after sitting there and listening — and the partial answer I came around to.

What I came away believing is this: in a project this big, capital and design are the visible inputs, but the binding constraint is whether the developer can stay relevant through twelve years of changing markets, politicians, and neighbors.

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

Halfway through, the talk pivoted in a way I didn't expect: it stopped being about Hines the global firm and started being about Hines the neighborhood operator.

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. And if the work is that local, then who remembers you locally turns into one of the most valuable things you carry around — which is where the next part of the story really starts.

The Riverwalk story made reputation feel very real

The first pitch didn’t work.

And honestly — hearing that landed with a strange relief.

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.

Bisnow's reporting on the deal gives the timeline more concretely: Hines pitched in 2013 and didn't get the project; in 2016 the Levi-Cushman family came back to them, and that became the engagement that turned into Riverwalk.

Eric Hepfer, the managing director leading that work, later described it as putting "everything I had into our proposal to create a legacy project — along with the Levi-Cushman family — that will serve San Diegans long into the future."

That detail is the one I keep replaying. A loss that didn't end the relationship — it just paused it. There's a quiet pattern in that, about how this industry actually allocates work.

Sometimes you don’t win immediately. But if people still trust your capability, the door might not actually be closed. And when Hines did walk back through it years later, the proposal had grown into something bigger: not one tower, but something much closer to a piece of a city.

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 laid out in the Riverwalk Specific Plan 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.

What stuck with me wasn't the scale. It was that someone was trying to build a place, not just units.

If you want a sense of what one of these finished — or half-finished — looks like at scale, The B1M's Hudson Yards walkthrough is a useful reference. Same playbook, different city, different decade.

The site itself is doing a lot of the storytelling

Some of the most concrete moments of the talk were about the site itself — how its physical edges quietly do most of the planning before anyone draws a thing.

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. But the land only dictates the rough shape. The people who live nearby end up dictating the edges — which is where the community side of this comes in.

Community outreach sounded structural, not cosmetic

The part of the talk that most changed how I think about good development 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 ten percent question I kept coming back to

Through all of that community goodwill, one number kept tugging at the corner of my attention. 430 affordable units out of 4,300 is 10%. In a city with one of the worst housing affordability crises in the country, that's the kind of fraction a thoughtful person could look at and reasonably say: three years of community outreach should have moved it higher. Sherry Arnstein wrote, way back in 1969, that most community participation ends up as tokenism rather than a real redistribution of benefit. Ten percent is the kind of figure that, on first read, proves her point.

So I sat with that for a while.

And then the picture got more complicated. The first thing actually being built on this site isn't a market-rate tower — it's a 188-unit affordable community by Wakeland Housing, which broke ground in August 2025, before Hines closed Phase 1 financing two months later. The 10% isn't the ceiling. It's the floor across the full build-out, and the affordable share is structured to land first — when later phases would still be the easiest thing to walk away from.

So both things stay true, side by side.

The number is genuinely low for what San Diego needs. And the project sequenced what 10% there is so that it actually gets delivered. The design changes that came out of those 100+ stakeholder meetings — height limits, setbacks, the Friars Road revisions — start to read less like tokenism the more concretely you look at them, and more like a developer being bound, in real ways, by what the neighbors said.

The number isn't satisfying. The structure isn't trivial. Holding both of those at the same time is part of what makes this work feel honest to me. And part of why the next thing the talk turned to — the developer's role — had to be so much broader than just putting up buildings.

The developer sounded like the center of a giant coordination system

By the end, the word developer had stretched in my head into something much bigger than the version I'd walked into the room with.

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. And all that coordination only matters if it produces a place people actually want to be in — which turns out to be harder than the brochures make it look.

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

The team kept circling one phrase: walkable, mixed-use, transit-oriented village. The more I rolled it around, the heavier each word got.

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

When Hepfer broke down the capital math, the room got a little quieter. This was the part I most wanted to keep.

Target investor returns are often around 16% to 18% on a levered basis, while development loans at that time were Libor plus 200 to 300 basis points. The spread between those two numbers — equity cost versus debt cost — is most of why leverage matters at all.

Hearing it laid out this way did something to my mental model of leverage. It stopped being a finance-textbook word and started feeling like the engine — the thing that lets a developer carry more than one bet at the same time.

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

There's a frame the team uses for whether to green-light a deal at all — and it's much plainer than I expected.

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

Infrastructure was the part of the talk where every nice idea had to look at its own price tag.

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.

Except the reality has more gravity than "fair enough" can hold up. Bent Flyvbjerg, the Oxford megaproject scholar, has spent decades documenting that 91.5% of megaprojects miss their budget or schedule, and 99.5% miss at least one of cost, time, or promised benefits. He calls it the Iron Law of Megaprojects. That's the gravity every infrastructure ask gets pulled into, whether anyone in the meeting is naming it or not.

Every requirement costs money, and those costs have to fit inside a working pro forma.

That tension hung over the rest of the conversation.

Good development doesn’t mean promising yes to everything. It means finding the version of yes that the project can actually afford to deliver. Which may be why every developer talk eventually circles back to the same point: in the end, this is a relationships business.

Networking sounded practical, not performative

The networking part of the talk could have been a throwaway. It wasn't.

The message wasn't some vague "network more." It was more concrete than that: 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.

If that mindset is the underlying thing, here's what it looks like once I try to reduce it to habits.

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. • A site’s physical constraints often shape the best land use answer. • The developer’s job is deeply cross-functional. • Leverage matters because the spread between equity cost and debt cost can be enormous. • And the mindset that seems most valuable here is disciplined optimism.

So what — and now what

The phrase that kept circling in my head, disciplined optimism, turns out to have an older name. Jim Collins calls it the Stockdale Paradox: hold absolute faith that you will prevail in the end, and the discipline to confront the most brutal facts of the current moment, whatever those facts happen to be. Admiral James Stockdale survived seven years in the Hanoi Hilton because he could do both. The optimists, the ones who kept saying we'll be home by Christmas and resetting the date when Christmas came and went — Stockdale told Collins they died of broken hearts.

Real estate development isn't war. But twelve years is a long time to keep two truths in the same room.

A few things I'm going to do differently because of this:

• If you're a student thinking about real estate — optimize for relationship half-life, not deal flow. The career arc Hepfer described isn't really transactional. It's a long pattern of being someone people still remember after a loss.
• If you're a citizen watching a mega-project in your own city — stop asking does the rendering look good? Start asking can this developer survive twelve years of changing markets, politicians, and neighbors? That's the question that actually predicts whether something gets built.
• And if you, like me, are just trying to figure out what to bet your years on — Edward Glaeser puts it well in Triumph of the City: cities are the engines that turn poor people into rich people and poor countries into rich countries, because density is where ideas meet. Projects like Riverwalk are how cities get rebuilt for the next generation that arrives. That still matters even when the 10% feels too low and the timelines feel too long.

So no — development didn't sound easy after that conversation.

It sounded like one of the most stubborn kinds of work a person can choose. And maybe, for that reason, one of the most worth doing.