Excerpt

Successful development rarely begins with a drawing. It begins with asking the right questions—about the site, the market, constraints, value, and the path from possibility to execution.

---

Development Begins Before Design

There is a natural temptation when looking at a property with development potential:

Start designing.

How large can the building be?
How many units might fit?
What should it look like?
How much square footage can we create?

These are important questions—but they may not be the first ones to ask.

Before meaningful design begins, a development opportunity needs to be understood from several perspectives at once: the site, regulations, market, economics, physical constraints, design possibilities, and path to execution.

A compelling concept does not automatically make a viable project.

Likewise, a difficult site does not automatically make a poor opportunity.

The quality of the development strategy often depends on what is understood before major decisions are made.

Here are five questions worth asking before you build.

---

1. What Does the Site Actually Allow?

The first question sounds simple.

It rarely is.

A property’s development potential cannot be understood from lot size alone.

Zoning may establish the broad framework, but actual development capacity can be influenced by factors such as:

• Allowed uses
• Density
• Floor area
• Building height
• Setbacks
• Lot coverage
• Open-space requirements
• Parking
• Access
• Existing improvements
• Easements
• Utilities
• Topography
• Environmental conditions

In other words:

What zoning allows in theory and what a site can realistically support are not always the same thing.

California’s Department of Housing and Community Development makes this distinction when evaluating realistic development capacity. Its guidance considers factors including development standards, existing uses, lot size and infrastructure—not simply theoretical zoning capacity.

That same thinking is useful at the individual-property level.

Before asking what to design, understand the development envelope.

What is possible?

What is constrained?

And where is there room to create value?

---

2. What Does the Market Actually Need?

Just because something can be built does not mean it should be built.

Development is ultimately connected to people, businesses and markets.

That means understanding more than recent comparable sales.

Depending on the project, useful questions might include:

Who is likely to use or buy this property?

What alternatives already exist?

What is changing in the surrounding neighborhood?

Which property types appear oversupplied?

Where might demand be underserved?

How important are location, views, outdoor space, parking, flexibility, amenities or design quality to the intended market?

Demographic and housing data from the U.S. Census Bureau’s American Community Survey can help establish part of that context, providing information on housing characteristics, households, income and other local conditions.

But data alone does not make the decision.

The purpose of research is not to accumulate information.

It is to develop a clearer point of view.

A strong development concept should respond to both the property and the people the property ultimately needs to serve.

---

3. Where Are the Real Constraints?

Every development project has constraints.

The mistake is treating all constraints as equally important.

Some may be manageable.

Others can fundamentally change the project.

Consider a hillside property.

The slope itself might initially appear to be the primary problem.

But deeper analysis could reveal that the more important issues are:

access + grading + retaining conditions + building height + construction complexity.

Or consider an existing commercial property.

The building may look outdated, suggesting redevelopment.

But the more valuable strategy might depend on:

existing use + entitlement position + renovation cost + replacement cost + market demand.

The point is not to eliminate constraints.

The point is to identify which constraints actually drive the project.

California HCD’s guidance similarly recognizes that land-use controls, development standards, permitting processes, infrastructure and other governmental and nongovernmental factors can affect housing development feasibility.

This leads to a useful development principle:

Don’t design around every problem. Identify the few problems that shape everything else.

Once those are understood, the strategy becomes much clearer.

---

4. Which Decisions Create the Most Value?

Development projects contain hundreds—sometimes thousands—of decisions.

But not every decision has the same impact.

A finish selection can matter.

A fixture can matter.

A material can matter.

But long before those decisions occur, a handful of larger choices may determine much more of the project’s ultimate value.

For example:

Site Planning

Where should the building sit?

Program

What should actually be built?

Massing

How should the project’s size and volume be organized?

Access & Circulation

How do people and vehicles move through the property?

Views & Orientation

What should the project face, preserve or capture?

Usable Area

Are we maximizing square footage—or maximizing useful square footage?

Indoor / Outdoor Relationship

Can the site itself become part of the experience?

Construction Complexity

Is additional design complexity creating enough additional value to justify its cost?

These are not purely architectural questions.

They are development questions.

And they often have greater financial consequences than many decisions made later in the project.

---

More Is Not Always More Valuable

This deserves special attention.

Development discussions often focus on maximizing:

square footage

or:

unit count

Sometimes that is absolutely the correct strategy.

Sometimes it is not.

The largest building envelope may create awkward circulation.

Additional square footage may increase construction cost without generating equivalent market value.

More units may compromise parking, outdoor space or market positioning.

A complicated structure may technically maximize the site while weakening project economics.

Development therefore should not simply ask:

How much can we build?

It should ask:

What should we build—and why?

Those are very different questions.

---

5. What Is the Clearest Path to Execution?

A development concept only creates value if it can move forward.

That means strategy must eventually connect:

Opportunity → Decision → Design → Approval → Construction → Use

Projects often become unnecessarily difficult when these stages are treated independently.

A concept is created.

Then planning issues appear.

The design changes.

Then structural realities appear.

The design changes again.

Then construction pricing arrives.

The project changes again.

Not every change can be prevented.

Development is inherently iterative.

But better early coordination can reduce avoidable surprises.

Before moving deeply into design, it helps to understand:

• Likely approval pathway
• Required consultants
• Major technical studies
• Utility conditions
• Entitlement requirements
• Probable construction approach
• Major cost drivers
• Critical decisions
• Project sequencing

California’s Permit Streamlining Act establishes timing and procedural requirements around development applications and agency review, while local jurisdictions retain their own project-specific approval processes and requirements.

Understanding the pathway does not guarantee a particular outcome.

It does something more practical:

It helps turn an idea into a plan.

Build With Clarity

Good development does not begin with certainty.

Every project contains unknowns.

Markets change. Costs move. Regulations evolve. Site conditions reveal themselves. Design develops.

The objective is not to predict every outcome before beginning.

It is to create enough clarity to make the next important decision well.

Research helps us understand the opportunity.

Analysis reveals constraints.

Strategy establishes direction.

Design gives that direction form.

Execution turns it into something real.