YT YouTube2Text

YouTube2Text → Transcripts → ARCH 1311 Lecture 12 - Video #2: Design Thinking

ARCH 1311 Lecture 12 - Video #2: Design Thinking — Transcript

by ArchitectureACC · 5,114 words · 774 segments · language en · Watch on YouTube

Open in transcriber Summarize with AI Download SRT/VTT

Full transcript

0:03in this lecture we're going to discuss
0:06the design process as it pertains to
0:08architecture we're coming up on the end
0:10of unit two talking about the profession
0:13of
0:14architecture and this is really a
0:16continuation of the subject of
0:19architectural projects and Architectural
0:23projects as we've discussed up to this
0:26point are a process all the timelines
0:32and procedures that we talk about in
0:35terms of Architects
0:37responsibilities and
0:40Construction and design are really all
0:45on a process and it's not necessarily a
0:49linear process meaning you do this then
0:52you do this some things on the
0:54architectural project process are but
0:57when we're talking about design it's
1:00more of a circular process meaning you
1:05have some ideas you keep adding more
1:08information you revisit those ideas you
1:12refine them you hopefully make them
1:14better and you kind of keep going in
1:17this forward moving yet circular type of
1:24process the design process is also
1:27integral to any discussion about
1:30architecture and Architectural design
1:33because you spend a great deal of your
1:36time as an architect and certainly an
1:38architecture student in the process of
1:40design and so because it's a practice
1:44like the practice of architecture you
1:47hopefully become better and better at
1:51making design
1:52decisions and that's really what we're
1:54talking about is how do you make design
1:56decisions how do you
1:58continually drive to uh make things
2:02better and um more refined along the way
2:06along that
2:12process when we talk about design and
2:15Architectural design specifically we're
2:17really talking about problem solving and
2:21often we hear people say well in
2:24architecture school I did design all the
2:26time and then I got out and started
2:29working and I feel like I don't do much
2:31design at all but I don't think that's
2:35necessarily true I think that when you
2:38are practicing the process of Designing
2:42that you are constantly honing your
2:46problem solving skills so whether it's a
2:49design problem or it's some other type
2:51of problem that you can apply that same
2:55process that you would in design to kind
2:59kind of any architectural problem so for
3:02example if you are working a design
3:06problem and you're constantly revisiting
3:09it and you're refining it and you're
3:12kind of going through this process and
3:13this procedure that let's say later on
3:16you have a technical problem or you have
3:20some building issue you can apply those
3:24same techniques to resolve the issue and
3:27so I think that when you become
3:30practiced and skilled at making design
3:33decisions and um moving your ideas
3:37through the design process that you
3:40become better at kind of problem solving
3:44in general and so really that that's all
3:46architectural design is it's continual
3:49problem solving and as issues arise
3:53you're trying to solve maybe more minor
3:56issues related to uh Central design
4:00problem or maybe they're major issues
4:02but if you keep kind of working through
4:05these ideas and constantly revisiting
4:08them refining them getting more input
4:12and making them better then the end
4:16result is going to be a much
4:20more rich and
4:23studied thing than it would have been if
4:26you had just said okay well here's my
4:29first idea for this for solving this
4:32problem and if it's your first idea and
4:35you havn't really thought about it not
4:36that the first idea can't be good but if
4:38you haven't really thought it through
4:41then maybe you're not really solving the
4:43problem you're just trying to come up
4:45with something in response to the
4:47problem
4:49so we look at that a lot in problem
4:52solving in terms of design you know are
4:54you really trying to solve the problem
4:56are you trying to resolve this or are
4:59you just trying to come up with
5:00something so that you can be done
5:02hopefully it's not the latter hopefully
5:03it's the former and hopefully that you
5:08are constantly kind of
5:10reworking your
5:12Solutions toward the end goal of
5:14becoming the best possible uh resolution
5:18to the
5:22problem architectural design is also
5:24about people now sometimes this gets for
5:29gotten a little bit and the irony is
5:32that often when you
5:34see famous works of architecture or
5:37buildings that are photographed they're
5:40pess which doesn't really make any sense
5:43because they are designed for people
5:46they're made for people to use
5:49and many of the design decisions that we
5:53make along the way as Architects are
5:56influenced by not just you know all
6:00humans but the specific humans who are
6:03going to be using the
6:04building we also look at issues of Life
6:09Safety you know Sheltering people
6:13preserving People's Health and so we
6:17have to kind of always remember that
6:19design is not necessarily this abstract
6:24formal
6:26exercise where architecture well it can
6:30be sculptural is not a piece of
6:32sculpture it will be inhabited by people
6:35and used by
6:39people architectural design is also
6:42about the place that it
6:45inhabits sometimes we refer to this as
6:48Place making or issues of place but
6:53design happens in an actual place it's
6:56kind of like people you know we can't
6:58forget that people are going to be
7:00occupying the architecture and the
7:03architecture is not floating in midair
7:05it's not on the moon it is in a place on
7:09Earth somewhere and that somewhere has
7:15issues that are specific to that
7:17location so that could be climactic
7:20issues it could be issues of topography
7:24or geography like in this
7:27photo it could be
7:30cultural Place related issues maybe
7:33local customs and local traditions and
7:36that really ties in to the issue of
7:40Designing for people because people will
7:44have characteristics of Being Human
7:47Beings but they will also have their
7:50own culture and traditions and practices
7:54and habits and behavior that are often
7:59very closely linked to the place in
8:02which those people
8:05inhabit so place can have many different
8:09influencing factors but we have to
8:11remember it's four people in a
8:17place architectural design is also
8:20aesthetic and so when we're discussing
8:24how a building is going to be used who
8:27is going to be occupying it where it's
8:30located we can't forget that we want it
8:34to look good also um but there are
8:36issues of form and
8:40composition
8:42Beauty the rhythm of the exterior and
8:45interior elements uh placement of
8:48Windows placement of
8:50doors um all kinds of things factor into
8:54the Aesthetics of a building and again
8:58the place and the people might also be
9:03heavily um influencing that
9:06because whatever people happen to
9:10believe is beautiful in that particular
9:13culture or that particular location
9:15that's going to have some impact on the
9:17Aesthetics of the building um because
9:21you know someplace in the world people
9:24may tend to favor a certain type of
9:28appearance or a certain type of look of
9:30buildings or even materials and that may
9:33appeal to them and that may not be the
9:36case somewhere else in the world so
9:38these things are all interrelated but
9:40they're all very critical components in
9:43terms of what the design can potentially
9:47be and what the overall design
9:52decisions uh will be made by the
9:57architect design for architecture is
10:00also
10:01technical when we
10:04discuss the building as a whole and also
10:08the individual parts of the building
10:10like all of the details that are you
10:14know converging together to make this
10:16whole building we need to look at issues
10:20of materiality and building science and
10:25comfort of the humans that are going to
10:28occupy this building
10:29again if it were simply a piece of
10:32sculpture it would be art only and not
10:37you know worrying about fire protection
10:39systems and exit stairwells and whether
10:43or not the seals on the windows
10:47are tight enough or not tight enough or
10:52the mechanical systems whether that's
10:54going to make people too hot or too cold
10:57inside
10:59so all of these technical issues come
11:02together and fuse with the Aesthetics to
11:07try and make something that is both
11:10beautiful and also beneficial to the
11:13people who are going to use it um we get
11:16into issues of
11:18efficiency
11:20and you know
11:23permanence
11:24and how long things are going to last
11:28and
11:30how well they're going to perform in
11:32that particular condition so again you
11:34know even technical issues we're basing
11:37decisions based on the people who are
11:40going to be using it and the place in
11:43which it
11:47exists this takes us to the central
11:51concept of an architectural design and I
11:56think most Architects would hopefully
11:58agree that the stronger your core
12:02concept with the design of your building
12:05the better off you're going to be in
12:06terms of making additional design
12:09decisions so if you can kind of early on
12:12as you gather information about the
12:14project if you can create kind of a
12:17strong central unifying concept then
12:21every time you have both major and minor
12:24design decisions to make you can kind of
12:26check it against your central concept
12:29and say is this in keeping with my
12:30concept and you can ask yourself kind of
12:33yes no and then it will help you to make
12:35some
12:37decisions in architecture we call this
12:39the party and this comes from a French
12:42term and it
12:44essentially uh
12:46means you know how you make decisions or
12:50um kind of the central concept of your
12:52decisions so the party is really kind of
12:55the unifying core idea
12:59of your
13:00design now as you start looking at
13:04buildings and maybe even analyzing other
13:08people's work it helps to know what
13:11their party was when they created the
13:13building sometimes
13:15it's a little bit easy to tell if you're
13:18visiting the building but sometimes it
13:20you can't sometimes you might think wow
13:22I really like this building but I'm not
13:24sure what their kind of core concept was
13:27in designing it but as we were looking
13:30at that video earlier where it discussed
13:34different Architects design
13:37processes um there was a building The
13:40Barnes Foundation in Philadelphia by
13:42Todd Williams and Billy Chen um they had
13:46this idea and it was a really simple
13:48sketch it one side said Gallery in a
13:52garden and the other side said Garden in
13:54a gallery and basically their concept
13:57was
13:59this art museum is is going to be very
14:02intense for the visitor because there's
14:04a lot of different um art pieces and if
14:09you were just to go into one giant room
14:11and put all these art objects in at one
14:13time you'd probably quite be quite
14:15overwhelmed and so they really thought
14:18about the experience of the visitor
14:22and had this idea that you would need
14:24some relief from the art as you moving
14:29through the gallery spaces and so their
14:31version of relief was to pull in nature
14:35and natural light and plantings and so
14:39on some places they showed that they had
14:42had um actual trees Central to some uh
14:47Gallery spaces and then in other places
14:51um there's an actual Garden or a split
14:54between the buildings and then there are
14:56pieces within that so that is one of
15:00those great Concepts where it's the idea
15:04once it's presented to you seems simple
15:08but I'm sure that you know it drove very
15:11complex decisions but it allowed them to
15:15keep coming back to that concept and
15:17saying is this related to the concept
15:20and a lot of times when you're in
15:22architecture school it's hard to
15:24understand why professors will keep
15:26saying well what's your concept you
15:28think well
15:30I don't know so you don't really want to
15:32come up with the concept after the fact
15:35I mean it it really does help you to
15:39create that concept based on information
15:42that you have potentially about the
15:45place and about the people using it and
15:48about the design problem and even based
15:51on that initial information a lot of
15:54times you can come up with a good part a
15:56strong concept that will drive all your
16:00decisions after that so you don't want
16:02to get to the end you're like well I
16:03guess my concept was whatever cuz that's
16:07not really the case if it didn't really
16:09help you drive all those decisions along
16:12the
16:15way in design we also talk about meaning
16:19and some buildings
16:22have more meaning than others to various
16:26groups of people um you know a lot lot
16:29of times we're talking about uh meaning
16:31on the side of the user now there could
16:35be meaning from the architect that was
16:39you know the architect tried to kind of
16:41imbue in the design but often times the
16:45meaning might evolve over time or as
16:49someone approaches a building or moves
16:52through a building they might have their
16:53own experience or connection with that
16:56building and that might have particular
16:59meaning to them so um it has a lot of
17:03different kind of facets when we're
17:06talking about architectural meaning this
17:08is a photo of the Dome of the Rock in
17:10Jerusalem and it actually holds a lot of
17:14religious significance but also cultural
17:17significance um for uh Islam
17:22Christianity Judaism and also the kind
17:26of cultural geography of the city
17:29and of the history of the region and it
17:33it really acts as a symbol for Jerusalem
17:37as a city and for the people who live
17:40there and so I'm sure that people who
17:44not only visit it but people who live
17:47there and um kind of go experience the
17:51building they might have their own
17:53meaning or connection associated with
17:56the building
18:00form is a huge part of architectural
18:03design and as you see Architects work
18:08and try and refine their process and
18:11refine their Design Concepts and their
18:14the actual design of the
18:16building formal issues are always you
18:19know very critical because a lot of
18:21times the form the mass the volume the
18:24shape of the building is really the B of
18:29the Aesthetics
18:31now you could factor in like materials
18:34and um other issues but the form often
18:39times really
18:41reinforces uh what the building is so
18:44this is the Air Force Academy Chapel in
18:48Colorado and the form of this building
18:51is is simple yet complex so you know
18:56when you first look at it it's like okay
18:58well there these repeating triangulated
19:01spires and that's it right it's just
19:04kind of the same pattern repeated over
19:06and over but because of the
19:09triangulation both at the top and bottom
19:12there're also these interstitial
19:14triangulated parts that stitch them um
19:17in between and then there's kind of this
19:20one uh almost seam that runs through on
19:24the two sides and then if you're looking
19:26at it from the ends you see this
19:29triangulated uh
19:31form that's reminiscent of many
19:34different types of chapels but this is
19:39um kind of a simple yet complex formal
19:43exercise but also very recognizable you
19:45know people who know this building when
19:48you see this form even if you see the
19:49outline of it or the shape of it you're
19:52very well aware of what that
19:55is and uh you know form can also be
20:01influenced by uh the people and the
20:04place but often the form is going to be
20:09driven by that party that strong
20:13hopefully strong central concept that
20:16will allow the architect to make
20:18decisions um with regard to
20:24form Theory and history are hugely in
20:28influential
20:30when the architect is going through the
20:32design process uh with regard to the
20:35building so sometimes when you're
20:39looking at a building especially a mo
20:41more modern
20:42building it's not like you'll
20:45see literal historical references where
20:49you might not see like you know a Doric
20:52column or some uh Roman reference to a
20:56building but you might might be able to
21:00tell that there's many layers of uh the
21:04architect's knowledge of history and
21:06Theory incorporated into the building
21:09and that's really what we're talking
21:10about is kind of having that base
21:13knowledge of theory and history so that
21:17you know um what Architects have done in
21:21the past what works what doesn't work
21:24and through your own practice you start
21:26to become aware of what works and what
21:28doesn't work and the theory and history
21:32knowledge also help to um drive those
21:36ideas of party and um the concept
21:40because there might be you know a
21:45fairly simple uh idea of architectural
21:49Theory or even some concept in
21:52architectural history that you can kind
21:54of utilize to help make some decisions
21:57even with a more modern
22:00structure most new architectural
22:03projects that you're working on and
22:06design problems that you're trying to
22:08solve typically require you to do some
22:12additional research and often that
22:15research involves studying some part of
22:20architectural history or theory that
22:23maybe you haven't looked at in a long
22:26time or you haven't visited before for
22:29and that can add a layer of richness and
22:35meaning and depth to your design
22:37decisions that you may not have been
22:39able to get any other way because the
22:42whole idea with the design process is
22:44that you don't want to become stuck you
22:47want to be able to um have ways
22:52to
22:53solve both minor and major problems that
22:57come up along the way throughout the
22:58design process so sometimes you know uh
23:02reading things or looking at uh
23:05additional buildings or historical
23:07buildings or really anything regarding
23:10Theory and or history can often
23:19help case studies are things that we
23:23look at to maybe analyze a building that
23:27has
23:29either been built or designed or existed
23:33previously in some way but a lot of
23:35times a case study will be almost like a
23:39picking apart of a building to examine
23:42all the individual workings and pieces
23:45of it either from a design point of view
23:48or from a technical point of
23:50view uh this is another way in which you
23:53can kind of
23:55analyze things that maybe you're trying
23:58trying to resolve in your particular
24:01design problem and it might be a way of
24:05learning about new systems or new
24:08processes in construction or building
24:11science that you haven't yet come across
24:14or you haven't used before it may even
24:18be that you are working on a new type of
24:20building that you haven't yet
24:23encountered or maybe you haven't worked
24:25on in a while and you can look at case
24:28studies to try and see what the current
24:31technology is on those particular
24:34buildings so case studies can be hugely
24:37helpful in terms
24:39of making design decisions and kind of
24:42uh adding to your knowledge to
24:45effectively make design decisions as you
24:50go building
24:53typologies are or building typology is
24:56looking at
24:58kind of all the variations of a
25:00particular building type that you happen
25:02to be working on so this one
25:06shows some isometric 3D views and plan
25:10views of all different types of
25:13apartment units and in architecture we
25:16just refer to that as multifam so
25:18instead of just saying apartment multif
25:20family describes any
25:22configuration of living units that are
25:25attached and these are all attached in
25:29wildly different configurations some
25:31have Towers some have
25:34Courtyards some have Terraces or penth
25:37houses but looking at the typology of
25:42the apartment building kind of helps to
25:46sort out your own ideas about the
25:49project that you happen to be working on
25:51CU sometimes looking
25:53at all these individual
25:56variations it's it's almost like seeing
25:59a a
26:01pattern all together of the same type of
26:05building and so often that helps to
26:08organize your thoughts about what it is
26:10that you're currently working on and
26:13sometimes it helps to influence various
26:17schemes that you might be thinking about
26:18or various variations on a particular
26:22design scheme that uh applies to your
26:26current project
26:30iterations are
26:32just different instances or different
26:35variations on the same project so for
26:38example if I were designing a building
26:41and you see this in these models and
26:44kind of these broken apart little 3D
26:47pieces on this particular model um the
26:50iterations are all of the different
26:53versions of that design so when we talk
26:58about something being iterative and
27:01you'll hear this quite a bit and I feel
27:04like Architects love that word iterative
27:06but it just means that you are working
27:09through the solution to the problem over
27:11and over and it's you didn't just come
27:14up with one solution to the design
27:16problem and then you said yep that's it
27:18that's what we're building you came up
27:21with many different variations and many
27:23different versions of it and not just
27:26all at once but you are
27:28refining and revising and kind of
27:31continually going through that design
27:34cycle to try and get to the best
27:36possible result or the best possible
27:42outcome and that leads us to design
27:45thinking now design thinking is a
27:47concept that you'll hear applied to all
27:51different professions and all
27:55different uh areas of study and you know
28:00uh
28:01businesses but really this is what
28:04architectural design is and this is not
28:08a a common uh kind of
28:11procedural path in in architectural
28:15design to teach these actual steps but
28:19you know design thinking is applied to
28:21so many different things in modern
28:23society these kind of five steps that I
28:26think it's a bit easier to kind of break
28:29architectural design down into these
28:31steps because it directly applies this
28:33is what we're doing anyway it's just
28:35that sometimes Architects can identify
28:38like yes these are the actual steps that
28:39I'm going through but um there is an
28:43assignment that you're going to be doing
28:45where you're going to need to go through
28:48some design steps and it's going to be
28:50very helpful to use these steps as a
28:54pathway for you to work through the
28:56problem instead of just staring at
28:58something and going I have no idea what
29:01I'm supposed to be doing I've got this
29:02design problem I don't know how to come
29:04up with a solution working through these
29:07steps is a great way to kind of guide
29:09you through the process and hopefully as
29:12you do this you won't end up in a kind
29:16of uh writer block for Architects stuck
29:20phase right so um when we look at this
29:24we have these five main steps we've got
29:27the first one is to empathize and just
29:29going left to right we need to empathize
29:33with the person or people for whom you
29:37designing so this describes it as the
29:39audience so again it goes back to that
29:42idea that architecture is for
29:44people and then we're going to construct
29:47a point of view that's based on user
29:49needs and insights and so that's
29:52defining the problem or and it might not
29:55even be defining the architectural
29:57problem but I think Define that is a
30:01great place to Define your part or your
30:05core
30:06concept because at the beginning you're
30:08probably given the design problem with
30:11the user and the place and so in the
30:14empathize State you start to begin
30:18to uh recognize the users and what their
30:22needs
30:24are so when we look at that first
30:29step EMP empathizing could mean a lot of
30:32different things if it is a culture or
30:35group of people that you're unfamiliar
30:38with just doing a lot of research and
30:41learning more about how they're going to
30:44use the building communicating directly
30:47with the users of the building um
30:49getting to know whoever the client is to
30:53really get a feel for what it is that uh
30:58will be best suited to their needs and
31:00so if you can empathize with the
31:04user then along the way you're going to
31:06make much better decisions because if
31:08you don't know who the users are and
31:11you're just making this building for
31:13some kind of unknown person then your
31:16decisions aren't going to be as
31:18effective because you're not empath
31:20empathizing with their situation or
31:23their needs or ultimately what the
31:25building should be for them
31:31so the second step is to Define and I
31:35would say here defining means defining
31:38your core concept you know based on
31:41knowing where the location of the
31:43building is you would know the location
31:46and place at this point you're going to
31:47know the people and the users you've
31:51talked to the users you've communicated
31:53with them so that you can empathize with
31:55them and their needs and
31:58defining
32:00the party at this point is is really
32:03critical and that's because the problem
32:06has already been defined for you before
32:08that so the problem was probably defined
32:10by the users thinking well we need a new
32:13building or we've outgrown our facility
32:15or we need to renovate or we need to add
32:17on so that the problem is kind of
32:20predefined but defined here means you as
32:23the designer need to Define what your
32:27concept for the project is going to be
32:29and what your part
32:35is and then the third step is to ideate
32:40and ideate means just get your ideas for
32:44this project out of your head and onto
32:47some format where you can record it now
32:50that could be a piece of paper um a
32:54Sketchbook a
32:56notebook a voice recorder just anything
32:59where you're going to be able to just
33:02kind of let your ideas about the project
33:05spill out you don't want to try and edit
33:07yourself at this point because it's like
33:10no idea is a bad idea at this point
33:13you're just trying to get out any
33:15thought that you have at all about this
33:18project and then as you ideate a lot
33:23more then you can start to kind of sort
33:25through the ideas like okay well
33:28maybe um this kind of works with the
33:31concept that I have and maybe this um
33:34really starts to align with my part and
33:37this might start to organize the spaces
33:40and work for the user and things like
33:42that so um you ideate just you know it's
33:46like a brainstorming session um and this
33:49could last a short time or or a long
33:52time but the idea is for you to really
33:54brainstorm a lot of ideas and you know
33:58again there are no bad ideas at this
33:59point because even if something that you
34:02draw is either a hideous drawing or a
34:05bad idea it's just on paper and so it's
34:08no big deal it's just part of the
34:10process so when we get into our design
34:14assignment too you really want to focus
34:17on the process don't worry about the
34:19product especially at the ideation phase
34:23because you're just getting ideas out
34:25and trying to brainstorm
34:29now once you've ideated and you've you
34:32know gotten a bunch of ideas kind of out
34:34of your head then you can begin
34:37prototyping and prototyping in
34:39architecture means either making some
34:42models uh making some drawings uh maybe
34:46you make a rendering or a photo collage
34:49or just something that starts to
34:52resemble some form of a building now
34:55maybe it's really rough at this point
34:58but that's okay that's that's the idea
35:01and
35:01so as we look at different tools for
35:04design communication whether
35:07it's a 3D representation or 2D sketch or
35:11some kind of 2D you know photo
35:16rendering the prototyping just starts to
35:19represent some of those ideas now you
35:22could Prototype all the ideas that you
35:25had done in the ideation phase but
35:27that's going to be a lot so you're
35:28probably going to start editing at this
35:32point and saying okay of these 50
35:35Concepts that I brainstormed or these 50
35:37forms that I brainstormed I'm going to
35:39try and make a model of five of these or
35:43seven of these and then you can see what
35:46they look like and then maybe of those
35:48seven you can say okay I think I've got
35:51three or four good ones and the other
35:53few are pretty hideous so then maybe uh
35:57of those those those three or four that
35:59you think are the best ones that you
36:02prototyped then you go into the last
36:04phase which is testing it and testing it
36:08um for architecture just means showing
36:10it to the client saying okay you're the
36:13user I'm testing this out on you what do
36:16you think and again this is you're in
36:19early stages and they might say I hate
36:23all of these or I love all of these or I
36:26like parts of this and not of the other
36:29but you're not going to build what
36:31you've got in your hands at this point
36:33you're just kind of going through the
36:35initial design process and then what
36:38happens is of those five steps then
36:41after you test it maybe the client says
36:44like okay I like this part of this I
36:46don't like this part but you know it's
36:47kind of back to the drawing board that
36:49doesn't mean you throw everything out it
36:51means you start refining and continually
36:54reworking those steps in the process now
36:57you're not going to go back to Step One
36:59to empathize with the user because you
37:01already know the user at this point
37:03probably not going to um
37:05completely redefine your concept you
37:08might based on some you know information
37:11that you get but you're probably just
37:13going to slightly refine or redefine
37:16slightly your party or your concept
37:19mostly what happens is you keep like
37:22reworking those last three steps in a
37:24circular way you go back to
37:28uh ideate you maybe you do some more
37:30sketches or then you prototype some of
37:33those maybe you just revise some of the
37:36prototypes that you made and then you go
37:38test it again you go talk to the client
37:40you talk to um the other architects in
37:42your firm you know you're bouncing ideas
37:45off each other and then you go keep
37:47going back to the client to see what
37:49works and so this process you know is
37:52super helpful in terms of just Contin
37:57contining to cycle through instead of
37:59saying well I came up with this one
38:01thing and they didn't like it so I guess
38:03that's over that's not really how it
38:05works you're constantly refining you
38:08don't give up you just kind of keep
38:10working through it and um you know as
38:15you keep taking the rough edges off and
38:18continually reworking it hopefully you
38:20end up with a a really good scheme um at
38:24the end of the design process and then
38:27you take it through the rest of the kind
38:29of architectural project phases where it
38:32becomes closer to reality and
38:34construction

About this transcript

This page contains the full transcript of ARCH 1311 Lecture 12 - Video #2: Design Thinking by ArchitectureACC, generated from the public captions YouTube serves with the video. The transcript has 5,114 words across 774 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to translate the transcript into 100+ languages.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.