Insight
One atomic statement made by an expert, a student or a publication, with its evidence status.
Expert Open for expert review · What do these labels mean?
On a commercial developer scheme, the brief’s setbacks, height and podium rules were fed into a generative engine; massing options were filtered by daylight, solar, microclimate and view-factor KPIs. The novelty was inviting the client into the process and surfacing KPIs up front.
— Paraphrased from the lecture
| Where in the source | mid — anchor: “we brought the KPIs up front” |
| Confidence | high |
Context
Jakob Strømann-Andersen (Henning Larsen)‘s second example of computational design is a developer-driven case for a very commercial investor (the name is garbled in the transcript), done with a local architect, where the client asked for a quick design brief and vision.
From the transcript
So there was some restriction of square meters, height restriction, podium and […] instead of doing a lot of [architectural] ideas, we put it into the engine and then start iterating and designing with those setback rules and podium rules. Then we did a lot of studies about daylight, solar and microclimate. […] and some of the more KPIs on view factor. Then we start filtering in it and use very much […] the client about like what is their business case […] What we did here was […] we invited the client into the design process instead of giving them the result, we invited them and understood the business case and then we brought the KPIs up front in the design process.
Automatic transcript, presentation, middle part. Lightly cleaned: repeated words and fillers removed, omissions marked […], editorial insertions in [brackets].
Connections
Something wrong or missing? Suggest a correction