Why homebuilders struggle to scale new initiatives

Despite the reputation production homebuilders get for resisting change – and failing at innovation – the best path to a homebuilding team member’s career advancement is by evangelizing a passion project. Homebuilders have dozens such initiatives in progress at any given time across their various departments, divisions and workflows.

So how does inertia survive in our industry despite these big incentives to innovate?

How an innovative idea normally spreads

An operations leader trials something new in their division, then shares the idea with a few friendly peers in other divisions. If those divisions carry out an experiment that produces an equally impressive outcome, they have formed a coalition of sponsors who can present the idea at the next meeting of whatever inter-divisional committee handles that topic.

If the approach is widely understood and flexible enough to implement in a way that each division feels best suits their unique operation, it tends to catch its own momentum. Holdout divisions are more likely to be slowly nurtured through the barriers to adoption than bullied into conformity.

Most initiatives fail because of a handful of common dynamics in builder organizations.

Despite the individual career incentive to innovate, builders are disincentivized from being first. Divisions avoid open conflict. Corporate avoids the perception of a cramdown. And the most stagnant initiatives are the ones that need complete buy-in from everyone before they have even proven out the concept.

None of these modes of failure have much to do with whether the idea itself is any good.

All parties are acting rationally

The first division to pilot an initiative carries the cost of resources spent building it and the risk that it does not work, while later beneficiaries simply adopt a functioning system that is already built. Being last to invest in a challenging initiative that produces a shared benefit is a rational decision.

Not every initiative that helps the company benefits every division equally. National rebate or supply contracts, for example, are usually tiered to reward volume, so the largest divisions capture most of the upside while smaller ones see comparatively little.

In a market with a mega-trade whose own volume dwarfs what the homebuilder buys across all its divisions combined, that trade may already be pricing as competitively as a national contract, leaving little room for the national deal to actually beat what’s already on the table.

Both are legitimate reasons to hesitate, but divisions shy from expressing them directly. Saying an idea is wrong for the company, or that it does not serve the company equitably, invites a debate nobody wants to stir up in a committee meeting. “We’re not ready” or “this doesn’t apply to us” are two indefinitely renewable excuses that end the conversation at once and cost nothing.

Corporate does not like to test its own authority

Homebuilders structure themselves around corporate consolidation of capital and balance sheets, not the consolidation of operations. Firms build corporate’s authority to oversee what divisions report, not to engineer what divisions do.

Because of that, corporate rarely pushes back on divisions’ excuses. The faintest sign of support for one division’s proposal can be interpreted by other divisions as the opening move toward a mandate. A modest ask to adopt a shared format or contribute data to a common structure gets the same response as a top-down directive, and divisions react to the authority they imagine corporate has, not the authority it is exercising.

That arrangement works well for everything a homebuilder needs centralized. But it also means corporate teams are just powerful enough to shut down an initiative when a division starts acting outside the bounds of established infrastructure, while never being powerful enough on their own to commit resources to a full-scale rollout of a novel idea.

Some ideas cannot start small

Another dynamic is divisibility – an economic term repurposed here for whether it is practical to split a good initiative into smaller units that each deliver value on their own, or whether it only has value once the whole thing exists.

High divisibility initiatives, such as a training program for the sales team, offer any participating division value regardless of the reach of their adoption across other divisions. A single division can pilot the idea, capture the benefit, and refine it entirely on its own timeline, independent of what any other division decides.

This is why bottom-up adoption works so well for this category: the concept proves itself before anyone else buys in, which is what lets a coalition of sponsors build momentum one division at a time.

Low divisibility initiatives have no smaller unit that pays for itself: they either exist company-wide or they do not really exist at all. A shared cost code taxonomy to support ERP enhancements that organize unit-cost estimating is a clean example – maximally beneficial and financially only workable to implement as a scaled, enterprise-wide solution.

That difference changes what bottom-up effort can do. Low divisibility initiatives require outsized first investment. It is unrealistic that a single division would have the resources or the knowledge to build a solution that fully meets their own division’s needs, let alone those of their entire organization. At the pilot stage, these initiatives rely on effort over infrastructure: a new role to support a move to centralized scheduling, or a homegrown database to capture material take-offs.

Low divisibility initiatives, regardless of how good the idea is or how much enthusiasm the sponsor builds, suffer the most inertia. And this is where corporate’s learned caution does its worst damage. A low divisibility initiative is the one case where corporate’s involvement is not optional. No division can build it alone, and the same trust deficit that makes corporate hesitant to support a simple shared format is even harder to overcome when requirement No. 1 is real investment in shared infrastructure.

When is innovation possible?

A leadership team that understands what sparks common objections to novel ideas has a chance to call them out. Anyone at the table can test whether “this doesn’t apply to us” masks an underlying philosophical disagreement by asking what the objection would sound like were it conveyed about the whole company, rather than about one division. Clarifying who would fund or build the new initiative alone tests divisibility.

 A genuinely low divisibility initiative cannot stand up and sustain itself drawing on the resources or domain expertise of a single enthusiastic division.

Inventing a solution, proving it works, and packaging it into a form any division could adopt with minimal resources takes a markedly different skill set than building homes. That is why the most innovative solutions homebuilders adopt today tend to be bought, not built.

From finding land, to training the next generation of superintendents, to spending marketing budgets effectively, the solution that works at scale tends to come in the form of a subscription product built to be globally applicable and locally customizable.

The entrepreneur who builds the product that solves an initiative gets to divide the work across people who design it, make a persuasive case for it and implement it. A homebuilder vice president working solo faces all that work while running a division.

A full-time designer focused on scalability faces a more tractable problem than the homebuilder because a genuinely global solution requires an elegant idea, while reconciling a group’s individual ways of doing things requires political deliberation.

A full-time salesperson or a marketing professional has a completely clean slate advocating for an initiative within a builder organization, while the VP must work against whatever petty grievances other divisions may have racked up over years of working together. Homebuilders often pay for the implementation of new systems, but how often do they make the same investment in a completely internal initiative?

The future of innovation in homebuilding will look more like procurement than invention. Inertia survives despite every individual incentive to innovate because homebuilders are better at building homes than they are at designing systems to build homes at scale.

The industry does not lack for people willing to champion ideas. It has a shortage of ideas good enough to survive being built by someone with a day job.