1 00:00:00,408 --> 00:00:03,528 Evan Troxel: This episode of the TRXL podcast is made possible 2 00:00:03,528 --> 00:00:05,108 with support from ArchIT. 3 00:00:05,495 --> 00:00:08,315 Are you tired of standard IT services that missed the mark. 4 00:00:08,525 --> 00:00:13,955 Choose ArchIT for specialized proactive, IT management, BIM support and robust 5 00:00:13,955 --> 00:00:16,295 data security tailored for architects. 6 00:00:16,595 --> 00:00:20,805 Whether you're a team of 10 or a growing firm of 50+, ArchIT understands 7 00:00:20,825 --> 00:00:24,515 the architecture industry and will empower your unique, creative vision 8 00:00:24,695 --> 00:00:26,705 to enable you to do your best work. 9 00:00:27,015 --> 00:00:31,515 Embrace a technology team that enhances, not hinders, your design process. 10 00:00:31,815 --> 00:00:37,635 Visit GetArchIT.com for your free IT assessment and start transforming your 11 00:00:37,635 --> 00:00:39,855 firm and your tech experience today. 12 00:00:40,185 --> 00:00:44,535 That's GetArchIT.com. 13 00:00:46,473 --> 00:00:47,953 Welcome to the TRXL podcast. 14 00:00:48,093 --> 00:00:49,023 I'm Evan Troxel. 15 00:00:49,353 --> 00:00:53,103 In this episode, I welcome Shane Burger back to the podcast. 16 00:00:53,133 --> 00:00:56,553 Uh, Shane is an internationally recognized leader in the advanced 17 00:00:56,553 --> 00:01:00,303 use of technology in design and experience for the built environment. 18 00:01:00,783 --> 00:01:04,923 And as a Principal at Woods Bagot, he directs a vision centered on 19 00:01:04,923 --> 00:01:08,973 technical innovation and leads a global team dedicated to researching, 20 00:01:09,183 --> 00:01:14,193 developing, and applying new models of design and delivery to projects. 21 00:01:14,413 --> 00:01:19,483 He has lectured widely on a range of topics, including design computation, BIM. 22 00:01:19,753 --> 00:01:24,973 Digital fabrication, building performance, VR, and AR smart buildings 23 00:01:25,183 --> 00:01:27,283 and digital culture and experience. 24 00:01:27,593 --> 00:01:31,402 Starting in the early two thousands, he was an early advocate and active 25 00:01:31,402 --> 00:01:35,393 developer of design computation methodologies in the AEC industry. 26 00:01:35,393 --> 00:01:35,423 Uh, 27 00:01:35,649 --> 00:01:39,939 During that time, his built work at Grimshaw architects focused on the 28 00:01:39,939 --> 00:01:42,729 design of arts and cultural institutions. 29 00:01:43,119 --> 00:01:47,469 And used an array of computational processes to synthesize geometry 30 00:01:47,739 --> 00:01:50,139 analysis and material fabrication. 31 00:01:50,499 --> 00:01:54,908 He also served for eight years as a director of the design computation 32 00:01:54,908 --> 00:01:59,619 and education non-profit smart geometry, firmly positioning it at the 33 00:01:59,619 --> 00:02:04,809 intersection of art design technology and the modern human experience. 34 00:02:05,259 --> 00:02:09,309 At smart geometry, he promoted the emergence of a new paradigm for 35 00:02:09,309 --> 00:02:13,629 digital designers and craftsmen where mathematics and algorithms 36 00:02:13,659 --> 00:02:16,299 are as natural as pen and paper. 37 00:02:16,759 --> 00:02:21,269 In this episode, you'll hear that before I had the chance to formally welcome Shane 38 00:02:21,289 --> 00:02:24,949 back to the show, we were chatting about what we were going to talk about, and it 39 00:02:24,949 --> 00:02:26,989 was so good I just had to leave it in. 40 00:02:27,259 --> 00:02:31,549 So the setup here for Shane's launching point is a tweet thread. 41 00:02:31,609 --> 00:02:35,599 He posted about software licensing models in AEC, which 42 00:02:35,599 --> 00:02:36,799 I've linked to in the show notes. 43 00:02:37,219 --> 00:02:41,209 So anyway, if you're wondering why it sounds like I didn't welcome him to the 44 00:02:41,209 --> 00:02:43,129 show, like I usually do with my guests. 45 00:02:43,429 --> 00:02:45,799 Now you are prepared for the cold open. 46 00:02:46,319 --> 00:02:50,279 Today we talk about current and potential future impacts of AI and 47 00:02:50,279 --> 00:02:52,439 automation on architectural practice. 48 00:02:52,799 --> 00:02:56,819 The shift from perpetual to per user licensing in AEC 49 00:02:56,819 --> 00:02:58,199 project delivery software. 50 00:02:58,589 --> 00:03:00,479 License management difficulties 51 00:03:00,789 --> 00:03:04,719 enhancing productivity and improving project delivery while maintaining a 52 00:03:04,719 --> 00:03:08,889 human centric approach re-evaluating business models towards valuing 53 00:03:08,949 --> 00:03:14,049 outcomes and performance, rethinking workflows, balancing technological 54 00:03:14,049 --> 00:03:18,159 advancements, and the essence of human intelligence and empathy. 55 00:03:18,639 --> 00:03:19,239 And more. 56 00:03:19,639 --> 00:03:23,478 This once again was a fantastic conversation with Shane and I 57 00:03:23,478 --> 00:03:26,539 hope you'll not only find value in it for yourself, but that you'll 58 00:03:26,569 --> 00:03:30,259 help add value to the profession by sharing it with your network. 59 00:03:30,619 --> 00:03:31,099 I'd love it. 60 00:03:31,099 --> 00:03:36,228 If you both subscribed to the podcast and to the YouTube channel or whichever 61 00:03:36,228 --> 00:03:40,069 is your preference for consuming the episodes, you can find all of the 62 00:03:40,069 --> 00:03:44,569 links from the conversation in the show notes at trxl.co, where you can. 63 00:03:44,599 --> 00:03:48,619 Also sign up to get an email from me Each time new episodes are released 64 00:03:48,799 --> 00:03:50,728 with those show notes and links within. 65 00:03:51,119 --> 00:03:56,279 So now without further ado, I bring you my conversation with Shane Berger. 66 00:04:03,284 --> 00:04:06,004 Shane Burger: There's been more than one tweet thread I've put out there 67 00:04:06,014 --> 00:04:07,764 related to some frustrations that I've 68 00:04:07,764 --> 00:04:12,024 had, um, with how the software industry deals with users, deals 69 00:04:12,024 --> 00:04:13,484 with pricing and things like that. 70 00:04:13,874 --> 00:04:17,764 Um, I, I think, you know, to give a little bit of context to what the, 71 00:04:17,983 --> 00:04:22,924 where, what led to this and where this conversation basically came from is that, 72 00:04:22,964 --> 00:04:29,179 um, um, I have found that a lot of the software companies have been pricing 73 00:04:29,179 --> 00:04:32,899 their software based upon how they measure its use, what they consider to 74 00:04:32,909 --> 00:04:36,089 be valuable from a profit perspective, which I don't blame them because 75 00:04:36,089 --> 00:04:37,929 they, they're a profit making company. 76 00:04:37,929 --> 00:04:39,808 They wouldn't exist if they weren't making a profit. 77 00:04:40,199 --> 00:04:44,769 Um, but what ends up, we run into an issue is that when these things butt heads with, 78 00:04:44,839 --> 00:04:47,649 um, how we actually operate as a company. 79 00:04:48,399 --> 00:04:52,519 So some of the examples would be, there is a company that we have been. 80 00:04:52,974 --> 00:04:56,614 Uh, working with, and I will say things have gotten better and resolved better 81 00:04:56,614 --> 00:04:59,714 out of this, but there's a company I've been working with, uh, from an 82 00:04:59,714 --> 00:05:03,524 infrastructure perspective to build out a whole visualization analytics 83 00:05:03,524 --> 00:05:06,804 platform that we've been working on for a good, probably two or three years 84 00:05:06,804 --> 00:05:12,304 now, and unfortunately, they switched over to a per user based pricing system. 85 00:05:12,654 --> 00:05:16,654 Uh, now that per user based pricing system was something that works 86 00:05:16,654 --> 00:05:18,324 well for other industries where. 87 00:05:18,924 --> 00:05:21,214 If someone's going to be using this particular platform, 88 00:05:21,244 --> 00:05:22,324 it's their full time job. 89 00:05:22,504 --> 00:05:24,114 They're going to be on it all the time, 90 00:05:24,484 --> 00:05:28,814 and it will be what they do for 8 hours a day, 365 days a year, right? 91 00:05:29,074 --> 00:05:34,074 And for that, I would expect to be paying 5 to 10 thousand dollars a year per user 92 00:05:34,074 --> 00:05:37,504 for that type of thing, because it is, it makes up the totality of your job. 93 00:05:37,933 --> 00:05:42,104 However, in other industries like ours, This is a platform that we 94 00:05:42,104 --> 00:05:44,194 would only use on an occasional basis. 95 00:05:44,344 --> 00:05:48,314 Um, it's something that is most suited towards early concept and schematic 96 00:05:48,314 --> 00:05:51,814 design, which means from a phase perspective, you're only going to be using 97 00:05:51,814 --> 00:05:56,504 it for the first few months of what might be 12 to 18 to 24 month long project. 98 00:05:56,894 --> 00:06:01,224 Um, so therefore, if you're going to be charging on a per user basis, Uh, for 99 00:06:01,224 --> 00:06:05,654 that type of thing, we are paying what is full price as if someone who's using 100 00:06:05,654 --> 00:06:10,514 365 days a year for something that would actually be used off and on for a few 101 00:06:10,514 --> 00:06:12,634 months and perhaps only by a few users. 102 00:06:13,024 --> 00:06:17,444 And even within that set, it might only be that, you know, someone like 103 00:06:17,444 --> 00:06:19,894 me might jump into it a few days. 104 00:06:20,359 --> 00:06:22,759 So I'm paying basically the same price at that point. 105 00:06:23,119 --> 00:06:27,319 And what happens then is when you start scaling that up across the practice, 106 00:06:27,689 --> 00:06:31,112 we are looking at something that was going to cost us you know, half to three 107 00:06:31,112 --> 00:06:32,572 quarters of a million dollars a year 108 00:06:32,882 --> 00:06:35,362 for something that was of occasional use. 109 00:06:35,607 --> 00:06:38,337 So that sort of mismatch between the pricing model and what 110 00:06:38,337 --> 00:06:41,577 our industry does and how we operate was a, was a frustration. 111 00:06:41,857 --> 00:06:44,957 Now, luckily in this sort of case, the conversations with this company, 112 00:06:45,187 --> 00:06:46,317 they understood that better. 113 00:06:46,387 --> 00:06:49,207 And after a while, they were able to change the model that actually 114 00:06:49,587 --> 00:06:53,647 better accounted for how much the tool is actually being used. 115 00:06:53,837 --> 00:06:56,797 So a good example for me about this is the difference between per user 116 00:06:56,797 --> 00:06:58,357 pricing and consumption pricing. 117 00:06:58,717 --> 00:07:03,457 Consumption pricing is, Um, so as opposed to per user pricing where 118 00:07:03,457 --> 00:07:07,667 you pay like 5, 000 per year for that user, consumption based pricing 119 00:07:07,667 --> 00:07:09,277 is if I use it a lot, I pay more. 120 00:07:09,317 --> 00:07:10,747 If I use it very little, I pay 121 00:07:10,957 --> 00:07:12,377 Evan Troxel: yeah, it's like a utility, right? 122 00:07:12,397 --> 00:07:13,777 Or it's like putting gas in your 123 00:07:13,777 --> 00:07:14,077 car. 124 00:07:14,077 --> 00:07:15,317 It's, it's, it's, yeah. 125 00:07:15,854 --> 00:07:18,894 Shane Burger: I tend to prefer consumption based pricing, especially 126 00:07:18,894 --> 00:07:24,164 for an industry like ours where, you know, Besides the core tools of Rhino 127 00:07:24,164 --> 00:07:29,514 and Revit, where we have our staff using them all the time, Um, a lot 128 00:07:29,514 --> 00:07:30,754 of the other tools are occasional. 129 00:07:31,214 --> 00:07:34,034 You're going to use them a few days in a week, a few hours in 130 00:07:34,034 --> 00:07:35,734 a day, or even less than that. 131 00:07:36,074 --> 00:07:39,964 So paying the exact same price, if it was your full time job versus 132 00:07:39,964 --> 00:07:42,414 if it's an occasional thing, it doesn't work out as well. 133 00:07:42,554 --> 00:07:45,314 So we've been trying to suggest when we're speaking with a lot of vendors 134 00:07:45,314 --> 00:07:50,664 about something closer to a consumption based pricing as a utility, as you said, 135 00:07:50,884 --> 00:07:55,474 or, um, and we've done this with, uh, a couple of other companies as well. 136 00:07:55,834 --> 00:08:00,004 Uh, we buy the licenses, they watch our use for three to six months, and they come 137 00:08:00,004 --> 00:08:04,914 back to us and say, okay, well you have, in our case, 800 users in the system. 138 00:08:05,194 --> 00:08:07,594 However, only 300 actually use it. 139 00:08:07,934 --> 00:08:09,334 on a very regular basis. 140 00:08:09,704 --> 00:08:12,644 So we're not going to make it hard for you to add users, but we're 141 00:08:12,644 --> 00:08:14,184 going to charge you 300 users. 142 00:08:14,354 --> 00:08:17,444 And then we'll come back a year from now and we'll top it up if we need to. 143 00:08:17,754 --> 00:08:21,374 So that sort of pricing model works a lot better for larger companies 144 00:08:21,374 --> 00:08:24,704 where we don't want to have to spend a lot of money to manage the users. 145 00:08:24,704 --> 00:08:27,444 We don't have to hire people full time to manage those users. 146 00:08:27,744 --> 00:08:31,124 Um, at the same time, I feel it right sizes it based upon the kind 147 00:08:31,124 --> 00:08:33,604 of company and the size of the company and how much you're using it. 148 00:08:34,779 --> 00:08:35,058 Evan Troxel: Okay. 149 00:08:35,068 --> 00:08:37,989 So I'm going to welcome you back to the podcast officially. 150 00:08:38,129 --> 00:08:38,318 I'm 151 00:08:38,318 --> 00:08:41,419 still putting, I'm, that is still going to be in the episode right 152 00:08:41,419 --> 00:08:41,869 there. 153 00:08:42,119 --> 00:08:43,938 We're just going to have jumped right into it. 154 00:08:44,269 --> 00:08:45,179 So welcome back. 155 00:08:45,179 --> 00:08:46,169 It's great to see you again. 156 00:08:46,169 --> 00:08:48,811 I'm glad we got to see each other at AU and make this happen. 157 00:08:48,811 --> 00:08:53,749 And you've been on a whirlwind, uh, tour of speaking gigs. 158 00:08:53,909 --> 00:08:56,059 I don't know if that's true or not, but that's what I'm going to say. 159 00:08:56,329 --> 00:09:01,469 And you've been presenting a lot of topics around, um, Digital practice and 160 00:09:01,489 --> 00:09:04,249 design technology and how firms work. 161 00:09:04,249 --> 00:09:06,225 And this subject is near and dear to my heart. 162 00:09:06,255 --> 00:09:10,895 I want to give the tech side of our industry a look behind the curtain 163 00:09:11,165 --> 00:09:13,275 of what it's actually like to. 164 00:09:13,645 --> 00:09:20,095 work in a firm, manage operations, people, users, licenses, IT, digital technology, 165 00:09:20,095 --> 00:09:21,485 design technology, all these things. 166 00:09:21,775 --> 00:09:25,105 So this is, this is a great place to kick off this episode. 167 00:09:25,635 --> 00:09:27,905 And you said it's good for big firms. 168 00:09:27,905 --> 00:09:31,945 I think it's good for small firms too, because it's even worse in a small firm. 169 00:09:31,945 --> 00:09:33,695 you have way more roles. 170 00:09:33,910 --> 00:09:38,790 Combined into a single person's daily, you know, set of tools 171 00:09:38,790 --> 00:09:39,740 that they're going to be using. 172 00:09:39,750 --> 00:09:43,130 They're going to be managing the project and designing the project and going to 173 00:09:43,130 --> 00:09:44,330 construction administration. 174 00:09:44,790 --> 00:09:48,790 In a larger firm, you do have more disparate roles for all of those things. 175 00:09:49,390 --> 00:09:51,120 But it still totally makes sense what you're saying 176 00:09:51,120 --> 00:09:53,010 because our projects last years, 177 00:09:53,320 --> 00:09:56,350 we don't do the same thing day in, day out. 178 00:09:56,730 --> 00:10:00,840 I don't need a visualization license when I'm, or maybe I do nowadays, but 179 00:10:00,840 --> 00:10:05,260 I didn't, used to need a visualization license in certain phases of design. 180 00:10:05,700 --> 00:10:10,610 and so as an example, now, now I think we, we tend to use those quite more 181 00:10:10,610 --> 00:10:12,800 often in, in many more stages of design. 182 00:10:12,800 --> 00:10:14,950 So maybe that's the worst example I could have chosen at 183 00:10:14,950 --> 00:10:16,510 the, at this, at this moment. 184 00:10:16,510 --> 00:10:18,150 But I think it's, it's. 185 00:10:18,595 --> 00:10:19,245 It's interesting. 186 00:10:19,245 --> 00:10:21,725 You said you're having these conversations with developers. 187 00:10:21,735 --> 00:10:23,205 How is it being received? 188 00:10:23,205 --> 00:10:25,405 And, and obviously you gave an example of where it's kind 189 00:10:25,405 --> 00:10:26,495 of working and you do this. 190 00:10:26,850 --> 00:10:31,380 annual reconciliation of what's actually been happening because 191 00:10:31,380 --> 00:10:32,920 you can measure all that. 192 00:10:33,410 --> 00:10:35,420 Um, but, but how is it being received? 193 00:10:35,450 --> 00:10:39,030 Because the, the per user, the named user license model, we've 194 00:10:39,030 --> 00:10:42,235 seen some big companies move back to that, like SketchUp. 195 00:10:42,375 --> 00:10:43,165 Recently, as, as 196 00:10:43,165 --> 00:10:46,335 an example, you know, within the last few years moved back to that model. 197 00:10:46,545 --> 00:10:50,535 And it was kind of shocking to firms who were like, we might have a designer 198 00:10:50,535 --> 00:10:53,495 jump in and jump out of SketchUp for a small portion of a project, and then 199 00:10:53,495 --> 00:10:54,745 they don't need it for quite a while. 200 00:10:54,745 --> 00:10:56,145 And I don't want to pay for it the whole time. 201 00:10:56,145 --> 00:10:57,045 It's expensive. 202 00:10:57,495 --> 00:11:00,335 And we can't spend a lot of money on all the tools. 203 00:11:00,375 --> 00:11:02,045 It just doesn't work for our budgets. 204 00:11:02,055 --> 00:11:02,275 Right. 205 00:11:02,275 --> 00:11:04,535 So how are they receiving this message? 206 00:11:04,912 --> 00:11:06,682 Shane Burger: I'd say it's, it's a bit hot and cold. 207 00:11:06,682 --> 00:11:07,702 It depends on the company. 208 00:11:07,732 --> 00:11:09,622 There's been some that we've spoken to. 209 00:11:10,472 --> 00:11:12,612 I would actually say the companies we've spoken to that 210 00:11:12,612 --> 00:11:14,632 are not as much in our industry. 211 00:11:15,022 --> 00:11:18,802 So the Miro's of the world and others who are doing things with us, 212 00:11:18,802 --> 00:11:21,572 but are not just a core AEC tool. 213 00:11:21,642 --> 00:11:21,972 Evan Troxel: Yeah. 214 00:11:22,842 --> 00:11:25,062 Shane Burger: Actually you're treating it quite well because it's, 215 00:11:25,072 --> 00:11:26,372 it's a bit of discovery for them. 216 00:11:26,392 --> 00:11:29,732 They're like, Oh, we didn't realize that we didn't know that's how you use it. 217 00:11:29,932 --> 00:11:30,382 And that's great. 218 00:11:30,382 --> 00:11:33,822 So it's been an open conversation and we've been very transparent and said, 219 00:11:33,822 --> 00:11:38,282 Hey, we'd love to show you what we do with it to help you out, to better understand 220 00:11:38,302 --> 00:11:40,092 what you can do to help our industry. 221 00:11:40,462 --> 00:11:47,072 I'm having mixed luck, arguably with, uh, those who are closer to the AEC industry. 222 00:11:47,402 --> 00:11:52,207 Um, You know, there are a few companies out there that have made that transition 223 00:11:52,207 --> 00:11:57,077 to the named users where, um, their answer and response, and I'm going to 224 00:11:57,677 --> 00:12:01,737 deliberately stay away from naming names in these cases, but, um, they would, 225 00:12:01,847 --> 00:12:05,927 they would basically say back to us, Okay, but this is what we're doing. 226 00:12:05,997 --> 00:12:07,967 And that's kind of been their response. 227 00:12:08,287 --> 00:12:12,017 And it's frustrating because in some of these cases, the perpetual 228 00:12:12,017 --> 00:12:16,627 license model, Especially the one that allowed you to put the licenses 229 00:12:16,627 --> 00:12:20,307 into a queue and then anybody in the company can use them wherever we want 230 00:12:20,767 --> 00:12:24,337 is the closest version to a consumption model without going to 231 00:12:24,337 --> 00:12:28,337 a consumption model because we would be watching after our license counts. 232 00:12:28,337 --> 00:12:31,257 We've got our own systems internally able to actually track how we're 233 00:12:31,257 --> 00:12:32,867 using these licenses over time. 234 00:12:33,227 --> 00:12:34,847 So we'd be able to look at and say, you know what? 235 00:12:35,207 --> 00:12:36,847 We've got 150 licenses. 236 00:12:36,847 --> 00:12:40,827 We've been hitting 145 consistently and that number is going up. 237 00:12:41,137 --> 00:12:44,457 Let's top it off with another 10 and we buy another 10 so that we 238 00:12:44,457 --> 00:12:48,167 never run out because larger company like us, you don't want to run out. 239 00:12:48,187 --> 00:12:50,847 You start getting emails and text messages from people. 240 00:12:51,217 --> 00:12:54,457 Um, so that model worked well for us. 241 00:12:54,707 --> 00:12:57,057 Um, but it also probably wasn't. 242 00:12:57,452 --> 00:13:01,592 an area of, uh, increased profitability for those who are selling the licenses. 243 00:13:01,602 --> 00:13:05,072 So I think a lot of the companies who changed to a named license model 244 00:13:05,072 --> 00:13:08,532 looked at that and said, well, here's a way that we can increase profits 245 00:13:08,532 --> 00:13:11,882 by selling more licenses, just by switching to a named user model. 246 00:13:12,402 --> 00:13:18,342 And, uh, frustratingly it's often sold as something that they think we would like. 247 00:13:18,662 --> 00:13:21,042 And I think in my case, it's, it's often. 248 00:13:21,332 --> 00:13:25,022 I've said, I understand how you want that, but this is absolutely not 249 00:13:25,022 --> 00:13:26,422 something that we actually want. 250 00:13:26,832 --> 00:13:29,882 Um, and we've had an increasing number of companies switch over to 251 00:13:29,882 --> 00:13:33,222 that sort of model, which now means that I have to start pricing it very 252 00:13:33,222 --> 00:13:35,112 differently, uh, as to how we do this. 253 00:13:35,412 --> 00:13:39,212 I don't want to be restricting the amount of people who use the licenses, um, but 254 00:13:39,372 --> 00:13:44,032 by going to a named license model, it forces me to either restrict it, to cap 255 00:13:44,032 --> 00:13:48,302 it at, say, 50 or 100 or whatever we have, and then we have to internally shuffle 256 00:13:48,302 --> 00:13:51,062 licenses around, or we have to manage. 257 00:13:51,407 --> 00:13:54,207 buying new licenses every few months to just top it up and 258 00:13:54,207 --> 00:13:55,427 keep going that direction. 259 00:13:55,727 --> 00:13:59,387 Um, it doesn't reflect the realities of how a business 260 00:13:59,387 --> 00:14:00,807 like ours actually operates. 261 00:14:01,362 --> 00:14:05,362 Evan Troxel: And the managerial aspect of that, just to open the 262 00:14:05,362 --> 00:14:09,112 window to give people an idea of what that is like, this is a big deal. 263 00:14:09,162 --> 00:14:13,762 Like just to have the staff in place to constantly be monitoring and 264 00:14:13,762 --> 00:14:18,492 managing and potentially purchasing and getting approvals to do all this. 265 00:14:19,017 --> 00:14:19,847 It's a nightmare. 266 00:14:19,897 --> 00:14:21,017 It's a literal nightmare 267 00:14:21,147 --> 00:14:22,317 with all the different software. 268 00:14:22,317 --> 00:14:24,177 And, and just, so paint that picture. 269 00:14:24,177 --> 00:14:27,007 What does it actually look like for you guys to have to deal with that? 270 00:14:27,847 --> 00:14:29,507 Shane Burger: I think the first thing is if I think about it 271 00:14:29,507 --> 00:14:32,957 from a user perspective, um, I've got a job I've got to do. 272 00:14:33,167 --> 00:14:35,007 I, I'm working on a project. 273 00:14:35,347 --> 00:14:38,767 I need to either access a particular file or do a piece of work. 274 00:14:38,787 --> 00:14:40,497 Got a deadline coming up in three days. 275 00:14:40,977 --> 00:14:44,007 Um, and I try to open the piece software and I don't have access to it. 276 00:14:44,447 --> 00:14:45,817 What am I going to do for that afternoon? 277 00:14:45,847 --> 00:14:48,927 So from a user perspective, it's incredibly frustrating because then 278 00:14:48,927 --> 00:14:53,257 they have to put in an IT support ticket or text somebody that they know 279 00:14:53,257 --> 00:14:54,537 who might be able to help them out. 280 00:14:54,877 --> 00:14:58,397 Um, usually that involves including a principal on the chat. 281 00:14:58,407 --> 00:15:02,267 So hoping that the principal can weigh in on it and say, please let us get that, 282 00:15:02,797 --> 00:15:03,957 make it happen, right? 283 00:15:04,197 --> 00:15:09,022 Um, in some cases that principal will bypass us and purchase it with 284 00:15:09,022 --> 00:15:11,922 a company card, which is something we don't want to have happen. 285 00:15:12,252 --> 00:15:16,172 Because whenever that happens, we start ending up with licenses just spread and 286 00:15:16,947 --> 00:15:17,297 Evan Troxel: Just 287 00:15:17,432 --> 00:15:19,102 Shane Burger: proliferating, right? 288 00:15:19,102 --> 00:15:22,032 And we don't, and all of a sudden we'll get a message from some 289 00:15:22,032 --> 00:15:24,262 company we've never heard of saying, are you going to renew this? 290 00:15:24,482 --> 00:15:25,982 It becomes difficult to manage. 291 00:15:26,272 --> 00:15:30,672 Um, It's the ad hoc license purchases and spreading around with different 292 00:15:30,672 --> 00:15:33,712 accounts and everything is just a significant amount of work to manage 293 00:15:33,932 --> 00:15:35,672 just from a logistics point of view. 294 00:15:35,742 --> 00:15:36,892 How do you actually deal with that? 295 00:15:37,222 --> 00:15:39,862 Um, and then when it gets to, say, the I. 296 00:15:39,862 --> 00:15:40,082 T. 297 00:15:40,082 --> 00:15:40,512 staff. 298 00:15:41,602 --> 00:15:45,432 they'll get it and they'll ask the question, well, what do they need it for? 299 00:15:45,492 --> 00:15:47,092 Um, is this actually necessary? 300 00:15:47,122 --> 00:15:49,992 So a judgment's call has system start to come into play. 301 00:15:50,262 --> 00:15:53,692 You know, they've been maybe told that we're supposed to cap it at 50 licenses. 302 00:15:53,962 --> 00:15:57,072 So we either need to contact someone else in the company and say, do 303 00:15:57,072 --> 00:15:58,362 you need your license anymore? 304 00:15:58,632 --> 00:16:01,172 Do we look at our dashboards and see who hasn't used it in the 305 00:16:01,172 --> 00:16:05,012 last 60 to 90 days and say, we're going to remove it for that user. 306 00:16:05,012 --> 00:16:07,502 That's not a good experience because they may need it next week. 307 00:16:07,742 --> 00:16:11,082 So we ended up having to shuffle licenses around and have a lot of. 308 00:16:11,302 --> 00:16:15,432 Uncomfortable conversations with staff who are rightly frustrated, who don't want 309 00:16:15,432 --> 00:16:16,932 to have to deal with this sort of thing. 310 00:16:17,342 --> 00:16:20,612 Um, then when it comes to the process of, you know, when we do need to 311 00:16:20,612 --> 00:16:23,722 make a judgment call, there's a lot of back and forth conversations. 312 00:16:23,722 --> 00:16:26,602 Can you use the free version if it's commercially viable? 313 00:16:26,792 --> 00:16:29,142 uh, someone else on your team already has a license. 314 00:16:29,182 --> 00:16:32,182 There's all these things that come into play when you have to deal with 315 00:16:32,182 --> 00:16:35,772 a per user license or you're capped in some sort of frustrating way. 316 00:16:36,182 --> 00:16:39,172 All of this creates an experience, I think, for the end user. 317 00:16:39,557 --> 00:16:44,077 That is, uh, understandable frustration towards the technology teams. 318 00:16:44,857 --> 00:16:48,327 But those technology teams have a hand tied behind their back, either by the 319 00:16:48,327 --> 00:16:52,607 licensing system, by the software vendor, or perhaps from a budget perspective. 320 00:16:53,017 --> 00:16:57,297 But then, arguably, the staff also has a sort of bad taste in their mouth, perhaps 321 00:16:57,297 --> 00:17:00,737 even towards the vendor who put this situation in play in the first place. 322 00:17:01,177 --> 00:17:04,446 And we'll have to communicate with those staff and say, listen, we're 323 00:17:04,446 --> 00:17:08,166 doing what we can, but the way that the vendor has the system set 324 00:17:08,166 --> 00:17:09,967 up, it's not easy to manage users. 325 00:17:10,247 --> 00:17:16,242 There's one vendor that we work with where, um, We actually have to, if a 326 00:17:16,242 --> 00:17:20,801 staff member was to leave the company or stop using the software, they, 327 00:17:20,821 --> 00:17:23,952 before they uninstall the software or leave the company, they have 328 00:17:23,952 --> 00:17:28,571 to, disconnect the license from the license manager system in the software. 329 00:17:28,772 --> 00:17:31,942 So, say you're leaving the company, I'm going to have to go up to you and say, 330 00:17:31,952 --> 00:17:36,232 please launch this program, log into here, disconnect your license, and move onward. 331 00:17:36,547 --> 00:17:39,697 Say their computer crashes and they have to rebuild the computer. 332 00:17:39,897 --> 00:17:44,567 That license is lost for a year and we've had that happen enough times. 333 00:17:44,707 --> 00:17:47,107 It's not to say our computers crash all the time, but it happens. 334 00:17:47,557 --> 00:17:49,427 Thousand person company, it happens. 335 00:17:49,827 --> 00:17:52,757 Um, there's lots of circumstances that actually prevent you 336 00:17:52,757 --> 00:17:53,747 from being able to do that. 337 00:17:54,017 --> 00:17:57,547 Because there's no central management interface, I have the email address of 338 00:17:57,547 --> 00:18:01,877 the person I have to shoot an email off to to get them to add licenses to top us up, 339 00:18:01,887 --> 00:18:06,867 because I can say, this user, uh, Either is no longer at the company, um, or, uh, 340 00:18:06,897 --> 00:18:08,117 they had an issue with their computer. 341 00:18:08,117 --> 00:18:10,217 So you see two versions, two licenses. 342 00:18:10,217 --> 00:18:11,267 They don't, they just have one. 343 00:18:11,847 --> 00:18:14,787 That's a lot of headaches that nobody should have to deal with. 344 00:18:14,817 --> 00:18:17,977 And it creates a sort of bad experience for everybody that's involved. 345 00:18:18,337 --> 00:18:23,007 Whereas very simple changes to how these licensee systems work, give 346 00:18:23,047 --> 00:18:25,017 people the opportunity to use the tools. 347 00:18:25,192 --> 00:18:27,382 They don't have to ask for permission. 348 00:18:27,672 --> 00:18:31,442 They don't have to fight to, you know, have one person release their 349 00:18:31,442 --> 00:18:32,992 license if someone else can use it. 350 00:18:33,362 --> 00:18:37,752 Um, I don't understand why any company would want to prevent 351 00:18:37,792 --> 00:18:41,372 people from using their software by actually making additional headaches 352 00:18:41,372 --> 00:18:42,702 from a management perspective. 353 00:18:44,082 --> 00:18:47,892 Evan Troxel: There's so much in there and I'm glad you brought up the 354 00:18:47,902 --> 00:18:51,502 staff leaving aspect to it because turnover happens and it happens 355 00:18:51,502 --> 00:18:53,122 quite often in architecture firms. 356 00:18:53,122 --> 00:18:55,222 I mean, they staff up, they staff down. 357 00:18:55,232 --> 00:18:55,442 There's 358 00:18:55,442 --> 00:18:56,842 certain firms that do that a lot. 359 00:18:56,842 --> 00:18:59,232 There's other firms that try to hang on to people as long as possible 360 00:18:59,232 --> 00:19:00,952 and maybe it's less of an issue. 361 00:19:01,532 --> 00:19:03,672 But other things in life happen too 362 00:19:04,035 --> 00:19:07,515 things change all the time or just getting new computers or whatever, right? 363 00:19:07,515 --> 00:19:08,215 And, and so. 364 00:19:08,870 --> 00:19:13,540 There's, there's so much nuance to this and I think what it all 365 00:19:13,620 --> 00:19:18,760 comes back to is like not caring about the actual users and it's 366 00:19:18,770 --> 00:19:25,060 more about looking like it, it, it's going to be more efficient because 367 00:19:25,070 --> 00:19:27,920 maybe, maybe that's the expectation is that it is going to be more efficient, 368 00:19:27,920 --> 00:19:29,210 but it's more efficient for the vendor. 369 00:19:29,240 --> 00:19:32,580 It's not more efficient for the firm itself to do all this. 370 00:19:33,040 --> 00:19:36,050 And, and who actually is monitoring email. 371 00:19:36,420 --> 00:19:41,110 Like a hawk all the time, because that's the expectation too, right? 372 00:19:41,290 --> 00:19:45,840 If I send in a support ticket that I need this thing right now, the expectation 373 00:19:45,840 --> 00:19:47,230 is I need this thing right now. 374 00:19:47,600 --> 00:19:51,500 And if you're in a 1000 person firm, that's not going to happen either. 375 00:19:51,520 --> 00:19:51,740 Right. 376 00:19:51,740 --> 00:19:55,340 And so like the, the, just the queuing times that are going 377 00:19:55,340 --> 00:19:57,230 to happen because of this. 378 00:19:57,560 --> 00:19:58,270 Uh, predicament. 379 00:19:58,500 --> 00:20:02,000 And, and I want to, I just want to double down on what you said. 380 00:20:02,010 --> 00:20:05,520 Maybe the, the staff gets a bad taste in their mouth towards the vendor. 381 00:20:05,560 --> 00:20:08,850 I think that is less the case than getting a bad taste in your mouth 382 00:20:08,860 --> 00:20:10,880 about your own IT department, your 383 00:20:10,900 --> 00:20:12,380 own DT department, 384 00:20:12,740 --> 00:20:16,730 because they're the ones telling you, no, you can't get into all the 385 00:20:16,730 --> 00:20:20,360 nuance of why this is happening like this, that it's actually the vendor 386 00:20:20,360 --> 00:20:22,130 that's forcing us to do it this way. 387 00:20:22,570 --> 00:20:27,300 And again, I think it's about the vendor not caring about the actual end user. 388 00:20:27,665 --> 00:20:29,815 of the software by creating these systems. 389 00:20:29,815 --> 00:20:34,445 And so, uh, it does suck to hear that they're, receiving this in a cold 390 00:20:34,445 --> 00:20:36,175 way for, you know, for the most part. 391 00:20:36,755 --> 00:20:40,005 Shane Burger: I have, um, I even had a conversation just over the last 392 00:20:40,005 --> 00:20:44,565 two days with, um, A company that provides, uh, generative AI image 393 00:20:44,565 --> 00:20:50,345 creation services, uh, uh, services that doesn't offer an enterprise approach. 394 00:20:50,365 --> 00:20:53,635 So their answer was, well, just set up individual accounts 395 00:20:53,635 --> 00:20:54,575 for every single person. 396 00:20:55,160 --> 00:20:58,660 Well, we've got between 75 to 90 people in the company who are playing 397 00:20:58,660 --> 00:21:02,110 around with these things, and that is now 75 to 90 people, individual 398 00:21:02,110 --> 00:21:04,680 accounts linked to my Work Amex card. 399 00:21:04,940 --> 00:21:07,220 And just, that's not how this is going to work. 400 00:21:07,510 --> 00:21:10,960 So, you know, and I've, I've had this with lots of different companies that 401 00:21:11,190 --> 00:21:14,150 you could create the most amazing piece of software in the world. 402 00:21:14,415 --> 00:21:16,145 People could absolutely love the features. 403 00:21:16,435 --> 00:21:21,555 If you make it a nightmare for IT and design technology staff to manage this 404 00:21:21,555 --> 00:21:25,875 system, I'm likely just going to say no because we don't want to put ourselves 405 00:21:25,875 --> 00:21:29,545 in the position of being the people that's having to tell staff, no, you 406 00:21:29,545 --> 00:21:33,065 can't have it because the licensing is preventing us from doing this in this way. 407 00:21:33,425 --> 00:21:38,925 Um, It makes it really hard for a company like ours ultimately to be 408 00:21:38,925 --> 00:21:40,195 able to manage this type of stuff. 409 00:21:40,570 --> 00:21:44,390 staff members shouldn't have to even know anything about licensing systems. 410 00:21:44,740 --> 00:21:45,880 They should not have to care. 411 00:21:46,190 --> 00:21:47,470 They just want to do their job. 412 00:21:47,820 --> 00:21:48,090 Right. 413 00:21:48,110 --> 00:21:49,420 They just want to do their jobs. 414 00:21:49,620 --> 00:21:52,100 They want to be able to open what they need, and get access 415 00:21:52,100 --> 00:21:53,250 to what they want, and use it. 416 00:21:53,660 --> 00:21:56,580 And then they shouldn't have to be doing, Oh, I have to release my 417 00:21:56,580 --> 00:22:00,680 license, or Who do I need to talk to whether we've hit our quota in the 418 00:22:00,680 --> 00:22:02,560 studio for such and such license. 419 00:22:03,190 --> 00:22:05,390 That should never be a conversation for them. 420 00:22:05,790 --> 00:22:09,800 And I, and ideally then you should make the lives of the technology staff and 421 00:22:09,800 --> 00:22:14,260 the company easier such that we're not having to then explain that or have 422 00:22:14,260 --> 00:22:17,570 to be the bad guys to tell people no in that situation because you've made 423 00:22:17,930 --> 00:22:19,290 the whole situation more difficult. 424 00:22:19,470 --> 00:22:23,010 So I do very much steer away from a company that's going to 425 00:22:23,010 --> 00:22:24,440 increase our management overhead. 426 00:22:24,750 --> 00:22:29,295 if we have to start adding staff, whose entire job is to just managing 427 00:22:29,295 --> 00:22:30,965 users and data in these systems. 428 00:22:31,235 --> 00:22:33,605 You start building up enough of that, it gets to be incredibly 429 00:22:33,605 --> 00:22:35,015 frustrating and difficult to deal with. 430 00:22:35,015 --> 00:22:38,555 Yeah. 431 00:22:39,000 --> 00:22:42,210 Evan Troxel: weird version of the consumption slash prepaid, 432 00:22:42,230 --> 00:22:43,270 you know, it's weird, right? 433 00:22:43,300 --> 00:22:46,430 You don't want to have a staff member like running out of tokens. 434 00:22:47,090 --> 00:22:47,830 Right when they're in the, 435 00:22:48,460 --> 00:22:50,060 on a deadline, for example. 436 00:22:50,070 --> 00:22:52,080 So that's not a good solution either. 437 00:22:52,995 --> 00:22:56,035 Shane Burger: Yeah, I, well, tokens for a few cases is, yeah, buying them in 438 00:22:56,035 --> 00:23:00,195 advance and topping them up versus, true consumption systems, just, you're going to 439 00:23:00,195 --> 00:23:01,705 pay for it after you've actually used it. 440 00:23:01,965 --> 00:23:04,875 I, I would say there's some there's some difficult parts 441 00:23:04,875 --> 00:23:06,945 about, um, consumption systems. 442 00:23:06,975 --> 00:23:08,285 It's harder to budget for them. 443 00:23:08,715 --> 00:23:12,435 But budgeting and restricting should not be the same thing. 444 00:23:12,445 --> 00:23:15,515 You don't budget in advance and then stop people from using things. 445 00:23:15,815 --> 00:23:18,415 A budget should be an estimate of where you think you're going to go. 446 00:23:18,425 --> 00:23:21,735 In any consumption based system, you should be able to watch the analytics 447 00:23:21,745 --> 00:23:23,505 to see you ultimately where they get to. 448 00:23:23,755 --> 00:23:26,805 The other frustrating thing about token based systems is, I'm generally 449 00:23:26,805 --> 00:23:32,015 not a fan of abstract, currencies in order to to pay for these things. 450 00:23:32,345 --> 00:23:33,395 How much is that? 451 00:23:33,655 --> 00:23:34,595 One token is a 1. 452 00:23:34,595 --> 00:23:36,655 90 US dollars. 453 00:23:36,655 --> 00:23:38,075 Like, what does that actually mean? 454 00:23:38,285 --> 00:23:40,005 And what does it mean to consume those tokens? 455 00:23:40,225 --> 00:23:45,235 Again, this seems to be adding a layer of abstraction to something where in 456 00:23:45,235 --> 00:23:49,185 the gray areas and the gaps in between, it will inevitably be more profitable 457 00:23:49,215 --> 00:23:52,625 for the software company versus just paying for actual consumption. 458 00:23:53,420 --> 00:23:53,820 Evan Troxel: Yeah. 459 00:23:53,860 --> 00:23:58,220 Like just defining the value and how much it costs to achieve that value, I 460 00:23:58,220 --> 00:24:03,460 think is a reckoning that really needs to happen and, I guess we could continue 461 00:24:03,460 --> 00:24:05,415 to flog this, but do you want to. 462 00:24:05,835 --> 00:24:07,605 Talk about who, who's doing this right. 463 00:24:07,685 --> 00:24:10,665 Like, you don't, we don't want to name who's doing it wrong, but is there anybody 464 00:24:10,665 --> 00:24:14,715 that like springs to the, to mind that, that you are enjoying 465 00:24:15,065 --> 00:24:17,805 their licensing model that you want to give a shout out to? 466 00:24:17,805 --> 00:24:20,575 Yeah. 467 00:24:20,840 --> 00:24:25,310 Shane Burger: to what happened for us with Miro, and Miro was a case of where 468 00:24:25,500 --> 00:24:30,100 it started off on a per user basis, um, and it was going down the direction 469 00:24:30,110 --> 00:24:35,180 of the named user approach, but then what we were able to show them is, uh, 470 00:24:35,190 --> 00:24:36,720 first of all, they gave us some room. 471 00:24:36,830 --> 00:24:39,560 They said, All right, we're gonna do a quarterly update 472 00:24:39,590 --> 00:24:40,700 top up agreement with you. 473 00:24:40,710 --> 00:24:43,620 You have a certain number of licenses, and every quarter we're gonna have 474 00:24:43,620 --> 00:24:45,130 a conversation to look at your use. 475 00:24:45,520 --> 00:24:48,730 And we won't restrict with how many users you have, but we're going to look at it. 476 00:24:48,960 --> 00:24:51,270 Ultimately, we end up signing a three year agreement with them 477 00:24:51,270 --> 00:24:54,630 based upon that sort of model, but it's a yearly kind of update. 478 00:24:54,870 --> 00:24:58,610 The thing I appreciate about them was, they, uh, used the 479 00:24:58,610 --> 00:25:00,120 data to inform the decision. 480 00:25:01,090 --> 00:25:06,460 They looked at how we were actually using their tool, frequency at which 481 00:25:06,460 --> 00:25:09,360 people were using it, how they were using it, even down to the point of 482 00:25:09,360 --> 00:25:13,795 understanding the difference between Uh, what a viewer license was versus 483 00:25:13,795 --> 00:25:16,725 a creator license, someone who's actually making boards and editing 484 00:25:16,725 --> 00:25:18,575 them versus who's just looking at them. 485 00:25:18,915 --> 00:25:22,175 They had the backend analytics to actually answer that question to which 486 00:25:22,175 --> 00:25:26,630 they were like, Oh, Okay, yes, you do want to have all 1, 000 people in. 487 00:25:26,880 --> 00:25:30,960 They listened to us when we said, we don't want, have to have one IT staff 488 00:25:30,960 --> 00:25:34,190 member sitting in there constantly adding and removing people all the time. 489 00:25:34,450 --> 00:25:37,880 And I, we did it for a few months to show them what the effort 490 00:25:37,880 --> 00:25:41,920 looked like and how it was kind of ridiculous that this was happening. 491 00:25:42,710 --> 00:25:47,110 Even to the point of pointing out to them that even our CEO and some of our global 492 00:25:47,110 --> 00:25:51,390 design leadership were viewer staff, which weren't really counting as full 493 00:25:51,390 --> 00:25:52,795 licenses, but they were going to get paid. 494 00:25:53,085 --> 00:25:56,055 Pulled out of the cutoff because of the frequency at which they 495 00:25:56,395 --> 00:25:58,835 did what was called, I think, a paid action or something. 496 00:25:58,845 --> 00:26:01,585 They were mostly viewers engaging in design reviews, 497 00:26:01,585 --> 00:26:02,655 not creating their own boards. 498 00:26:02,865 --> 00:26:07,565 So we explained to them, you're putting us in a scenario where, um, arguably if 499 00:26:07,565 --> 00:26:11,985 we follow our rules, our design leadership would not always be given full licenses. 500 00:26:12,985 --> 00:26:14,065 They understood what that meant. 501 00:26:14,065 --> 00:26:16,915 And they came back to us and said, all right, here's a pricing model that 502 00:26:16,915 --> 00:26:18,085 we're going to put together for you. 503 00:26:18,675 --> 00:26:20,235 That is, um, based upon. 504 00:26:21,175 --> 00:26:22,725 how much you actually use the tools. 505 00:26:23,005 --> 00:26:24,065 So we're going to open it up. 506 00:26:24,065 --> 00:26:27,345 we'll use single sign on, allow you to add all the users that you need in the 507 00:26:27,345 --> 00:26:30,905 system, but what you're going to pay for is people who are actively using it. 508 00:26:31,305 --> 00:26:33,605 And that was a, that ended up working out a lot better. 509 00:26:34,125 --> 00:26:37,195 I would say though, that that is likely a scenario that's only going 510 00:26:37,195 --> 00:26:41,215 to work for a large company because it does require a direct engagement 511 00:26:41,225 --> 00:26:44,625 with a sales representative to be part of reviewing and kind of a customer 512 00:26:44,835 --> 00:26:46,375 success manager sort of system. 513 00:26:46,595 --> 00:26:50,055 So that's something that I think you would definitely need is it 514 00:26:50,055 --> 00:26:52,945 would benefit from being a larger company to be able to negotiate 515 00:26:52,945 --> 00:26:54,385 that sort of relationship with them. 516 00:26:54,795 --> 00:26:57,325 I have been finding there's other companies out there that 517 00:26:57,325 --> 00:26:58,615 do similar types of models. 518 00:26:59,070 --> 00:27:03,090 Well, we haven't done it yet, but our work with Atlassian, my team uses JIRA. 519 00:27:03,090 --> 00:27:04,500 The IT team uses JIRA as well. 520 00:27:04,680 --> 00:27:07,590 We have increasing numbers of people in our operations team using it. 521 00:27:07,930 --> 00:27:10,440 When we pass a certain threshold, they do the same type of thing. 522 00:27:10,500 --> 00:27:13,570 We haven't really passed that threshold, but the conversations 523 00:27:13,570 --> 00:27:14,750 have gone really well with that. 524 00:27:15,110 --> 00:27:18,340 Um, there are other companies out there that I think do a 525 00:27:18,340 --> 00:27:21,320 relatively good job of it, even if I have some of my frustrations. 526 00:27:21,730 --> 00:27:25,980 I do fundamentally like Autodesk's model it's a token based system. 527 00:27:26,180 --> 00:27:30,220 However, it is a consumption based system and there are things I like about how 528 00:27:30,220 --> 00:27:35,040 they do it and it puts us in a position where it does right size it based upon 529 00:27:35,040 --> 00:27:36,620 how much we actually use the tool. 530 00:27:36,920 --> 00:27:40,716 Now, granted, it's, you know, it's not, recorded hourly. 531 00:27:40,716 --> 00:27:43,166 It's if you use it during the day, you pay for the whole day's worth. 532 00:27:43,786 --> 00:27:47,306 I can maybe understand that sort of scenario, but I do appreciate their 533 00:27:47,306 --> 00:27:52,246 approach on that because that is closer to actually paying for our real use. 534 00:27:52,536 --> 00:27:56,606 Um, other companies like McNeel have kept to the traditional 535 00:27:56,606 --> 00:27:57,946 perpetual license model. 536 00:27:58,306 --> 00:28:02,276 Um, and in that sort of case, we, I think we own something like 150, 537 00:28:02,276 --> 00:28:05,536 160 licenses and it covers our whole company globally that actually use it. 538 00:28:06,891 --> 00:28:11,441 Our peak use period is pretty much when we get to New York City evenings and West 539 00:28:11,441 --> 00:28:14,361 Coast afternoons and Australian mornings. 540 00:28:14,391 --> 00:28:17,251 I think that's typically our peak use or a little bit further when 541 00:28:17,251 --> 00:28:21,181 China starts to come online, but we have purchased it based upon that 542 00:28:21,181 --> 00:28:22,811 amount and we're able to watch. 543 00:28:23,026 --> 00:28:26,396 Using their analytics to see when we're peaking up to that particular level. 544 00:28:26,606 --> 00:28:29,556 So that's the traditional older style perpetual license model, 545 00:28:29,746 --> 00:28:33,356 but it works really well and we keep buying licenses and nobody 546 00:28:33,446 --> 00:28:34,916 loses their chance at a license. 547 00:28:35,266 --> 00:28:38,216 There's other companies that have done perpetual license models though, 548 00:28:38,256 --> 00:28:40,346 that have not provided analytics. 549 00:28:40,676 --> 00:28:44,676 So one in particular, I won't mention, but around some visualization tools 550 00:28:44,676 --> 00:28:48,686 we've run into where, uh, it is a perpetual license model, which is great, 551 00:28:48,986 --> 00:28:52,116 But they don't provide any insight into how much we're actually using. 552 00:28:52,426 --> 00:28:55,936 And we're having trouble internally recording how much it's actually 553 00:28:55,936 --> 00:28:57,556 used because it's a plugin to a tool. 554 00:28:57,676 --> 00:28:59,726 So it's not easy to actually get insight into it. 555 00:28:59,976 --> 00:29:04,906 So that's one of those ones where we have run into issues where, um, we don't end 556 00:29:04,906 --> 00:29:08,706 up topping up licenses until we run out and someone starts talking to us about it. 557 00:29:09,026 --> 00:29:11,926 But we also don't know if we can downscale licenses. 558 00:29:12,296 --> 00:29:14,186 Visualization market is really competitive. 559 00:29:14,216 --> 00:29:15,666 There's lots of competing tools. 560 00:29:15,916 --> 00:29:17,486 We have people trying more than once. 561 00:29:17,486 --> 00:29:18,736 We might actually be able to. 562 00:29:19,081 --> 00:29:21,091 shift the balance of licenses between them. 563 00:29:21,361 --> 00:29:23,631 But unfortunately we don't have enough insights into how 564 00:29:23,631 --> 00:29:24,851 much is actually being used. 565 00:29:25,571 --> 00:29:30,321 Evan Troxel: And you can deploy kind of insight machines on your side of the 566 00:29:30,601 --> 00:29:31,301 pond as well. 567 00:29:31,441 --> 00:29:31,711 Right. 568 00:29:31,711 --> 00:29:36,241 But again, more to manage, more to watch, more to track, a lot 569 00:29:36,241 --> 00:29:37,881 more conversations with users. 570 00:29:38,661 --> 00:29:39,001 Shane Burger: Right. 571 00:29:39,062 --> 00:29:40,922 a lot of these companies have their own tools. 572 00:29:40,932 --> 00:29:43,762 Sometimes they will allow you access to those analytics. 573 00:29:44,172 --> 00:29:46,622 Um, so that is, uh, that is great. 574 00:29:46,682 --> 00:29:50,882 A good example, actually, also on the positive side is, um, the 575 00:29:50,882 --> 00:29:54,462 company Avail that makes the Revit content management system, which is 576 00:29:54,462 --> 00:29:56,082 our preferred choice for a system. 577 00:29:56,432 --> 00:30:00,037 Um, they have provided us with, um, Uh, Power BI. 578 00:30:00,337 --> 00:30:01,157 I think it's Power BI. 579 00:30:01,207 --> 00:30:02,157 I could be wrong. 580 00:30:02,417 --> 00:30:05,297 But dashboards that gives us insight into the actual use. 581 00:30:05,527 --> 00:30:09,557 There are another company that also has given us open access or unlimited 582 00:30:09,567 --> 00:30:11,527 access, but we top it up every year. 583 00:30:11,667 --> 00:30:13,867 We have conversation with them to say, this is how much we're 584 00:30:13,867 --> 00:30:15,147 using and how much we pay. 585 00:30:15,347 --> 00:30:18,877 So they watch what our numbers are, and they provide access to all 586 00:30:18,877 --> 00:30:21,957 the analytics for us to actually understand, is it being effective? 587 00:30:22,017 --> 00:30:22,757 Is that good for us? 588 00:30:23,107 --> 00:30:25,557 It's something I would like to see more of from other companies. 589 00:30:25,882 --> 00:30:30,112 So either access, they either provide the dashboards or give us access 590 00:30:30,112 --> 00:30:31,722 to dashboards to pull data in. 591 00:30:32,382 --> 00:30:35,322 If those aren't the case, we end up having to use some of our own tools. 592 00:30:35,332 --> 00:30:39,472 So we're in the process now of consolidating our tracking systems 593 00:30:39,472 --> 00:30:40,622 on all of our various tools. 594 00:30:40,622 --> 00:30:44,512 And that's everything from commercially purchased software, where they sometimes 595 00:30:44,552 --> 00:30:49,082 provide analytics to platforms, which we have no analytics and we're having to. 596 00:30:49,532 --> 00:30:53,362 You know, use systems built into Windows to be able to keep an eye on how much 597 00:30:53,362 --> 00:30:58,782 people are using the tool, down to some of our own tools, um, that, uh, are 598 00:30:58,802 --> 00:31:02,122 plugins, automation tools, so we can track how much people are using them. 599 00:31:02,552 --> 00:31:07,217 Really, for us, it's, it's a combination of, um, Wanting to know, are we 600 00:31:07,227 --> 00:31:08,857 investing our money in the right place? 601 00:31:08,887 --> 00:31:12,587 Do we need to buy more licenses so people don't run out, but also ensuring we're 602 00:31:12,587 --> 00:31:14,357 providing the right balance of support. 603 00:31:14,577 --> 00:31:17,557 So if we start seeing significant amount of use in one tool versus 604 00:31:17,557 --> 00:31:21,147 another, it might highlight to us to say, we should be investing more 605 00:31:21,147 --> 00:31:23,197 energy and keeping that up to date. 606 00:31:23,207 --> 00:31:26,497 If it's a tool we've built, maybe providing updates to it, but also 607 00:31:26,497 --> 00:31:28,027 making sure we can support the users. 608 00:31:28,037 --> 00:31:31,207 So our analytics work is going to become pretty important, I think, 609 00:31:31,207 --> 00:31:34,717 over the next six months to try to pull all those dashboards together. 610 00:31:35,502 --> 00:31:39,351 Evan Troxel: That was a really nice unplanned, unscripted, high five to 611 00:31:39,351 --> 00:31:40,911 Avail, who's also sponsoring this 612 00:31:41,166 --> 00:31:42,456 Shane Burger: Oh yeah, there you go. 613 00:31:42,696 --> 00:31:43,216 That's great. 614 00:31:43,776 --> 00:31:46,286 Now it's, um, I appreciate when. 615 00:31:47,216 --> 00:31:51,626 Companies, uh, understand the needs of what an architecture practice is 616 00:31:51,626 --> 00:31:56,856 looking for and do something that suits and balances without it is 617 00:31:57,186 --> 00:31:58,736 how, how those companies operate. 618 00:31:58,766 --> 00:31:59,826 Avail's been one of them. 619 00:32:00,056 --> 00:32:02,446 There's, as I said, Miro, not from our industry has 620 00:32:02,456 --> 00:32:04,086 learned and has helped with it. 621 00:32:04,306 --> 00:32:07,316 There's others that are out there that I'm probably not remembering at this moment, 622 00:32:07,326 --> 00:32:13,266 but, um, I do appreciate when it's a, uh, a more reasonable conversation about, 623 00:32:13,406 --> 00:32:15,506 uh, how the tool is actually being used. 624 00:32:16,540 --> 00:32:19,783 Evan Troxel: This episode is made possible with support from avail Avail 625 00:32:19,783 --> 00:32:23,893 makes the best software to manage all of your AEC digital content. 626 00:32:24,158 --> 00:32:27,908 Dedicated to developing tools that save AEC team's time. 627 00:32:28,248 --> 00:32:32,508 Avail has now added Revit application version management to its suite of 628 00:32:32,508 --> 00:32:34,278 content management capabilities. 629 00:32:34,738 --> 00:32:37,038 Once a painful manual process. 630 00:32:37,038 --> 00:32:38,148 Revit application. 631 00:32:38,178 --> 00:32:41,118 Versioning is now automatic for avail customers. 632 00:32:41,448 --> 00:32:44,028 Publishers simply upload files to an avail channel. 633 00:32:44,328 --> 00:32:47,658 And the files are automatically converted to newer versions from 634 00:32:47,658 --> 00:32:50,748 Revit 2021 through Revit 2025. 635 00:32:51,062 --> 00:32:53,702 For users, the experience is then seamless. 636 00:32:54,002 --> 00:32:58,772 They can search select and utilize the Revit content and avail, regardless of 637 00:32:58,772 --> 00:33:00,632 what Revit version they are working in. 638 00:33:00,972 --> 00:33:04,542 inquire about a demo of avail and its new Revit application 639 00:33:04,542 --> 00:33:10,572 version management features today at get avail.com/request-demo. 640 00:33:10,871 --> 00:33:13,421 My thanks to avail for supporting this episode. 641 00:33:13,421 --> 00:33:14,711 of the TRXL podcast. 642 00:33:15,071 --> 00:33:17,351 And now let's get back to the conversation. 643 00:33:18,927 --> 00:33:22,797 I feel like that's more of a partnership, like they, they have a genuine interest 644 00:33:22,807 --> 00:33:26,427 in the value you're deriving from their tool to do your work, right? 645 00:33:26,427 --> 00:33:26,837 It's not 646 00:33:26,837 --> 00:33:30,737 just to have this relationship with them. 647 00:33:30,787 --> 00:33:32,617 Like you're not buying their software just so that you get 648 00:33:32,617 --> 00:33:33,617 to talk to each other, right? 649 00:33:33,617 --> 00:33:36,087 you're employing it for a purpose. 650 00:33:36,097 --> 00:33:40,047 And if they're genuinely interested in what people are getting out of that 651 00:33:40,057 --> 00:33:43,897 and what you're doing with it, that partnership, I think does lead to the 652 00:33:43,897 --> 00:33:46,787 kind of relationship that you're talking about rather than the other way around. 653 00:33:47,487 --> 00:33:47,767 Yeah, 654 00:33:47,767 --> 00:33:49,647 Shane Burger: I think we've had some successes with that. 655 00:33:49,657 --> 00:33:50,917 We've had some frustrations. 656 00:33:50,947 --> 00:33:54,887 I think that most of the frustrations have occurred when this is a company 657 00:33:54,887 --> 00:33:58,507 that provides the same software to multiple parts of your industry 658 00:33:58,507 --> 00:34:00,017 that may be used in different ways. 659 00:34:00,087 --> 00:34:03,827 So an example would be a software that is used by contractors and architects. 660 00:34:03,987 --> 00:34:05,257 Well, which one do you price it for? 661 00:34:05,707 --> 00:34:08,237 Do you price it based on what the contractor is going to look for, which 662 00:34:08,237 --> 00:34:12,827 they tend to have, um, you know, uh, a larger ability to spend money on software 663 00:34:12,827 --> 00:34:16,456 than an architecture practice, or what the architecture practice is, is going for? 664 00:34:16,456 --> 00:34:19,627 And when we have imbalances or differences like that, we usually 665 00:34:19,627 --> 00:34:23,056 run into some, uh, differences of opinion about how we should price it. 666 00:34:23,822 --> 00:34:26,431 Evan Troxel: And in contrast to manufacturing where you're making 667 00:34:26,431 --> 00:34:29,902 widgets or you have an assembly line where somebody does a specific 668 00:34:29,902 --> 00:34:33,002 thing day after day to your point much earlier in the conversation. 669 00:34:33,391 --> 00:34:37,687 This is not that this is your we're An architecture firm is not 670 00:34:37,687 --> 00:34:41,257 a company that makes the same, the same person makes the same thing day 671 00:34:41,257 --> 00:34:42,377 after day after day. 672 00:34:42,377 --> 00:34:43,657 It just doesn't work like that. 673 00:34:44,016 --> 00:34:48,887 Project teams disband, come back together in a different amalgamation to tackle 674 00:34:48,887 --> 00:34:52,927 a new project at a different phase in a different part of the world with all 675 00:34:52,927 --> 00:34:59,117 these differences amongst multiple years throughout the phases of a project. 676 00:34:59,477 --> 00:35:01,737 And, and that I think is something that is difficult. 677 00:35:02,527 --> 00:35:05,327 I don't know if it's unique about architecture, but it's definitely 678 00:35:05,337 --> 00:35:09,617 different than, like when Miro comes to you and they're working with somebody like 679 00:35:09,627 --> 00:35:12,477 GE, let's say, who's making jet engines. 680 00:35:12,952 --> 00:35:15,422 Like, that's going to be very different from what an 681 00:35:15,432 --> 00:35:16,852 architecture firm does, right? 682 00:35:16,852 --> 00:35:21,512 So really interesting to me to hear that they were interested in finding that out 683 00:35:21,542 --> 00:35:25,252 and not just sticking to like, this is how we do it, which is the answer that 684 00:35:25,252 --> 00:35:27,462 you also showed as a contrasting answer. 685 00:35:27,462 --> 00:35:29,332 It's like, Nope, this is how we're doing it. 686 00:35:29,742 --> 00:35:34,032 Um, and not willing to listen, not willing to maybe care about 687 00:35:34,032 --> 00:35:35,392 what the users actually need. 688 00:35:35,402 --> 00:35:39,812 And so just, just maybe to wrap this part of the conversation up, um. 689 00:35:40,752 --> 00:35:44,182 Have you actually gone through, and I assume the answer is yes, 690 00:35:44,182 --> 00:35:47,032 but I want to hear it from you, to just say, okay, that tool's gone. 691 00:35:47,102 --> 00:35:50,702 Like we can't use that tool, at least until we come back and 692 00:35:50,702 --> 00:35:52,002 revisit it at some other time. 693 00:35:53,987 --> 00:35:56,227 Shane Burger: yes, it's hard to do. 694 00:35:56,267 --> 00:35:57,697 And I, I would say I'm not 695 00:35:57,762 --> 00:35:59,252 Evan Troxel: People love their tools, man. 696 00:35:59,617 --> 00:36:02,897 Shane Burger: They, they do and I get it and I understand because it's, it's, 697 00:36:03,147 --> 00:36:08,527 it's what you've been using for years or a decade or more and it is the, it's 698 00:36:08,527 --> 00:36:11,577 the instrument that you are used to expressing the work that you're doing. 699 00:36:11,657 --> 00:36:13,587 Um, you're efficient at it. 700 00:36:14,097 --> 00:36:15,407 It's like learning any instrument. 701 00:36:15,487 --> 00:36:19,197 Um, you know, you're going to say, Nope, you're not going to play violin anymore. 702 00:36:19,197 --> 00:36:19,897 Here's a trumpet. 703 00:36:19,927 --> 00:36:21,667 I, you know, when am I supposed to do that? 704 00:36:21,697 --> 00:36:23,817 I, I have lost my ability to. 705 00:36:24,827 --> 00:36:27,167 you know, to execute on the work that I'm used to doing. 706 00:36:27,167 --> 00:36:30,287 So it's disruptive, uh, for what is already a stressful, 707 00:36:30,287 --> 00:36:32,087 high pace sort of profession. 708 00:36:32,387 --> 00:36:35,477 When you are removing people's access to the tools and systems that they're 709 00:36:35,477 --> 00:36:39,567 using, that they're used to using to do their job, it's a significant stress. 710 00:36:39,567 --> 00:36:40,867 It's a high level of frustration. 711 00:36:41,257 --> 00:36:46,342 Um, But yeah, we've had situations where we've had to basically say, well, 712 00:36:46,342 --> 00:36:48,342 we no longer use this particular tool. 713 00:36:48,582 --> 00:36:51,252 I'd say it's more common that we limited its use. 714 00:36:51,812 --> 00:36:55,842 So, you know, one of the modeling tools that we've limited use on is a case 715 00:36:55,842 --> 00:36:59,992 of where we have selected particular sectors or subsets or studios that 716 00:37:00,002 --> 00:37:04,182 have access to it because It may be necessary based on the market that 717 00:37:04,182 --> 00:37:05,862 they're working in that particular region. 718 00:37:06,092 --> 00:37:09,282 It's the most common tool that people used to share models back and forth. 719 00:37:09,282 --> 00:37:10,942 So, okay, I get that. 720 00:37:11,002 --> 00:37:15,132 Or, um, there's a particular set of features or workflows that are 721 00:37:15,132 --> 00:37:19,642 essential for this and they need to use it quickly for this work. 722 00:37:19,642 --> 00:37:22,782 It's short, you know, a short turnaround sort of work and it is 723 00:37:22,782 --> 00:37:23,722 the most effective one to do that. 724 00:37:23,772 --> 00:37:24,422 I get that. 725 00:37:24,422 --> 00:37:25,082 I understand it. 726 00:37:25,572 --> 00:37:30,052 that desire to have an individual choice of the tools that you use runs up against 727 00:37:30,052 --> 00:37:34,242 not just things from a cost perspective, but also from a collaboration perspective. 728 00:37:34,622 --> 00:37:39,442 Uh, if we don't try to unify around a small set of tools, when you start 729 00:37:39,442 --> 00:37:42,662 sharing projects from studio to studio, it becomes next to impossible 730 00:37:42,662 --> 00:37:44,322 to actually be effective on that. 731 00:37:44,622 --> 00:37:48,477 So if one person is using a completely different tool, Then everybody else 732 00:37:48,477 --> 00:37:51,747 is, then that person is kind of separated from how the rest of the 733 00:37:51,747 --> 00:37:52,897 group is actually going to operate. 734 00:37:53,137 --> 00:37:55,727 And you have immediately some built in inefficiencies. 735 00:37:56,447 --> 00:37:59,107 Evan Troxel: And people say, Oh, just, just export your 3d model. 736 00:37:59,377 --> 00:38:01,607 And you lose something every single time you lose 737 00:38:01,607 --> 00:38:03,167 stuff every time that happens. 738 00:38:03,167 --> 00:38:03,357 Right. 739 00:38:03,367 --> 00:38:05,317 That's, that's the biggest downside to that. 740 00:38:05,317 --> 00:38:05,587 So, 741 00:38:06,227 --> 00:38:08,627 Shane Burger: It's not just that you've lost things from a. 742 00:38:09,052 --> 00:38:11,942 technology standpoint, it's lost from a workflow standpoint. 743 00:38:11,952 --> 00:38:15,312 You have now decoupled the work of one person in the team 744 00:38:15,322 --> 00:38:16,382 from the rest of the team. 745 00:38:16,792 --> 00:38:20,942 Um, it effectively just turns into, okay, I see what you have over there. 746 00:38:20,942 --> 00:38:23,182 I'm going to look at that while I'm working on what is our 747 00:38:23,182 --> 00:38:24,452 main tool that we work within. 748 00:38:24,672 --> 00:38:28,729 And when you decouple those sort of processes, uh, in delivery, you 749 00:38:28,729 --> 00:38:33,512 have inherent inefficiencies even beyond, um, issues of file formats. 750 00:38:34,187 --> 00:38:34,927 Evan Troxel: Yeah, for sure. 751 00:38:35,337 --> 00:38:37,757 I want to shift now to maybe the future of the profession, but I 752 00:38:37,757 --> 00:38:41,427 want to kind of couch that, at least get into it with tools. 753 00:38:41,457 --> 00:38:43,387 And so you mentioned AI earlier, right? 754 00:38:43,417 --> 00:38:43,637 And 755 00:38:43,637 --> 00:38:45,907 so we're we're seeing changes happen. 756 00:38:45,947 --> 00:38:48,307 We're seeing disruption happening. 757 00:38:48,557 --> 00:38:51,457 And you also talked about kind of the limiting factors of licensing 758 00:38:51,457 --> 00:38:53,067 for enterprise and things like that. 759 00:38:53,067 --> 00:38:57,237 But let's start to talk about AI and the future of the profession as 760 00:38:57,237 --> 00:39:01,017 a, as a lead in, because obviously the future of the profession. 761 00:39:01,342 --> 00:39:02,862 does not equal AI, right? 762 00:39:02,862 --> 00:39:06,512 So I want to talk about that in a, in a bigger scale, um, 763 00:39:06,522 --> 00:39:08,452 but in a way to get there. 764 00:39:08,912 --> 00:39:12,452 Let's just talk about kind of the emergence of AI and what 765 00:39:12,452 --> 00:39:16,212 that's meant at Woods Bagot and, and for you and your teams, 766 00:39:16,667 --> 00:39:19,585 Shane Burger: Yeah, I think, um, we've been keeping an eye on what 767 00:39:19,585 --> 00:39:23,485 were the potential opportunities for us for many years now, but it wasn't 768 00:39:23,485 --> 00:39:26,465 until, and this is probably the same for a lot of architecture practices, 769 00:39:26,785 --> 00:39:30,345 um, tools like mid journey and stable diffusion and DALL-E coming 770 00:39:30,345 --> 00:39:32,445 out in combination with chat GPT. 771 00:39:32,885 --> 00:39:37,635 And I think for us, it was initially catching up to what the conversations 772 00:39:37,635 --> 00:39:40,815 that everybody was having around those tools where we think they would be a 773 00:39:40,815 --> 00:39:44,225 value to the practice, where we think there are some concerns and limitations 774 00:39:44,225 --> 00:39:47,755 for each of them, but at the same time, actually trying to project forward. 775 00:39:47,755 --> 00:39:49,105 Well, what's next after this? 776 00:39:49,455 --> 00:39:52,525 We didn't want to be in a position where we're always running to catch up. 777 00:39:52,525 --> 00:39:54,265 And every three months there's something new. 778 00:39:54,700 --> 00:39:58,460 Uh, when I presented to our shareholders conference just two weeks ago, I 779 00:39:58,460 --> 00:40:02,960 ran a two hour afternoon workshop on AI and architecture and design. 780 00:40:03,340 --> 00:40:07,350 Um, wasn't just two hours of presentation, but a lot of back and forth and debate and 781 00:40:07,350 --> 00:40:11,610 discussion about what this means for us as a practice and, and how does this fit with 782 00:40:11,610 --> 00:40:13,760 our, our credo, how we approach our work. 783 00:40:14,110 --> 00:40:17,230 Um, one of the key things to point out was that just the week 784 00:40:17,230 --> 00:40:21,220 before, it was when OpenAI's Sora, Came out the video creation tool. 785 00:40:21,630 --> 00:40:24,330 Uh, not something I had in my presentation, but of course I 786 00:40:24,340 --> 00:40:27,310 added it right in there and just basically explained to everybody 787 00:40:27,650 --> 00:40:30,610 these sort of innovations are happening on a regular basis. 788 00:40:30,870 --> 00:40:33,440 So what are the fundamental trends? 789 00:40:33,890 --> 00:40:36,750 What are some of the things that sit underneath this that gives you 790 00:40:36,900 --> 00:40:39,640 a sense of what direction these things might actually be going? 791 00:40:40,010 --> 00:40:43,950 Um, and that was where we kind of ended on a series of topics 792 00:40:43,950 --> 00:40:45,000 that should be discussed. 793 00:40:45,350 --> 00:40:48,080 Um, and we should be considering how they affect our practice. 794 00:40:48,350 --> 00:40:51,640 One of the biggest and first ones is the fundamental change 795 00:40:51,640 --> 00:40:53,020 about how we access knowledge. 796 00:40:53,890 --> 00:40:58,410 And we started asking questions of, we've got 150, 160 years of 797 00:40:58,410 --> 00:41:03,750 practice, 18 studios around the globe, multiple sectors, a thousand people. 798 00:41:04,440 --> 00:41:08,590 What happens when you have access to that kind of information in the context, in 799 00:41:08,590 --> 00:41:12,420 a context relevant way, uh, to answer things that you need to know, you know, 800 00:41:12,420 --> 00:41:13,900 what happens in this sort of scenarios? 801 00:41:13,900 --> 00:41:18,410 And that became, beyond the excitement, I think, about the image creation, which 802 00:41:18,410 --> 00:41:22,580 we can talk about and get into, I got more interested into what it means to 803 00:41:22,660 --> 00:41:26,340 tap into and harness knowledge, not just within our practice, but within 804 00:41:26,340 --> 00:41:27,770 potentially the broader industry. 805 00:41:27,770 --> 00:41:33,345 Yeah. 806 00:41:33,450 --> 00:41:35,360 Evan Troxel: that we had a conversation on the podcast. 807 00:41:35,360 --> 00:41:39,290 What you were, we were talking about second brain, Roam Research, right? 808 00:41:39,300 --> 00:41:42,210 The interconnectedness potential of notes. 809 00:41:42,270 --> 00:41:42,720 Like just 810 00:41:42,720 --> 00:41:44,400 talking about like, where do you take your notes? 811 00:41:44,400 --> 00:41:45,210 Where do you take your notes? 812 00:41:45,220 --> 00:41:46,070 How do you, how do you. 813 00:41:46,210 --> 00:41:47,200 link between notes. 814 00:41:47,210 --> 00:41:51,440 Is there a way to get insight out of then all the notes you've taken, right? 815 00:41:51,460 --> 00:41:53,700 And now you're talking about that at scale. 816 00:41:53,720 --> 00:41:54,220 You're talking 817 00:41:54,220 --> 00:41:59,470 about that in an organization and it's a very, it's, it's the same conversation, 818 00:41:59,470 --> 00:42:01,700 but it's just at a way larger scale. 819 00:42:01,770 --> 00:42:04,933 And so I'm, I'm interested in, hearing it from, from that side, but I'm also 820 00:42:04,953 --> 00:42:08,243 interested in hearing about like the pursuit of creativity as well, because 821 00:42:08,243 --> 00:42:11,468 I think that's kind of the existential Crisis that we 822 00:42:11,468 --> 00:42:13,518 see going on in firms as well. 823 00:42:13,718 --> 00:42:17,158 Not only from a, like, where does creativity come from? 824 00:42:17,228 --> 00:42:22,948 Is it going to take our jobs, but also ethics, governance, things like that too. 825 00:42:22,958 --> 00:42:23,028 Right. 826 00:42:23,038 --> 00:42:25,228 There, there's a lot going on here in, in the whole 827 00:42:25,228 --> 00:42:28,588 AI sphere, but, but let's, let's continue to go down the, the 828 00:42:28,588 --> 00:42:30,498 knowledge side of the graph. 829 00:42:30,558 --> 00:42:34,187 And, and I I'm curious to hear what, what you guys have come up with. 830 00:42:34,187 --> 00:42:34,635 Mm hmm. 831 00:42:34,833 --> 00:42:35,143 Shane Burger: Yeah. 832 00:42:35,143 --> 00:42:38,743 So, um, we have a set of documents in the company called 833 00:42:38,743 --> 00:42:40,183 design intelligence documents. 834 00:42:40,183 --> 00:42:43,213 I may or may not have talked about them in the previous podcast. 835 00:42:43,583 --> 00:42:47,813 It's effectively a, an overview of all the major decisions around a project. 836 00:42:48,183 --> 00:42:51,453 Um, it's a way that if you're a new member of the team or want to know about what 837 00:42:51,453 --> 00:42:55,083 happened on a previous project and go back, you'll say, well, this is the site. 838 00:42:55,083 --> 00:42:55,783 This is the client. 839 00:42:55,783 --> 00:42:56,823 This is what they asked for. 840 00:42:57,053 --> 00:42:58,803 Here's some of the early concept designs. 841 00:42:59,088 --> 00:43:02,258 This is how we got to where we were, the decisions that we made, 842 00:43:02,278 --> 00:43:03,968 the major concepts behind this. 843 00:43:04,388 --> 00:43:08,298 Um, and one of the questions that I started asking when things like 844 00:43:08,328 --> 00:43:12,968 ChatGPT came out was, Alright, well, they are large language models trained 845 00:43:12,968 --> 00:43:15,928 on the internet, so yes, they speak English and understand English, 846 00:43:15,948 --> 00:43:17,598 and they can work with us that way. 847 00:43:17,888 --> 00:43:21,988 Um, what happens when we can train it on a particular subset of documents 848 00:43:22,048 --> 00:43:23,678 and ask questions of those documents? 849 00:43:23,968 --> 00:43:26,128 And this is something that I had seen others do. 850 00:43:26,498 --> 00:43:30,048 You know, a year or so ago, come out and say, well, what happens when I feed 851 00:43:30,378 --> 00:43:33,358 my favorite book into a chat engine? 852 00:43:33,568 --> 00:43:36,068 And now I can basically have a conversation with the book. 853 00:43:36,388 --> 00:43:40,098 Ask things about it, query it, and have it bring up information for me. 854 00:43:40,358 --> 00:43:41,958 So we thought, why not try this out? 855 00:43:42,228 --> 00:43:47,748 So we actually used some of OpenAI's tools via our Microsoft kind of 856 00:43:47,748 --> 00:43:51,538 enterprise agreement to build a version of a chatbot that was a 857 00:43:51,578 --> 00:43:53,588 design intelligence knowledge chatbot. 858 00:43:53,998 --> 00:43:56,258 We just vetted 50 of them to start off with. 859 00:43:57,028 --> 00:43:58,338 We had to do some work. 860 00:43:58,408 --> 00:44:01,492 I would say that it's not the easiest thing in the world. 861 00:44:01,492 --> 00:44:04,782 You can't just put any formatted document into a system like this. 862 00:44:05,032 --> 00:44:09,782 And I think we realize that sometimes our documents are more, uh, human 863 00:44:09,782 --> 00:44:11,212 readable than machine readable. 864 00:44:11,222 --> 00:44:15,512 So there's some differences with how it would be good to, to put into these 865 00:44:15,512 --> 00:44:20,262 systems to, to deal with potential hallucinations, but we fed 50 into this 866 00:44:20,302 --> 00:44:24,462 and we're able to ask questions like, you know, tell me about, uh, any of the 867 00:44:24,462 --> 00:44:26,842 projects that have, uh, timber structures. 868 00:44:27,192 --> 00:44:30,322 What are common characteristics or what were the core concepts behind them? 869 00:44:30,812 --> 00:44:36,082 And we started thinking about this to say, okay, well, if I'm wanting to know, if I, 870 00:44:36,132 --> 00:44:40,292 if I'm guessing that someone within our practice or some project has encountered 871 00:44:40,292 --> 00:44:43,982 the problem that I'm encountering on my project right now, what's the best 872 00:44:43,982 --> 00:44:45,542 way for me to find that information? 873 00:44:45,952 --> 00:44:48,122 Uh, a standard search will pick up. 874 00:44:48,647 --> 00:44:52,767 topic names, uh, maybe even headings of particular chapters, but not 875 00:44:52,777 --> 00:44:55,437 really dig into the insights that are within these documents. 876 00:44:55,777 --> 00:44:59,067 It also won't be able to draw correlations between a concept in 877 00:44:59,067 --> 00:45:00,787 this project and a concept over here. 878 00:45:01,267 --> 00:45:05,237 Um, and often we found that while we create these documents, we've got 879 00:45:05,237 --> 00:45:11,832 something like you know, 300 or 400 of these now, um, if not more, um, usually 880 00:45:11,832 --> 00:45:14,702 it's just principles and people who worked on the projects who actually 881 00:45:14,702 --> 00:45:18,932 are aware that they exist and not even knowing, however, unless they worked on 882 00:45:18,932 --> 00:45:20,642 it, the insights that sit within them. 883 00:45:21,032 --> 00:45:25,062 So for us, this became a potential rich opportunity for us to train up 884 00:45:25,302 --> 00:45:29,302 a knowledge bot that would be able to Um, understand the history of 885 00:45:29,302 --> 00:45:32,292 our projects, and that could come in play in a few different places. 886 00:45:32,292 --> 00:45:34,042 One would be for business development. 887 00:45:34,342 --> 00:45:37,602 So for chasing after new work, we're having to answer to an RFP. 888 00:45:37,912 --> 00:45:43,122 Um, I, rather than just going to my standard five projects I know that had 889 00:45:43,122 --> 00:45:46,932 a strong sustainability, story along with them, I now have access to all the 890 00:45:46,932 --> 00:45:50,942 projects that have that information, and I can query them, and it will bring them up, 891 00:45:50,942 --> 00:45:53,612 and perhaps even help me author content. 892 00:45:53,612 --> 00:45:53,672 for listening. 893 00:45:53,992 --> 00:45:57,242 Not always the best authoring of the content, but it's going to surface 894 00:45:57,242 --> 00:46:01,132 things and insights that I may not have gotten unless I had actually 895 00:46:01,132 --> 00:46:05,812 read all 300 to 400 of those and internalized all the knowledge within. 896 00:46:06,702 --> 00:46:08,952 It might help during project design, during concepts. 897 00:46:09,352 --> 00:46:11,492 putting in queries, asking questions of this. 898 00:46:11,832 --> 00:46:14,912 Um, it might even help in later phases, especially when we're 899 00:46:14,912 --> 00:46:18,292 getting down into some material selections and later decisions, what 900 00:46:18,292 --> 00:46:19,722 projects have used this material. 901 00:46:20,102 --> 00:46:23,662 So we then started to extend this to say, well, how about not just 902 00:46:23,662 --> 00:46:25,042 design intelligence documents? 903 00:46:25,352 --> 00:46:27,552 What about some of our technical guidance material? 904 00:46:27,622 --> 00:46:31,372 Best practices for Revit, our global standards, so that when you're in 905 00:46:31,372 --> 00:46:33,862 Revit, you've got a little chat bot, you can ask it a question. 906 00:46:34,302 --> 00:46:37,672 Um, maybe it's the second coming of Microsoft Clippy, I don't know, 907 00:46:37,962 --> 00:46:39,612 but it's some version of that, right? 908 00:46:39,932 --> 00:46:43,152 And then it went further to say, and this is where we, we haven't gotten here 909 00:46:43,152 --> 00:46:44,582 yet, but we started to talk about it. 910 00:46:45,057 --> 00:46:51,707 Um, why can't we be querying our library of, uh, BIM models in our system? 911 00:46:52,247 --> 00:46:55,237 Why can't we create something that's able to crawl through that and ask 912 00:46:55,237 --> 00:46:56,817 questions of all of our projects? 913 00:46:57,177 --> 00:47:01,137 Um, and be able to bring certain project metrics out or different things 914 00:47:01,137 --> 00:47:02,597 about the execution of that work. 915 00:47:02,927 --> 00:47:07,077 So, this is where we saw the very beginnings of saying, All 916 00:47:07,077 --> 00:47:12,797 right, we've seen some companies teach or GPT like system. 917 00:47:13,237 --> 00:47:15,487 on a particular subset of documents. 918 00:47:15,487 --> 00:47:17,597 There's one, for example, in scientific journals. 919 00:47:17,597 --> 00:47:20,407 There's a few, there are up codes has done this obviously 920 00:47:20,407 --> 00:47:22,147 for code review in North America. 921 00:47:22,617 --> 00:47:24,477 What can we do when we do that? 922 00:47:24,747 --> 00:47:26,937 And then what are the next logical steps? 923 00:47:26,937 --> 00:47:28,707 Well, it need not necessarily be documents. 924 00:47:28,707 --> 00:47:32,347 What if it's other kinds of information that we have, for example, model content. 925 00:47:32,797 --> 00:47:37,857 So that's one example where that initial insight led us down the path into 926 00:47:38,047 --> 00:47:42,697 multiple potential opportunities for creating, basically surfacing context 927 00:47:42,697 --> 00:47:44,117 relevant knowledge about our work. 928 00:47:45,631 --> 00:47:48,991 Evan Troxel: This episode is made possible with support from avail, 929 00:47:49,231 --> 00:47:52,981 along with their newly released Revit application version management. 930 00:47:53,252 --> 00:47:57,422 AEC software company avail has added another powerful new workflow feature 931 00:47:57,452 --> 00:48:02,042 called pallets To its suite of content management capabilities, pallets are user 932 00:48:02,042 --> 00:48:06,551 customized lists of content and avail and can function as a favorites list as 933 00:48:06,551 --> 00:48:08,651 starter content for a specific project. 934 00:48:08,921 --> 00:48:13,061 Or to drive workflows such as redlining, construction details, customers. 935 00:48:13,061 --> 00:48:15,731 Administrators can add pallets to their accounts through the 936 00:48:15,731 --> 00:48:17,861 avail managed portal page today. 937 00:48:18,251 --> 00:48:20,561 Interested in seeing pallets and action first. 938 00:48:20,801 --> 00:48:26,141 Request a demo at get avail.com/request-demo. 939 00:48:26,479 --> 00:48:31,549 Avail helps AECO firms better manage, organize, and navigate information faster. 940 00:48:31,849 --> 00:48:35,959 My thanks to avail for supporting this episode of the TRXL podcast. 941 00:48:36,319 --> 00:48:38,209 And now let's return to the conversation. 942 00:48:39,965 --> 00:48:43,815 I think that's what's so interesting about it is like, once you start going in a 943 00:48:43,815 --> 00:48:46,305 direction, light bulbs start turning on, 944 00:48:46,675 --> 00:48:49,025 you're like, Oh, what if we try this? 945 00:48:49,035 --> 00:48:52,825 Or, and I find like really surprising results when I try 946 00:48:52,825 --> 00:48:55,795 something like I'll feed it images and just say, transcribe these. 947 00:48:55,885 --> 00:48:56,255 And it, 948 00:48:56,430 --> 00:48:56,810 Shane Burger: Yeah. 949 00:48:56,935 --> 00:48:58,865 Evan Troxel: I didn't know if it could do that or not. 950 00:48:59,050 --> 00:48:59,370 Right. 951 00:48:59,390 --> 00:49:03,930 But it can, it turns out and, or, or I'll just feed it a webpage that I 952 00:49:03,930 --> 00:49:05,790 didn't, and I said, pull all the names. 953 00:49:05,810 --> 00:49:07,130 Cause I, I have pictures. 954 00:49:07,470 --> 00:49:09,240 Like when we were at AU, we took a picture. 955 00:49:09,260 --> 00:49:10,720 I put it, it's Evan and Shane. 956 00:49:10,730 --> 00:49:12,470 Here's a link to our previous episode. 957 00:49:12,900 --> 00:49:17,190 And I just grabbed that whole page and I said, just make me a list 958 00:49:17,190 --> 00:49:18,260 of all the names on this page. 959 00:49:18,280 --> 00:49:19,125 I didn't tell it what to do. 960 00:49:19,565 --> 00:49:20,725 What format those names are 961 00:49:20,725 --> 00:49:22,585 in, and it just made a list. 962 00:49:22,835 --> 00:49:27,505 And I'm, I'm surprised by that because like that would have taken me a lot of 963 00:49:27,505 --> 00:49:31,065 copying and pasting and a lot of time to do, but with a simple prompt, it's 964 00:49:31,065 --> 00:49:32,095 just like, pull all the names out. 965 00:49:32,405 --> 00:49:32,705 Boom. 966 00:49:32,805 --> 00:49:33,505 There, there they are. 967 00:49:33,915 --> 00:49:35,525 I'm, I'm so happy that that worked. 968 00:49:35,525 --> 00:49:37,675 And I think that's what's kind of fun about this. 969 00:49:37,685 --> 00:49:40,575 It's kind of like when you learned how to start 3D modeling. 970 00:49:40,575 --> 00:49:43,565 It's like, I don't know how to build all the geometry. 971 00:49:43,575 --> 00:49:45,935 I'm just going to try something and see if it works. 972 00:49:46,375 --> 00:49:47,525 And if it works, it's great. 973 00:49:47,545 --> 00:49:49,345 And if it doesn't, okay, I'll try something else. 974 00:49:49,395 --> 00:49:52,405 It's a lot like building a piece of code or something, right? 975 00:49:52,405 --> 00:49:53,615 You're just constantly. 976 00:49:54,005 --> 00:49:58,345 Trying things and just being curious about it, I think is one of the 977 00:49:58,355 --> 00:50:03,005 best positions to be in because Then it's really non committal, right? 978 00:50:03,005 --> 00:50:07,195 You don't have to worry about it performing Explicitly so that you get 979 00:50:07,195 --> 00:50:10,805 the outcome you're looking for But of course that will happen over time because 980 00:50:10,815 --> 00:50:12,425 you will get actually get good at it, 981 00:50:13,675 --> 00:50:16,345 Shane Burger: I think we're in a spot where the technology is quite 982 00:50:16,345 --> 00:50:20,105 advanced and can get super detailed in certain areas, but we haven't 983 00:50:20,105 --> 00:50:23,585 really looked at what the broader potentialities across our practice is. 984 00:50:23,585 --> 00:50:26,725 It's very easy to look right in front of you and say, well, yes, we want to have 985 00:50:26,725 --> 00:50:28,515 a chat bot that looks at our projects. 986 00:50:28,895 --> 00:50:32,035 And yes, we want to be able to do lots of image creation. 987 00:50:32,035 --> 00:50:34,625 And at some point, maybe it'll become model creation. 988 00:50:34,625 --> 00:50:35,905 I can see those sorts of things. 989 00:50:36,305 --> 00:50:39,715 Um, but the issue with this is that this is. 990 00:50:41,205 --> 00:50:42,375 I was about to say immature. 991 00:50:42,375 --> 00:50:45,305 I mean, it's been, you know, it's been talked about since the late fifties. 992 00:50:45,305 --> 00:50:47,035 So, you know, it's not immature, 993 00:50:47,305 --> 00:50:47,665 but 994 00:50:47,745 --> 00:50:48,135 um, 995 00:50:48,575 --> 00:50:50,575 it's early days for these types of things. 996 00:50:50,815 --> 00:50:54,725 Um, I think every practice needs to be in a position of experimentation. 997 00:50:55,150 --> 00:50:57,740 And I think they need to be in a spot where the experimentation is 998 00:50:57,740 --> 00:50:59,680 happening broadly across the practice. 999 00:51:00,010 --> 00:51:04,240 One of the things that we've discussed with our company is to, to have a 1000 00:51:04,240 --> 00:51:09,820 group of people, sort of a catalyst for conversations about AI and the broad 1001 00:51:09,820 --> 00:51:11,870 potential application on their projects. 1002 00:51:12,270 --> 00:51:16,930 But then that group is supported by those who can take a deep dive from a 1003 00:51:16,930 --> 00:51:19,010 technology and implementation perspective. 1004 00:51:19,300 --> 00:51:23,465 So if someone sees an opportunity with a client to say, All right, well, we 1005 00:51:23,465 --> 00:51:27,365 have a bunch of data from the client about their, um, about their workplace. 1006 00:51:27,555 --> 00:51:31,165 We want to work with that information to then drive some auto layout features. 1007 00:51:31,455 --> 00:51:34,915 Okay, they have the idea, they have the potential application on our project, 1008 00:51:35,255 --> 00:51:39,385 but they don't necessarily have the, the technology muscle or the infrastructure 1009 00:51:39,385 --> 00:51:43,075 or systems to then really take a deep dive to implement that system. 1010 00:51:43,680 --> 00:51:47,510 So what I think we need to be doing as an industry is allowing that 1011 00:51:47,510 --> 00:51:52,460 experimentation, especially at the face of projects, but then giving significant 1012 00:51:52,470 --> 00:51:54,820 muscle and support behind those people. 1013 00:51:55,130 --> 00:51:58,810 They themselves shouldn't be on off alone doing this, but there should 1014 00:51:58,820 --> 00:52:02,410 be people who are then back within the kind of core of the company who 1015 00:52:02,410 --> 00:52:04,030 are looking at these opportunities. 1016 00:52:04,410 --> 00:52:07,790 Some software developers within that group who are building out these systems and 1017 00:52:07,790 --> 00:52:11,830 supporting them, maybe data scientists or data analysts, some combination of this 1018 00:52:11,830 --> 00:52:16,320 group, um, who then also looks at what that person's doing and that person and 1019 00:52:16,320 --> 00:52:21,850 that person and says, well, her work over there actually has an interesting overtone 1020 00:52:21,850 --> 00:52:23,340 to the work that he's doing over there. 1021 00:52:23,850 --> 00:52:26,070 So here's something now, some commonality. 1022 00:52:26,070 --> 00:52:29,120 And now this suggests we should be building systems 1023 00:52:29,120 --> 00:52:30,220 that connect these together. 1024 00:52:30,660 --> 00:52:32,200 We're in a spot with AI where. 1025 00:52:32,895 --> 00:52:36,395 If you're just looking for the solutions that are right in front of your face, 1026 00:52:36,795 --> 00:52:39,915 by the time you implement them, the industry would have already gone three 1027 00:52:39,915 --> 00:52:41,295 or four iterations down the road, 1028 00:52:42,135 --> 00:52:42,445 right? 1029 00:52:42,625 --> 00:52:45,335 So you need to be in a spot where, yes, you are doing those. 1030 00:52:45,695 --> 00:52:47,225 That's just to keep up with the Joneses. 1031 00:52:47,745 --> 00:52:50,845 I think you also need to have some experimentation within your practice 1032 00:52:50,865 --> 00:52:52,615 to be asking the big questions. 1033 00:52:52,875 --> 00:52:54,555 How is this relevant for us? 1034 00:52:54,785 --> 00:52:57,675 It's not just about automating things. 1035 00:52:57,675 --> 00:53:01,165 It's not just going to speed things up, but where does it provide 1036 00:53:01,165 --> 00:53:03,215 increased value to your practice? 1037 00:53:03,535 --> 00:53:07,495 Um, and not just in a generic way to architecture and interiors 1038 00:53:07,495 --> 00:53:10,785 or urban design in general, but specifically how you do your work. 1039 00:53:11,045 --> 00:53:12,555 How does this fit to how you work? 1040 00:53:12,745 --> 00:53:16,775 So there needs to be conversations at a, at a technical implementation standpoint. 1041 00:53:17,335 --> 00:53:20,325 But also from a strategic and vision standpoint, what does this mean 1042 00:53:20,325 --> 00:53:23,675 for my company based on all those experiments that I'm seeing out there? 1043 00:53:24,795 --> 00:53:26,825 Evan Troxel: And I think what's interesting about the tools that 1044 00:53:26,825 --> 00:53:29,585 we're seeing is you mentioned up codes, you mentioned your design 1045 00:53:29,585 --> 00:53:31,395 intelligence chat bot, right? 1046 00:53:31,395 --> 00:53:36,165 You've got these really specific tools and that's how they work, right? 1047 00:53:36,195 --> 00:53:36,515 We've, 1048 00:53:36,815 --> 00:53:37,135 Shane Burger: Yeah. 1049 00:53:37,625 --> 00:53:39,185 Evan Troxel: that's exactly how they work. 1050 00:53:39,195 --> 00:53:42,592 They're super specific, but now we're starting to see like this idea of an 1051 00:53:42,592 --> 00:53:49,127 AI agent that then connects these APIs together so that This one can go talk 1052 00:53:49,127 --> 00:53:52,427 to that one and bring information back and they can talk to a third one and 1053 00:53:52,427 --> 00:53:56,637 they can all connect and kind of huddle and bring back information that pulls 1054 00:53:56,637 --> 00:53:58,027 a little bit out of each one of them. 1055 00:53:58,457 --> 00:54:02,437 And to do what you're talking about, like you, you basically 1056 00:54:02,437 --> 00:54:04,947 described your AI team of, of what 1057 00:54:05,007 --> 00:54:06,657 would be a firm's AI team. 1058 00:54:07,037 --> 00:54:08,447 They have to have that big picture. 1059 00:54:08,627 --> 00:54:12,197 They have to be tied into the business side and talking about strategies and 1060 00:54:12,527 --> 00:54:14,247 the culture of the firm and what the. 1061 00:54:14,862 --> 00:54:15,002 the. 1062 00:54:15,002 --> 00:54:19,942 values of the firm and the specific roles and tasks that people have 1063 00:54:19,942 --> 00:54:25,262 to do on a day to day basis and start to link up what problems and 1064 00:54:25,262 --> 00:54:28,562 challenges do we actually have and then pick the right tools for the job. 1065 00:54:28,832 --> 00:54:32,512 But have a really great understanding of all the tools on offer, and going 1066 00:54:32,512 --> 00:54:36,182 back to like the budgeting and the user license thing, I think this is, 1067 00:54:36,212 --> 00:54:40,002 it's making things actually way more complicated because we're seeing a 1068 00:54:40,082 --> 00:54:42,472 boom in all of these tools, right? 1069 00:54:42,482 --> 00:54:45,852 Just AI tools alone, if you just kept it in that bucket. 1070 00:54:46,007 --> 00:54:49,077 There's hundreds and hundreds and hundreds of them all of a sudden, and 1071 00:54:49,077 --> 00:54:51,277 they're all going straight to the users. 1072 00:54:51,307 --> 00:54:54,497 They're not going through the traditional channels of how you would 1073 00:54:54,497 --> 00:54:58,187 implement technology in a firm, if I worked at a firm and they didn't 1074 00:54:58,207 --> 00:55:03,147 offer access to open AI, like I, I would go get my own license of it 1075 00:55:03,157 --> 00:55:07,297 so that I could play around with it, but because I can, because open 1076 00:55:07,297 --> 00:55:13,217 AI is talking directly to me or making me able to do that, so Talk 1077 00:55:13,227 --> 00:55:15,327 about a nightmare for a firm, right? 1078 00:55:15,367 --> 00:55:19,237 Like to go back to our earlier and budgeting and figuring out like crystal 1079 00:55:19,237 --> 00:55:22,617 balling, how much we're going to spend in different categories over the year. 1080 00:55:23,217 --> 00:55:26,327 There's, it's, it's just a big, giant guess, right? 1081 00:55:26,327 --> 00:55:29,287 Like we don't know what tools we're going to be using because we don't even know the 1082 00:55:29,287 --> 00:55:31,077 projects we're going to have this year. 1083 00:55:31,087 --> 00:55:31,317 Right. 1084 00:55:31,317 --> 00:55:31,587 So 1085 00:55:31,967 --> 00:55:35,087 I think there's always going to be some of the usual suspects that of 1086 00:55:35,087 --> 00:55:37,977 course, we're going to use this and that on this project because we always 1087 00:55:37,977 --> 00:55:41,957 use this and that, but there's all these other things now too, that. 1088 00:55:42,357 --> 00:55:46,957 are proving to be incredibly useful or we're experimenting, right? 1089 00:55:46,967 --> 00:55:49,907 We're trying to find that out if they're going to be useful or not. 1090 00:55:49,917 --> 00:55:53,397 And then we have to keep our fingers on the pulse constantly over time because 1091 00:55:53,397 --> 00:55:58,407 they're also changing and updating and they're pivoting quickly as well. 1092 00:55:58,437 --> 00:55:59,587 We see that happening all the time. 1093 00:55:59,587 --> 00:56:05,267 So from a DT, IT perspective, bigger nightmare, bigger team, like 1094 00:56:05,277 --> 00:56:09,777 what do you have to do to actually keep abreast of what's going on? 1095 00:56:10,512 --> 00:56:10,852 Shane Burger: Right. 1096 00:56:10,902 --> 00:56:15,752 I, I mean, unfortunately it does end up needing to have a bigger team to cover 1097 00:56:15,752 --> 00:56:21,032 this amount of, of, um, Spread between different tools that are out there. 1098 00:56:21,362 --> 00:56:25,282 I mean, we don't, you know, the, the work happening on, uh, image 1099 00:56:25,292 --> 00:56:29,022 diffusion is mostly, mostly myself with another member of my team who 1100 00:56:29,022 --> 00:56:32,562 have been experimenting with it for, you know, a good year or more. 1101 00:56:32,852 --> 00:56:35,852 Um, but even then there's a number of the tools that we haven't had a 1102 00:56:35,852 --> 00:56:39,302 chance to, to properly try out or really to push ourselves through. 1103 00:56:39,742 --> 00:56:46,612 Um, I can think of at least three, three, diffusion right now. 1104 00:56:46,957 --> 00:56:50,897 Um, at some point we'd like to get it to one would be the ideal scenario. 1105 00:56:51,187 --> 00:56:55,597 Um, and we're talking with companies about, uh, which one we end up going with. 1106 00:56:55,927 --> 00:56:58,227 Um, but there's, you know, strong preferences and 1107 00:56:58,227 --> 00:56:59,377 experience with each of these. 1108 00:56:59,407 --> 00:57:02,757 And every two months, another one comes out with a different model or a new 1109 00:57:02,757 --> 00:57:04,497 feature and they leapfrog each other. 1110 00:57:04,557 --> 00:57:08,887 And everybody rightly and understandably has preferences as to which one 1111 00:57:08,887 --> 00:57:10,107 that they like to work with. 1112 00:57:10,387 --> 00:57:12,107 But as a company, we need to, at some point. 1113 00:57:13,442 --> 00:57:16,702 What is the primary tool that we're going to be using when it comes to the 1114 00:57:16,702 --> 00:57:21,102 chatbots you add on top of this, and this is arguably so in the image section to 1115 00:57:21,462 --> 00:57:23,422 the concerns about intellectual property. 1116 00:57:23,472 --> 00:57:28,122 They all have different rules about what information that you could submit to 1117 00:57:28,122 --> 00:57:30,432 them that won't be training their model. 1118 00:57:31,022 --> 00:57:32,337 I've appreciated that. 1119 00:57:32,647 --> 00:57:36,777 Things like, uh, you know, the, the chatbot, the copilots that Microsoft is 1120 00:57:36,777 --> 00:57:41,837 releasing based upon chat GPT 4, uh, do have protections for a company like ours 1121 00:57:41,837 --> 00:57:43,597 if you have an enterprise agreement. 1122 00:57:44,337 --> 00:57:47,467 Uh, things that you submit into it will not be going to train the model. 1123 00:57:47,747 --> 00:57:50,067 Uh, so I do appreciate that that sort of thing is happening. 1124 00:57:50,387 --> 00:57:54,747 But, um, a lot of this is going direct to the consumers, direct to the staff. 1125 00:57:54,827 --> 00:57:56,947 They're experimenting with this at home. 1126 00:57:56,947 --> 00:57:59,387 They've got, you know, the apps on their phone that they're 1127 00:57:59,587 --> 00:58:00,907 popping in queries and stuff. 1128 00:58:01,367 --> 00:58:02,027 Don't blame them. 1129 00:58:02,027 --> 00:58:03,397 It's like it's right in front of them. 1130 00:58:03,397 --> 00:58:04,217 It's easy to use. 1131 00:58:04,247 --> 00:58:05,787 Sometimes it's completely free. 1132 00:58:06,077 --> 00:58:10,822 But we have to be very aware that if there's project information, Or staff 1133 00:58:10,822 --> 00:58:13,792 information that are going into these systems, we have to start thinking 1134 00:58:13,792 --> 00:58:17,832 about, uh, privacy rights, intellectual property, copyright, all those types 1135 00:58:17,832 --> 00:58:19,112 of things have to come into play. 1136 00:58:19,452 --> 00:58:23,962 So, unfortunately, um, just around the time as we started creating 1137 00:58:23,962 --> 00:58:27,642 some forms that would help us better understand the full list of things we 1138 00:58:27,642 --> 00:58:31,542 need to consider for new platforms, there was a huge explosion of the 1139 00:58:31,542 --> 00:58:34,752 amount of those platforms of which we need to answer those same questions. 1140 00:58:35,042 --> 00:58:38,902 So, it's getting harder to manage that significant increase that's out there. 1141 00:58:39,287 --> 00:58:44,127 I really do appreciate, though, the significant competition that's out there. 1142 00:58:44,467 --> 00:58:47,967 I think a lot of these companies started off by saying, Well, we know 1143 00:58:47,967 --> 00:58:50,967 how to do this with AI, so let's find the market that will work with it. 1144 00:58:51,177 --> 00:58:55,037 And now they're starting to get feedback from customers like ourselves, who are 1145 00:58:55,037 --> 00:58:58,787 saying, Hey, that's cool and all, but we really needed to do this, this, and this. 1146 00:58:59,077 --> 00:59:03,897 Um, a good example, just with the, the image tools, is, uh, the first versions 1147 00:59:03,897 --> 00:59:08,082 that were out there were, Very much a, um, we know how to create this sort 1148 00:59:08,082 --> 00:59:10,592 of technology, throw it out there, see what people are doing with it. 1149 00:59:10,852 --> 00:59:13,822 Now, the next sets of features that are showing up are based upon 1150 00:59:13,822 --> 00:59:15,942 feedback that people are giving it. 1151 00:59:15,952 --> 00:59:19,342 We've given similar types of feedback to AI tools that have 1152 00:59:19,342 --> 00:59:20,992 been built into Rhino and Revit. 1153 00:59:21,252 --> 00:59:24,822 Saying, Hey, that's great, but it actually would help everybody if 1154 00:59:24,822 --> 00:59:28,622 you, you know, if it understood the materials that it was looking at, or 1155 00:59:28,622 --> 00:59:32,372 the three dimensionality of the object in order to inform the image creation. 1156 00:59:32,672 --> 00:59:36,002 So, um, I, at one point, I'm excited. 1157 00:59:36,622 --> 00:59:37,557 I love seeing all the new tools. 1158 00:59:38,287 --> 00:59:40,597 I love seeing the companies leapfrog over each other. 1159 00:59:40,867 --> 00:59:42,377 I love seeing all the innovation. 1160 00:59:42,647 --> 00:59:48,347 Um, but then if I, I put my, my, um, IT, you know, management sort of hat 1161 00:59:48,377 --> 00:59:51,937 back on my head again, I start getting scared of the amount of things that 1162 00:59:51,957 --> 00:59:53,457 we have to cover at the same time. 1163 00:59:53,757 --> 00:59:56,757 And again, we don't want to be in a spot where we're telling people no, 1164 00:59:57,097 --> 01:00:01,857 but as a company that has clients with confidential information and there's 1165 01:00:01,857 --> 01:00:04,187 issues of intellectual property ownership. 1166 01:00:04,497 --> 01:00:08,457 And there's costs associated with all of that, as well as buying licenses. 1167 01:00:08,727 --> 01:00:11,277 Um, we have to be on the conservative side. 1168 01:00:11,707 --> 01:00:15,487 Evan Troxel: Yeah There's a subject that I've been kind of knocking around in my 1169 01:00:15,487 --> 01:00:20,347 head, which is unrelated So we're gonna take a turn here but I'm curious what 1170 01:00:20,347 --> 01:00:23,077 your feedback would be on it because I you know if we talk about the future of 1171 01:00:23,077 --> 01:00:28,682 the profession one one of the things that We are mired in, and we're not alone. 1172 01:00:28,832 --> 01:00:34,532 This is, this seems to be everybody is this idea of like pseudo productivity. 1173 01:00:34,832 --> 01:00:38,852 it's very hard to measure productivity in architecture. 1174 01:00:38,872 --> 01:00:42,482 And, and now we're talking about tools that we're encouraging people 1175 01:00:42,482 --> 01:00:46,212 to play with from a creative sense, but also from an efficiency sense. 1176 01:00:46,982 --> 01:00:51,312 We've seen tools come along in the past that have promised 1177 01:00:51,392 --> 01:00:55,962 efficiency and productivity, but it really hasn't led to that, right? 1178 01:00:55,982 --> 01:01:00,962 Like our main production pipeline has enabled us to put more into projects, but 1179 01:01:00,962 --> 01:01:07,822 it hasn't really enabled us to spend less time doing that, but email, Slack, Teams, 1180 01:01:07,972 --> 01:01:12,032 Zoom, that's what I'm talking about when I'm talking about pseudoproductivity. 1181 01:01:12,062 --> 01:01:18,232 And when we're talking about a thousand people at a firm who spend a lot of time 1182 01:01:18,452 --> 01:01:24,632 in email and in tracking all of the, and in conversations, and what's your general 1183 01:01:24,632 --> 01:01:28,332 sense about how much time people spend doing that versus actually doing the job? 1184 01:01:28,342 --> 01:01:32,322 Because what, what I kind of feel like a reckoning that needs to happen is. 1185 01:01:32,822 --> 01:01:36,392 Actual valuable output of architecture. 1186 01:01:36,692 --> 01:01:40,232 And that doesn't even necessarily mean creating drawings, right? 1187 01:01:40,292 --> 01:01:41,452 That is a. 1188 01:01:42,567 --> 01:01:45,577 a thing that we have to do to get the permits to build the building 1189 01:01:45,577 --> 01:01:47,437 to satisfy the contract documents. 1190 01:01:47,777 --> 01:01:51,407 And something that Clifton Harness said on a podcast a long time ago was like, if 1191 01:01:51,417 --> 01:01:54,427 you want to really change architecture, change the OAC agreement, right? 1192 01:01:54,437 --> 01:01:58,397 Like actually go to the root of where a lot of this is. 1193 01:01:58,817 --> 01:02:01,147 And that's where the big fundamental changes. 1194 01:02:01,427 --> 01:02:06,507 And I feel like we've been boiling the frog with email and with, it's 1195 01:02:06,507 --> 01:02:09,747 like, okay, this is just the way that it is, but everybody is spending an 1196 01:02:10,182 --> 01:02:16,192 Unending amount of time being on call for anybody who dips into your inbox. 1197 01:02:16,662 --> 01:02:17,552 unwelcomed, right? 1198 01:02:17,552 --> 01:02:19,722 It's never, it's never like the other way around. 1199 01:02:19,722 --> 01:02:21,132 It's not like you invited them in. 1200 01:02:21,142 --> 01:02:24,162 No, they just dumped something onto your to do list for today. 1201 01:02:24,542 --> 01:02:26,372 What's your sense in a firm like yours? 1202 01:02:27,072 --> 01:02:30,132 That big, I mean, it's just got to be an enormous, like, you probably 1203 01:02:30,132 --> 01:02:33,322 don't even want to know, but at the same time, like this is the stuff that 1204 01:02:33,322 --> 01:02:34,482 people are actually doing every day. 1205 01:02:34,482 --> 01:02:36,312 And you want to say, we're architects, we're building, we're 1206 01:02:36,632 --> 01:02:38,142 designing the world of the future. 1207 01:02:38,142 --> 01:02:38,352 Right. 1208 01:02:38,402 --> 01:02:42,062 And, and at the same time we're doing email and we're on Slack all day long. 1209 01:02:42,947 --> 01:02:47,907 Shane Burger: Yeah, I, I, some of this is probably predating 1210 01:02:47,917 --> 01:02:49,917 me by a number of years. 1211 01:02:49,927 --> 01:02:54,317 Although I think when I started into, uh, started working for architecture 1212 01:02:54,317 --> 01:02:57,187 practices, I started doing my first internships in the late nineties. 1213 01:02:57,567 --> 01:03:00,892 And I would see this at this point as well, because not, not You 1214 01:03:00,892 --> 01:03:04,452 know, not everybody in the in the practice at that point had an email 1215 01:03:04,452 --> 01:03:06,792 address associated with material. 1216 01:03:06,812 --> 01:03:09,252 As an intern, I didn't have an email address. 1217 01:03:09,252 --> 01:03:12,142 So people came up to talk to me and I did what I was told to do. 1218 01:03:12,492 --> 01:03:17,582 Um, and as part of that, The teams were structured in a way, were more formally 1219 01:03:17,582 --> 01:03:21,372 structured to have people who are kind of document and communication controllers. 1220 01:03:21,642 --> 01:03:24,532 So they were basically holding back the floodgates of the information that was 1221 01:03:24,532 --> 01:03:27,792 coming from clients and consultants who were there in charge of communicating 1222 01:03:27,792 --> 01:03:28,912 the material that was out there. 1223 01:03:29,382 --> 01:03:35,652 Even when I started off at Grimshaw, my job as a job captain was I was primarily 1224 01:03:35,652 --> 01:03:40,787 responsible for dealing with Issuing the updated drawing sets for backgrounds to 1225 01:03:40,787 --> 01:03:43,947 our consultants to work with, receiving their information, coordinating, 1226 01:03:43,947 --> 01:03:45,147 making sure that was all set. 1227 01:03:45,417 --> 01:03:48,007 No one else in the team got involved in that conversation. 1228 01:03:48,447 --> 01:03:51,677 Um, if there were particular flows of communication coming 1229 01:03:51,677 --> 01:03:54,257 in, they had a particular person that they were associated with. 1230 01:03:54,707 --> 01:03:59,097 Uh, at some point, it started turning into, uh, why don't we just create 1231 01:03:59,127 --> 01:04:01,327 a, uh, project number email address? 1232 01:04:01,407 --> 01:04:02,377 Everything goes through that. 1233 01:04:02,797 --> 01:04:04,347 Well then everybody has access to that. 1234 01:04:04,687 --> 01:04:08,207 And then after a while it becomes, no, just everybody gets all the emails. 1235 01:04:08,597 --> 01:04:10,997 That's too much work to deal with the project control email. 1236 01:04:11,122 --> 01:04:11,972 Evan Troxel: And this was back in the 1237 01:04:11,972 --> 01:04:13,672 days when email was pop, right? 1238 01:04:13,692 --> 01:04:14,172 And so 1239 01:04:14,172 --> 01:04:16,922 it was like, if, if one person logged into that email address, 1240 01:04:16,942 --> 01:04:19,412 they were the only person going to download that email because it was 1241 01:04:19,412 --> 01:04:20,692 going to get deleted off the server. 1242 01:04:20,692 --> 01:04:22,602 We weren't even dealing with IMAP at that point. 1243 01:04:23,157 --> 01:04:23,387 Shane Burger: right. 1244 01:04:23,567 --> 01:04:27,277 And so this was, this is a case of where, um, we had limitations 1245 01:04:27,277 --> 01:04:30,897 with the technology, but they, in a way, weren't too far off from how 1246 01:04:30,897 --> 01:04:33,767 we were kind of managing projects and controlling those projects. 1247 01:04:34,107 --> 01:04:37,747 Um, we now have, uh, project management systems. 1248 01:04:37,757 --> 01:04:39,747 We use A Connects for a lot of our work. 1249 01:04:39,747 --> 01:04:42,957 People, we use all sorts of things that the contractors bring to the table. 1250 01:04:43,297 --> 01:04:47,471 Um, But we haven't necessarily picked up, you know, returned too much 1251 01:04:47,482 --> 01:04:50,682 of the idea of document control or particular flows of communication 1252 01:04:51,062 --> 01:04:55,912 because, um, email made it, uh, effectively democratized access to 1253 01:04:55,912 --> 01:04:57,692 communication and access to information. 1254 01:04:57,942 --> 01:05:01,642 So then it meant, well, why don't I just go and ask the person that I know has the 1255 01:05:01,642 --> 01:05:05,721 answer rather than going through, I would like the answer to my question, so I'm 1256 01:05:05,721 --> 01:05:08,842 going to email you, Evan, like you're the person I know that has it, doesn't matter 1257 01:05:08,842 --> 01:05:11,872 if you're not the, you know, don't have time to answer this right, I'm going to 1258 01:05:11,882 --> 01:05:13,532 ask you or I'm going to text you in Teams. 1259 01:05:14,187 --> 01:05:14,467 Right? 1260 01:05:14,857 --> 01:05:19,087 When we opened up the flood of communication to be as ubiquitous across 1261 01:05:19,087 --> 01:05:24,137 the entire project team, um, we lost control of the moments at which we can 1262 01:05:24,137 --> 01:05:26,017 keep ourselves separated from that. 1263 01:05:26,047 --> 01:05:29,717 And, and you end up having this sort of constant multitasking where there's 1264 01:05:29,717 --> 01:05:33,346 always communications happening, um, about a project that's interrupting 1265 01:05:33,346 --> 01:05:34,497 my workflow and what I'm doing. 1266 01:05:34,737 --> 01:05:37,307 I tend to be a person that works with headphones on because I 1267 01:05:37,317 --> 01:05:40,147 get easily distracted, and I cut out everything I possibly can. 1268 01:05:40,232 --> 01:05:42,482 We can because I'll shut off notifications. 1269 01:05:42,482 --> 01:05:46,492 I'll shut off everything because it's too easy to just say, Oh, there's a little 1270 01:05:46,502 --> 01:05:47,902 drip feed of things that are going on. 1271 01:05:48,202 --> 01:05:50,442 I think it's it's beyond just our profession. 1272 01:05:50,482 --> 01:05:53,622 It's just made it very easy to be distracted about these things. 1273 01:05:53,852 --> 01:05:57,372 The other thing about this, though, is that even when we attend 1274 01:05:57,382 --> 01:05:59,662 meetings, especially post pandemic. 1275 01:05:59,927 --> 01:06:01,047 We're distracted. 1276 01:06:01,427 --> 01:06:04,977 Um, not telling on anybody in particular, and I'm sure this is the 1277 01:06:04,977 --> 01:06:07,247 case across every architecture practice. 1278 01:06:07,307 --> 01:06:09,537 But when you walk through a studio and people are on video 1279 01:06:09,537 --> 01:06:12,377 conferences with others, they have other programs that are up. 1280 01:06:12,507 --> 01:06:14,727 They're doing drawing sets, they're doing other work. 1281 01:06:14,932 --> 01:06:15,302 Evan Troxel: Totally. 1282 01:06:15,457 --> 01:06:17,977 Shane Burger: Only half their attention is in the meeting at that point. 1283 01:06:17,977 --> 01:06:19,977 They're catching up other things, because they're busy. 1284 01:06:19,977 --> 01:06:23,807 They've been handed way too many things to do, and there's no separation between 1285 01:06:23,807 --> 01:06:24,721 what you, you know, what you're doing. 1286 01:06:25,012 --> 01:06:28,782 Um, how you communicate and when you work in these things, so it's a divided 1287 01:06:28,782 --> 01:06:32,672 attention, so it's a, it's a, it's a constant issue about distractions in 1288 01:06:32,672 --> 01:06:37,112 terms of communications and these things have not provided greater value to the 1289 01:06:37,112 --> 01:06:42,142 work that they've done, we've done, it's just made us a lot, a lot busier, um, 1290 01:06:42,512 --> 01:06:49,102 I have mixed feelings about automation, about how we use automation and what the 1291 01:06:49,102 --> 01:06:53,882 point of automation is, but ultimately for me, the, the real point around 1292 01:06:53,882 --> 01:06:58,752 automation is, I'll back up for a second and then hopefully this isn't necessarily 1293 01:06:58,752 --> 01:07:05,572 changing topics, but, um, automation for me, uh, you could say, uh, it's the 1294 01:07:05,572 --> 01:07:07,102 client that benefits from automation. 1295 01:07:07,452 --> 01:07:10,372 Well, if that's the case, then, you know, the client should have to pay 1296 01:07:10,412 --> 01:07:13,842 less money for your project because you were able to automate, you know, a 1297 01:07:13,852 --> 01:07:15,692 third of your construction document set. 1298 01:07:15,692 --> 01:07:17,072 So I'm going to pay you less money for that. 1299 01:07:17,202 --> 01:07:19,682 Okay, that's not necessarily going to benefit us. 1300 01:07:20,142 --> 01:07:23,532 If I go and say, okay, it should be the owners and shareholders 1301 01:07:23,672 --> 01:07:24,652 that benefit from this. 1302 01:07:25,247 --> 01:07:25,537 All right. 1303 01:07:25,867 --> 01:07:28,077 Um, fine, that's possible, right? 1304 01:07:28,077 --> 01:07:30,637 So we still charge the client the same amount of money, but we get 1305 01:07:30,637 --> 01:07:31,977 increased profit from that side. 1306 01:07:32,807 --> 01:07:36,267 The third option would be to say, it's the staff who benefit from automation. 1307 01:07:36,767 --> 01:07:41,617 And the reason why I focus on that is because ultimately, any tool that we use, 1308 01:07:41,637 --> 01:07:47,122 I want it to create, A better quality of experience, a better value of experience 1309 01:07:47,122 --> 01:07:49,022 for the people sitting at their desks. 1310 01:07:49,432 --> 01:07:54,592 If we can automate away something that was a mundane or repetitive tasks and giving 1311 01:07:54,592 --> 01:08:00,221 them agency to then choose what they do in replacement of that, whether it's 1312 01:08:00,272 --> 01:08:04,932 investing in the project in a different way, or God forbid, going to home to 1313 01:08:04,932 --> 01:08:06,502 have dinner with their family, right? 1314 01:08:06,532 --> 01:08:09,552 Like, or not working a weekend and getting good sleep. 1315 01:08:10,082 --> 01:08:11,471 All of those things. 1316 01:08:11,917 --> 01:08:16,447 Significantly benefit their life and their project, um, their experience 1317 01:08:16,466 --> 01:08:19,727 working for you, which is better for, you know, talent retention. 1318 01:08:20,107 --> 01:08:22,947 Um, they then contribute better to the project. 1319 01:08:22,957 --> 01:08:23,836 They're well rested. 1320 01:08:23,877 --> 01:08:25,716 They've appreciated the work that they've done. 1321 01:08:25,977 --> 01:08:29,336 They haven't had to sit there for eight hours working on a door schedule, which 1322 01:08:29,336 --> 01:08:32,426 they think is of low value to what they think they could provide to a project. 1323 01:08:32,727 --> 01:08:35,942 Which then means, The project is higher quality, delivered more 1324 01:08:35,942 --> 01:08:38,841 efficiently, so the shareholders of the company and principals benefit 1325 01:08:38,841 --> 01:08:41,551 from that, and ultimately the client benefits from it as well. 1326 01:08:41,812 --> 01:08:45,942 So, the, because they get a higher quality project, uh, or product out of that work. 1327 01:08:46,142 --> 01:08:50,932 So for me, If I look at any selection of tool that we're purchasing, anything 1328 01:08:50,932 --> 01:08:56,532 that promises greater efficiencies, um, better, you know, um, better 1329 01:08:56,532 --> 01:08:59,912 communication, speeding things up, automating things, or a tool that we 1330 01:08:59,912 --> 01:09:05,077 built, the question I keep coming back to every single time is, Is it creating 1331 01:09:05,077 --> 01:09:08,947 a better quality experience for the staff who are actively working on the project? 1332 01:09:09,267 --> 01:09:12,346 If it's not doing that, then it's less likely we're going 1333 01:09:12,346 --> 01:09:13,426 to go that sort of direction. 1334 01:09:13,647 --> 01:09:19,357 That's my measure, is, uh, will people actually, not just necessarily that they 1335 01:09:19,357 --> 01:09:23,657 need to enjoy it, but will it give them more agency over their time, and give 1336 01:09:23,657 --> 01:09:28,227 them an ability to provide greater value to the work that they do in the studios? 1337 01:09:28,907 --> 01:09:32,047 Evan Troxel: My fear is that, and I don't think that that is disconnected 1338 01:09:32,047 --> 01:09:33,547 from, from the topic at all. 1339 01:09:33,557 --> 01:09:35,737 I think it's right, it's right in, right in there. 1340 01:09:36,437 --> 01:09:38,367 It's just a different way of looking at it. 1341 01:09:38,417 --> 01:09:41,692 Because I don't think anybody goes to work and says they're 1342 01:09:41,702 --> 01:09:43,322 planning on doing a bad job. 1343 01:09:43,381 --> 01:09:43,862 And I think 1344 01:09:43,872 --> 01:09:50,952 that's why BIM has led us down the path that we're on, which is, it's, it enabled 1345 01:09:50,952 --> 01:09:52,682 us to put more data into the project. 1346 01:09:52,692 --> 01:09:58,172 And, and there is a thinking that more data is higher quality. 1347 01:09:58,172 --> 01:09:58,432 It's a 1348 01:09:58,442 --> 01:09:59,652 better project. 1349 01:10:00,352 --> 01:10:02,962 It hasn't taken away how much time it takes to do it. 1350 01:10:02,972 --> 01:10:05,742 And in some cases, in many cases, it actually takes more 1351 01:10:05,742 --> 01:10:07,662 time to do it the right way. 1352 01:10:08,182 --> 01:10:09,752 And so that's my fear is that like. 1353 01:10:10,007 --> 01:10:16,557 Tools will be sold under the guise of efficiency, productivity, um, deeper, 1354 01:10:16,617 --> 01:10:21,247 higher quality work, but we will be spending more time because it's additive. 1355 01:10:21,287 --> 01:10:24,387 Like all of these other communication tools that are swimming around us 1356 01:10:24,387 --> 01:10:28,647 and distracting us and we're forced to use them because my supervisor 1357 01:10:28,717 --> 01:10:32,581 sent me an email and now I have to respond to it, um, even though I 1358 01:10:32,581 --> 01:10:34,602 wasn't planning on doing that today. 1359 01:10:35,082 --> 01:10:38,222 Because I need this software license back to the earlier part in our, in 1360 01:10:38,222 --> 01:10:38,882 our conversation. 1361 01:10:39,092 --> 01:10:42,272 Like there's all of these things pulling at us and, and they're all additive. 1362 01:10:42,292 --> 01:10:44,882 Like there, there's never part of the conversation is like, 1363 01:10:44,892 --> 01:10:46,982 okay, what do I deprioritize now? 1364 01:10:47,662 --> 01:10:50,332 because there's this new thing on my plate all of a sudden. 1365 01:10:50,752 --> 01:10:52,242 And so that, that's where my fear is. 1366 01:10:52,252 --> 01:10:55,712 And I, I, I love how you kind of bring it back to quality. 1367 01:10:55,762 --> 01:10:58,112 My fear is that it's just more quality. 1368 01:10:58,132 --> 01:10:58,862 It's just more. 1369 01:10:59,182 --> 01:10:59,772 And, and 1370 01:10:59,992 --> 01:11:02,542 that, because I, we, we've seen this before. 1371 01:11:02,882 --> 01:11:06,302 Um, I think that there's like a reckoning that needs to happen at 1372 01:11:06,302 --> 01:11:09,672 the highest levels of leadership in a company, which, which says like, 1373 01:11:09,682 --> 01:11:11,802 we have to change the way we work. 1374 01:11:12,212 --> 01:11:16,912 We have to, we have to be productive in the right ways with the kind of output. 1375 01:11:16,912 --> 01:11:18,502 Like, why do we exist? 1376 01:11:18,502 --> 01:11:21,102 We do not exist to process email. 1377 01:11:21,142 --> 01:11:21,802 We do not 1378 01:11:21,802 --> 01:11:24,622 exist to be on call for everyone all the time. 1379 01:11:24,892 --> 01:11:25,972 And you're a global company. 1380 01:11:25,972 --> 01:11:27,272 You have workers in Australia. 1381 01:11:27,462 --> 01:11:30,042 There's a new bill that just passed the Senate. 1382 01:11:30,042 --> 01:11:31,642 They are the right to disconnect. 1383 01:11:31,652 --> 01:11:32,462 Have you seen this? 1384 01:11:32,870 --> 01:11:34,210 Shane Burger: I heard about it briefly, but yeah, 1385 01:11:34,405 --> 01:11:37,205 Evan Troxel: I mean, the idea of it is, is kind of insane and 1386 01:11:37,205 --> 01:11:39,015 also totally expected, right? 1387 01:11:39,035 --> 01:11:39,235 It's 1388 01:11:39,235 --> 01:11:43,105 like, I don't have to answer emails or text messages after work hours. 1389 01:11:43,525 --> 01:11:46,955 And, and what's crazy is, is like, we're, we're, we're at that point. 1390 01:11:46,965 --> 01:11:48,915 Architecture has been at this point forever, right? 1391 01:11:48,915 --> 01:11:52,830 So this is nothing new for architecture, but it's, it's like, After hours is 1392 01:11:52,830 --> 01:11:55,420 when I actually get work done because I'm so distracted all day long, 1393 01:11:55,920 --> 01:11:56,140 right? 1394 01:11:58,750 --> 01:12:02,720 So, I mean, you have a, you have an Australian studio, right? 1395 01:12:02,750 --> 01:12:05,860 And, and so I, I don't know if this affects you guys or not. 1396 01:12:05,880 --> 01:12:09,360 I'm sure it does in some ways, but it's like, it's, it's, this is kind of a, 1397 01:12:09,730 --> 01:12:13,890 again, like a boiling the frog, like this is just the way it is and we expect it. 1398 01:12:14,340 --> 01:12:18,440 And, and I also feel like a reckoning needs to happen to say like, no, we're, 1399 01:12:18,670 --> 01:12:21,240 We do creative, world changing work. 1400 01:12:21,250 --> 01:12:23,270 We are creators of the built environment. 1401 01:12:23,430 --> 01:12:25,030 That's why we exist. 1402 01:12:25,420 --> 01:12:29,550 And people hire us because Woods Bagot is going to come up with 1403 01:12:29,550 --> 01:12:31,640 ideas that we've never dreamed of. 1404 01:12:31,680 --> 01:12:35,640 And, and that's why we chose to, and, and it's like, Yeah, but you, we're 1405 01:12:35,640 --> 01:12:38,610 spending most of our time processing email and replying to Slack messages, 1406 01:12:39,130 --> 01:12:42,230 Shane Burger: and to go back to a little bit of the AI conversation, a 1407 01:12:42,230 --> 01:12:46,490 lot of that stuff is the, is the sort of material that I would rather we focus 1408 01:12:46,490 --> 01:12:51,090 more energy on as an industry to automate or to deal with to get that stuff away. 1409 01:12:51,300 --> 01:12:54,570 I mean, number one, I have to say, we have always have to ask the question, 1410 01:12:54,580 --> 01:12:57,660 are we spending time developing automation tools for processes we 1411 01:12:57,660 --> 01:12:59,010 should never do in the first place? 1412 01:12:59,260 --> 01:13:00,900 That's always the first thing, Right. 1413 01:13:01,240 --> 01:13:02,930 Should you even be doing that? 1414 01:13:03,240 --> 01:13:06,350 But for the things that we're doing, are there better ways of us actually 1415 01:13:06,350 --> 01:13:10,975 providing access to the answers to the question, getting you to the outcomes 1416 01:13:10,975 --> 01:13:12,515 that you're actually looking for. 1417 01:13:12,755 --> 01:13:15,125 It's not just that you say you need this big report. 1418 01:13:15,145 --> 01:13:16,585 What's the outcome you're looking for? 1419 01:13:16,595 --> 01:13:18,615 I can probably provide that in a better way, 1420 01:13:18,915 --> 01:13:22,055 or I can build in systems or work with tools to help me kind 1421 01:13:22,055 --> 01:13:23,605 of achieve that sort of goal. 1422 01:13:24,175 --> 01:13:28,375 Instead, we've gotten excited about, uh, uh, interjecting 1423 01:13:28,445 --> 01:13:29,695 AI into the creative work. 1424 01:13:29,695 --> 01:13:32,755 The thing that we, a lot of us love and value and that we think 1425 01:13:32,755 --> 01:13:34,415 we provide additional value to. 1426 01:13:34,735 --> 01:13:38,035 What I'm really appreciating about these conversations that we're having within 1427 01:13:38,035 --> 01:13:43,595 our practice right now is, uh, in addition to looking at what we automate and where 1428 01:13:43,595 --> 01:13:47,915 there's inefficiencies and problems and, you know, any of our processes that we 1429 01:13:47,915 --> 01:13:52,215 think we can be better at and do better at, we're also asking some real questions. 1430 01:13:52,215 --> 01:13:54,525 What is the human intelligence value? 1431 01:13:54,875 --> 01:13:56,335 Where do we combine it? 1432 01:13:56,855 --> 01:14:00,105 an AI and an HI or human intelligence component. 1433 01:14:00,395 --> 01:14:05,805 And what does this help us revalue about what we, as designers, as architects, 1434 01:14:05,805 --> 01:14:10,135 interior designers, urban designers, consultants, um, uh, value about our work? 1435 01:14:10,145 --> 01:14:12,795 What, what's unique about what we provide to our clients. 1436 01:14:13,015 --> 01:14:15,134 So it's actually turned into a really. 1437 01:14:15,625 --> 01:14:19,985 Interesting, empathetic conversation, you know, how does empathy come back into it? 1438 01:14:20,035 --> 01:14:22,795 Understanding what others are thinking, how others are working. 1439 01:14:23,184 --> 01:14:28,085 I think, I think we're going to get to this point where, um, my 1440 01:14:28,085 --> 01:14:32,445 reference for this is, uh, the, uh, MIT researcher, Marvin Minsky's 1441 01:14:32,505 --> 01:14:34,195 concept of society of the mind. 1442 01:14:34,515 --> 01:14:35,475 We're going to get to this point. 1443 01:14:35,475 --> 01:14:36,255 We're going to have. 1444 01:14:36,620 --> 01:14:40,240 a collection of AIs around us, this sort of society of the mind of AIs 1445 01:14:40,240 --> 01:14:44,140 that help us automate portions of our processes and the work that we do. 1446 01:14:44,430 --> 01:14:49,390 Um, but my hope is that the end result of that is we become much more 1447 01:14:49,390 --> 01:14:54,980 empathetic designers and people out of that, because we can get rid of more 1448 01:14:54,980 --> 01:14:59,690 and more of these things that are less necessary for our work and actually bring 1449 01:14:59,700 --> 01:15:04,245 those qualities, those uniquely human qualities, to the How we design, how 1450 01:15:04,245 --> 01:15:07,445 we work with our partners here in the studio, how we work with our partners 1451 01:15:07,445 --> 01:15:08,985 outside, and how we work with our clients. 1452 01:15:09,315 --> 01:15:14,605 So I, I think it's, we've hit this real point of tension of where our industry 1453 01:15:14,605 --> 01:15:18,565 feels like it's not as efficient as it could be, but we're overloaded with things 1454 01:15:18,565 --> 01:15:21,355 that we think aren't of as great value. 1455 01:15:21,805 --> 01:15:24,295 I would hope it brings about real questions about what outcomes 1456 01:15:24,295 --> 01:15:27,068 we're looking for, but also what value we bring to the table. 1457 01:15:27,632 --> 01:15:28,502 Evan Troxel: there's a lot there. 1458 01:15:28,502 --> 01:15:32,312 And you talked earlier about kind of automating away, maybe 1459 01:15:32,312 --> 01:15:37,452 potentially having to do less, but, but having a higher quality, more 1460 01:15:37,462 --> 01:15:40,092 valuable experience as well as. 1461 01:15:42,567 --> 01:15:45,797 I'm curious what you think about the idea with when AI gets 1462 01:15:45,797 --> 01:15:48,067 involved in the creative process. 1463 01:15:48,077 --> 01:15:51,647 So you just talked about kind of augmenting people, kind of co designing 1464 01:15:51,647 --> 01:15:55,477 human intelligence, artificial intelligence, augmented intelligence. 1465 01:15:55,477 --> 01:15:55,707 I don't know. 1466 01:15:55,707 --> 01:15:56,667 There's a lot of ways we could 1467 01:15:57,117 --> 01:15:58,217 play with those words. 1468 01:15:58,237 --> 01:16:02,477 But what kinds of things are you seeing there that, you know, You 1469 01:16:02,477 --> 01:16:03,547 said you're playing with this. 1470 01:16:03,567 --> 01:16:06,207 You've got a couple other people in the, in the firm playing with this. 1471 01:16:06,507 --> 01:16:11,727 What potentials are you seeing here and what potential impact do you see it 1472 01:16:11,817 --> 01:16:13,967 having on the architectural profession? 1473 01:16:13,968 --> 01:16:15,336 Right. 1474 01:16:15,408 --> 01:16:19,818 Shane Burger: So I think the way that I this came up in a conversation 1475 01:16:19,827 --> 01:16:23,178 with our principals a few weeks ago, and I gave a presentation or global 1476 01:16:23,178 --> 01:16:24,708 studio just last week about this. 1477 01:16:25,077 --> 01:16:26,128 We're asking the question. 1478 01:16:26,128 --> 01:16:27,708 Can AI's be creative? 1479 01:16:28,038 --> 01:16:29,918 Um, and a lot of this came back to we. 1480 01:16:30,783 --> 01:16:31,843 presented to the group. 1481 01:16:31,923 --> 01:16:33,073 What is machine learning? 1482 01:16:33,073 --> 01:16:33,783 How does it work? 1483 01:16:34,003 --> 01:16:37,843 You know, statistical model, uh, that effectively generative AI is just 1484 01:16:37,843 --> 01:16:39,833 an upgraded version of autocomplete. 1485 01:16:40,163 --> 01:16:42,423 That seems like I'm dismissing it, but it's actually, that's 1486 01:16:42,423 --> 01:16:44,333 an incredibly powerful concept. 1487 01:16:44,623 --> 01:16:47,433 So it led to discussions about where it can make mistakes, 1488 01:16:47,673 --> 01:16:49,693 things that can and cannot do. 1489 01:16:50,023 --> 01:16:53,443 Um, for example, uh, it doesn't have a mental model of the world. 1490 01:16:53,643 --> 01:16:59,363 It doesn't have a, a concept of mind, of, um, of how other people think. 1491 01:16:59,373 --> 01:17:03,243 I know you as a human, so I look at you and I can make some assumptions about 1492 01:17:03,243 --> 01:17:07,233 your method of judgment and your reasoning that gives me trust in what you're doing. 1493 01:17:07,563 --> 01:17:10,613 And we can also speak a certain language with each other and understand 1494 01:17:10,613 --> 01:17:12,683 that there's some similarities in the sort of backgrounds. 1495 01:17:12,963 --> 01:17:16,723 But the things that we're looking at were, um, I talked about three different kinds 1496 01:17:16,723 --> 01:17:21,603 of creativity, um, and I'm blanking on the author that this came from at the moment. 1497 01:17:21,603 --> 01:17:24,613 Don't have my notes in front of me, but, um, one was called 1498 01:17:24,633 --> 01:17:26,103 combinatorial creativity. 1499 01:17:26,353 --> 01:17:28,452 Another was exploratory creativity. 1500 01:17:28,452 --> 01:17:31,722 And then there's transformational creativity and combinatorial creativity. 1501 01:17:31,883 --> 01:17:33,053 Actually, I'll hit the second first. 1502 01:17:33,093 --> 01:17:37,213 Exploratory creativity is taking the context of a single style 1503 01:17:37,403 --> 01:17:40,513 and exploring all the potential opportunities that sit within it. 1504 01:17:40,823 --> 01:17:43,643 Um, and I've seen some examples of this out here when I looked at 1505 01:17:43,693 --> 01:17:48,423 presentations, for example, by um, Patrik Schumacher for Zaha Hadid's office. 1506 01:17:48,423 --> 01:17:53,483 They were showing how they fed in, Images of Zaha Hadid's work into DALL-E and 1507 01:17:53,493 --> 01:17:57,053 explored all the potential opportunities that were sitting within that by 1508 01:17:57,053 --> 01:17:58,633 giving just different descriptions. 1509 01:17:59,003 --> 01:18:02,303 Um, at one point I can see how maybe that would yield some 1510 01:18:02,303 --> 01:18:03,583 new and interesting ideas. 1511 01:18:03,833 --> 01:18:06,543 However, I had to back up for a moment and think to myself. 1512 01:18:07,013 --> 01:18:10,173 Those are not Zaha Hadid projects. 1513 01:18:10,503 --> 01:18:14,463 Those are professional photographs of Zaha Hadid projects. 1514 01:18:14,743 --> 01:18:18,333 You are not pulling out of them the sort of essences that are really 1515 01:18:18,333 --> 01:18:20,113 possible with these types of things. 1516 01:18:20,443 --> 01:18:22,473 it's not that you want to mimic a style. 1517 01:18:23,008 --> 01:18:25,958 You actually, through looking at the work of other people, want to get 1518 01:18:25,958 --> 01:18:29,398 your head into the thinking of the artist and architect that created it. 1519 01:18:29,798 --> 01:18:32,358 And this system is not permitting you to do that. 1520 01:18:32,398 --> 01:18:35,668 Um, uh, it is stopping you at a certain point. 1521 01:18:35,678 --> 01:18:37,858 So that really frustrated me to see that. 1522 01:18:37,858 --> 01:18:39,548 So then I started to think, okay, well, hold on. 1523 01:18:39,818 --> 01:18:41,318 There's other methods that are out there. 1524 01:18:41,318 --> 01:18:44,068 And that's when I get into combinatorial creativity. 1525 01:18:44,318 --> 01:18:47,593 So with combinatorial creativity, there might be, ways at which I 1526 01:18:47,593 --> 01:18:49,193 mash up two styles with each other. 1527 01:18:49,202 --> 01:18:50,413 You see this all the time. 1528 01:18:50,753 --> 01:18:54,613 Um, I saw some great work from some, um, architecture professors 1529 01:18:54,613 --> 01:18:59,053 at university that were looking at skyscrapers and designs influenced by 1530 01:18:59,063 --> 01:19:01,113 billowing fabric, and it was gorgeous. 1531 01:19:01,113 --> 01:19:01,863 It was amazing. 1532 01:19:01,863 --> 01:19:05,493 And it, it, the ideas that started to pop up for you because it was 1533 01:19:05,493 --> 01:19:08,643 combining something you knew, maybe it was something that you didn't know. 1534 01:19:08,952 --> 01:19:11,603 So it's opening up the wide array of possibilities. 1535 01:19:11,933 --> 01:19:15,613 And in those sorts of cases, we were also, uh, In our practice, looking 1536 01:19:15,613 --> 01:19:19,333 at the opportunities for narrative to influence that, so we'd almost tell a 1537 01:19:19,333 --> 01:19:25,183 story or we describe an experience and see what images and things would come up. 1538 01:19:25,213 --> 01:19:29,282 And it wouldn't be architecture, but it would be something evocative 1539 01:19:29,282 --> 01:19:32,293 of a concept, something that got you excited and got you thinking. 1540 01:19:32,543 --> 01:19:36,263 So never something you would show a client except maybe if it was like a mood board. 1541 01:19:36,543 --> 01:19:37,532 It's not architecture. 1542 01:19:37,773 --> 01:19:38,583 It's a feeling. 1543 01:19:38,613 --> 01:19:39,223 It's a mood. 1544 01:19:39,263 --> 01:19:40,333 And there might be. 1545 01:19:40,657 --> 01:19:46,248 Colors, textures, shapes, things that pop up that are representative of that 1546 01:19:46,248 --> 01:19:47,638 mood, that influence your thinking. 1547 01:19:47,818 --> 01:19:52,168 So that was a spot where we had some level of excitement, but then we get 1548 01:19:52,168 --> 01:19:55,868 to the third level of creativity, which is transformational creativity. 1549 01:19:56,178 --> 01:20:00,657 And that is honestly where you take core concepts that might 1550 01:20:00,657 --> 01:20:02,188 exist in other professions. 1551 01:20:02,538 --> 01:20:05,728 Um, it might be, um, allegory. 1552 01:20:06,538 --> 01:20:12,058 It might be, um, meaning that's derived from particular historic contexts, 1553 01:20:12,577 --> 01:20:16,698 things that are beyond what you can see just within an image, um, shapes 1554 01:20:16,698 --> 01:20:20,168 and colors and textures and, and types of movement that have particular 1555 01:20:20,168 --> 01:20:24,298 kinds of meaning combined with what we experience with our, our bodies. 1556 01:20:24,298 --> 01:20:26,718 You know, our, our cognition is embodied cognition. 1557 01:20:26,728 --> 01:20:28,077 So we have a different kind of experience. 1558 01:20:28,558 --> 01:20:31,948 That is where transformational creativity comes into play because you've got to 1559 01:20:31,948 --> 01:20:33,568 take things from other disciplines. 1560 01:20:33,813 --> 01:20:36,363 That are abstract concepts and apply it to your work. 1561 01:20:36,743 --> 01:20:39,213 Um, that might be taken from music or dance. 1562 01:20:39,223 --> 01:20:42,773 It might be taken from a scientific context or a historic 1563 01:20:42,773 --> 01:20:44,123 event that happened on the site. 1564 01:20:44,613 --> 01:20:48,543 That is where I've seen a lot more interesting innovations and 1565 01:20:48,543 --> 01:20:51,643 architectures that get to that level of transformational creativity. 1566 01:20:51,893 --> 01:20:55,333 Those are the things that move our cultural needle ahead, right? 1567 01:20:55,773 --> 01:20:57,023 Culture is not stagnant. 1568 01:20:57,023 --> 01:20:58,343 Language is not stagnant. 1569 01:20:58,663 --> 01:20:59,963 Style is not stagnant. 1570 01:21:00,003 --> 01:21:02,623 Those transformational moments really move things forward. 1571 01:21:02,973 --> 01:21:04,303 We don't get that out of an A. 1572 01:21:04,303 --> 01:21:04,443 I. 1573 01:21:04,452 --> 01:21:10,003 system because it's based upon the particular two dimensional representation 1574 01:21:10,263 --> 01:21:11,963 of what we have seen in the past. 1575 01:21:12,223 --> 01:21:16,383 So I think what we need to understand is that there are absolutely possibilities 1576 01:21:16,383 --> 01:21:19,523 to explore ideas and extend our thinking and how we approach work. 1577 01:21:19,853 --> 01:21:23,313 But we have to absolutely understand what those limitations are. 1578 01:21:23,643 --> 01:21:28,143 Um, those, I almost, you know, the way that I've referred to it with our, our 1579 01:21:28,143 --> 01:21:32,938 staff is, um, Treat it like it's a, uh, junior member of your team that comes 1580 01:21:32,938 --> 01:21:36,598 from, you know, you know, didn't go to school with you, went to some other 1581 01:21:36,598 --> 01:21:40,308 sort of school, has crazy, whacked out ideas that they're throwing under the 1582 01:21:40,308 --> 01:21:44,688 table, and one out of every 50 is going to be worth looking at and considering. 1583 01:21:45,198 --> 01:21:48,478 They're not realistic, they're not the answer, but they 1584 01:21:48,478 --> 01:21:50,407 create a new space to explore. 1585 01:21:50,838 --> 01:21:53,538 They prompt your thinking, they get something happening, and that's 1586 01:21:53,538 --> 01:21:55,907 a value, but it's not the answer. 1587 01:21:55,998 --> 01:21:58,808 It's not a solution, it's a, it's a space to explore. 1588 01:21:59,437 --> 01:22:02,347 Evan Troxel: I did an episode with Ben Guler from Evolve Lab, and 1589 01:22:02,347 --> 01:22:05,387 they make the rendering application Veras, which is an AI rendering 1590 01:22:05,387 --> 01:22:09,137 application for Rhino, and Revit, and Vectorworks, and now Forma, 1591 01:22:09,697 --> 01:22:12,357 um, and ArchiCAD, and SketchUp. 1592 01:22:12,707 --> 01:22:16,837 So the, the, the idea that, that we talked about in there was that 1593 01:22:16,857 --> 01:22:18,857 it's prompting us, and that's why 1594 01:22:18,857 --> 01:22:19,416 I bring it up. 1595 01:22:19,467 --> 01:22:21,437 It's, it's like, it is a feedback loop, right? 1596 01:22:21,457 --> 01:22:25,497 And so one out of 50 isn't bad when you're in the design exploration, 1597 01:22:26,068 --> 01:22:26,268 Shane Burger: Yeah. 1598 01:22:26,592 --> 01:22:28,672 Evan Troxel: Because I mean, that's, this is what designers do. 1599 01:22:28,672 --> 01:22:29,902 Like, it's all a training model. 1600 01:22:29,912 --> 01:22:30,452 We are 1601 01:22:30,452 --> 01:22:34,602 constantly taking input from all over the place, filing it away. 1602 01:22:34,642 --> 01:22:35,842 You don't know when you're going to use it. 1603 01:22:36,142 --> 01:22:38,232 And then the opportunity presents itself. 1604 01:22:38,242 --> 01:22:40,892 You and creativity doesn't happen when you want it to. 1605 01:22:40,942 --> 01:22:41,402 It just 1606 01:22:41,402 --> 01:22:42,262 happens, right? 1607 01:22:42,291 --> 01:22:46,882 We can't explain that, but it's like, we're connecting dots. 1608 01:22:46,902 --> 01:22:48,242 That's what we do as designers. 1609 01:22:48,262 --> 01:22:52,082 I love talking to you about this, Shane, because, and maybe this is, 1610 01:22:52,153 --> 01:22:57,272 That's a total aside, but I think it is so important for somebody in your 1611 01:22:57,272 --> 01:22:59,032 position to come from the practice side. 1612 01:22:59,572 --> 01:23:02,782 I think that is so key because the things that you're talking 1613 01:23:02,782 --> 01:23:07,291 about and, and then you get into implementation and licensing and, and 1614 01:23:07,302 --> 01:23:11,992 application and all of these things, but, but you're coming at it from a really pure 1615 01:23:12,002 --> 01:23:15,442 place of like the pursuit of our craft. 1616 01:23:15,812 --> 01:23:18,032 And that to me is so important. 1617 01:23:18,062 --> 01:23:20,342 And there's, there's a lot of people out there. 1618 01:23:20,666 --> 01:23:25,437 Like you, who are in positions, and I just think like it is a huge advantage 1619 01:23:25,437 --> 01:23:31,057 for firms to have somebody come from that perspective or that approach or that 1620 01:23:31,057 --> 01:23:35,842 way of thinking about it, because It's about architecture, and you're constantly 1621 01:23:35,852 --> 01:23:37,782 bringing it back to architecture. 1622 01:23:37,782 --> 01:23:40,252 You're not just trying to solve this very narrow problem. 1623 01:23:40,912 --> 01:23:46,332 Sometimes that may be a narrow solution to a much larger piece of the puzzle, um, but 1624 01:23:46,332 --> 01:23:48,182 you're looking at it puzzle scale, right? 1625 01:23:48,202 --> 01:23:50,212 And, and I think that that's, that's really cool. 1626 01:23:50,632 --> 01:23:54,202 It's really interesting to think about the hit rate. 1627 01:23:54,472 --> 01:23:56,672 of, of interesting things. 1628 01:23:56,712 --> 01:23:57,192 And that, 1629 01:23:57,202 --> 01:23:58,692 that, but that's what creativity is. 1630 01:23:58,702 --> 01:24:01,712 Like it's, it's funny that people want to throw up a red flag 1631 01:24:01,712 --> 01:24:02,752 and be like, it makes mistakes. 1632 01:24:02,762 --> 01:24:05,932 It's like, okay, I make mistakes, you make mistakes, we all make mistakes. 1633 01:24:05,952 --> 01:24:06,692 And sometimes 1634 01:24:06,692 --> 01:24:12,312 the mistakes lead to unexpected outcomes, surprising things that 1635 01:24:12,342 --> 01:24:15,102 all of a sudden that's a new path that wasn't available to us before. 1636 01:24:15,112 --> 01:24:17,932 Like Bob Ross, the painter said, happy little accidents, right? 1637 01:24:17,942 --> 01:24:18,202 It's 1638 01:24:18,202 --> 01:24:20,152 totally true when it comes to creativity. 1639 01:24:20,803 --> 01:24:23,083 Shane Burger: there's an aspect of cultural transformation 1640 01:24:23,083 --> 01:24:24,093 that comes out of mistakes. 1641 01:24:24,202 --> 01:24:28,183 There was a debate that we had about six months ago, a playful 1642 01:24:28,193 --> 01:24:31,893 debate that I was organized in as part of the World City Conference. 1643 01:24:31,893 --> 01:24:35,653 And it was a two teams pitted against each other around the role of the 1644 01:24:35,653 --> 01:24:37,913 architect in urban design in a city. 1645 01:24:38,183 --> 01:24:42,143 And one group, not necessarily that they actually agreed with this perspective, 1646 01:24:42,143 --> 01:24:46,023 but three people were picked to be, yes, it's AI is going to replace the architect. 1647 01:24:46,032 --> 01:24:49,263 I was on the, no, AI isn't going to replace the architect side. 1648 01:24:49,708 --> 01:24:52,858 One of the arguments that we made was, this presentation was in New 1649 01:24:52,858 --> 01:24:59,338 York City, um, a, a, an AI would want to create a city that was hyper 1650 01:24:59,338 --> 01:25:02,918 efficient, you know, as pure and as clean and as simple as possible, 1651 01:25:03,228 --> 01:25:03,907 but it would become, 1652 01:25:04,047 --> 01:25:04,837 Evan Troxel: gotta start over. 1653 01:25:04,867 --> 01:25:06,597 You can't, you can't make a New York City. 1654 01:25:07,278 --> 01:25:07,508 Shane Burger: Right. 1655 01:25:07,538 --> 01:25:09,488 It would be completely devoid of culture. 1656 01:25:09,618 --> 01:25:10,618 It wouldn't have any depth. 1657 01:25:10,648 --> 01:25:11,558 It wouldn't have meaning. 1658 01:25:11,848 --> 01:25:17,088 There are all sorts of happy accidents, to quote Bob Ross, that have happened 1659 01:25:17,268 --> 01:25:18,768 in the urban planning of New York City. 1660 01:25:18,918 --> 01:25:21,268 Now, granted, a lot weren't happy accidents. 1661 01:25:21,268 --> 01:25:25,228 They were very angry accidents in terms of, um, you know, bulldozing 1662 01:25:25,228 --> 01:25:28,468 over portions of the Bronx and Brooklyn and disadvantaged neighborhoods. 1663 01:25:28,698 --> 01:25:31,708 But there were other things that happened that were in the gaps, in 1664 01:25:31,708 --> 01:25:34,508 the gray areas, in the mistakes, in the overlaps, in the oddities. 1665 01:25:34,868 --> 01:25:38,968 Um, it's in the movement from one neighborhood to another, encountering 1666 01:25:38,978 --> 01:25:41,407 one cultural group butting up against another cultural group. 1667 01:25:41,688 --> 01:25:44,708 Things that an AI would want to make more efficient and organized and more 1668 01:25:44,708 --> 01:25:48,178 productive with a different, completely different set of goals, where we have 1669 01:25:48,178 --> 01:25:53,368 actually appreciated those accidents and differences and what happens in a temporal 1670 01:25:53,368 --> 01:25:55,657 quality over time, what changes over time. 1671 01:25:55,988 --> 01:26:00,228 Those cultural changes do, uh, are things that, um, do happen in those 1672 01:26:00,228 --> 01:26:03,428 gray spaces and I think we as humans are very good at operating them. 1673 01:26:03,843 --> 01:26:07,543 We're also very good at, because we're not a black box, people can 1674 01:26:07,613 --> 01:26:10,603 have a, again, a theory mind about what others are thinking about. 1675 01:26:10,773 --> 01:26:13,063 We can work with each other and make our way through these 1676 01:26:13,063 --> 01:26:16,063 changes and make compromises and come up with solutions together. 1677 01:26:16,303 --> 01:26:19,503 Um, those again are some of these unique qualities as humans we have. 1678 01:26:19,863 --> 01:26:23,893 Uh, and I, I also just keep coming back to, there's, you know, there's multiple 1679 01:26:23,923 --> 01:26:25,663 types of intelligence that humans have. 1680 01:26:25,663 --> 01:26:28,273 And those are the things that we have to end up bringing to the table. 1681 01:26:28,273 --> 01:26:31,023 I do, AI will absolutely be part of our work. 1682 01:26:31,213 --> 01:26:35,657 Um, Um, and it will be in multiple aspects of our work going forward, but we 1683 01:26:35,657 --> 01:26:37,378 have to come back and ask the question. 1684 01:26:37,378 --> 01:26:39,098 Why are we doing this in the first place? 1685 01:26:39,338 --> 01:26:40,838 What's the role of our practice? 1686 01:26:40,838 --> 01:26:42,838 What's the role of our profession in the industry? 1687 01:26:43,248 --> 01:26:45,998 Um, what's our role in society and how we interface with the 1688 01:26:45,998 --> 01:26:48,948 people who are ultimately going to inhabit the spaces that we create? 1689 01:26:49,208 --> 01:26:52,198 And it's their experience that we should be aiming for. 1690 01:26:52,378 --> 01:26:57,577 So if there is a way for AI to help provide a more positive experience for 1691 01:26:57,577 --> 01:26:59,988 them by helping us do some of our work. 1692 01:27:00,363 --> 01:27:04,532 By maybe automating portions of work so we can focus on that end user in the 1693 01:27:04,532 --> 01:27:06,113 end, then absolutely we should do it. 1694 01:27:06,393 --> 01:27:10,763 And my hope would be anybody leading strategy in a technology practice has to 1695 01:27:10,763 --> 01:27:13,823 look at it from that kind of perspective because that's ultimately your goal. 1696 01:27:13,823 --> 01:27:18,183 It's not just to save money on your next contract with a large software vendor. 1697 01:27:18,463 --> 01:27:19,423 We have to do that. 1698 01:27:19,423 --> 01:27:19,983 Yes. 1699 01:27:20,253 --> 01:27:23,293 But in the end, the reason why you were there. 1700 01:27:23,693 --> 01:27:27,463 It's to ultimately help the designers in that practice create transformational 1701 01:27:27,463 --> 01:27:30,473 experiences for the people who live out in the built environment. 1702 01:27:30,743 --> 01:27:32,183 That's, that's your goal. 1703 01:27:32,373 --> 01:27:35,193 If you help them get there, then you're successful. 1704 01:27:36,437 --> 01:27:38,957 Evan Troxel: I kind of want to end the episode right there, but I get, 1705 01:27:38,977 --> 01:27:40,567 I'm not going to, I want to just say 1706 01:27:40,567 --> 01:27:44,307 that like it's through failure that learning happens, right? 1707 01:27:44,317 --> 01:27:47,377 And you cannot learn without failure. 1708 01:27:47,677 --> 01:27:49,597 You're just going to be regurgitating the same old crap. 1709 01:27:49,607 --> 01:27:51,867 I mean, that's one of my concerns with AI is that we're just going 1710 01:27:51,867 --> 01:27:54,467 to keep regurgitating the same crap because it was trained on the 1711 01:27:54,467 --> 01:27:55,777 internet and there's a lot of crap. 1712 01:27:55,787 --> 01:27:57,467 There's a lot of garbage in and garbage out. 1713 01:27:57,947 --> 01:28:00,047 So I, I'm, I'm concerned about that. 1714 01:28:00,057 --> 01:28:02,127 But, but the idea of. 1715 01:28:02,327 --> 01:28:05,247 The imperfections in New York City, to your example, like there's 1716 01:28:05,247 --> 01:28:08,537 something also to be said about it, that it is exactly perfect in 1717 01:28:08,537 --> 01:28:10,147 all of its imperfections, right? 1718 01:28:10,467 --> 01:28:13,377 There's something amazing and beautiful. 1719 01:28:13,377 --> 01:28:14,677 And there's these moments. 1720 01:28:15,317 --> 01:28:18,477 that could have never, you could have never planned for those, right? 1721 01:28:18,507 --> 01:28:20,967 And, and there's something really special about that. 1722 01:28:20,977 --> 01:28:22,867 And that is what makes it incredibly human. 1723 01:28:22,907 --> 01:28:27,666 Like to get back to the whole, why we do what we do part of this, it's, it's for 1724 01:28:27,666 --> 01:28:31,407 the people and to create experiences and to make their lives better so that they 1725 01:28:31,407 --> 01:28:34,877 can better contribute back to society and their community and their families and all 1726 01:28:34,877 --> 01:28:37,067 these things like architecture elevates. 1727 01:28:37,562 --> 01:28:40,222 The built environment, and it has the ability to do that. 1728 01:28:40,222 --> 01:28:44,282 We literally, it's so weird that this has come up three times in this episode, but 1729 01:28:44,282 --> 01:28:46,162 we literally can change the world, right? 1730 01:28:46,512 --> 01:28:51,322 And we're concerned about so many things, the, the environmental impact. 1731 01:28:51,322 --> 01:28:55,332 And there, there's just so many layers to that, the building code and health, safety 1732 01:28:55,332 --> 01:29:00,632 and welfare and the human experience and all of these things that it's, it's just 1733 01:29:00,632 --> 01:29:03,172 an incredible profession to work within. 1734 01:29:03,552 --> 01:29:07,302 And at the same time, like we're so run down. 1735 01:29:07,357 --> 01:29:10,687 By all of this stuff that happens on the day-to-day basis on the 1736 01:29:10,687 --> 01:29:15,577 distractions, doing so much email, worrying about licensing and like 1737 01:29:15,577 --> 01:29:17,647 all that's just getting in the way of 1738 01:29:17,647 --> 01:29:20,677 us doing the thing that we're supposed to be doing, that we 1739 01:29:20,677 --> 01:29:22,477 actually can contribute to the world. 1740 01:29:22,477 --> 01:29:26,097 And, uh, I mean, this has been a wonderful conversation to have with you. 1741 01:29:26,097 --> 01:29:29,087 I, I really appreciate you taking the time to hang out with us today. 1742 01:29:29,512 --> 01:29:31,272 Shane Burger: I'm really enjoying where things are going 1743 01:29:31,272 --> 01:29:32,132 right now in the industry. 1744 01:29:32,132 --> 01:29:35,882 And I, I really appreciate that at least for us in our practice, but this 1745 01:29:35,882 --> 01:29:42,332 is happening lots of places is the buzz around AI has focused the attention 1746 01:29:42,342 --> 01:29:46,092 back on human experience and what we do as architects and what our role is. 1747 01:29:46,412 --> 01:29:49,192 And I, I, in a way, I think people wanted that to happen when 1748 01:29:49,192 --> 01:29:52,982 BIM came along and it didn't. 1749 01:29:53,357 --> 01:29:53,787 Evan Troxel: Mm hmm. 1750 01:29:54,142 --> 01:29:55,982 Shane Burger: BIM kind of kicked the can down the road. 1751 01:29:55,992 --> 01:30:01,322 It automated some things for us, but it didn't necessarily, uh, necessarily 1752 01:30:01,382 --> 01:30:06,202 increase the Maybe the quality of what was being delivered or the value which 1753 01:30:06,202 --> 01:30:10,212 we are providing society, if anything, it kind of pointed towards how dependent we 1754 01:30:10,212 --> 01:30:14,162 are on technology to actually deliver on parts of our work, all those additional 1755 01:30:14,162 --> 01:30:15,682 drawing sets that we now had to create. 1756 01:30:16,052 --> 01:30:19,312 Um, this is actually starting to ask the question, what is our value? 1757 01:30:19,322 --> 01:30:20,712 What are we supposed to be providing? 1758 01:30:20,962 --> 01:30:24,572 Um, I don't agree with some of the heads of technology companies who 1759 01:30:24,572 --> 01:30:27,587 seem to think that on five years, Architects are gonna disappear. 1760 01:30:27,587 --> 01:30:29,987 It's, they don't understand what we actually provide. 1761 01:30:30,287 --> 01:30:34,277 But I do think we as an industry have to step up and advocate for ourselves, 1762 01:30:34,607 --> 01:30:38,447 but also really point out, you know, uh, where there are opportunities to use 1763 01:30:38,447 --> 01:30:42,587 AI to then provide that kind of unique human value that we do, uh, provide 1764 01:30:42,587 --> 01:30:44,027 to the built in built environment. 1765 01:30:44,916 --> 01:30:48,797 Evan Troxel: I guess this prompts me to ask you, you know, maybe, maybe a final 1766 01:30:48,797 --> 01:30:53,497 question, but at Woods Bagot, or maybe just in your head, have you started 1767 01:30:53,497 --> 01:30:58,467 to think about changes in business model that are going to need to happen? 1768 01:30:59,347 --> 01:31:00,847 Shane Burger: Yeah, I think, uh. 1769 01:31:01,517 --> 01:31:04,987 A few things that have come up for us as we've been asking, okay, if we're, if it's 1770 01:31:04,987 --> 01:31:08,166 no longer just fee for services, we're not just counting the amount of hours 1771 01:31:08,166 --> 01:31:11,947 that we're doing for the work and it's not going to be the model of, uh, oh, 1772 01:31:11,947 --> 01:31:15,357 the fee for that project is, well, I know it's going to take this many drawing sets. 1773 01:31:15,367 --> 01:31:18,267 So, okay, that thick of a drawing set costs this amount of money, right? 1774 01:31:18,407 --> 01:31:21,037 Those sort of models have to continue to disappear. 1775 01:31:21,037 --> 01:31:22,557 It's not where our value is. 1776 01:31:22,777 --> 01:31:24,157 They were an easy way for us. 1777 01:31:25,517 --> 01:31:28,177 Maybe it's similar to what we said at the previous conversation, uh, 1778 01:31:28,257 --> 01:31:29,666 at the beginning about licensing. 1779 01:31:29,677 --> 01:31:32,197 It's the easiest way for us to just have an answer of how much to 1780 01:31:32,207 --> 01:31:35,437 charge, but it's not the value we're actually providing to the end product. 1781 01:31:35,757 --> 01:31:39,497 Um, some of the things that come up, um, have more to do 1782 01:31:39,497 --> 01:31:41,187 with, uh, building performance. 1783 01:31:41,487 --> 01:31:43,217 So, are there performance incentives? 1784 01:31:43,217 --> 01:31:45,897 I know Phil Bernstein has talked about this, a handful of others. 1785 01:31:45,898 --> 01:31:50,187 If your building performs 10 or 20 percent better than the metric. 1786 01:31:50,897 --> 01:31:54,697 On particular metrics that were agreed upon in advance with the client, is there 1787 01:31:54,697 --> 01:31:58,247 an incentive for us that we, you know, get more money associated out of that? 1788 01:31:58,567 --> 01:32:01,587 Um, some of this comes down to then proving that through 1789 01:32:01,617 --> 01:32:02,727 evidence based design. 1790 01:32:02,767 --> 01:32:06,547 So we've had increased amount of conversations about both, Environmental 1791 01:32:06,557 --> 01:32:09,817 and building performance, but also social performance, getting into the 1792 01:32:09,817 --> 01:32:12,977 social sciences and understanding how our spaces are performing and 1793 01:32:12,977 --> 01:32:14,327 showing that value to clients. 1794 01:32:14,697 --> 01:32:18,497 Um, it has caused us to talk a lot more about what our 1795 01:32:18,497 --> 01:32:20,587 value is and how we might be. 1796 01:32:20,877 --> 01:32:24,637 partnering with our clients to effectively get paid for what value 1797 01:32:24,637 --> 01:32:27,487 we're actually bringing to them, their end product, where they want to have 1798 01:32:27,666 --> 01:32:31,067 an amazing space for their employees or for the public or whatever it is. 1799 01:32:31,416 --> 01:32:34,797 Um, I don't know that I necessarily have an answer, but it's something 1800 01:32:34,797 --> 01:32:37,707 we're absolutely like very actively looking after right now. 1801 01:32:37,967 --> 01:32:41,797 And there's some real questions as to whether It might be a multitude 1802 01:32:41,797 --> 01:32:44,197 of answers, depending on the kind of service and the kind of 1803 01:32:44,237 --> 01:32:45,247 sector that we're working with. 1804 01:32:45,248 --> 01:32:48,947 What works for retail might be different from workplace and might be different 1805 01:32:48,957 --> 01:32:50,707 from residential versus transport. 1806 01:32:51,497 --> 01:32:54,217 Evan Troxel: But your leadership is open to having those conversations. 1807 01:32:54,217 --> 01:32:57,497 And it's not like, this is definitely something that just keeps, the can 1808 01:32:57,497 --> 01:32:58,807 keeps getting kicked down the road. 1809 01:32:58,807 --> 01:32:58,987 Right. 1810 01:32:58,987 --> 01:33:01,687 It's like, maybe someday we'll have to think about that. 1811 01:33:01,687 --> 01:33:04,077 it's literally happening right now where the 1812 01:33:04,077 --> 01:33:09,827 value proposition has to be stated for what, where we add value to the process. 1813 01:33:09,827 --> 01:33:12,477 And I like what you're talking about, extending that into 1814 01:33:12,477 --> 01:33:14,257 building performance over time. 1815 01:33:14,297 --> 01:33:17,987 You talked about the temporal nature of like that projects don't stop when 1816 01:33:17,987 --> 01:33:20,242 we, The occupancy happens, right? 1817 01:33:20,262 --> 01:33:21,192 It continues. 1818 01:33:21,192 --> 01:33:24,291 And therefore I think there is a huge opportunity for us to continue to 1819 01:33:24,291 --> 01:33:29,402 have a relationship with a client to ensure that that happens because the 1820 01:33:29,402 --> 01:33:33,812 prototypical nature of buildings is just that, like we, you have to prove it. 1821 01:33:34,237 --> 01:33:34,627 once the 1822 01:33:34,627 --> 01:33:38,947 building is built, so this starts to lead into ideas about having a real 1823 01:33:38,947 --> 01:33:45,037 research arm of a company as well, because you can't just ask dumb questions. 1824 01:33:45,037 --> 01:33:48,067 You're gonna get dumb answers at the end, and, and truly 1825 01:33:48,067 --> 01:33:49,987 taking the time to understand. 1826 01:33:50,727 --> 01:33:53,857 Empathetically, like what clients are experiencing in spaces. 1827 01:33:53,867 --> 01:33:57,227 Cause if, if you just send a form over the fence, they're just going to check 1828 01:33:57,237 --> 01:34:00,147 boxes, they're, they're going to take the least path of resistance to get that 1829 01:34:00,147 --> 01:34:03,877 form done because they're just being forced to do it, but actually sitting 1830 01:34:03,877 --> 01:34:09,157 with those users, experiencing space, talking about operations, maintenance 1831 01:34:09,157 --> 01:34:13,887 of facilities, all of these things that happen after occupancy is where now 1832 01:34:13,887 --> 01:34:19,187 you're shifting the conversation to a later phase of service and relationship 1833 01:34:19,187 --> 01:34:20,677 with clients potentially as well. 1834 01:34:21,621 --> 01:34:23,962 Shane Burger: we've had good luck with those conversations with a 1835 01:34:23,962 --> 01:34:27,232 lot of repeat clients, clients that we've done lots of work for. 1836 01:34:27,272 --> 01:34:31,672 That's definitely happened in workplace, um, and, uh, some of our retail work. 1837 01:34:31,992 --> 01:34:35,342 Um, but increasingly having those conversations with new clients coming 1838 01:34:35,342 --> 01:34:38,612 in to say, you know, we don't, we're not just there to build you one space. 1839 01:34:38,892 --> 01:34:41,302 Um, we'd like to have an ongoing relationship with you. 1840 01:34:41,541 --> 01:34:45,682 And our goal is through things like post occupancy analysis, through building 1841 01:34:45,692 --> 01:34:51,377 and spatial simulation, all these things is to Uh, take, um, critical insights 1842 01:34:51,517 --> 01:34:53,227 and turn them into thoughtful outputs. 1843 01:34:53,447 --> 01:34:57,127 So the answers that we're providing, the directions that we're providing are based 1844 01:34:57,127 --> 01:35:02,297 upon data and our constant learning of our work as we go from project to project. 1845 01:35:02,752 --> 01:35:03,102 Evan Troxel: Yeah. 1846 01:35:03,291 --> 01:35:07,802 And that's where this feedback loop with your GPT and your design intelligence 1847 01:35:08,272 --> 01:35:12,682 could really benefit your firm over time, because you're, if you're continually 1848 01:35:12,682 --> 01:35:16,972 putting in high quality insights and things you're pulling from clients of 1849 01:35:16,982 --> 01:35:21,102 projects, and that is generating the feedback loop for what's coming next. 1850 01:35:21,607 --> 01:35:23,916 You could really see this stepping up over time. 1851 01:35:24,334 --> 01:35:24,844 Shane Burger: Absolutely. 1852 01:35:24,984 --> 01:35:25,174 Yeah. 1853 01:35:25,294 --> 01:35:25,564 Evan Troxel: Yeah. 1854 01:35:25,834 --> 01:35:28,824 Well, again, Shane, thank you so much for taking the time. 1855 01:35:28,824 --> 01:35:30,773 This has been a fantastic conversation. 1856 01:35:30,804 --> 01:35:34,874 I'll put links to where everybody can follow you online in the show notes. 1857 01:35:35,394 --> 01:35:36,644 And, uh, I appreciate it, man. 1858 01:35:36,764 --> 01:35:37,314 It's been fun. 1859 01:35:37,574 --> 01:35:37,754 Shane Burger: Hey. 1860 01:35:38,154 --> 01:35:38,994 Yeah, thank you so much. 1861 01:35:38,994 --> 01:35:40,404 I appreciate you reaching out to me again. 1862 01:35:40,974 --> 01:35:41,273 Evan Troxel: All right. 1863 01:35:41,273 --> 01:35:42,034 Until next time,