Move Fast and Break Things. Just Not Your House.

Mark Zuckerberg famously encouraged his early Facebook employees to “move fast and break things.” The philosophy helped define a generation of Silicon Valley entrepreneurs who came to believe that speed, experimentation, and a willingness to fail were essential ingredients of innovation. Rather than spending years perfecting a product before bringing it to market, the idea was to launch quickly, learn from mistakes, and improve through successive iterations.

It's a compelling approach to developing software, particularly when the cost of making changes is relatively low and the rewards for capturing market share are enormous. A flawed product can be updated, an unsuccessful feature can be removed, and a new version can be deployed to millions of users almost overnight. Failure becomes a source of information, and speed becomes a competitive advantage.

But what happens when someone who has spent a career working this way decides to build a custom home?

I've encountered a surprising number of successful technology executives who approach residential construction with the conviction that the industry is fundamentally broken. They see long schedules, extensive documentation, layers of consultants, and a seemingly endless procession of tradespeople, and conclude that the process must be ripe for disruption. Surely, with enough intelligence, determination, and financial resources, a better and faster way can be found.

I understand the impulse. In fact, I've spent a considerable part of my career thinking about precisely this problem. But there's a fundamental difference between accelerating the development of software and accelerating the construction of a building, and misunderstanding that difference can become extraordinarily expensive.

The Problem With Moving Fast

A substantial custom home in Northern California can easily take three years from the beginning of design to move-in, sometimes longer. Depending on the site, complexity, permitting jurisdiction, and construction approach, the schedule can vary considerably. But the underlying reality remains: designing and constructing a sophisticated building involves an enormous number of interdependent decisions and activities that must occur in a particular order.

Before a foundation can be poured, the building must be designed, engineered, permitted, and laid out. Before walls can be closed, structural connections, plumbing, electrical wiring, mechanical systems, insulation, and inspections must be completed. Before cabinetry can be installed, dimensions, equipment, finishes, and the work of multiple trades must be reconciled. Thousands of individual decisions must eventually converge into a single physical object.

These dependencies aren't simply administrative conventions invented by an inefficient industry. Many are consequences of the materials, technologies, and physical processes through which buildings are constructed.

Concrete needs time to cure. Structural systems must support the loads placed upon them. Waterproofing must be installed before it can be concealed. Mechanical equipment requires space, access, and connections to other systems. And unlike software, a building cannot be revised by issuing an update to everyone who happens to be using it.

Once materials have been fabricated and installed, changing course becomes a very different proposition.

The Cost of Iterating in the Field

During design, moving a wall six inches might require a few minutes of drawing and some coordination with the other consultants. During construction, that same change can affect foundations, framing, structural engineering, plumbing, electrical systems, cabinetry, finishes, and the work of several subcontractors.

What was once a relatively inexpensive decision becomes a chain of demolition, redesign, replacement materials, additional labor, and schedule disruption. The financial consequences are rarely limited to the cost of the immediate change. A delayed decision can affect work that follows, creating inefficiencies that ripple through the entire project.

This is one of the most important distinctions between designing a building and constructing one. Design is the appropriate place to explore alternatives, test assumptions, challenge ideas, and discover what doesn't work. Construction is where those decisions are translated into physical reality, and where experimentation becomes considerably more expensive.

That doesn't mean construction should be inflexible. Unforeseen conditions arise, discoveries are made, and thoughtful adjustments can improve a project. But there is a profound difference between responding intelligently to new information and beginning construction with significant portions of the design unresolved.

The former is an inevitable part of building. The latter is often a recipe for unnecessary expense and delay.

Why Construction Resists Disruption

I have some firsthand experience with the ambition to reinvent how buildings are made. In the early 2000s, I founded a company developing flat-pack prefabricated building systems. The premise was straightforward: if conventional construction was too slow, too expensive, and too dependent on skilled labor in the field, perhaps we could rethink the way buildings were designed, manufactured, transported, and assembled.

It was an extraordinary education.

What became clear was that meaningful improvements in construction productivity require more than a better scheduling application, a new management philosophy, or a more aggressive contractor. They require changes to the underlying building system itself.

A prefabricated building must be conceived around manufacturing, transportation, tolerances, connections, installation sequences, and the practical limitations of working both in a factory and on a construction site. The architecture, engineering, fabrication, and assembly processes have to be developed together. Simply taking a conventionally designed house and attempting to manufacture its components elsewhere doesn't necessarily solve the problem.

Real innovation in construction is possible, and I remain interested in the potential of prefabrication, mass timber, digital fabrication, robotics, and other emerging technologies. But these approaches demand substantial investment in research, development, testing, manufacturing infrastructure, and the coordination of entire supply chains.

They are fundamentally different undertakings from commissioning a one-of-a-kind residence.

A homeowner with a generous budget can purchase a great deal of architectural and construction expertise. What they generally cannot do, within the schedule of a single project, is reinvent an entire building technology and expect the resulting experiment to be faster, cheaper, and more reliable than established methods.

That kind of ambition might make sense for someone prepared to invest $100 million and ten years developing a new building platform. It makes considerably less sense for someone who wants to move into a beautiful home three years from now.

The Illusion of Saving Time

One of the most common ways clients attempt to accelerate a project is by shortening the design and documentation process. The reasoning is understandable: if construction is going to take a long time, why not begin sooner? Why spend additional months coordinating drawings when contractors could already be pouring foundations or framing walls?

Sometimes overlapping design and construction is entirely appropriate. Large commercial projects routinely employ carefully managed fast-track strategies, and certain residential projects can benefit from early work packages. But these approaches don't eliminate the need for coordination. They redistribute it, often while increasing the consequences of decisions that haven't yet been made.

Beginning construction before the design is sufficiently resolved can create the appearance of progress without actually improving the completion date. A contractor may be moving dirt, placing concrete, or erecting framing while critical decisions about structure, mechanical systems, windows, and finishes remain unsettled. Eventually, the unresolved questions catch up with the work.

And when they do, the construction team must either stop, improvise, or proceed based on assumptions that may later prove incorrect.

None of these options is particularly attractive.

The irony is that a client attempting to save three months in design can easily introduce six months of disruption during construction. The project may have started sooner, but it doesn't necessarily finish sooner.

Documentation Is Not Bureaucracy

Architectural drawings are sometimes misunderstood as a necessary but burdensome step toward obtaining a building permit. From that perspective, the goal is to produce enough information to satisfy the building department and then allow the contractor to figure out the rest.

For a sophisticated custom home, that approach misses much of the value of architectural documentation.

A well-developed set of construction documents is the result of an extended conversation among architects, structural engineers, mechanical and electrical engineers, interior designers, landscape architects, lighting designers, specialty consultants, and builders. Each discipline brings its own expertise, but the building ultimately has to function as a coherent whole.

The structural engineer's beams must coexist with the mechanical engineer's ductwork. Plumbing must fit within floors and walls without compromising structural integrity. Lighting, sprinklers, air distribution, and architectural finishes must share the same ceilings. Windows must coordinate with waterproofing, cladding, shading, and interior detailing. These relationships need to be resolved somewhere, and the most economical place to resolve them is usually before labor and materials have been committed.

Good documentation doesn't eliminate every question that will arise during construction. No set of drawings can anticipate everything. But it dramatically improves the likelihood that the people responsible for building the house are working from a shared understanding of what they're trying to accomplish.

The drawings aren't simply instructions for making a building. They're the record of thousands of decisions that have already been considered, tested, and coordinated.

The Fastest Path Is Often the Most Disciplined

There is a counterintuitive lesson here for clients accustomed to operating at the speed of technology: slowing down at the beginning can be the most effective way to accelerate the project as a whole. I call this the “going slow to go fast” approach.

A thoughtful design process allows alternatives to be explored while they are still inexpensive. Early collaboration with builders can reveal construction challenges, procurement constraints, and opportunities for simplification. Thorough coordination among consultants can identify conflicts before they become field problems. And a sufficiently complete set of drawings allows contractors to price, plan, procure, and execute their work with far greater confidence.

This doesn't mean spending unlimited time designing or documenting every conceivable detail. Good project leadership also requires knowing when enough information exists to make a decision and move forward. Indecision can be just as damaging as haste, particularly when it affects procurement or work already underway.

The objective is to establish a disciplined process in which decisions are made at the right time, by the right people, with an appropriate understanding of their consequences.

Speed then becomes a product of preparation rather than pressure.

What Clients Can Actually Control

A custom home is a significant undertaking, and even the best-managed projects encounter unexpected conditions. Weather, permitting, labor availability, supply chains, and the complexities of working with existing sites can all affect the schedule. No architect or contractor can honestly promise that every uncertainty will disappear.

But clients have considerable influence over the factors that are within their control. They can assemble a capable and collaborative team, establish realistic budgets and schedules, make decisions when they're needed, and resist the temptation to reopen fundamental questions after construction has begun.

Perhaps most importantly, they can recognize that the quality of the design and documentation process is directly related to the quality of the construction experience.

The right architect isn't simply someone who can imagine a beautiful house. It's someone who understands how to lead a complex design process, coordinate the contributions of multiple professionals, and translate architectural ambition into information that can be reliably built.

Similarly, the right contractor isn't necessarily the one who promises the shortest schedule. It's the one who understands the work, anticipates its challenges, and can demonstrate a credible plan for executing it.

The relationship between these two disciplines is especially important. When architects and builders collaborate effectively, problems are identified earlier, decisions are better informed, and the project benefits from the combined judgment of people who understand both design and construction.

Get It Right Before You Build It

I have enormous respect for the entrepreneurial instinct to challenge conventional wisdom. Much of the progress in architecture and construction has come from people who refused to accept that buildings must always be made the way they've been made before. We should continue to experiment with new materials, methods, and technologies, and I suspect the coming decades will bring meaningful changes to how we design and build.

But there's a difference between developing a new construction technology and attempting to force an established one to operate beyond its practical limits.

For the homeowner commissioning a custom residence today, the most reliable path to a beautiful, well-executed, fiscally disciplined project is rarely to move fast and figure things out later. It's to invest in thoughtful design, rigorous coordination, sound documentation, and a team capable of making good decisions before those decisions become expensive to change.

In software, the ability to fail quickly can be an extraordinary advantage. In construction, failure often means tearing out something you've already paid to build.

The opportunity is to do the experimenting on paper, where ideas can be challenged, revised, and improved with relatively little consequence, and to arrive at the construction site with the confidence that comes from having done the work.

Because when you're building a home intended to last for generations, the goal isn't simply to start sooner. It's to finish well.