Buildings are products, not projects.
Who This Matters To (And Why)
Critical: Developer,Architect,Investor. These parties make or lose money directly based on this thesis.
Important: GC,Banker,Broker. These parties execute decisions shaped by this thesis.
Context: City,Engineer,Interior Design. These parties need to understand it to avoid friction.
Highest typology impact: Multifamily,Office,Mixed Use,Hotel. Lower impact: Retail,Industrial.
Buildings are products. They have users, features, and release cycles. Projects are how amateurs think about them.
How It Shapes Development
Buildings are products because they are manufactured objects that generate revenue streams over extended operating periods. A project is a one-time endeavor with a defined end. A product is a repeatable offering that serves a market. A multifamily building serves a rental housing market for 30–50 years. Its floor plans, unit features, and amenity set are product decisions that determine its competitive position in that market. A building that was designed as a project — optimized for delivery on time and on budget, with no regard for 10-year operating performance — will underperform a building that was designed as a product from day one.
Product thinking changes the design decision calculus. A project manager asks: does this design choice affect construction cost or schedule? A product manager asks: does this design choice affect occupancy rate, rent trajectory, or operating cost over the life of the asset? Durable flooring that costs $3/SF more than standard costs $300 per unit in construction. If it reduces flooring replacement from every 7 years to every 15 years, the net present value of the savings over a 30-year hold period is positive at any reasonable discount rate. Project thinking says the $300 is an overrun. Product thinking says it is an investment with a calculable return.
Iterative product improvement is not standard practice in building development. Most buildings are designed once, built once, and then operated without feedback informing future designs. The developer who delivers a 200-unit building and moves on to the next project without analyzing which unit types leased fastest, which amenities were used most, and which building systems generated the most maintenance calls is discarding the product feedback that would improve their next building. Consumer product companies treat post-launch feedback as their most valuable design input. Development companies treat it as someone else's problem.
Product liability thinking should extend to building design. A manufactured product that fails causes the manufacturer to pay warranty claims, suffer reputational damage, and lose market share. A building that fails — HVAC system breakdown, water intrusion, elevator downtime — causes the owner to pay operating costs, suffer tenant attrition, and accept rent discounts. The developer who treats the building as a product takes responsibility for performance over the hold period. The developer who treats it as a project hands off responsibility at certificate of occupancy and moves on. The market ultimately prices the difference: buildings with strong operating performance trade at lower cap rates because investors recognize the product quality.