← Blog

Innovation Has Been Killing the Planet (Part 2)

In part 1, Innovation is Killing the Planet, I discussed innovation's role in climate change. Innovation has created abundance, and abundance has created waste. And unfortunately, the built environment is the #1 producer of waste in the world...

January 18, 2020


In part 1, Innovation is Killing the Planet, I discussed innovation's role in climate change. Innovation has created abundance, and abundance has created waste. And unfortunately, the built environment is the #1 producer of waste in the world. Technology created this mess--but it's also the solution.

The next couple of blog posts will highlight the specific phases of creating a building and the many points of waste along the way.

Phase 1: Need.

The decision to build a building should be based on need. This need is based on user requirements. Here's our example: a lot of people like coffee in Brookhaven. Starbucks runs an analysis and determines there's a need for one of their stores in Brookhaven. They are Starbucks, so they must have some great data to back it up, right?

Not exactly. Here's what typically happens behind the scenes. There's a real estate developer out there who wants to make some money. So he runs around Brookhaven, finds a piece of property, and puts it under contract. He gets a civil engineer to create a site plan, pulls some demographic data, and builds the case for a Starbucks. This data is fairly simple. He creates a "book" to convince Starbucks. This includes competitive landscape (coffee shops in the area, nearest Starbucks) and demographic data, and it is skewed for success. Starbucks does very limited analysis of the deal. Why? Because they have so much money that they decide based on opportunity cost. They would rather open a location and shut it down in 5 years than miss out on a great opportunity. Hey retail developer friends--please correct me here if I'm wrong.

The developer negotiates a lease term and a rate. Starbucks signs a lease. The developer uses this lease to get a loan to close on the property and build the building. Motive check: the developer has now set his rent. That is not changing. Hopefully the price of the land didn't change, and he has a price for design and construction. Starbucks knows what these prices are because they want to get a deal. They have to sell a lot of $10 coffees to pay the rent.

So what's the problem? The reality is that Brookhaven doesn't need another Starbucks. The data was flawed; the scope was based on what Starbucks was sold, and not reality. The developer is not thinking about developing a property that will last for the next 50 years. This is short term thinking with a long term impact. Could technology have helped? Absolutely.

Phase 2: Definition/Design.

The developer hires an architect, who in turn hires engineers, landscape architects, etc. to build construction drawings. Starbucks has some templates of approved designs, but these need to be adapted to local conditions and codes. That seems efficient, right? Wrong again. The architect keeps iterating the drawings (ignoring BIM for the moment) because the developer wants the cheapest solution, but Starbucks wants the square feet and brand aesthetic. Every time there's another change to the drawings, every professional involved has to make changes. There could be hundreds of changes.

Then once the design is finalized (it's never really 100%), they ask a bunch of contractors to bid. The bidding process involves each general contractor calling a bunch of subcontractors asking them for a price to do the various pieces: electrical, drywall, etc. Let's say 3 general contractors bid a job. They will likely get prices from 3 electrical subcontractors each. So, approximately 9 electrical contractors are bidding the job. Multiply this by every trade… that's a lot of work in hopes of getting the project. 9 electrical contractors count all the light fixtures, conduit runs, receptacles, etc. They are all doing the same work. All wasting time and energy.

Finally, each general contractor picks the lowest subcontractor bids and adds everything up. The general contractor with the lowest total bid wins the job. It turns out the bids are 25% over budget. The developer gets mad and tells the architect to make changes to get the scope to meet the price. This is called value engineering (which makes no sense, by the way, because there's no engineering involved). Another few hundred hours of re-design, then re-bid and negotiation. Now we have a price that works and a building that's mediocre at best. Technology could (and has, to a certain degree) fix this entire process.

So what just happened? We designed a terrible building that isn't really needed. This will be continued in a few more posts. I will discuss what happens in the construction and management phases.

More News

Why BuiltTech, why now? My talk at Lat59 in Estonia. (Video)

Watch KP Reddy's talk about "Why BuiltTech, why now" at Lat59 in Estonia.

Read Post
Your building is talking. Are you listening?

Your building is talking. Eric Hall asks, "Are you listening?" Eric is Founder and Chief Innovation Officer at Site 1001, a smart building performance and operations platform that...

Read Post
Why the incubator system is broken.

When we launched Shadow Labs almost two years ago, I didn't want to call it an incubator. Instead, we called it a lab. We still call it Shadow Labs, but when people ask us what it is, we usually refer to it as an incubator...

Read Post