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,236 --> 00:00:47,856 Welcome to the Troxel podcast. 14 00:00:47,966 --> 00:00:48,896 I'm Evan Troxel. 15 00:00:48,936 --> 00:00:52,346 And in this episode, I welcome Nirva Fereshetian. 16 00:00:52,666 --> 00:00:57,906 Nirva is a Principal and Chief Information Officer at CBT Architects, which is 17 00:00:57,906 --> 00:01:01,906 a Boston based award winning design firm providing services nationally 18 00:01:01,916 --> 00:01:06,436 and internationally in architecture, interior design, and urban design. 19 00:01:06,856 --> 00:01:10,826 Nirva holds an undergraduate degree in architecture and a master's degree in 20 00:01:10,826 --> 00:01:13,156 architecture and computation from UCLA. 21 00:01:13,566 --> 00:01:17,486 At CBT, she leads multiple teams within the digital practice group, 22 00:01:17,746 --> 00:01:22,636 including design technology, business technology, and computational design. 23 00:01:22,966 --> 00:01:27,446 And in her day to day role as CBT's CIO, she was also named one of the 24 00:01:27,456 --> 00:01:29,566 Top Women in Tech in Boston this year. 25 00:01:29,946 --> 00:01:33,336 In this episode, Nirva and I explore the complexities of implementing 26 00:01:33,346 --> 00:01:37,056 and managing digital practice within an architecture firm, including the 27 00:01:37,056 --> 00:01:40,735 challenges posed by tool fatigue, the importance of understanding business 28 00:01:40,735 --> 00:01:44,716 problems, and the intricacies of vetting and adopting new technologies. 29 00:01:45,101 --> 00:01:48,431 Our discussion covers the evolving role of technology in architectural 30 00:01:48,431 --> 00:01:53,360 practice, the benefits of collaboration between firms within the AEC industry, 31 00:01:53,661 --> 00:01:56,860 and the importance of building a continuous learning culture. 32 00:01:57,211 --> 00:02:01,151 Nirva also shares her insights on integrating technology seamlessly 33 00:02:01,181 --> 00:02:05,321 into architectural practice and fostering innovation through effective 34 00:02:05,341 --> 00:02:07,991 communication and relationship building. 35 00:02:08,531 --> 00:02:13,031 As always, my ask of you is to help the show by subscribing to Troxel on 36 00:02:13,041 --> 00:02:17,096 YouTube and in your favorite podcast app to let me know that you're a fan. 37 00:02:17,476 --> 00:02:21,176 If you're watching this video on YouTube right now, please click that like button, 38 00:02:21,426 --> 00:02:25,596 and if you'd like to get an email when episodes are published with all the 39 00:02:25,596 --> 00:02:31,226 links and other information from the episode, you can sign up at trxl.co. 40 00:02:31,626 --> 00:02:37,123 You can also directly support the show by becoming a member at that site as well. 41 00:02:37,123 --> 00:02:39,339 Again, that's trxl.co. 42 00:02:40,216 --> 00:02:44,146 So, thank you for listening, and now, without further ado, I bring you my 43 00:02:44,146 --> 00:02:46,956 conversation with Nirva Fereshetian. 44 00:02:55,377 --> 00:02:56,107 to the podcast. 45 00:02:56,117 --> 00:02:57,477 Great to have you and see you again. 46 00:02:57,487 --> 00:02:59,877 It hasn't been that long, but it's always a pleasure to 47 00:02:59,877 --> 00:03:00,427 speak with you. 48 00:03:01,102 --> 00:03:02,742 Nirva Fereshetian: Well, thank you for having me, Evan. 49 00:03:02,772 --> 00:03:05,842 Um, I have certainly been the beneficiary of listening to 50 00:03:05,842 --> 00:03:09,782 so many great conversations you've had with other guests. 51 00:03:09,792 --> 00:03:14,152 So, I'm hoping that, uh, this conversation will be a good one for others. 52 00:03:14,447 --> 00:03:15,227 Evan Troxel: I'm sure it will be. 53 00:03:15,257 --> 00:03:18,706 I, you know, I want to focus on the practice side and definitely 54 00:03:18,706 --> 00:03:20,901 give voice to that part of it. 55 00:03:21,211 --> 00:03:23,541 part of AEC tech, right? 56 00:03:23,541 --> 00:03:28,071 Because the practice side has to implement, we have to train people, 57 00:03:28,071 --> 00:03:32,741 we have to vet the software and the tech and we have to roll it out. 58 00:03:32,741 --> 00:03:37,591 And I know that you know how difficult that is, but I want to give voice to 59 00:03:37,641 --> 00:03:42,371 that and what digital practice leaders are dealing with out there in the real 60 00:03:42,371 --> 00:03:46,701 world, not just kind of the fantasy world where everything works perfectly because. 61 00:03:47,361 --> 00:03:49,841 Turns out it doesn't, doesn't really go that, it's not 62 00:03:49,841 --> 00:03:51,471 smooth sailing like everybody 63 00:03:51,541 --> 00:03:52,741 hopes it could be, right? 64 00:03:53,506 --> 00:03:58,036 So give us an idea of, of your, what your role is at CBT. 65 00:03:58,076 --> 00:04:02,576 I mean, we've, let's assume that I've already read your bio because people 66 00:04:02,576 --> 00:04:06,026 listening to this will have already heard it, but introduce what, what you're 67 00:04:06,026 --> 00:04:09,556 actually doing because there's, there's a title, but then there's what you actually 68 00:04:09,556 --> 00:04:13,596 do at a firm and, and give us an idea of the size of CBT and, and where your 69 00:04:13,596 --> 00:04:14,646 practice is located. 70 00:04:14,646 --> 00:04:14,661 Okay. 71 00:04:14,831 --> 00:04:15,211 Nirva Fereshetian: Right. 72 00:04:15,701 --> 00:04:16,611 Um, sure. 73 00:04:16,680 --> 00:04:21,281 Um, so the title is chief information officer, but as you said, uh, title 74 00:04:21,281 --> 00:04:25,871 is, uh, one thing, but what we actually do in different firms, depending on 75 00:04:25,871 --> 00:04:30,061 size of firms or the practice culture, it's a lot, a little different. 76 00:04:30,321 --> 00:04:36,191 Um, for me, um, um, for the, due to our size, um, it's everything digital. 77 00:04:37,396 --> 00:04:41,366 But my main interest is that I have an undergraduate degree and 78 00:04:41,366 --> 00:04:42,766 a graduate degree in architecture. 79 00:04:42,766 --> 00:04:46,656 So my main difference is, um, the intersection of 80 00:04:46,686 --> 00:04:48,296 technology and architecture. 81 00:04:48,616 --> 00:04:52,566 But firms our size, I also have to take care of everything else. 82 00:04:52,596 --> 00:04:54,346 That is the framework. 83 00:04:54,656 --> 00:04:58,216 So, um, a lot of learning that has happened on that end. 84 00:04:58,216 --> 00:05:02,486 So, um, we have a business technology group. 85 00:05:02,526 --> 00:05:07,516 Uh, Design technology group, computational technology group, and a couple of years 86 00:05:07,516 --> 00:05:13,956 before, I've added a knowledge manager and a training, um, um, team member who 87 00:05:13,956 --> 00:05:20,926 is attached to our digital practice, um, and not to, um, HR, or, um, so it has been 88 00:05:20,926 --> 00:05:26,886 really, um, a journey, sort of, and my responsibilities have grown as the culture 89 00:05:26,886 --> 00:05:33,086 and the tech and the, um, implementation of things have changed, um, um, Recently, 90 00:05:33,286 --> 00:05:38,006 and more, you know, in the last 10 years, but more recently, right after COVID, um, 91 00:05:38,186 --> 00:05:44,356 I think the opportunity to connect with the business, the opportunity to solve the 92 00:05:44,756 --> 00:05:49,056 business problems is what me and the rest of the group are really interested in. 93 00:05:51,071 --> 00:05:55,611 Evan Troxel: and so maybe you could give, paint a picture of what it, that evolution 94 00:05:55,611 --> 00:05:59,601 has looked like and, and maybe not every step along the way, but, but what, what 95 00:05:59,631 --> 00:06:03,431 do you traditionally see as, as this kind of a role in a firm and what you 96 00:06:03,431 --> 00:06:05,261 used to do versus what you're doing now? 97 00:06:05,271 --> 00:06:06,391 Kind of paint, paint a picture of 98 00:06:06,391 --> 00:06:07,131 what that looks like. 99 00:06:07,466 --> 00:06:12,891 Nirva Fereshetian: I think the phenomenal difference has been that, um, A lot 100 00:06:12,891 --> 00:06:17,141 of, uh, you know, a lot of people have started similar to me, where they 101 00:06:17,141 --> 00:06:20,761 have an architecture background and somehow got involved to technology. 102 00:06:21,141 --> 00:06:28,561 Um, and, uh, but the major difference I see from now than it was before is that, 103 00:06:28,601 --> 00:06:35,566 um, technology has gained, um, to be not really in the forefront still, but 104 00:06:35,586 --> 00:06:37,456 to be on the table of the discussion. 105 00:06:37,846 --> 00:06:41,156 Before used to be, can you make something work? 106 00:06:41,176 --> 00:06:43,136 Or are we using the right version? 107 00:06:43,416 --> 00:06:45,056 Or can we get on Revit? 108 00:06:45,206 --> 00:06:46,476 We're on AutoCAD. 109 00:06:46,496 --> 00:06:52,596 But I think now the difference is, um, do we understand what the business does? 110 00:06:52,856 --> 00:06:54,536 Can we solve their problems? 111 00:06:54,656 --> 00:06:59,036 Can we enhance the, the, the strategy? 112 00:06:59,146 --> 00:07:02,416 Um, and so it's a very different role. 113 00:07:02,696 --> 00:07:04,716 Um, especially firms our size. 114 00:07:05,146 --> 00:07:09,416 Um, I think if you are in the much larger and you still have a lot of 115 00:07:09,416 --> 00:07:14,916 segregation of, you know, infrastructure technology and other, um, things versus 116 00:07:14,916 --> 00:07:20,106 digital practice, uh, for our size, um, it's really or interdependent. 117 00:07:20,146 --> 00:07:26,216 And I think the main purpose of our existence is to show that it's not about 118 00:07:26,506 --> 00:07:31,926 the software, it's about the people and it's about how we implement and how we. 119 00:07:32,326 --> 00:07:36,056 Um, PR it inside our firms. 120 00:07:36,096 --> 00:07:40,516 I mean, certainly none of these skills were things that I learned neither 121 00:07:40,516 --> 00:07:46,906 at school nor at graduate school, or so seems a lot of the skill sets that 122 00:07:46,926 --> 00:07:53,516 are necessary, um, to, um, implement things is less technical, more, 123 00:07:53,896 --> 00:07:57,736 um, I'm not going to call it soft skills, but a lot of understanding, 124 00:07:58,096 --> 00:08:04,486 um, and a business acumen, um, uh, Relationship Acumen, PR, everything. 125 00:08:04,576 --> 00:08:06,166 Everything that comes in that, 126 00:08:06,476 --> 00:08:07,816 um, scope. 127 00:08:08,186 --> 00:08:12,366 Um, it's one thing to be good at the technology, um, but it's another thing 128 00:08:12,366 --> 00:08:15,696 to have those skill sets, and not just for me, but even the team members. 129 00:08:16,036 --> 00:08:22,756 Um, they have to have that convincing aptitude, um, and the psychology behind 130 00:08:22,766 --> 00:08:24,496 the scenes to make something happen. 131 00:08:25,711 --> 00:08:29,591 Evan Troxel: feel like that's kind of a role of something, at least an 132 00:08:29,601 --> 00:08:33,331 outcome that I would like to see come out of episodes like this is giving 133 00:08:33,331 --> 00:08:38,780 people the tools to be able to have those conversations because by hearing 134 00:08:39,001 --> 00:08:43,140 us talk about these things, it kind of sets the table for how we talk 135 00:08:43,150 --> 00:08:46,451 about technology and the practice of architecture and the merging of those 136 00:08:46,461 --> 00:08:50,491 things to give people I don't want to necessarily say the arguments. 137 00:08:50,491 --> 00:08:52,821 It's not like you're trying to win an argument, but at least 138 00:08:53,031 --> 00:08:58,491 present these things in a way that, to your point, drives business 139 00:08:58,491 --> 00:09:00,571 forward, solves business problems. 140 00:09:00,591 --> 00:09:04,961 And that is a great approach to getting technology implemented in firms. 141 00:09:04,961 --> 00:09:08,641 It's not just, here's the latest thing that we should be using, but here's 142 00:09:08,661 --> 00:09:13,851 why we should be using it or why we should be testing it and trying to find 143 00:09:13,851 --> 00:09:16,351 out if this is the right tool to use. 144 00:09:16,351 --> 00:09:21,241 Because the end goal is why do we practice architecture at all? 145 00:09:21,251 --> 00:09:23,211 Why do we do things the way that we do them? 146 00:09:23,601 --> 00:09:26,121 It's not the tools that we actually use, right? 147 00:09:26,121 --> 00:09:30,231 You, you want to define the goals and then backfill that with potential 148 00:09:30,231 --> 00:09:32,111 ways to accomplish those goals. 149 00:09:32,790 --> 00:09:34,571 That could be any number of technology. 150 00:09:34,571 --> 00:09:39,911 It could be any number of people, teams, training, coaches, all kinds 151 00:09:39,911 --> 00:09:42,011 of things to get to that end goal. 152 00:09:42,011 --> 00:09:46,091 But you have to kind of state what that end goal is and then reverse engineer it. 153 00:09:46,171 --> 00:09:49,486 And, and to your point, like, Why do we do what we do? 154 00:09:49,486 --> 00:09:53,086 What that, that is the real driver and how do we do business? 155 00:09:53,086 --> 00:09:56,476 And then how are we gonna achieve those are much more secondary to all that. 156 00:09:57,866 --> 00:10:01,496 Nirva Fereshetian: Uh, to understand the goal is certainly the first, um, 157 00:10:02,071 --> 00:10:07,231 Requirement and a lot of team members when they, I always recommend them to 158 00:10:07,231 --> 00:10:11,921 go and sit to different presentations, different lunch sessions, even though 159 00:10:11,921 --> 00:10:16,041 it's not involving technology, because that's how you understand the business. 160 00:10:16,061 --> 00:10:18,291 And you could see their side of the story. 161 00:10:18,541 --> 00:10:23,151 Um, so just set up standards and say, you need to follow them or, or set up things. 162 00:10:23,161 --> 00:10:24,611 It's just doesn't work. 163 00:10:24,611 --> 00:10:28,301 So the goal is the very primary, but I think moving. 164 00:10:28,871 --> 00:10:35,906 Um, Achieving that goal is, um, the key element is how to talk about 165 00:10:35,906 --> 00:10:40,836 it, how to present it, how to, not just internally, but even working 166 00:10:40,836 --> 00:10:44,546 with the technology companies, even working with the startups, um, it's 167 00:10:44,556 --> 00:10:47,146 how you present and how you receive. 168 00:10:47,656 --> 00:10:48,996 that makes a success. 169 00:10:49,086 --> 00:10:53,596 Sometimes, um, they don't understand what the workflow is, although some 170 00:10:53,596 --> 00:10:59,226 of them claim to be, have had past architectural experience or, um, not 171 00:10:59,226 --> 00:11:03,406 claim, but they really have had it and then moved on to work, um, at a startup. 172 00:11:03,406 --> 00:11:09,196 And some do not really understand why are things not working. 173 00:11:09,526 --> 00:11:14,396 And essentially a lot of it is about how you present it and how you talk about it. 174 00:11:14,706 --> 00:11:20,886 Um, Technology is factual, you know, does it work or does it not work, or, 175 00:11:21,186 --> 00:11:26,776 but a lot of others, the, that, that part you can fix, what you cannot fix 176 00:11:27,146 --> 00:11:34,086 is if you've accidentally messed up the implementation, you know, so, um, 177 00:11:34,126 --> 00:11:38,196 sometimes you can never have those people back, um, to use the same tool. 178 00:11:38,336 --> 00:11:42,926 So, um, some things that work in other offices don't work in, 179 00:11:42,996 --> 00:11:45,561 um, Our office and vice versa. 180 00:11:45,571 --> 00:11:50,511 I think to understand the culture to understand sort of to be in their 181 00:11:50,521 --> 00:11:53,711 shoes Is how you can implement? 182 00:11:54,371 --> 00:11:59,371 You can't just say well, this is our stamp And why are you not following it 183 00:11:59,391 --> 00:12:02,731 or this is the tool we use and therefore we're not going to give you the other 184 00:12:02,741 --> 00:12:07,881 tool So it doesn't work that way So 185 00:12:08,116 --> 00:12:10,546 Evan Troxel: how you learned how to do that. 186 00:12:10,576 --> 00:12:15,526 If it was just kind of how you're wired already as a person, or if these are 187 00:12:15,966 --> 00:12:20,066 techniques that you developed along your journey to get to where you are 188 00:12:20,066 --> 00:12:26,381 now, because When I, when I was leading digital practice at my firm, I felt like 189 00:12:26,381 --> 00:12:31,441 my success in that role was very much dependent on my career as an architect, 190 00:12:31,481 --> 00:12:35,921 getting to that point, working with client groups, learning how to, as a 191 00:12:35,921 --> 00:12:42,026 designer, I had to synthesize ideas from 30 to 50 people on a project into 192 00:12:42,026 --> 00:12:44,216 a single, into a real project, right? 193 00:12:44,216 --> 00:12:46,676 And actually implement their ideas and design. 194 00:12:47,046 --> 00:12:51,336 And that happens through building consensus, communicating clearly, 195 00:12:51,796 --> 00:12:56,496 taking people through a step by step process to get from A to Z, 196 00:12:56,776 --> 00:12:58,446 not just starting at the end, right? 197 00:12:58,466 --> 00:13:03,046 And so I developed those skills over two decades to learn 198 00:13:03,056 --> 00:13:04,696 how to do that effectively. 199 00:13:04,726 --> 00:13:06,746 And then when I stepped into digital practice. 200 00:13:07,401 --> 00:13:10,191 I could actually do that inside the firm. 201 00:13:10,231 --> 00:13:12,721 I didn't have to go outside the firm anymore, right, to do that. 202 00:13:13,171 --> 00:13:17,051 But there's various stakeholders of all different levels inside the firm 203 00:13:17,091 --> 00:13:21,281 that you need to build consensus, get everybody on the same page, talk about 204 00:13:21,301 --> 00:13:27,211 a, a strategy that, that encompasses all of those aspects of training and 205 00:13:27,221 --> 00:13:32,991 PR and communication and implementation and support and all of those things. 206 00:13:33,581 --> 00:13:36,451 I'm curious how that worked for you to get to, to where you 207 00:13:36,451 --> 00:13:36,671 are. 208 00:13:37,641 --> 00:13:42,790 Nirva Fereshetian: I certainly wasn't wired like that, so I think it's a and 209 00:13:42,790 --> 00:13:50,071 And I think it's, um, the status is always learning and in, in process, 210 00:13:50,171 --> 00:13:53,281 you know, so I don't think there is a place you can achieve that you could 211 00:13:53,281 --> 00:13:55,011 say, oh, well, I'm perfect at this. 212 00:13:55,341 --> 00:13:58,411 I can, I can do any implementation or I can communicate. 213 00:13:58,671 --> 00:14:04,121 It's, um, it's personal relationship building inside the firm. 214 00:14:05,061 --> 00:14:09,501 Um, we, I have tried to rely on, um, the team. 215 00:14:10,721 --> 00:14:16,051 Storytelling the way our designers, I've tried, I've aspired to do the storytelling 216 00:14:16,061 --> 00:14:20,671 that our designers do on a daily basis when they present to their clients. 217 00:14:20,941 --> 00:14:25,981 Um, it is about that and it's hard to explain to younger staff who 218 00:14:25,981 --> 00:14:30,881 are very savvy in tools and very savvy in coding and computational 219 00:14:30,881 --> 00:14:34,271 design and very frustrated when they cannot find the right words. 220 00:14:34,631 --> 00:14:39,471 That, um, communication with the parties that they're trying to work with. 221 00:14:39,491 --> 00:14:47,011 And, um, and I always think that there is a, it's all about human relationships, 222 00:14:47,040 --> 00:14:52,461 how we can make, we can understand each other and it's less about technology and 223 00:14:52,461 --> 00:14:58,771 it's more about trying to relay, um, my position to them and their position to us. 224 00:14:59,141 --> 00:15:05,771 Um, so how can we bridge the gap, uh, where You know, typical problems 225 00:15:05,771 --> 00:15:09,121 are like, we want to, we don't want everyone to do whatever they want, 226 00:15:09,721 --> 00:15:14,041 but at the same time, we want to have the leeway for people to experiment. 227 00:15:14,161 --> 00:15:19,481 So it's a very fine balance, and I think every day is a new day to 228 00:15:19,481 --> 00:15:20,791 figure out how to do it better. 229 00:15:21,651 --> 00:15:22,256 With who? 230 00:15:23,106 --> 00:15:25,176 Depends on who is on the other side. 231 00:15:25,186 --> 00:15:26,696 Personalities are different. 232 00:15:28,056 --> 00:15:30,186 People's experiences are different. 233 00:15:30,216 --> 00:15:33,596 There's always, well, we did this in another office or something. 234 00:15:33,606 --> 00:15:36,926 You know, so, there's always that challenge that comes by. 235 00:15:37,165 --> 00:15:41,706 And, um, yes, it might be different with clients, with different team members. 236 00:15:41,926 --> 00:15:43,646 And we just have to learn to adjust. 237 00:15:44,316 --> 00:15:49,766 But we also have to relay properly why are we as technologists saying 238 00:15:49,786 --> 00:15:51,206 that these things are important. 239 00:15:51,406 --> 00:15:54,646 So, it's, it's, you know, it's a very collaborative and yet 240 00:15:54,686 --> 00:15:57,596 very fractured process to me. 241 00:15:57,596 --> 00:16:02,776 Like, the designers at the front end produce things, um, and, um, 242 00:16:03,056 --> 00:16:07,276 without really, um, I'm not going to use the word caring, without really 243 00:16:07,336 --> 00:16:09,946 thinking through of how downstream. 244 00:16:10,361 --> 00:16:13,791 that might or might not affect, um, other people's work. 245 00:16:13,801 --> 00:16:17,311 And then the kind of, the ball is passed forward and other team 246 00:16:17,311 --> 00:16:19,491 members take the, uh, model. 247 00:16:19,621 --> 00:16:23,531 And then it's passed forward and other team members take the CA process and 248 00:16:23,531 --> 00:16:30,941 pass forward to the owner or, so my take has been like, how can we make sure that 249 00:16:31,231 --> 00:16:32,931 all of us care about the same thing? 250 00:16:33,581 --> 00:16:37,040 Because everything is connected and it's not just, you know, 251 00:16:37,781 --> 00:16:39,411 do my task and throw it. 252 00:16:39,851 --> 00:16:44,511 Over the fence and send it to somebody else and the success of a firm I think 253 00:16:44,521 --> 00:16:48,651 is about understanding that and then carrying that success on a project 254 00:16:48,651 --> 00:16:54,411 level outside of our firm It's highly corroborative, but very much not caring 255 00:16:54,471 --> 00:17:00,261 about the transitional aspects And once those pieces come together, um, you are 256 00:17:00,271 --> 00:17:05,521 have a successful project It shouldn't be that hard to convince at each stage 257 00:17:05,911 --> 00:17:09,911 that there is something to think about when you move forward Move the baton. 258 00:17:10,996 --> 00:17:13,685 Evan Troxel: You have not once said, and I congratulate you, 259 00:17:13,695 --> 00:17:15,205 you never said the word handoff. 260 00:17:17,665 --> 00:17:19,786 And this gets back to that communication thing, right? 261 00:17:19,786 --> 00:17:22,116 It's like, what words do you use? 262 00:17:22,175 --> 00:17:25,955 And, and you're using like, Words that are building, you're using, 263 00:17:26,236 --> 00:17:30,136 moving the ball forward, you know, progressing, you're talking about this 264 00:17:30,146 --> 00:17:34,536 in a, handing the baton, like it's a progression to the next, who's going 265 00:17:34,536 --> 00:17:37,226 to take this and build upon it, right? 266 00:17:37,236 --> 00:17:41,126 Instead of, The idea of handing off has always been kind of a 267 00:17:41,126 --> 00:17:43,396 dirty word in practice, right? 268 00:17:43,396 --> 00:17:47,156 It's like the designers hand it off to production, then the production people 269 00:17:47,156 --> 00:17:50,486 just grumble, grumble, grumble, hate the designers for all these things that 270 00:17:50,486 --> 00:17:55,826 they, no, it's a, how can we smoothly transition and get the most without 271 00:17:55,836 --> 00:18:00,256 having to redo work, without having to guess at what somebody was trying to 272 00:18:00,256 --> 00:18:02,801 do, without, You know, screwing it up. 273 00:18:03,731 --> 00:18:06,871 They did it wrong, and now we have to build, we garbage in, garbage out. 274 00:18:06,891 --> 00:18:10,461 Like, there's a, there's definitely a completely different approach. 275 00:18:10,791 --> 00:18:14,721 And that, to me, I think, is one of the, one of the really cool things 276 00:18:14,721 --> 00:18:16,561 that digital practice enables. 277 00:18:16,561 --> 00:18:20,841 And to your point earlier, where earlier in practice, technology was 278 00:18:20,841 --> 00:18:22,941 very much kind of an add on menu item. 279 00:18:22,941 --> 00:18:24,611 It was like, well, do you want renderings? 280 00:18:24,661 --> 00:18:26,421 And then you're going to pay for those, and you're going to 281 00:18:26,421 --> 00:18:27,771 get them at these milestones. 282 00:18:27,771 --> 00:18:30,536 And it was really, It really was because it was so hard 283 00:18:30,536 --> 00:18:31,906 and it was so time consuming. 284 00:18:31,906 --> 00:18:35,096 It really was an add on, but now it's not like renderings are free, right? 285 00:18:35,096 --> 00:18:36,886 That's just part of the design process. 286 00:18:37,326 --> 00:18:38,966 And that has really evolved. 287 00:18:39,176 --> 00:18:44,986 And that's just one example of this kind of integration, uh, and not 288 00:18:44,986 --> 00:18:48,421 only integration, but it's like, Technology is the backbone, right? 289 00:18:48,421 --> 00:18:49,911 It no longer is an add on. 290 00:18:49,951 --> 00:18:56,251 It is the way that we deliver projects and getting everybody on board with, 291 00:18:56,291 --> 00:19:03,296 with that process and how it can be utilized in a very efficient and positive 292 00:19:03,296 --> 00:19:08,556 way to enable success at every step along the path of project delivery 293 00:19:09,066 --> 00:19:10,616 is really where digital practice is. 294 00:19:10,616 --> 00:19:15,036 And early on when you were just talking about digital practice at CBT, you 295 00:19:15,036 --> 00:19:16,656 mentioned off four or five groups. 296 00:19:16,656 --> 00:19:20,276 Can you mention what those are again to kind of give everybody a holistic 297 00:19:20,276 --> 00:19:22,296 picture of what digital practice is? 298 00:19:22,296 --> 00:19:22,856 Because I'm sure it 299 00:19:22,856 --> 00:19:24,036 didn't start off like that. 300 00:19:24,086 --> 00:19:25,296 Like it probably started off as 301 00:19:25,826 --> 00:19:27,176 IT, like that's right. 302 00:19:27,176 --> 00:19:27,996 And, but now it's 303 00:19:27,996 --> 00:19:28,956 evolved into something 304 00:19:29,061 --> 00:19:29,601 Nirva Fereshetian: Right. 305 00:19:29,611 --> 00:19:35,161 So, it started as IG T and I was the component of computer aided 306 00:19:35,161 --> 00:19:41,091 design or taking care of the um, um, specific tools for this vertical. 307 00:19:41,111 --> 00:19:45,271 But, I have tried very hard the last ten, more than ten 308 00:19:45,271 --> 00:19:47,281 years to remove that word word. 309 00:19:47,741 --> 00:19:51,561 Um, and not talk about IT, but talk about digital practice 310 00:19:51,591 --> 00:19:53,731 being, encompassing all of that. 311 00:19:53,991 --> 00:19:59,351 Um, so there is the business technology, um, which is just, um, basic, 312 00:19:59,381 --> 00:20:02,791 um, need for, uh, things to work. 313 00:20:03,011 --> 00:20:06,571 You know, um, whether that is internet access, your devices, your 314 00:20:06,591 --> 00:20:12,366 communication, and, uh, Um, design technologists who are, um, individuals 315 00:20:12,366 --> 00:20:16,426 with architectural background, passionate with technology, try to, 316 00:20:16,786 --> 00:20:22,966 try to stay, um, 5 or 10 steps ahead of everybody and, um, do the research. 317 00:20:22,996 --> 00:20:28,036 And then computational design is, um, something we have tried to, um, 318 00:20:28,826 --> 00:20:34,316 Plan and do for the last, uh, last 4 or 5 years and now has taken off 319 00:20:34,656 --> 00:20:38,706 in terms of the necessity as being part of the design technology. 320 00:20:39,006 --> 00:20:44,816 Colleagues and then, um, the last 1 was, um, something we added right 321 00:20:44,816 --> 00:20:51,031 before coven and because I thought that, um, Just parading these technologies 322 00:20:51,031 --> 00:20:56,741 without proper training with proper monitoring of those training. 323 00:20:56,741 --> 00:21:01,641 So that's a knowledge manager that we have that manages our learning programs 324 00:21:01,641 --> 00:21:04,411 or our individual set up programs. 325 00:21:04,451 --> 00:21:08,941 Um, and, uh, lunch and learns, or, you know, I think a lot of it 326 00:21:08,941 --> 00:21:11,911 comes from, um, seeing, um, so. 327 00:21:13,366 --> 00:21:16,806 The ticketing system is a database of everything, Evan. 328 00:21:17,076 --> 00:21:20,726 I feel like if you look at it, you can figure out what is the pulse of the 329 00:21:20,726 --> 00:21:25,096 company, where are we lacking, why are they asking so many questions, something 330 00:21:25,106 --> 00:21:30,626 is broken, we haven't set it up correctly, or we haven't taught them or trained them. 331 00:21:30,736 --> 00:21:33,636 So a lot of the training ideas come from that. 332 00:21:34,241 --> 00:21:38,971 So if it's repeatedly asking the same thing or repeatedly we're having 333 00:21:39,001 --> 00:21:44,231 issues, um, in, um, um, setting up a model or whatever that means that 334 00:21:44,441 --> 00:21:46,841 I always say it's not them, it's us. 335 00:21:46,881 --> 00:21:49,761 And I want to make sure that there is no them and us. 336 00:21:50,001 --> 00:21:51,781 I shouldn't even have used that word. 337 00:21:52,081 --> 00:21:57,071 I've tried to make it feel like we are embedded in their teams, that 338 00:21:57,071 --> 00:22:02,211 we are the partnership and not, hey, call them and something's wrong. 339 00:22:02,231 --> 00:22:03,621 And, um, so. 340 00:22:04,131 --> 00:22:05,881 That is the entire effort. 341 00:22:07,391 --> 00:22:09,711 Are we successful a hundred percent of the time? 342 00:22:09,711 --> 00:22:09,961 No. 343 00:22:09,961 --> 00:22:14,411 Like I said, it's always a new day and a new way of working, but 344 00:22:14,461 --> 00:22:19,211 we want to be considered as part of their embedded teams, be part 345 00:22:19,211 --> 00:22:20,601 of them, be part of the business. 346 00:22:20,871 --> 00:22:25,451 And even on the business technology side, which is a little bit further out than all 347 00:22:25,451 --> 00:22:29,941 the others architecturally, I always tell them that if you don't understand what 348 00:22:29,941 --> 00:22:32,271 we're doing, you can't fix our devices. 349 00:22:32,616 --> 00:22:36,166 Because you have to understand what the outcome of the business 350 00:22:36,176 --> 00:22:39,726 is and what they're trying to do to give any kind of support. 351 00:22:40,911 --> 00:22:41,281 Evan Troxel: Yeah. 352 00:22:41,321 --> 00:22:42,281 That, that's a great point. 353 00:22:42,311 --> 00:22:44,351 And so when you said ticketing system, obviously 354 00:22:44,361 --> 00:22:45,211 you're talking about help 355 00:22:45,496 --> 00:22:46,476 Nirva Fereshetian: Helpdesk, yeah. 356 00:22:47,056 --> 00:22:50,186 Yeah, but all these, all these three, four groups look at that 357 00:22:50,196 --> 00:22:51,336 ticketing system, you know? 358 00:22:51,336 --> 00:22:54,226 So, yeah, so it's one common system. 359 00:22:54,446 --> 00:22:59,426 If the, whether there's a computational design issue or a design technology 360 00:22:59,466 --> 00:23:03,686 issue or a knowledge issue or some training issue, everybody looks at it. 361 00:23:03,916 --> 00:23:08,126 And You know, it's kind of, to me, it's the psychology of the firm, you 362 00:23:08,126 --> 00:23:12,346 know, you could really detect there what is the pulse of the firm, what 363 00:23:12,346 --> 00:23:20,336 is our, um, uh, support structure, um, how many people are having problems, 364 00:23:20,336 --> 00:23:25,116 and so it's, it's a lot of help for decision making, just, just in general. 365 00:23:25,911 --> 00:23:26,341 Evan Troxel: Mm hmm. 366 00:23:26,386 --> 00:23:30,851 Nirva Fereshetian: Are people even, Evan, are people In the right groups, 367 00:23:30,941 --> 00:23:35,481 you know, uh, in the right teams with their skill sets, you know, sometimes, 368 00:23:35,491 --> 00:23:40,421 as you know, scheduling happens, um, on the fly in all of our offices. 369 00:23:40,421 --> 00:23:43,501 Well, let's grab this person and that person because 370 00:23:43,501 --> 00:23:44,831 they're not, they're available. 371 00:23:45,151 --> 00:23:51,106 Um, so we can detect that immediately that the person might not be, um, available. 372 00:23:51,516 --> 00:23:56,256 In the right role or might need something to be in help of or training 373 00:23:56,286 --> 00:23:58,166 of some kind to be in the right role. 374 00:23:58,526 --> 00:24:04,106 So I, I feel like, um, we're trying to connect technology, the right technology 375 00:24:04,106 --> 00:24:07,606 with the right people constantly, whether it's inside or outside. 376 00:24:08,431 --> 00:24:08,811 Evan Troxel: Yeah. 377 00:24:09,711 --> 00:24:10,471 That, that's interesting. 378 00:24:10,471 --> 00:24:12,611 How, how large is CBT? 379 00:24:12,841 --> 00:24:13,101 How many 380 00:24:13,136 --> 00:24:15,676 Nirva Fereshetian: Oh, we're between 200 and 250. 381 00:24:15,706 --> 00:24:17,216 Depends when you ask us. 382 00:24:17,376 --> 00:24:17,666 Yeah. 383 00:24:17,941 --> 00:24:18,201 Evan Troxel: Okay. 384 00:24:18,201 --> 00:24:20,571 I'm just curious because I think, you know, there's smaller firms 385 00:24:20,571 --> 00:24:21,351 that don't have help 386 00:24:21,351 --> 00:24:22,861 desks implemented. 387 00:24:22,861 --> 00:24:23,121 Right. 388 00:24:23,121 --> 00:24:28,111 And so at some point it becomes like, this is how we manage the flow of 389 00:24:28,111 --> 00:24:32,191 information in these ways, like for support or for information, right. 390 00:24:32,191 --> 00:24:32,901 That you're talking about. 391 00:24:32,901 --> 00:24:36,921 So, uh, smaller firms probably struggle with that a little bit more and 392 00:24:36,921 --> 00:24:38,501 they don't have the data to look at. 393 00:24:38,501 --> 00:24:42,311 But I think this kind of makes an argument for a system like this, because 394 00:24:42,621 --> 00:24:45,041 if you want insight into the pulse of. 395 00:24:45,796 --> 00:24:48,396 And, and it has to be a thing where people get results out of, or 396 00:24:48,396 --> 00:24:49,426 else they're not going to use it. 397 00:24:49,426 --> 00:24:49,686 Right. 398 00:24:49,686 --> 00:24:52,526 So if you have a help desk and you're just collecting information, 399 00:24:52,536 --> 00:24:53,806 you're never acting on it, like 400 00:24:53,806 --> 00:24:54,816 that doesn't work either. 401 00:24:54,856 --> 00:24:55,096 Right. 402 00:24:55,096 --> 00:24:56,986 So people just won't use it. 403 00:24:56,996 --> 00:25:00,536 And then you still won't have insight into the pulse of what's actually 404 00:25:00,536 --> 00:25:02,006 going on on the floor of your office. 405 00:25:02,016 --> 00:25:04,656 So this is, these all go together. 406 00:25:04,676 --> 00:25:08,206 And I think what's so interesting about kind of what the structure 407 00:25:08,206 --> 00:25:11,536 that you just laid out as far as digital practice goes and how, Yeah. 408 00:25:11,871 --> 00:25:15,811 It operates as one unit, but you have several different special roles 409 00:25:15,811 --> 00:25:21,831 within that or groups that it really is a holistic, strategic endeavor. 410 00:25:22,111 --> 00:25:24,611 And you have to think about it that way, or else it's just 411 00:25:24,611 --> 00:25:26,091 not going to be effective in 412 00:25:26,091 --> 00:25:26,991 your organization. 413 00:25:27,206 --> 00:25:27,516 Nirva Fereshetian: right. 414 00:25:27,516 --> 00:25:32,566 And I see it like, um, A practice unit, you know, like, you know, interior 415 00:25:32,566 --> 00:25:35,886 design is a practice unit and then urban design is a practice unit. 416 00:25:35,896 --> 00:25:37,626 And it's a practice unit. 417 00:25:37,666 --> 00:25:43,166 That kind of, um, is the center of all of the practice units to try to 418 00:25:43,306 --> 00:25:46,786 help as, you know, it's not only just. 419 00:25:47,656 --> 00:25:51,516 One size doesn't fit all outside of our firms, but one size doesn't fit 420 00:25:51,516 --> 00:25:56,936 all even inside of our firms, depending on the scale of a project or, um, the 421 00:25:56,946 --> 00:26:01,116 typology of a project and, um, the people that are involved in the project. 422 00:26:02,412 --> 00:26:05,654 Evan Troxel: This episode is made possible with support from avail Avail 423 00:26:05,654 --> 00:26:09,764 makes the best software to manage all of your AEC digital content. 424 00:26:10,030 --> 00:26:13,780 Dedicated to developing tools that save AEC team's time. 425 00:26:14,120 --> 00:26:18,380 Avail has now added Revvit application version management to its suite of 426 00:26:18,380 --> 00:26:20,150 content management capabilities. 427 00:26:20,570 --> 00:26:22,910 Wants a painful manual process. 428 00:26:22,940 --> 00:26:24,020 Revvit application. 429 00:26:24,050 --> 00:26:26,990 Versioning is now automatic for avail customers. 430 00:26:27,320 --> 00:26:29,900 Publishers simply upload files to an avail channel. 431 00:26:30,200 --> 00:26:33,530 And the files are automatically converted to newer versions from 432 00:26:33,530 --> 00:26:36,620 Revvit 2021 through Revvit 2025. 433 00:26:36,933 --> 00:26:39,573 For users, the experience is then seamless. 434 00:26:39,873 --> 00:26:44,643 They can search select and utilize the Revvit content and avail, regardless of 435 00:26:44,643 --> 00:26:46,503 what Revvit version they are working in. 436 00:26:46,843 --> 00:26:50,413 inquire about a demo of avail and its new Revvit application 437 00:26:50,413 --> 00:26:56,443 version management features today at get avail.com/request-demo. 438 00:26:56,743 --> 00:26:59,293 My thanks to avail for supporting this episode. 439 00:26:59,293 --> 00:27:00,583 of the Troxell podcast. 440 00:27:00,943 --> 00:27:03,223 And now let's get back to the conversation. 441 00:27:05,527 --> 00:27:08,217 When I used to present the structure of digital practice and how it would 442 00:27:08,217 --> 00:27:12,837 be comma thing at the firm that I was at, first I thought about it as like 443 00:27:12,837 --> 00:27:17,197 we have these different practice groups and digital practice was a layer that 444 00:27:17,197 --> 00:27:19,147 kind of ran on top of all of those. 445 00:27:19,167 --> 00:27:23,087 But later on, I switched the diagram to be more like what you just said, 446 00:27:23,097 --> 00:27:24,057 where it's a hub 447 00:27:24,197 --> 00:27:24,937 in the middle. 448 00:27:25,457 --> 00:27:29,427 And all of these pieces come off of, but also feed back into. 449 00:27:29,992 --> 00:27:33,042 That hub, because it really is, like I said earlier, like the 450 00:27:33,052 --> 00:27:35,632 backbone of how we deliver projects. 451 00:27:35,632 --> 00:27:38,962 We're not going to do, we're not going to deliver projects any other way. 452 00:27:39,292 --> 00:27:42,922 We're not going to deliver Vellum, we're not going to, right, we're not going to 453 00:27:42,932 --> 00:27:46,512 do Blueprints, we're not going to make, we don't have the Ammonia machines. 454 00:27:46,512 --> 00:27:49,132 We're not doing it like that anymore, so we actually have to 455 00:27:49,172 --> 00:27:55,307 reconfigure the way that we think about this, so that everybody can 456 00:27:55,317 --> 00:27:56,817 use it to its fullest potential. 457 00:27:56,817 --> 00:28:00,567 Because if you, if you can't get out of your old way of thinking about the way 458 00:28:00,567 --> 00:28:05,557 that technology was implemented as a separate layer, if you can't think about 459 00:28:05,557 --> 00:28:09,617 it the new way, it's not going to actually reach its potential in the, in the 460 00:28:09,627 --> 00:28:10,367 organization. 461 00:28:10,627 --> 00:28:13,287 Nirva Fereshetian: Right, and I think it's the hub that, and the 462 00:28:13,307 --> 00:28:19,977 success of the hub is how far the extensions are and that relationship. 463 00:28:20,592 --> 00:28:21,862 To the surrounding, 464 00:28:22,322 --> 00:28:25,752 um, I don't know what you, whatever you call it, either typologies or 465 00:28:25,762 --> 00:28:29,522 studios or whatever you have in terms of structure of an office or 466 00:28:29,562 --> 00:28:31,542 practice units, other practice units. 467 00:28:31,552 --> 00:28:36,132 So, if you have, and I've tried to establish that on different 468 00:28:36,142 --> 00:28:37,972 levels of communication. 469 00:28:37,972 --> 00:28:42,192 So I have a group of people that I've picked from those practice units 470 00:28:42,222 --> 00:28:47,312 as I call them like, um, technology allies, you know, so to kind of 471 00:28:47,312 --> 00:28:49,332 run some of our ideas with them. 472 00:28:49,342 --> 00:28:49,832 Um, first. 473 00:28:50,192 --> 00:28:52,092 Um, to say, hey, is this right? 474 00:28:52,092 --> 00:28:55,792 And then also get information from them as the inner workings 475 00:28:55,822 --> 00:29:00,022 of their practices and what their, what their experience has been. 476 00:29:00,022 --> 00:29:01,382 Why are people complaining? 477 00:29:01,452 --> 00:29:06,522 Uh, what is it that not, what is it that, um, truly not working? 478 00:29:06,552 --> 00:29:08,102 Not the technology, you know? 479 00:29:08,102 --> 00:29:12,972 So those are, like, not the fix and break things, but what, what is the process? 480 00:29:12,972 --> 00:29:18,442 And in some instances it, the solution is ha might not have anything to do with 481 00:29:18,442 --> 00:29:22,622 technology, but it might have something to do with the way the process is set 482 00:29:22,622 --> 00:29:27,912 up or the, the way client demands are different from other, uh, projects. 483 00:29:27,922 --> 00:29:28,232 So 484 00:29:28,492 --> 00:29:34,172 there is so many factors and essentially, um, I think that 485 00:29:34,952 --> 00:29:36,382 we have changed processes. 486 00:29:36,382 --> 00:29:40,852 Yes, we don't use vellum and we don't use other things, but in some instances 487 00:29:40,852 --> 00:29:42,822 we haven't changed the way we think. 488 00:29:43,842 --> 00:29:44,232 So. 489 00:29:44,732 --> 00:29:48,732 We, there, there is this, uh, you know, I think I can give the analogy 490 00:29:48,732 --> 00:29:53,072 of if your native language is not English, you kind of end up thinking 491 00:29:53,072 --> 00:29:57,762 or counting or whatever in your head with your native language, although 492 00:29:57,762 --> 00:29:59,342 you are saying it in English, right? 493 00:29:59,502 --> 00:30:01,342 So I feel that that's the analogy. 494 00:30:01,362 --> 00:30:08,092 A lot of people are so much, um, um, rooted in the old way of doing 495 00:30:08,112 --> 00:30:11,722 things, even though the technology has changed and it's a PDF now, 496 00:30:12,032 --> 00:30:14,092 but, uh, and not a piece of paper. 497 00:30:14,727 --> 00:30:16,377 but their thinking hasn't changed. 498 00:30:17,207 --> 00:30:21,337 and, and and that's fundamentally an obstruction in moving forward. 499 00:30:21,357 --> 00:30:28,707 And, and that goes outside of our firm into, you know, uh, not 500 00:30:28,757 --> 00:30:30,347 change contractual agreements. 501 00:30:30,367 --> 00:30:35,487 Now, I feel in some ways, the technology is a little bit ahead of the game 502 00:30:35,577 --> 00:30:41,997 always and kind of retracts a little to support this types of, um, Thought 503 00:30:42,007 --> 00:30:43,837 processes that are not changing. 504 00:30:43,877 --> 00:30:49,307 So it's funny because last week someone told me and on a projects 505 00:30:49,307 --> 00:30:52,517 like, Oh, you know that, you know, what do you mean the RFIs will be less? 506 00:30:52,527 --> 00:30:57,947 Well, then that party that is benefiting from Making money 507 00:30:58,247 --> 00:30:59,657 out of the RFIs is not happy. 508 00:30:59,717 --> 00:31:04,957 So, Evan, how, how can you solve that problem when technology is out there? 509 00:31:05,397 --> 00:31:08,277 Yeah, technology is out there to solve that, but we don't want to 510 00:31:08,277 --> 00:31:11,477 solve it because certain people were out of business for that, right? 511 00:31:11,747 --> 00:31:17,247 So, the same goes to, internally, when we show all these tools about, 512 00:31:17,597 --> 00:31:22,287 um, clash detections or other ways of figuring out things and solving problems 513 00:31:22,317 --> 00:31:27,832 before it gets to site, then these They ask us, well, are we contractually 514 00:31:27,832 --> 00:31:29,312 supposed to deliver these things? 515 00:31:29,342 --> 00:31:30,742 Why are we doing these things? 516 00:31:30,742 --> 00:31:31,422 Well, wait a minute. 517 00:31:31,822 --> 00:31:32,362 You know, we're, 518 00:31:32,632 --> 00:31:33,532 that's what, yeah. 519 00:31:33,532 --> 00:31:34,792 Which is why I said 520 00:31:35,102 --> 00:31:40,702 that it says it's a collaborative firm, uh, collaborative ecosystem. 521 00:31:41,222 --> 00:31:46,597 But it's not actually a collaborative ecosystem because, Um, we have, 522 00:31:46,617 --> 00:31:51,067 we're still thinking the old ways, we're delivering in new technologies 523 00:31:51,357 --> 00:31:55,277 and I can't wait to see what that AI thing is going to do in terms 524 00:31:55,307 --> 00:31:57,107 of that type of process, right? 525 00:31:57,437 --> 00:31:57,847 So, 526 00:31:58,227 --> 00:32:03,867 um, we, the tools have changed but mine, it's hard to change mindsets. 527 00:32:04,967 --> 00:32:05,387 Evan Troxel: Yeah. 528 00:32:05,437 --> 00:32:05,697 Yeah. 529 00:32:05,697 --> 00:32:09,667 I, for the longest time I said behavior and I found out that people 530 00:32:09,667 --> 00:32:11,497 don't like their behavior to change. 531 00:32:11,527 --> 00:32:12,657 They don't like that idea, right? 532 00:32:12,667 --> 00:32:17,687 So mindset's a better word to use there because it's not so offensive to people. 533 00:32:18,017 --> 00:32:21,247 Uh, but, but your, your point is absolutely correct. 534 00:32:21,247 --> 00:32:26,157 It's, there's this, picture that gets painted of an ideal future scenario. 535 00:32:26,867 --> 00:32:32,817 And the only thing we can actually disrupt is ourselves and our processes, because 536 00:32:32,817 --> 00:32:37,227 there are so many hard constraints just outside of the organization, whether it's 537 00:32:37,677 --> 00:32:42,097 who's doing plan check or how they're accepting submittals or what's in the 538 00:32:42,097 --> 00:32:43,967 contract, who wrote that contract? 539 00:32:43,967 --> 00:32:45,967 How has that ever been updated? 540 00:32:45,967 --> 00:32:46,747 Like there's so many 541 00:32:46,747 --> 00:32:49,717 things that we're kind of butting up against all the time. 542 00:32:50,267 --> 00:32:53,317 Like Clifton Harness from TestFit said, if you want to change things. 543 00:32:53,547 --> 00:32:54,897 The industry changed the 544 00:32:54,897 --> 00:32:56,237 owner architect contract 545 00:32:56,247 --> 00:32:56,687 like that. 546 00:32:56,697 --> 00:33:01,027 The agreement is where you need, you need to start there, not in the 547 00:33:01,037 --> 00:33:02,977 digital twin that you deliver, right? 548 00:33:02,977 --> 00:33:07,757 Because like that, that to me is like, you're, you're aiming at the wrong thing. 549 00:33:07,757 --> 00:33:10,947 You have to start at the fundamentals that are actually going to have. 550 00:33:11,262 --> 00:33:16,482 the ability to ripple throughout the ecosystem to actually create change 551 00:33:16,692 --> 00:33:18,262 if you want to see change happen. 552 00:33:18,802 --> 00:33:23,332 But so many times we're focused on the shiny thing that looks like it's 553 00:33:23,332 --> 00:33:26,882 going to do something when in fact it's just, it's never going to make 554 00:33:26,882 --> 00:33:31,302 it because we can't get past the other barriers that are really hard to disrupt 555 00:33:31,302 --> 00:33:34,827 because that's somebody's That's where they're making their money, right? 556 00:33:35,337 --> 00:33:38,897 There's no incentive there to get rid of that for them, and so why would they? 557 00:33:39,227 --> 00:33:41,727 And we fight up against that all the time, and I think it's important for 558 00:33:41,727 --> 00:33:46,417 technology companies to understand that ecosystem approach that we have to 559 00:33:46,417 --> 00:33:52,167 operate within as architects and engineers because we don't have control over the 560 00:33:52,177 --> 00:33:54,542 changes that are happening over there. 561 00:33:54,542 --> 00:33:57,540 We have to work within the system that exists. 562 00:33:57,540 --> 00:34:00,538 It is evolving slowly, um, but it's very slow. 563 00:34:00,538 --> 00:34:02,536 Like, let's be honest about that. 564 00:34:02,536 --> 00:34:03,202 Mm hmm. 565 00:34:03,832 --> 00:34:04,092 Nirva Fereshetian: Yeah. 566 00:34:04,092 --> 00:34:07,982 And I think, uh, you know, I always, um, you know, there is all these things about 567 00:34:08,022 --> 00:34:09,922 innovate and what firms are innovating. 568 00:34:09,922 --> 00:34:15,292 And I've spoken in places where the titles of the conferences are innovate, and it's 569 00:34:15,292 --> 00:34:22,242 hard to see that a lot of things a lot of us are doing can be labeled as innovate. 570 00:34:22,532 --> 00:34:27,871 Um, I think innovate means to me that a fundamental change 571 00:34:27,902 --> 00:34:30,072 of the practice overall. 572 00:34:30,387 --> 00:34:36,667 The entire ecosystem, we can only innovate when we get there using different tools 573 00:34:36,667 --> 00:34:42,147 and kind of solving internal problems or evolving to better practices. 574 00:34:42,147 --> 00:34:43,677 Yes, it gets better. 575 00:34:43,927 --> 00:34:45,237 You know, we get better at it. 576 00:34:45,257 --> 00:34:45,786 It gets 577 00:34:46,547 --> 00:34:46,746 less. 578 00:34:46,786 --> 00:34:48,117 Yeah, it's not. 579 00:34:48,117 --> 00:34:50,027 Yes, it's absolutely evolution. 580 00:34:50,087 --> 00:34:54,237 And, you know, I know the reputation is that change doesn't come easily. 581 00:34:54,467 --> 00:34:57,927 Um, to specifically, it doesn't come easily to any humans, but 582 00:34:57,937 --> 00:35:04,017 specifically to this industry largely because we are chained to all these 583 00:35:04,027 --> 00:35:09,797 mindsets and not until those are collectively worked on and changed. 584 00:35:10,317 --> 00:35:12,297 I don't see innovation. 585 00:35:12,657 --> 00:35:16,887 I see gradual evolving of things to get a little bit better than 586 00:35:16,887 --> 00:35:20,567 yesterday, but I can't see innovate. 587 00:35:20,757 --> 00:35:22,667 You know, there's some examples of, you know. 588 00:35:23,237 --> 00:35:27,207 Um, there's always that Uber innovating, you know, the whole process 589 00:35:27,207 --> 00:35:30,567 of, uh, the taxi, um, situation. 590 00:35:30,767 --> 00:35:36,317 Um, I, I think that's a, like a, um, a complete change of how we 591 00:35:36,317 --> 00:35:41,527 do things, um, that can be called, you know, beginning of innovation. 592 00:35:41,637 --> 00:35:47,447 But Swapping some tools for others or creating some automations, which 593 00:35:47,447 --> 00:35:52,517 are necessary, um, to avoid waste of time or redundancies or things like 594 00:35:52,517 --> 00:35:56,437 that are good things, definitely, but not necessarily innovating. 595 00:35:57,632 --> 00:35:59,972 Evan Troxel: There's confusion around those words because the 596 00:35:59,972 --> 00:36:02,812 confusion even comes from within our firms themselves, right? 597 00:36:02,822 --> 00:36:06,052 Our marketing departments in our firms want to. 598 00:36:06,797 --> 00:36:10,627 Pat ourselves on the back in front of our clients and say, look, 599 00:36:10,637 --> 00:36:11,817 we're innovating. 600 00:36:12,487 --> 00:36:12,747 Right. 601 00:36:12,767 --> 00:36:16,087 And so there's, there's confusion because a lot of times it's like, 602 00:36:16,087 --> 00:36:19,847 well, we're doing AI in our firms and here's some, maybe some different 603 00:36:19,847 --> 00:36:21,417 ways that we're doing AI, right? 604 00:36:21,417 --> 00:36:22,987 So that at least we look like we're. 605 00:36:23,007 --> 00:36:32,677 Um, but the fact is like, a lot of times that's, that's like 606 00:36:32,687 --> 00:36:37,467 innovation theater being put out there and it's not actually taking a 607 00:36:37,467 --> 00:36:39,867 foothold in the offices themselves. 608 00:36:40,502 --> 00:36:45,352 And, and it becomes this game that we play with words to position 609 00:36:45,352 --> 00:36:49,402 ourselves to get the right perspective, like to, to, I shouldn't say get 610 00:36:49,402 --> 00:36:53,412 the right perspective, but to, to tailor the perspective that others 611 00:36:53,422 --> 00:36:54,122 have about 612 00:36:54,122 --> 00:36:54,772 us, right? 613 00:36:54,802 --> 00:36:59,072 And so then we start using those words inside the firms, and 614 00:36:59,072 --> 00:37:01,292 then there's confusion, like what's actually happening here? 615 00:37:01,312 --> 00:37:03,672 Is it really innovation or is it just evolution? 616 00:37:03,702 --> 00:37:07,692 And, and, and words do matter, but at the same time, getting back 617 00:37:07,692 --> 00:37:11,112 to kind of, people's interests, like where the incentives are. 618 00:37:11,492 --> 00:37:14,822 The incentive is to show that we're leaders. 619 00:37:14,842 --> 00:37:15,862 And how are we doing that? 620 00:37:15,872 --> 00:37:17,492 We're doing it through innovation. 621 00:37:17,642 --> 00:37:18,812 But how are we really doing that? 622 00:37:18,972 --> 00:37:20,932 By automating parking layout. 623 00:37:20,972 --> 00:37:22,262 Like, not really, right? 624 00:37:22,502 --> 00:37:24,282 So, we are 625 00:37:24,282 --> 00:37:25,162 at odds with these 626 00:37:25,392 --> 00:37:28,692 Nirva Fereshetian: Alright, I, I, I, but I think I've learned, um, you know, like 627 00:37:28,692 --> 00:37:32,552 I said, there is a lot of things that I learned along the process of skills 628 00:37:32,552 --> 00:37:37,052 that, um, not that I, I, that skills that I should be interested in improving, 629 00:37:37,062 --> 00:37:43,292 not that I am there, but perception is everything, Evan, you know, so, yeah, 630 00:37:43,332 --> 00:37:47,762 so, even in technology, perception is everything, even though it is, you know, 631 00:37:48,702 --> 00:37:50,652 Technology to me is just black and white. 632 00:37:50,652 --> 00:37:52,092 Does it work or does it not work? 633 00:37:52,092 --> 00:37:55,462 You know, so I, I can never be a salesperson because when those people 634 00:37:55,472 --> 00:37:57,412 start, they can embellish everything. 635 00:37:57,422 --> 00:37:57,862 Yeah. 636 00:37:58,312 --> 00:37:59,252 So, so, 637 00:38:00,012 --> 00:38:02,232 but still perception is everything. 638 00:38:02,252 --> 00:38:06,212 Like, I'm going to come back to what I said in terms of how you. 639 00:38:06,212 --> 00:38:12,622 How you, uh, present it, how you say it, how you talk about it, and I think, uh, 640 00:38:12,682 --> 00:38:14,732 you know, we work with dozens of startups. 641 00:38:14,762 --> 00:38:17,692 It's something that I am very, very passionate about. 642 00:38:17,692 --> 00:38:23,162 That it is anybody in this ecosystem needs to contribute to 643 00:38:23,192 --> 00:38:28,822 those, all those people that are trying hard to innovate, you know? 644 00:38:28,842 --> 00:38:35,682 Do something very different, or go up against incumbents that never Had, had, 645 00:38:35,752 --> 00:38:39,352 was not a real reality in the last decade. 646 00:38:39,602 --> 00:38:44,012 So I think by contributing whatever, you know, I think we're a beneficiary 647 00:38:44,012 --> 00:38:48,482 of others who've contributed and worked with the, um, startups. 648 00:38:48,482 --> 00:38:51,802 And so we need to put in some things to our share of it. 649 00:38:51,882 --> 00:38:54,882 So I feel very, um, passionate about that. 650 00:38:54,882 --> 00:38:56,842 And we have worked with lots of them. 651 00:38:57,132 --> 00:39:03,807 Um, but I feel like, Them and us, it's all about perception, and sometimes they're 652 00:39:03,807 --> 00:39:10,127 not good at showing, you know, um, they're not good at presenting, they're not good 653 00:39:10,137 --> 00:39:13,167 at, um, although their product is good. 654 00:39:13,247 --> 00:39:17,247 And sometimes they're so good at presenting, but their product is not good. 655 00:39:17,667 --> 00:39:22,707 You know, so, yeah, so, and the same goes for us internally, um, it's 656 00:39:22,717 --> 00:39:29,367 how good are we, um, to communicate with all and with all those other 657 00:39:29,367 --> 00:39:32,717 practice units and, um, collaborate. 658 00:39:33,567 --> 00:39:36,197 I think it's all about how we're perceived. 659 00:39:36,487 --> 00:39:40,897 And once we're, you know, we're, once with a bad perception is 660 00:39:40,907 --> 00:39:42,677 broken, Evan, it's, it's like trust. 661 00:39:42,697 --> 00:39:43,737 It's hard to get it back. 662 00:39:43,737 --> 00:39:45,127 Right. 663 00:39:45,167 --> 00:39:48,237 Evan Troxel: Yeah, I was speaking with a building product manufacturer 664 00:39:48,247 --> 00:39:52,427 just yesterday, actually, and innovation is happening. 665 00:39:52,827 --> 00:39:56,927 Evolution, I'll say, is happening in their, in their category of 666 00:39:56,927 --> 00:40:02,687 product, but maybe an old version of that project, of that product. 667 00:40:03,102 --> 00:40:05,242 didn't fly with architects, right? 668 00:40:05,302 --> 00:40:07,492 And therefore the category has been written off. 669 00:40:07,542 --> 00:40:11,652 And it's very hard to reestablish yourself as, well, we fixed 670 00:40:11,652 --> 00:40:13,932 all those problems and now 671 00:40:13,962 --> 00:40:14,822 you can count on 672 00:40:14,822 --> 00:40:15,212 us. 673 00:40:15,652 --> 00:40:18,382 That's a super hard barrier to overcome. 674 00:40:18,402 --> 00:40:21,932 And so you're talking about that from like technology standpoint, right? 675 00:40:21,932 --> 00:40:22,602 It's the same. 676 00:40:22,832 --> 00:40:24,732 It's, this is a human condition. 677 00:40:24,742 --> 00:40:26,842 Like this, it happens in all categories. 678 00:40:26,842 --> 00:40:29,212 It's like, Oh, I don't trust that brand of vacuum 679 00:40:29,212 --> 00:40:29,872 because. 680 00:40:30,467 --> 00:40:31,037 Nirva Fereshetian: You've had one 681 00:40:31,047 --> 00:40:31,727 Evan Troxel: me after a week. 682 00:40:32,087 --> 00:40:35,957 It doesn't, yeah, it's, it's all based on experience and it is very hard 683 00:40:35,957 --> 00:40:39,037 to, to reestablish, um, maybe a new 684 00:40:39,037 --> 00:40:43,782 version of that in the market once you've already created a, a bad situation. 685 00:40:44,062 --> 00:40:47,582 I want to talk about these startups that you're working with, not necessarily 686 00:40:47,582 --> 00:40:51,132 by name, but just in implementation, because something that you've talked about 687 00:40:51,162 --> 00:40:52,242 is tool fatigue. 688 00:40:52,762 --> 00:40:56,482 I've I've categorized it as digital fatigue or app fatigue. 689 00:40:56,482 --> 00:40:59,862 It's like more and more of our time is consumed sitting in front of 690 00:40:59,862 --> 00:41:05,352 a screen, whether it's a desktop or a tablet or a phone, right? 691 00:41:05,672 --> 00:41:06,962 It's just more and more screens. 692 00:41:06,982 --> 00:41:12,937 And there's so, we're being inundated with with the tool explosion that's going on in 693 00:41:13,297 --> 00:41:15,617 AEC, but everywhere else as well, right? 694 00:41:15,617 --> 00:41:18,957 So they, these do bleed into each other for sure. 695 00:41:19,337 --> 00:41:23,117 And you talked about the different groups that operate under digital practice. 696 00:41:23,117 --> 00:41:27,167 And I'm interested from an implementation standpoint, because we're getting the 697 00:41:27,167 --> 00:41:31,107 fire hose of new tools, especially right now, it feels like more than 698 00:41:31,107 --> 00:41:34,697 ever now with, with AI and everything's AI, and there's all these different. 699 00:41:35,212 --> 00:41:38,032 Really specific AI tools, not to really 700 00:41:38,032 --> 00:41:43,252 go down the AI lane here, but just tools in general in AEC. 701 00:41:43,682 --> 00:41:50,102 I'm, I'm interested in vetting and implementation and support and training. 702 00:41:50,112 --> 00:41:53,972 And just for you to kind of tell a story about how you go 703 00:41:53,972 --> 00:41:55,202 about trying to accomplish that. 704 00:41:55,202 --> 00:42:00,212 And the reason why I want to talk about this is because these tech companies come 705 00:42:00,212 --> 00:42:03,872 to you like they are the only thing that you need to pay attention to right now. 706 00:42:05,007 --> 00:42:06,677 Because that's their world, right? 707 00:42:06,687 --> 00:42:10,497 It makes sense, but at the same time, they don't really look around and have 708 00:42:10,497 --> 00:42:14,057 the bigger picture perception that you have to have as a digital practice 709 00:42:14,057 --> 00:42:19,157 leader, CIO of CBT architects to say, we have to look at everything and how 710 00:42:19,187 --> 00:42:22,737 everything works together and how we would roll this out to 200 plus people 711 00:42:22,737 --> 00:42:25,767 across this many offices, and then we have to support it and we have to train. 712 00:42:26,037 --> 00:42:27,957 Like all of that responsibility falls on you. 713 00:42:27,967 --> 00:42:29,847 All they have to do is sell you the subscription. 714 00:42:30,087 --> 00:42:30,337 Right. 715 00:42:30,587 --> 00:42:32,207 And get you to buy into that subscription. 716 00:42:32,497 --> 00:42:36,657 But talk about the real world challenges with all of those things. 717 00:42:36,667 --> 00:42:40,337 Once it actually gets through the wall and maybe even step before that, 718 00:42:40,347 --> 00:42:44,227 how do you, how do you even go about vetting or trying out or getting 719 00:42:44,227 --> 00:42:45,717 excited about these tools that are 720 00:42:45,777 --> 00:42:46,357 on offer? 721 00:42:46,762 --> 00:42:52,022 Nirva Fereshetian: Yeah, I think, I think, um, the, you know, I don't know, 722 00:42:52,022 --> 00:42:56,012 there are lists, AEC hub everywhere, over a thousand tools to look at, and, 723 00:42:56,277 --> 00:42:56,677 Evan Troxel: Only a 724 00:42:56,902 --> 00:43:00,352 Nirva Fereshetian: yeah, I don't know, over a thousand or whatever, but also the 725 00:43:00,352 --> 00:43:06,892 entire other ecosystem of non AEC tools that there is also, uh, a thousand of 726 00:43:06,892 --> 00:43:13,437 them to look at, and I think that, um, It's very much for me that I'm, one of 727 00:43:13,437 --> 00:43:18,477 the other skill sets is, uh, uh, I now investigate how they're backed up and 728 00:43:18,477 --> 00:43:22,457 what's their VC funding, things that I never looked at before, Evan, like, uh, 729 00:43:22,487 --> 00:43:23,607 Evan Troxel: Because of longevity 730 00:43:23,857 --> 00:43:24,197 Nirva Fereshetian: right. 731 00:43:24,347 --> 00:43:27,227 Oh, because things that, you know, I always say that we're 732 00:43:27,227 --> 00:43:28,887 putting bets on the table. 733 00:43:29,337 --> 00:43:32,507 Um, and sometimes the company is disappearing. 734 00:43:32,637 --> 00:43:36,117 Like, uh, we never attested one, but like, I think the company's 735 00:43:36,117 --> 00:43:38,987 named co design or something like after four or five years, they just. 736 00:43:39,657 --> 00:43:40,447 Disappeared. 737 00:43:40,757 --> 00:43:40,987 Right. 738 00:43:41,007 --> 00:43:41,837 They closed for good. 739 00:43:41,987 --> 00:43:44,807 And, and that doesn't only happen with startups. 740 00:43:44,827 --> 00:43:49,367 It happens with, uh, established companies, you know, like, um, Autodesk 741 00:43:49,367 --> 00:43:53,467 decided that they're not going to support Formit anymore, although they, they 742 00:43:54,227 --> 00:43:57,027 really hard pushed it for a few years before that. 743 00:43:57,037 --> 00:44:01,947 So it's, it's, um, there is certainly risks. 744 00:44:02,307 --> 00:44:08,527 Um, but I think part of it is that I kind of categorize tools. 745 00:44:09,047 --> 00:44:13,507 Um, it's very important to look at them as to what process they belong to. 746 00:44:14,407 --> 00:44:21,917 So, for the front end, and which is why everybody, you know, when you ask, does 747 00:44:21,917 --> 00:44:27,267 an office use AI, and mostly they talk about the image generation part of AI, 748 00:44:27,757 --> 00:44:32,997 because, you know, I think not only that is the most, you know, design seems to be 749 00:44:33,007 --> 00:44:40,287 the king of our, you know, it's always the flashiest, uh, role in our offices, you 750 00:44:40,287 --> 00:44:45,327 know, so, but beyond that, it's more of a one to one relationship with the tool. 751 00:44:45,667 --> 00:44:46,107 So. 752 00:44:46,792 --> 00:44:50,782 if it's an individual workflow, it's relatively easy to say, well, 753 00:44:50,782 --> 00:44:52,212 we can test all of these things. 754 00:44:52,212 --> 00:44:54,832 And it's just personal preference to say yes or no. 755 00:44:55,192 --> 00:44:59,842 So the examples are that if, if, um, they want to use Verus because they used it 756 00:44:59,842 --> 00:45:04,022 a couple of times and they think it's good, or even on a basic level, the, you 757 00:45:04,022 --> 00:45:08,532 know, we have designers who want Enscape, others want Twinmotion, others want 758 00:45:08,532 --> 00:45:13,772 something else, but those are relatively easy to say, well, we can test it. 759 00:45:13,772 --> 00:45:15,372 And even if we don't. 760 00:45:15,887 --> 00:45:22,717 You know, if there's personal prefaces, we can, uh, kind of consent to that, right? 761 00:45:22,717 --> 00:45:25,127 So, this designer uses that and not that. 762 00:45:25,657 --> 00:45:30,437 Um, but when it moves beyond that, it becomes extremely critical to 763 00:45:31,047 --> 00:45:34,077 make, um, try to make good decisions. 764 00:45:34,377 --> 00:45:38,377 Um, and kind of pass it through, it says, uh, a couple of things. 765 00:45:38,377 --> 00:45:40,982 Does, is this, uh, uh, solving a problem? 766 00:45:41,242 --> 00:45:44,952 Is this better than what we, is it replacing another tool we have? 767 00:45:44,982 --> 00:45:47,662 Is it an adding to another tool we have? 768 00:45:47,962 --> 00:45:49,942 Um, definitely. 769 00:45:50,262 --> 00:45:57,372 Is it providing some, um, service that we can, um, do now that we weren't able to 770 00:45:57,372 --> 00:45:59,352 do before because we didn't have the tool? 771 00:46:00,092 --> 00:46:02,152 It has to kind of comply to one of these things. 772 00:46:02,162 --> 00:46:03,942 Is it faster than what we have? 773 00:46:04,242 --> 00:46:07,212 So we, Kind of, I divide it to parts. 774 00:46:07,242 --> 00:46:12,862 It's some things the design technology team looks at some products as a 775 00:46:12,862 --> 00:46:19,422 replacement to an existing product that is not working or people in the teams 776 00:46:19,422 --> 00:46:24,372 have heard it or tried something and they think that it solves a problem they have. 777 00:46:24,562 --> 00:46:30,842 So our initial step is to actually create a small, um, testing, uh, 778 00:46:30,852 --> 00:46:35,052 group, whether it's inside our teams or, uh, the design technology and kind 779 00:46:35,052 --> 00:46:37,562 of validate that before we move on. 780 00:46:37,862 --> 00:46:42,602 And in many instances, it's real hard conversations with the startups 781 00:46:42,602 --> 00:46:48,092 to explain to them if that fits or does not fit in our workflow. 782 00:46:49,382 --> 00:46:56,652 So, even established products is hard, uh, to implement if it doesn't fit. 783 00:46:56,672 --> 00:47:02,662 So, sometimes there's so many overlaps, um, the product builds a 784 00:47:02,662 --> 00:47:07,012 3D model, but our designers don't want to use anything but Rhino. 785 00:47:07,772 --> 00:47:09,462 So, how does that work out? 786 00:47:09,492 --> 00:47:12,222 Because then they ask for the plug in to Rhino to that 787 00:47:12,222 --> 00:47:14,602 product and not build it there. 788 00:47:14,782 --> 00:47:20,937 So, if you don't understand, um, the workflow, Um, if you're trying to build 789 00:47:20,947 --> 00:47:28,347 something, um, where there is a industry accepted, uh, sort of industry accepted 790 00:47:28,347 --> 00:47:33,437 product, if you're replacing that, you need to at least be as good as that. 791 00:47:33,707 --> 00:47:34,907 Don't come before that. 792 00:47:35,127 --> 00:47:35,547 You know? 793 00:47:35,847 --> 00:47:38,167 Don't come before that because we're not replacing it. 794 00:47:38,677 --> 00:47:43,877 So there is so many things to look at as barriers to move, and then there are 795 00:47:43,877 --> 00:47:50,067 things that are really expert products, like, I give the example of Upcodes and, 796 00:47:50,397 --> 00:47:55,677 um, it just services a small group of people, you know, our code experts use it. 797 00:47:55,867 --> 00:48:01,447 But then we proliferated that to say, okay, it's also kind of a training and 798 00:48:01,447 --> 00:48:06,497 education for people who are up and, up and coming and trying to learn that. 799 00:48:06,517 --> 00:48:11,687 But that's sliver of a, you know, it's not, it's not really everybody. 800 00:48:11,997 --> 00:48:17,247 Um, so the last thing is, the most challenging thing is to implement 801 00:48:17,257 --> 00:48:20,957 platform products, which are supposed to be used by everyone. 802 00:48:20,987 --> 00:48:22,437 Otherwise it doesn't make sense. 803 00:48:23,197 --> 00:48:26,537 So, and those decisions are really hard to revert. 804 00:48:26,897 --> 00:48:31,467 So if we made a mistake, and we don't want to use that, or we want to transition 805 00:48:31,467 --> 00:48:35,657 to another product like that, it takes a long time, because all that data sets 806 00:48:35,657 --> 00:48:39,587 are there, we have to move them to the new place, we have to train everybody, 807 00:48:39,907 --> 00:48:44,617 um, so the having the training person attached to our department certainly 808 00:48:44,617 --> 00:48:50,892 helps, but, um, really looking at all of the implementations in their 809 00:48:50,892 --> 00:48:54,032 own context is what we try to do. 810 00:48:55,022 --> 00:48:58,982 We try to make sure that we're not inundating people. 811 00:48:58,992 --> 00:49:04,602 So for example, a lot of things are now possible and available 812 00:49:04,622 --> 00:49:08,372 in Construction Cloud, including marking up drawings or whatever. 813 00:49:08,372 --> 00:49:11,802 So the question is, do we really need these other extra tools? 814 00:49:12,092 --> 00:49:17,587 But they're used to it, Evan, you know, so like, it takes a, it takes a, a 815 00:49:17,587 --> 00:49:22,547 whole training session to say, well, you could stay in this one product and 816 00:49:22,547 --> 00:49:27,437 do some of the things that you're doing with parts and pieces of other tools. 817 00:49:29,017 --> 00:49:29,177 Evan Troxel: Yeah. 818 00:49:29,177 --> 00:49:33,607 I think the, the, what you're, what you're saying about implementing at the platform 819 00:49:33,607 --> 00:49:38,267 level is it is very difficult because of the reasons it plus, plus cost, right? 820 00:49:38,267 --> 00:49:42,537 It's, it's also a very expensive endeavor plus training and all of the things that 821 00:49:42,547 --> 00:49:48,877 you have to do to bring people up to speed and keep them up to speed as it evolves. 822 00:49:49,447 --> 00:49:52,677 But then those platforms naturally leave holes, like they can't 823 00:49:52,677 --> 00:49:54,417 do everything perfectly well. 824 00:49:54,417 --> 00:49:59,937 So we see startups coming in with really specific things that they do 825 00:49:59,957 --> 00:50:04,117 and Now we're feeling like okay Well, I need to use this for the feasibility 826 00:50:04,117 --> 00:50:04,977 study then I need to 827 00:50:04,977 --> 00:50:09,337 use this for the programming I need to use this for the Conceptual design, 828 00:50:09,337 --> 00:50:11,907 then I need to use this for the design development and construction 829 00:50:11,907 --> 00:50:14,977 documents, and I need all these other plug ins to do all the little holes 830 00:50:14,977 --> 00:50:19,147 that those platforms leave, and all of a sudden we've just, we've gotta know 831 00:50:19,537 --> 00:50:21,747 a lot about a lot of apps out there. 832 00:50:21,747 --> 00:50:24,227 And this is, and then you have to manage that. 833 00:50:24,257 --> 00:50:28,957 Your group manages all of the, all of the help desk tickets that come 834 00:50:28,957 --> 00:50:30,977 in for all those different apps. 835 00:50:31,377 --> 00:50:35,207 And I, and I just, it's worth saying all this because this is what firms 836 00:50:35,247 --> 00:50:37,987 are dealing with every single day. 837 00:50:38,007 --> 00:50:40,527 And then there's the cloud, and then there's where are the files, 838 00:50:40,527 --> 00:50:43,747 and then there's the governance and the ethics around the AI stuff. 839 00:50:43,747 --> 00:50:43,987 And there's. 840 00:50:44,572 --> 00:50:48,262 There's all these other pieces to that puzzle, and it is incredibly 841 00:50:48,262 --> 00:50:53,882 complex to manage all that, and have happy users, and get great outcomes, 842 00:50:53,902 --> 00:50:56,192 and all of those things, and that's what, that's what you're in charge 843 00:50:56,192 --> 00:50:56,852 of at your firm, 844 00:50:57,227 --> 00:50:57,677 Nirva Fereshetian: Right. 845 00:50:57,967 --> 00:51:03,727 I, I think that we have to learn, um, um, celebrate small 846 00:51:03,737 --> 00:51:06,147 victories in order to get the, 847 00:51:06,647 --> 00:51:09,577 the, to kind of have the bigger victories. 848 00:51:09,717 --> 00:51:18,167 So sometimes the, these tools plug holes, but you have to really think about, um, 849 00:51:20,467 --> 00:51:24,927 was it really worth the time and effort to learn something totally new 850 00:51:24,947 --> 00:51:26,917 because it plugged a temporary hole. 851 00:51:26,947 --> 00:51:28,737 Some of them are plugging real holes. 852 00:51:29,742 --> 00:51:32,522 and really worthwhile to give it an effort. 853 00:51:32,812 --> 00:51:38,632 And the other thing is like, um, the, the, the way some of the startups 854 00:51:38,652 --> 00:51:40,202 are progressing is incredible. 855 00:51:40,232 --> 00:51:42,702 You know, something that did not work a couple of weeks ago, they 856 00:51:42,702 --> 00:51:44,062 can make it work in two weeks. 857 00:51:44,522 --> 00:51:47,802 So you can't just leave them and say, well, it didn't work. 858 00:51:48,032 --> 00:51:53,672 So in some of our instances, um, it's so refreshing to talk to owners 859 00:51:53,672 --> 00:52:00,297 and, um, Um, directly or developers directly on the issue, um, and 860 00:52:00,347 --> 00:52:02,327 immediately get response and fix it. 861 00:52:02,627 --> 00:52:07,177 And those are really, um, great experiences we're having in terms 862 00:52:07,177 --> 00:52:13,577 of using products that, you know, develop that fast or change that fast. 863 00:52:13,897 --> 00:52:14,187 Um, 864 00:52:14,342 --> 00:52:15,222 Evan Troxel: Versus the ones that 865 00:52:15,387 --> 00:52:15,987 Nirva Fereshetian: that's right. 866 00:52:16,127 --> 00:52:21,682 That's versus the ones that, you know, people have been complacent about, right? 867 00:52:21,682 --> 00:52:22,752 So it's not going to work. 868 00:52:22,822 --> 00:52:23,382 That's it. 869 00:52:23,522 --> 00:52:27,212 We're set where we have 10 different workarounds and 870 00:52:27,252 --> 00:52:28,432 that's how we're going to live. 871 00:52:28,782 --> 00:52:32,872 Uh, because we know that nobody's going to do anything about it. 872 00:52:33,072 --> 00:52:33,292 Yeah. 873 00:52:33,352 --> 00:52:33,752 Evan Troxel: Yeah. 874 00:52:35,195 --> 00:52:39,125 This episode is made possible with support from avail, along 875 00:52:39,155 --> 00:52:42,545 with their newly released Revvit application version management. 876 00:52:42,816 --> 00:52:46,986 AEC software company avail has added another powerful new workflow feature 877 00:52:47,016 --> 00:52:51,606 called pallets To its suite of content management capabilities, pallets are user 878 00:52:51,606 --> 00:52:56,115 customized lists of content and avail and can function as a favorites list as 879 00:52:56,115 --> 00:52:58,215 starter content for a specific project. 880 00:52:58,485 --> 00:53:02,625 Or to drive workflows such as redlining, construction details, customers. 881 00:53:02,625 --> 00:53:05,295 Administrators can add pallets to their accounts through the 882 00:53:05,295 --> 00:53:07,425 avail managed portal page today. 883 00:53:07,815 --> 00:53:10,125 Interested in seeing pallets and action first. 884 00:53:10,365 --> 00:53:15,705 Request a demo at get avail.com/request-demo. 885 00:53:16,043 --> 00:53:21,113 Avail helps AECO firms better manage, organize, and navigate information faster. 886 00:53:21,413 --> 00:53:25,523 My thanks to avail for supporting this episode of the Troxell podcast. 887 00:53:25,883 --> 00:53:27,773 And now let's return to the conversation. 888 00:53:29,775 --> 00:53:35,330 Yeah, so, or how do you develop and And just keep a continued, um, 889 00:53:35,390 --> 00:53:38,960 like learning environment going, because there's probably all 890 00:53:38,960 --> 00:53:40,590 kinds of experiences around that. 891 00:53:40,590 --> 00:53:43,680 There's the, like, oh, I'm just going to keep doing it the way I've always 892 00:53:43,680 --> 00:53:48,270 done it because I know it works, and I'm okay with the holes because I know 893 00:53:48,270 --> 00:53:53,460 the ten workarounds that I need to do, versus, you know, vetting through a 894 00:53:53,460 --> 00:53:58,810 myriad of options of, of promises to fill those holes and finding the one needle 895 00:53:58,810 --> 00:54:00,510 in the haystack that actually works. 896 00:54:00,850 --> 00:54:03,620 Like, okay, that could be fatiguing just going through that process. 897 00:54:03,620 --> 00:54:03,830 Right. 898 00:54:03,830 --> 00:54:07,410 And that, that leaves, you could get a lot of different outcomes there. 899 00:54:07,410 --> 00:54:11,470 I'm just curious about how you keep this culture of continuous 900 00:54:11,510 --> 00:54:14,070 learning going and create. 901 00:54:14,520 --> 00:54:19,850 time for people to actually try new products because that's, I think, another 902 00:54:19,850 --> 00:54:21,570 thing a lot of firms struggle with, right? 903 00:54:21,570 --> 00:54:22,470 It's like, we have deadlines. 904 00:54:22,500 --> 00:54:26,380 We don't have time to figure out if this new tool is going to do something for us. 905 00:54:26,380 --> 00:54:26,870 And so 906 00:54:27,670 --> 00:54:28,720 can you talk about that side of 907 00:54:28,805 --> 00:54:29,085 Nirva Fereshetian: Yeah. 908 00:54:29,085 --> 00:54:34,215 I mean, time, time is essentially the root of the challenge. 909 00:54:34,215 --> 00:54:36,165 Actually, it's not the cost of the products. 910 00:54:36,175 --> 00:54:38,905 It's actually time, uh, to you. 911 00:54:39,240 --> 00:54:41,800 Um, implement it properly, test it properly. 912 00:54:41,800 --> 00:54:45,050 Some of the startups don't understand that things can't happen in 30 days. 913 00:54:45,660 --> 00:54:48,460 You know, so, oh, yeah, you're going to have to give, I'd rather 914 00:54:48,470 --> 00:54:51,160 pay, um, and have a paid trial. 915 00:54:51,350 --> 00:54:55,610 So we all can sanely think about it, you know, rather than 30 days 916 00:54:55,630 --> 00:54:59,280 and so and so had the deadline and all we good intentions. 917 00:54:59,280 --> 00:55:02,490 We want to try it and they'll have a lot of eager people who want to try it. 918 00:55:02,490 --> 00:55:07,290 But, um, you know, how the deadline driven are we and how last minute projects change 919 00:55:07,290 --> 00:55:09,260 and then people get pulled from those. 920 00:55:09,590 --> 00:55:10,680 So I think. 921 00:55:11,085 --> 00:55:12,905 Time is really a challenge. 922 00:55:12,925 --> 00:55:20,615 And, um, a lot of times it's the person's enthusiasm that has made a mark, Evan. 923 00:55:20,945 --> 00:55:25,315 And people have gone, if the product is good, have gone above and beyond, 924 00:55:25,875 --> 00:55:30,215 uh, to test it, even outside of our working hours to make it work. 925 00:55:30,515 --> 00:55:33,525 Um, so, but that, I'm not advocating that at all. 926 00:55:33,805 --> 00:55:40,690 But what I'm, what I have tried to do is present the successes through Through, 927 00:55:40,960 --> 00:55:43,480 um, others, not through our team members. 928 00:55:44,080 --> 00:55:50,140 So, uh, we want to, uh, showcase in our presentations, them, not us. 929 00:55:50,750 --> 00:55:55,610 Is, they trust each other more than they trust someone 930 00:55:55,930 --> 00:55:59,450 saying that, Hey, you know, we think this is better than that, or 931 00:55:59,590 --> 00:56:01,070 you need to use this tool and that. 932 00:56:01,080 --> 00:56:01,629 So, let's show them. 933 00:56:02,080 --> 00:56:03,300 It's all by example. 934 00:56:03,310 --> 00:56:08,590 If we haven't been able to successfully make a team use it, make a few people 935 00:56:08,600 --> 00:56:12,510 test it, and share the outcomes, then there's nothing to talk about, Evan. 936 00:56:13,380 --> 00:56:13,980 Absolutely 937 00:56:14,060 --> 00:56:15,985 Evan Troxel: like, That's great framing. 938 00:56:15,995 --> 00:56:18,825 And I think that's a great way to think about it because it may, and it makes so 939 00:56:18,825 --> 00:56:23,795 much sense because it actually makes, it puts the impetus on the information coming 940 00:56:23,795 --> 00:56:29,315 from them to you rather than the other way around, which like now you're in a mode 941 00:56:29,335 --> 00:56:32,155 of supporting for success. 942 00:56:32,205 --> 00:56:32,505 Right. 943 00:56:32,535 --> 00:56:35,265 But you're not going to go out and find the things and then 944 00:56:35,275 --> 00:56:36,245 force them to use 945 00:56:36,480 --> 00:56:40,890 Nirva Fereshetian: Right, and it's, it's, if the, we always want, we're always in 946 00:56:40,890 --> 00:56:45,030 search of success stories, whether it's computationally, we've helped someone, 947 00:56:45,330 --> 00:56:50,170 uh, automate something, or we've helped someone to use a different tool, um, 948 00:56:50,190 --> 00:56:55,400 to figure out something, or we asked a, a group of people, like I said, we 949 00:56:55,400 --> 00:57:01,425 do have, um, what I call our technology allies inside different practices. 950 00:57:01,625 --> 00:57:03,135 And we rely on them. 951 00:57:03,435 --> 00:57:07,765 Um, and some of them have gone above and beyond to test something to a way that 952 00:57:08,155 --> 00:57:13,345 sometimes we, we don't have a real project to test on, so we go back and use an old 953 00:57:13,395 --> 00:57:20,135 project, uh, that has that scenario and say, can we, can we, if we had this tool, 954 00:57:20,165 --> 00:57:21,815 then would it have made a difference? 955 00:57:22,570 --> 00:57:27,610 Um, but these are real, but these are real commitments of time and 956 00:57:27,630 --> 00:57:33,250 effort and enthusiasm, um, that not, it's not like everybody has it. 957 00:57:33,280 --> 00:57:38,170 So, you, you kind of have to pick and choose and, uh, accommodate 958 00:57:38,190 --> 00:57:41,500 people's schedule, which is kind of hard to explain to our startups. 959 00:57:42,610 --> 00:57:45,620 Like, they, once we start, they keep emailing me. 960 00:57:45,620 --> 00:57:46,110 So. 961 00:57:46,975 --> 00:57:47,785 What happens next? 962 00:57:47,835 --> 00:57:48,595 Are we doing it? 963 00:57:48,605 --> 00:57:50,345 So, are we going to buy it? 964 00:57:50,345 --> 00:57:54,385 And unfortunately, I understand their predicament because they have a 965 00:57:54,385 --> 00:57:58,175 certain amount of money and a certain amount of time to prove themselves. 966 00:57:58,495 --> 00:58:03,075 And I think that's the, that's the challenge we have together to minimize. 967 00:58:03,085 --> 00:58:05,795 So, understand each other to minimize that. 968 00:58:05,795 --> 00:58:09,915 So, it's a beneficiary, we're, we both are a beneficiary of the process. 969 00:58:10,615 --> 00:58:15,115 So, which is why I think that this ecosystem needs to collaborate, 970 00:58:15,155 --> 00:58:17,195 really collaborate with the big C. 971 00:58:17,555 --> 00:58:23,505 You know, so, sometimes, um, for example, I have found it refreshing that, um, some 972 00:58:23,505 --> 00:58:29,785 startups have set up calls where many of the people who have tried, like us, other 973 00:58:29,785 --> 00:58:31,775 firms, are sharing in the conversation. 974 00:58:32,795 --> 00:58:34,735 It's not just us and the startup. 975 00:58:35,460 --> 00:58:39,150 But we're getting the outcomes of others who have tested, 976 00:58:39,550 --> 00:58:41,080 because we cannot do this alone. 977 00:58:41,910 --> 00:58:46,500 And so you, lots of people have made lists of some kinds, and I've commented 978 00:58:46,540 --> 00:58:50,030 on the list, and like, don't put things in there that you've never, have 979 00:58:50,030 --> 00:58:52,490 never touched or know about, you know? 980 00:58:52,730 --> 00:58:57,800 And, and so, or make us contribute and say, we've tested this, and I don't mean 981 00:58:57,800 --> 00:59:04,125 in a, In a negative way necessarily, you know, but sharing of our experiences 982 00:59:04,145 --> 00:59:08,055 and sharing why it worked in some place and did not work in another or 983 00:59:08,075 --> 00:59:13,875 contributing on how they continue to develop the product is really important. 984 00:59:14,165 --> 00:59:20,035 So, one of the other factors is that there remains big name products that 985 00:59:20,065 --> 00:59:27,490 are, um, uh, like Rhino and Revit that are the dominant tools and everything 986 00:59:27,510 --> 00:59:29,000 else kind of has to talk to them. 987 00:59:29,730 --> 00:59:33,960 And if they don't talk to them in the beginning, it's just not going to work. 988 00:59:34,530 --> 00:59:34,870 So, 989 00:59:34,945 --> 00:59:37,885 Evan Troxel: seems like the strategy is, is it has to talk to them before 990 00:59:37,885 --> 00:59:38,875 it can replace 991 00:59:38,875 --> 00:59:39,475 them, right? 992 00:59:39,545 --> 00:59:43,505 Because, because of the, there's so much already invested by 993 00:59:43,505 --> 00:59:44,945 the firms into those platforms. 994 00:59:44,945 --> 00:59:49,095 It's going to be very tough to switch to something at, at some point anyway, right? 995 00:59:49,095 --> 00:59:51,265 So it has to work its way. 996 00:59:51,425 --> 00:59:52,275 The Trojan horse 997 00:59:52,285 --> 00:59:52,945 has to work its 998 00:59:52,945 --> 00:59:53,485 way into the 999 00:59:53,810 --> 00:59:56,270 Nirva Fereshetian: Yeah, and even if it's not replacing them, Evan, 1000 00:59:56,270 --> 00:59:57,470 it still has to work with them. 1001 00:59:58,255 --> 00:59:59,005 Evan Troxel: Absolutely. 1002 00:59:59,155 --> 00:59:59,535 Yeah. 1003 00:59:59,560 --> 01:00:04,815 Nirva Fereshetian: And, and there's a lack of understanding that and then A 1004 01:00:04,815 --> 01:00:09,575 lot of overlap, you know, so like I said, so if you're developing your startup 1005 01:00:09,575 --> 01:00:14,075 and there is a tool out there that is doing some part of your thing very well 1006 01:00:14,115 --> 01:00:15,745 that I don't see why you're building it. 1007 01:00:16,690 --> 01:00:17,010 Evan Troxel: Yeah, 1008 01:00:17,105 --> 01:00:18,535 Nirva Fereshetian: I don't see why you're building it. 1009 01:00:18,615 --> 01:00:18,915 Yep. 1010 01:00:19,730 --> 01:00:24,920 Evan Troxel: I want to talk more about your, this, the refreshing change in 1011 01:00:24,960 --> 01:00:29,100 practice of this, this outward sharing, because I don't, I think that's kind 1012 01:00:29,100 --> 01:00:33,580 of a, lots of firms have kept things to themselves and they're developing ideas 1013 01:00:33,580 --> 01:00:35,850 and they're, they want to, they think it's their IP and they want to keep it 1014 01:00:35,850 --> 01:00:39,270 to themselves and, and there is much more of a sharing culture developing there. 1015 01:00:39,280 --> 01:00:43,635 Before we go there though, I just wanted to ask, how do you, Spotlight 1016 01:00:43,755 --> 01:00:47,665 these success stories that you talked about with the people who are 1017 01:00:48,105 --> 01:00:52,445 doing interesting, useful, valuable things with technology in your firm. 1018 01:00:52,465 --> 01:00:54,435 Do you, do you have an intranet? 1019 01:00:54,445 --> 01:00:55,895 Do you post those on there? 1020 01:00:55,905 --> 01:00:57,875 Do you do it outside of the firm as well? 1021 01:00:57,915 --> 01:01:00,225 Like, how do you approach that and how do you 1022 01:01:00,225 --> 01:01:01,245 actually communicate those 1023 01:01:01,545 --> 01:01:06,475 Nirva Fereshetian: We, um, we internally have, uh, sessions every other week 1024 01:01:06,475 --> 01:01:10,575 or at least, um, at least two or three times a month that something is 1025 01:01:10,575 --> 01:01:13,335 profiled, something that has been done. 1026 01:01:13,585 --> 01:01:14,285 And, uh. 1027 01:01:15,645 --> 01:01:19,665 Mostly, we try to encourage others to present or co present with them. 1028 01:01:20,025 --> 01:01:24,795 Um, we developed recently, um, a platform called Employee Experience 1029 01:01:24,805 --> 01:01:29,255 Platform, uh, which is purely based on, um, communication. 1030 01:01:29,255 --> 01:01:30,575 It's a communication site. 1031 01:01:30,845 --> 01:01:33,120 And, uh, Not an intranet. 1032 01:01:33,140 --> 01:01:38,070 I don't want to use that word, uh, is that as that is like a documentation and 1033 01:01:38,070 --> 01:01:43,620 a depository of things and this one, so we just Deployed that about a month ago, 1034 01:01:43,660 --> 01:01:49,820 month and a half ago, and we're trying to use that also as a way and means of 1035 01:01:49,860 --> 01:01:52,860 internally sharing that information. 1036 01:01:52,880 --> 01:01:56,320 Part of the stuff is like sometimes people complain Oh, I didn't know we 1037 01:01:56,320 --> 01:02:00,490 knew that or I didn't know we were using that so that's, that's a Equally. 1038 01:02:00,490 --> 01:02:04,180 So I have tried very hard to pr that externally. 1039 01:02:04,180 --> 01:02:09,520 Like I said, I've learned a lot and still need to learn a lot to move some 1040 01:02:09,520 --> 01:02:11,980 of that engagement outside of our firm. 1041 01:02:12,280 --> 01:02:13,570 Um, even 1042 01:02:13,930 --> 01:02:17,890 I've organized things with our clients, with our internally, uh, with our 1043 01:02:17,890 --> 01:02:21,640 clients and collaborators to have sessions inside to talk about things. 1044 01:02:21,790 --> 01:02:25,810 How could we have done something better or how could have we collaborated? 1045 01:02:26,080 --> 01:02:26,890 It starts small. 1046 01:02:27,810 --> 01:02:31,270 I think the personal relationships are key. 1047 01:02:31,420 --> 01:02:35,630 We can put things out there, but it's very hard, Evan, to make them read, 1048 01:02:35,980 --> 01:02:40,100 to make them see, and even in the communication site that we're trying 1049 01:02:40,100 --> 01:02:45,280 to push information to, my take has been like, say short things, put an 1050 01:02:45,290 --> 01:02:49,191 image so they can, yeah, so they can see like something changed, you know, 1051 01:02:49,191 --> 01:02:51,390 maybe I should, yes, the attention is 1052 01:02:51,830 --> 01:02:57,230 and truthfully, I'm, always worried at the amount of information we're pushing or 1053 01:02:57,250 --> 01:03:03,310 amount of tools and training we're pushing and I always say that Well, they roll they 1054 01:03:03,310 --> 01:03:10,030 need to have time to spend to live to live and learn their professional expertise 1055 01:03:10,060 --> 01:03:16,290 Evan, you know, they're interior designers and architects and urban designers who 1056 01:03:16,290 --> 01:03:21,740 need to learn and learn Uh, educate, you know, keep, keep, uh, their professional 1057 01:03:21,740 --> 01:03:23,720 growth, you know, for their topics. 1058 01:03:23,960 --> 01:03:29,710 On top of it, there is an avalanche of tools and technology and things like that. 1059 01:03:29,730 --> 01:03:34,510 And in some instances, some people can't keep up with it. 1060 01:03:35,230 --> 01:03:35,520 Evan Troxel: Yeah. 1061 01:03:36,130 --> 01:03:41,120 Yeah, the outward communication also I'm sure helps with recruitment and just, just 1062 01:03:41,130 --> 01:03:45,840 getting eyeballs on the types of work, the kind of things that you're doing, 1063 01:03:45,840 --> 01:03:50,040 the way that you're going about doing it to attract talent to the firm, which 1064 01:03:50,050 --> 01:03:51,820 otherwise is kind of a black box, right? 1065 01:03:51,820 --> 01:03:55,810 It's like they see a job posting on LinkedIn or wherever, and they, they 1066 01:03:55,810 --> 01:03:58,900 get to read what their roles and responsibilities would be because they're 1067 01:03:58,910 --> 01:04:02,650 just like everybody else's roles and responsibilities for that job profile. 1068 01:04:02,650 --> 01:04:06,465 But, but then there's like, To me, it seems like there's this opportunity for 1069 01:04:06,465 --> 01:04:12,015 these channels to be presented out there for people to tune into and, and get more 1070 01:04:12,035 --> 01:04:18,055 insight into the practice of architecture at CBT, as an example, and the kinds of 1071 01:04:18,904 --> 01:04:24,135 user profiles and wins and success stories that you're talking about, that to me 1072 01:04:24,145 --> 01:04:30,585 is a great way to get the word out about the culture at CBT and the, and so like 1073 01:04:30,585 --> 01:04:34,310 the audience there is, you know, people who are interested in that content, but 1074 01:04:34,320 --> 01:04:36,220 also people who are job hunting, right? 1075 01:04:36,220 --> 01:04:41,340 And looking for a fit for them and their, the kind of culture they want to work for. 1076 01:04:41,850 --> 01:04:42,800 So I could see that being 1077 01:04:42,890 --> 01:04:46,120 Nirva Fereshetian: Yeah, I think that social media in general, specifically 1078 01:04:46,120 --> 01:04:53,935 Instagram type things, are mostly translate, you know, um, Mostly they 1079 01:04:53,935 --> 01:04:59,455 are presenting our culture, mostly it's for recruitment, mostly it's to have 1080 01:04:59,455 --> 01:05:01,565 an idea of what kind of a firm are we. 1081 01:05:01,875 --> 01:05:02,365 Um, 1082 01:05:02,785 --> 01:05:08,705 really the, uh, I think it's rare that people have found us and even given us 1083 01:05:08,705 --> 01:05:14,755 a project because they've seen us, uh, um, on an Instagram feed or something. 1084 01:05:14,785 --> 01:05:16,815 It's, it helps. 1085 01:05:17,400 --> 01:05:21,020 After they know about us, or after they talk to us to check out all of 1086 01:05:21,029 --> 01:05:26,090 those things, uh, to figure out what kind of a firm are we and what are we 1087 01:05:26,090 --> 01:05:30,250 posting and what are we talking about and what our thought leadership is. 1088 01:05:30,610 --> 01:05:37,040 So, I have, I think that part of it is that, uh, learning internal PR is 1 1089 01:05:37,050 --> 01:05:43,270 thing also learning how to do external PR and, but also making that as, um. 1090 01:05:44,630 --> 01:05:51,320 Not just about technology, not, it can't be about technology, it has to be about 1091 01:05:51,320 --> 01:05:57,580 the business and our technology things should be incorporated in the project 1092 01:05:57,580 --> 01:06:02,100 examples or what did it do for the project or what did it do for the team building or 1093 01:06:02,460 --> 01:06:06,870 because the story is not about the tool, it's the story is about the outcomes. 1094 01:06:07,720 --> 01:06:13,220 And technology is just a facilitator to make some outcome better. 1095 01:06:13,625 --> 01:06:17,435 or create an outcome that we couldn't have created without it. 1096 01:06:17,755 --> 01:06:20,485 But it's, the story is about the end result. 1097 01:06:20,605 --> 01:06:22,455 It's not about technology. 1098 01:06:23,420 --> 01:06:23,640 Evan Troxel: Yeah. 1099 01:06:23,640 --> 01:06:24,290 It's why, why 1100 01:06:24,290 --> 01:06:25,340 do we do what we do, 1101 01:06:25,360 --> 01:06:25,630 right? 1102 01:06:25,640 --> 01:06:30,610 If you're, if you're into architecture, if you've chosen this as your career path, it 1103 01:06:30,610 --> 01:06:34,760 should be to, change the built environment to make a better built environment 1104 01:06:34,779 --> 01:06:36,710 to affect, like I did schools, right? 1105 01:06:36,710 --> 01:06:39,410 It's, it's like to create the best learning environments possible for, 1106 01:06:39,510 --> 01:06:40,150 for children, 1107 01:06:40,220 --> 01:06:40,520 right? 1108 01:06:41,029 --> 01:06:45,610 And tools that help us get there are, are exactly that. 1109 01:06:45,620 --> 01:06:50,180 They're leveraged to get there faster, better, cheaper. 1110 01:06:51,425 --> 01:06:52,275 more beautiful. 1111 01:06:52,285 --> 01:06:55,225 Like there's so many different ways that we could go about doing that. 1112 01:06:55,225 --> 01:06:58,205 But, but that those aren't why we do what we do, right? 1113 01:06:58,325 --> 01:07:01,015 Those are how we do what we do and what we use. 1114 01:07:01,045 --> 01:07:04,255 But the clients often even don't care how you get there. 1115 01:07:04,305 --> 01:07:05,705 It's like, just create the outcome. 1116 01:07:05,715 --> 01:07:07,355 That's the value in it for them. 1117 01:07:07,355 --> 01:07:08,955 And that's what matters for our 1118 01:07:08,955 --> 01:07:10,195 businesses to survive. 1119 01:07:10,385 --> 01:07:12,404 Nirva Fereshetian: And absolutely don't care about the tool. 1120 01:07:12,415 --> 01:07:13,345 Why should they care? 1121 01:07:13,365 --> 01:07:15,185 All they should care is about the outcome. 1122 01:07:15,195 --> 01:07:19,355 And even internally, you know, at the end of the day, when there is this 1123 01:07:19,585 --> 01:07:24,635 discussion about this tool or the other, I always say like, stop and let's go 1124 01:07:24,635 --> 01:07:27,365 back and ask why are we doing this again? 1125 01:07:28,425 --> 01:07:29,715 Why are we doing this? 1126 01:07:29,745 --> 01:07:33,245 Is it because we're going to change the outcome? 1127 01:07:33,485 --> 01:07:39,685 So the basic example is, you know, Enscape has taken off like fire and, um, as in 1128 01:07:39,685 --> 01:07:44,635 many firms and when other things come into play, um, there's always this workflow 1129 01:07:44,645 --> 01:07:48,725 issue, you know, like, um, somebody can't pick up somebody else's work if you do 1130 01:07:48,725 --> 01:07:50,565 it in a lot of different formats, right? 1131 01:07:50,805 --> 01:07:52,785 Which, which is an efficiency issue. 1132 01:07:53,075 --> 01:07:57,190 But, so when, when, Another product comes into play, then we always 1133 01:07:57,230 --> 01:08:01,270 ask that, yeah, you can use that product, but is it doing something 1134 01:08:01,279 --> 01:08:03,040 that this other product is not doing? 1135 01:08:03,220 --> 01:08:07,250 And you, if it's an outcome based, and that you want to put motion that 1136 01:08:07,250 --> 01:08:12,240 the other one isn't doing well, or you want to put some, um, you know, um, uh, 1137 01:08:12,250 --> 01:08:16,979 different, um, analysis that the other, then it is rightfully so the tool to use. 1138 01:08:17,670 --> 01:08:21,979 But the client doesn't care whether we use A or B, all they care is they 1139 01:08:21,979 --> 01:08:23,290 ask for something and they got it. 1140 01:08:25,090 --> 01:08:29,180 Evan Troxel: It's always interesting to me when a client does kind of prescriptively 1141 01:08:29,270 --> 01:08:33,660 say we want this to be used on this project and you're like, okay, now, now, 1142 01:08:33,660 --> 01:08:34,410 we have to talk about 1143 01:08:34,569 --> 01:08:35,520 Nirva Fereshetian: Yes, yes. 1144 01:08:36,080 --> 01:08:39,260 Well, that was a long time ago, decades ago when people wrote 1145 01:08:39,290 --> 01:08:44,390 in the, in the project RFPs, uh, BIM and Revit, and really didn't 1146 01:08:44,390 --> 01:08:45,609 know what they were asking for. 1147 01:08:45,630 --> 01:08:46,050 Evan Troxel: They didn't 1148 01:08:46,050 --> 01:08:46,390 have any 1149 01:08:46,640 --> 01:08:47,670 Nirva Fereshetian: they had no clue. 1150 01:08:47,870 --> 01:08:48,080 Yeah, 1151 01:08:48,330 --> 01:08:49,170 they had no clue. 1152 01:08:49,390 --> 01:08:49,950 And I'm not, 1153 01:08:49,970 --> 01:08:50,410 Evan Troxel: hadn't trained 1154 01:08:50,410 --> 01:08:51,470 anybody how to use 1155 01:08:51,470 --> 01:08:51,770 it. 1156 01:08:51,779 --> 01:08:54,790 And yeah, any of those things that actually come along with that request. 1157 01:08:55,420 --> 01:09:00,040 Let's get back to the, that collaboration or, you know, the, the sharing that's 1158 01:09:00,040 --> 01:09:03,710 going on within the industry that you were talking about seeing on some of 1159 01:09:03,710 --> 01:09:08,050 these panels that are put together or these, these zoom meetings or whatever 1160 01:09:08,050 --> 01:09:12,109 they are, but also at the large firm round table that, that you're a 1161 01:09:12,109 --> 01:09:13,569 part of that I used to be a part of. 1162 01:09:14,160 --> 01:09:17,660 That was definitely a shift that's been happening is there's been a lot 1163 01:09:17,660 --> 01:09:22,210 more sharing, and there's a lot more acknowledgement that these tools and these 1164 01:09:22,210 --> 01:09:26,410 workflows are not IP for a firm, right? 1165 01:09:26,420 --> 01:09:29,080 They're, it's like, are you having this problem? 1166 01:09:29,340 --> 01:09:30,080 Raise your hand. 1167 01:09:30,160 --> 01:09:31,500 Everybody raises their hand. 1168 01:09:31,520 --> 01:09:33,479 Okay, it's not just us, right? 1169 01:09:33,479 --> 01:09:34,920 Let's talk about this, right? 1170 01:09:34,920 --> 01:09:38,410 It makes it easier to talk about things when, when we acknowledge 1171 01:09:38,410 --> 01:09:39,970 like, oh, I thought it was just us. 1172 01:09:39,970 --> 01:09:41,210 No, it's actually everybody. 1173 01:09:41,950 --> 01:09:44,680 talk about the culture of sharing the evolution that you've seen 1174 01:09:44,680 --> 01:09:48,940 there and, and why that's important for the industry to do more of. 1175 01:09:48,940 --> 01:09:49,690 Because it's, 1176 01:09:49,690 --> 01:09:50,920 it's leading to something. 1177 01:09:50,940 --> 01:09:53,850 Nirva Fereshetian: Yeah, so at least from that end, you know, in 1178 01:09:53,850 --> 01:09:58,360 terms of the A, you know, the large form round taper is mostly A's. 1179 01:09:58,705 --> 01:10:02,745 You know, although some of the firms are, have, um, um, easy, 1180 01:10:02,795 --> 01:10:09,315 uh, with them, um, there is a considerable effort to, um, share. 1181 01:10:09,315 --> 01:10:13,665 And as you know, the large firm roundtable from the large firm 1182 01:10:13,665 --> 01:10:18,405 roundtable, um, a group has developed called innovation design consortium, 1183 01:10:18,755 --> 01:10:24,165 where it's officially sharing information and being a member of that. 1184 01:10:24,465 --> 01:10:31,175 Um, there's, um, It's, it's really, um, not very hard to think that many of us 1185 01:10:31,175 --> 01:10:36,315 are doing the same things, um, and that could benefit of making, sharing those, 1186 01:10:36,605 --> 01:10:41,115 uh, resources or doing it once and sharing it all and not seeing it as a 1187 01:10:41,115 --> 01:10:43,355 competitive advantage because they're not. 1188 01:10:43,875 --> 01:10:48,835 Um, so, I feel, so that has started about a year ago and, um, 1189 01:10:48,845 --> 01:10:50,475 certainly they're making progress. 1190 01:10:50,505 --> 01:10:55,455 They have, uh, um, uh, they're trying, they have, it's outside 1191 01:10:55,455 --> 01:10:56,835 of the large firm roundtable. 1192 01:10:56,865 --> 01:11:01,525 It started from there, but, uh, it's an independent organization now. 1193 01:11:01,825 --> 01:11:07,075 And, um, hopefully it gives a voice also to develop things, um, together. 1194 01:11:07,325 --> 01:11:14,845 Or have a voice to talk to, um, um, with the larger numbers, you know, because, 1195 01:11:14,885 --> 01:11:19,695 uh, not every firm is two, three thousand people and has the leverage, um, to, 1196 01:11:19,925 --> 01:11:22,815 um, make a change or request a change. 1197 01:11:22,815 --> 01:11:27,115 So, um, but there is certainly common things, uh, computational 1198 01:11:27,135 --> 01:11:31,055 things or, uh, things that every firm is doing on their own. 1199 01:11:31,055 --> 01:11:35,205 And we hope that we share that and do it once and share it. 1200 01:11:35,455 --> 01:11:37,865 And, uh, so that's, that's moving along. 1201 01:11:37,925 --> 01:11:43,215 But I feel like, um, The first success of the ecosystem, something has to be 1202 01:11:43,215 --> 01:11:49,985 developed that kind of goes across, uh, the entire chain, um, all the way to, um, 1203 01:11:50,315 --> 01:11:52,285 the people who are operating the building. 1204 01:11:52,595 --> 01:11:59,505 Um, like I said, you know, before, um, the, it is born in our offices, the 1205 01:11:59,505 --> 01:12:06,835 data sets as designers, but how we move that downstream and make it at least 1206 01:12:06,845 --> 01:12:14,770 partially, um, Beneficial down and without recreating it at every phase and rehiring 1207 01:12:14,770 --> 01:12:17,990 people to It's a very big disconnect. 1208 01:12:18,260 --> 01:12:26,370 So The same similar way where we all are trying on the A side Share 1209 01:12:26,430 --> 01:12:30,395 and give a boost to our ecosystem. 1210 01:12:30,555 --> 01:12:34,365 And in terms of just time, we share a lot of information about who has 1211 01:12:34,375 --> 01:12:38,505 tested what, and that information is valuable when you have a thousand 1212 01:12:38,505 --> 01:12:39,825 things to look at, you know? 1213 01:12:39,835 --> 01:12:41,875 So, and, and, um, 1214 01:12:42,385 --> 01:12:51,365 if that framework can move downstream, um, and also on every Every process 1215 01:12:51,365 --> 01:12:55,015 need to be re examined, you know, contractual things, uh, relationships 1216 01:12:55,055 --> 01:12:57,005 as we move from one phase to the other. 1217 01:12:57,355 --> 01:13:03,495 Um, if that becomes more and more thought about and those are the 1218 01:13:03,835 --> 01:13:09,755 things that give us a heads up how to innovate, how to change us completely. 1219 01:13:10,395 --> 01:13:17,585 And, you know, I think that, um, in this, um, I'm not sure we can evolve in AI. 1220 01:13:17,615 --> 01:13:19,885 It's a drastic, drastic change. 1221 01:13:20,165 --> 01:13:25,695 Um, the fact that we use small tools, uh, um, you know, render, 1222 01:13:25,925 --> 01:13:31,195 rendering tools, or code tools, or anything, um, is not necessarily, 1223 01:13:31,195 --> 01:13:32,949 in my opinion, make any difference. 1224 01:13:33,600 --> 01:13:38,250 A big use of the AI ecosystem yet, you know, once the data sets are 1225 01:13:38,270 --> 01:13:43,880 coming in, once we're making real conclusions, once we have shared, um, 1226 01:13:43,890 --> 01:13:50,230 data sets where we're making some, um, Deductions from our previous 1227 01:13:50,240 --> 01:13:56,004 projects, collectively experiences, so that we can project, um, you know, 1228 01:13:56,625 --> 01:14:00,925 Potential predictions for how should we move ahead with the next project? 1229 01:14:00,934 --> 01:14:04,135 And what is the learning that's going to happen across that platform? 1230 01:14:04,335 --> 01:14:08,375 Those are AI things, uh, which we are still pretty far from. 1231 01:14:09,430 --> 01:14:09,670 Evan Troxel: Yeah. 1232 01:14:09,675 --> 01:14:12,700 Where's the standardized, structured 1233 01:14:12,700 --> 01:14:13,840 data between all 1234 01:14:13,965 --> 01:14:14,495 Nirva Fereshetian: That's right. 1235 01:14:14,860 --> 01:14:15,730 Evan Troxel: How, how's that gonna 1236 01:14:15,925 --> 01:14:16,495 Nirva Fereshetian: That's right. 1237 01:14:16,675 --> 01:14:19,235 We can't even structure our own data in one firm. 1238 01:14:19,475 --> 01:14:24,355 But I think those are the things that would let us innovate and that's actually 1239 01:14:24,434 --> 01:14:29,305 the term that we can legitimately use if we do collaborate on that level 1240 01:14:29,575 --> 01:14:31,245 and, and change the way we think. 1241 01:14:32,275 --> 01:14:37,425 We still are, we still are in the old mindsets of how things should be. 1242 01:14:38,465 --> 01:14:40,525 Evan Troxel: Yeah, yeah, interesting. 1243 01:14:40,555 --> 01:14:45,545 I'm curious about this idea of the tools proliferating their value 1244 01:14:45,565 --> 01:14:50,535 beyond the role, our current role as architects, and what, what the incentive 1245 01:14:50,535 --> 01:14:55,615 is there, because the business model hasn't changed or is it changing? 1246 01:14:55,735 --> 01:14:58,425 Uh, the contracts haven't changed or are they changing? 1247 01:14:58,434 --> 01:15:01,125 I'm just curious what the incentive is. 1248 01:15:01,145 --> 01:15:03,955 I mean, there's, I think everybody agrees that that would 1249 01:15:03,965 --> 01:15:05,434 be great if we didn't have to 1250 01:15:05,785 --> 01:15:06,585 redo the 1251 01:15:06,585 --> 01:15:10,415 work at all of these different steps and pay somebody to implement that. 1252 01:15:10,434 --> 01:15:16,175 And it seems odd that that happens, but it does happen because there's no incentive 1253 01:15:16,184 --> 01:15:18,445 for the, like, like at that point, it 1254 01:15:18,445 --> 01:15:19,645 literally is a handoff. 1255 01:15:19,665 --> 01:15:19,995 Right. 1256 01:15:20,125 --> 01:15:20,785 And so. 1257 01:15:21,790 --> 01:15:26,040 So what is the incentive to drive that from the architect's 1258 01:15:26,080 --> 01:15:27,710 and engineer's point of view? 1259 01:15:28,775 --> 01:15:29,684 Nirva Fereshetian: It is changing. 1260 01:15:30,045 --> 01:15:31,585 but not at a speed way. 1261 01:15:31,585 --> 01:15:37,425 So I think before where, um, years ago where we never gave our Revit model to 1262 01:15:37,425 --> 01:15:40,915 anybody, um, that has drastically changed. 1263 01:15:41,065 --> 01:15:44,955 So, yeah, I mean, even if we gave it, we gave it with all kinds of 1264 01:15:44,955 --> 01:15:48,125 written statements not to use it, not to measure it from, you know, so, 1265 01:15:48,475 --> 01:15:55,684 but now, um, a lot of our, uh, contractors and CMs are saying, 1266 01:15:55,684 --> 01:15:56,955 well, we want to use the model. 1267 01:15:57,690 --> 01:16:01,660 So, and if that means that we need to be a little bit better at 1268 01:16:01,660 --> 01:16:04,570 building it, or understand how, 1269 01:16:04,770 --> 01:16:05,100 Evan Troxel: Can you 1270 01:16:05,120 --> 01:16:05,690 imagine? 1271 01:16:05,870 --> 01:16:10,040 I can't even imagine being a, a Suffolk construction getting Revit 1272 01:16:10,040 --> 01:16:13,130 models from all these different teams and all these different firms 1273 01:16:13,130 --> 01:16:15,100 and the different Wild West nature 1274 01:16:15,100 --> 01:16:19,550 of every single project out there and having to pick that up and deal with it. 1275 01:16:19,610 --> 01:16:20,540 It's just gotta be 1276 01:16:20,950 --> 01:16:21,320 crazy 1277 01:16:21,600 --> 01:16:25,290 Nirva Fereshetian: It is crazy, but the technology's out there to kind of, 1278 01:16:25,300 --> 01:16:30,540 before when the, you know, years ago when there was this IPD concept, the 1279 01:16:30,730 --> 01:16:33,400 technology wasn't there to support it. 1280 01:16:33,410 --> 01:16:36,770 Like, I know we experimented it with a little couple of different things. 1281 01:16:37,020 --> 01:16:41,110 Uh, projects where they had to come to our office and, or we had to come to 1282 01:16:41,110 --> 01:16:45,960 their, go to their office because the structure was not there, uh, we couldn't 1283 01:16:45,960 --> 01:16:51,130 share a Revit file, so we had to use Revit server, whatever, but now I think there 1284 01:16:51,140 --> 01:16:58,090 has been the cloud and, uh, posting about all of that content there, uh, makes it 1285 01:16:58,090 --> 01:17:04,925 really, gives hope that these things are, can be, um, shared and work together. 1286 01:17:05,385 --> 01:17:11,135 And if you think about it, I, uh, the, you know, the, if you think that we are 1287 01:17:11,135 --> 01:17:16,035 one company and do downstream everything, then we would behave very differently. 1288 01:17:16,880 --> 01:17:17,210 Right? 1289 01:17:17,530 --> 01:17:22,650 So if we are the designers and have the engineers and it's just there is a big 1290 01:17:22,660 --> 01:17:30,900 company above it and all of us are working for the same concept to make it if but 1291 01:17:30,910 --> 01:17:39,620 the fact of it is is just so fractured that no one can see that this is it's 1292 01:17:39,620 --> 01:17:42,380 a it's possible if we worked for one 1293 01:17:42,770 --> 01:17:46,680 Owner, which is, I guess, what the IPD thing was to make an, to make an 1294 01:17:46,690 --> 01:17:53,400 organization that is, um, one ownership and make sure that everybody, um, 1295 01:17:53,420 --> 01:17:54,340 Evan Troxel: In this together, 1296 01:17:54,400 --> 01:17:55,170 Nirva Fereshetian: is together. 1297 01:17:55,230 --> 01:17:59,640 Yeah, so not until we feel that, I think it's hard to change anything 1298 01:17:59,960 --> 01:18:01,320 because we don't feel that, 1299 01:18:02,510 --> 01:18:05,050 Evan Troxel: Are there tools out there that are making that kind 1300 01:18:05,050 --> 01:18:08,470 of restructuring of data, maybe even after the fact, easier? 1301 01:18:09,290 --> 01:18:10,361 Is that even a 1302 01:18:10,361 --> 01:18:12,046 possibility, do you 1303 01:18:12,046 --> 01:18:12,608 think? 1304 01:18:12,608 --> 01:18:13,169 Hmm. 1305 01:18:13,500 --> 01:18:16,670 Nirva Fereshetian: I feel in one sense, some of these platform based 1306 01:18:16,670 --> 01:18:24,205 things, um, are making, um, like Speckle and others are, have, I 1307 01:18:24,205 --> 01:18:25,575 think they have a great future. 1308 01:18:26,365 --> 01:18:33,055 The problem I see is that we are so much chained in products, um, and before 1309 01:18:33,425 --> 01:18:39,645 if I feel that it's, before I felt changing of tools is, uh, uh, an issue. 1310 01:18:39,675 --> 01:18:41,675 Now I feel the platforms are the issue. 1311 01:18:42,450 --> 01:18:42,850 Evan Troxel: Mm 1312 01:18:43,100 --> 01:18:43,450 hmm. 1313 01:18:43,665 --> 01:18:46,305 Nirva Fereshetian: changing of tools is relatively easier. 1314 01:18:46,860 --> 01:18:51,590 But because we post and collaborate in certain platforms, um, 1315 01:18:51,750 --> 01:18:53,950 that is not going to go away. 1316 01:18:54,190 --> 01:18:54,720 So, 1317 01:18:55,080 --> 01:18:59,010 um, it is hard to see, to be optimistic about that. 1318 01:18:59,040 --> 01:19:00,410 I'm trying, but it's hard 1319 01:19:00,415 --> 01:19:03,335 Evan Troxel: that, that is a very difficult reality to deal with, right? 1320 01:19:03,335 --> 01:19:08,415 Because all of the, the consultants on the team have to also 1321 01:19:08,415 --> 01:19:09,315 be using 1322 01:19:09,430 --> 01:19:09,840 Nirva Fereshetian: The same thing. 1323 01:19:09,875 --> 01:19:11,645 Evan Troxel: the same version of 1324 01:19:11,655 --> 01:19:12,365 the software, 1325 01:19:12,495 --> 01:19:12,785 right? 1326 01:19:12,825 --> 01:19:16,934 Not, not just the same platform, the same version, exactly, right? 1327 01:19:17,005 --> 01:19:17,765 Or else you're going to run 1328 01:19:17,765 --> 01:19:19,235 into potential problems. 1329 01:19:19,684 --> 01:19:20,095 Yeah, 1330 01:19:20,530 --> 01:19:21,220 Nirva Fereshetian: Definitely. 1331 01:19:21,240 --> 01:19:24,339 Um, 1332 01:19:24,445 --> 01:19:26,475 Evan Troxel: Is there anything else that you wanted to talk 1333 01:19:26,485 --> 01:19:28,215 about before we call it? 1334 01:19:29,920 --> 01:19:32,620 Nirva Fereshetian: uh, no, I, I really enjoyed the conversation. 1335 01:19:32,670 --> 01:19:34,059 Uh, it's been great, Evan. 1336 01:19:34,090 --> 01:19:43,059 And, uh, I hope, um, the, I, I hope that these conversations and multi, uh, layer 1337 01:19:43,080 --> 01:19:49,770 and multi people conversation actually make us, uh, become more aware of how we 1338 01:19:49,770 --> 01:19:52,180 can contribute to this, uh, ecosystem. 1339 01:19:52,200 --> 01:19:57,925 I think, um, We do a lot of talking, we do a lot of, uh, planning, but, um, 1340 01:19:57,955 --> 01:20:03,315 IC not very much action, and all of us complain, uh, all of us are, uh, 1341 01:20:03,365 --> 01:20:11,075 not happy, um, but I hope that, um, we actually do something about it. 1342 01:20:11,795 --> 01:20:13,605 Evan Troxel: Yeah, the complaint department, right? 1343 01:20:13,625 --> 01:20:17,005 And then, and then the, the accountability part of, of like 1344 01:20:17,105 --> 01:20:18,955 the next part after the complaint. 1345 01:20:18,965 --> 01:20:19,805 It's like everybody kind of 1346 01:20:19,845 --> 01:20:20,705 looks over their shoulder. 1347 01:20:20,715 --> 01:20:20,855 I 1348 01:20:21,035 --> 01:20:22,625 Nirva Fereshetian: Blaming somebody else, yes. 1349 01:20:23,855 --> 01:20:26,445 Evan Troxel: To actually do the thing to fix this problem 1350 01:20:26,895 --> 01:20:28,265 is not the complaint part. 1351 01:20:28,275 --> 01:20:29,695 That's the easy part, right? 1352 01:20:29,695 --> 01:20:30,385 The hard 1353 01:20:30,385 --> 01:20:31,485 part is the actual 1354 01:20:31,559 --> 01:20:32,160 Nirva Fereshetian: That's right. 1355 01:20:32,330 --> 01:20:36,540 I mean, I hope, I mean, I see some hope on some of those things and 1356 01:20:36,550 --> 01:20:41,330 some conversations of real change and some conversations of sharing, but, 1357 01:20:41,620 --> 01:20:44,190 um, there's definitely less action. 1358 01:20:44,230 --> 01:20:49,040 I mean, uh, uh, podcasts like this are terrific, Evan, in terms of, um, 1359 01:20:49,100 --> 01:20:55,000 bringing us, um, bringing our voices from different perspectives, from 1360 01:20:55,000 --> 01:21:03,455 different roles from together to, um, to validate all of our issues. 1361 01:21:03,485 --> 01:21:09,245 But, um, what, what is disappointing is there's less, little action 1362 01:21:09,265 --> 01:21:12,175 and more, um, more conversation. 1363 01:21:12,175 --> 01:21:18,545 So, I, I do see some data, um, efforts, uh, the common data platforms and 1364 01:21:18,555 --> 01:21:23,325 other things that, um, several, um, companies or other efforts that are 1365 01:21:23,325 --> 01:21:27,465 coming together between the, Different European architects and others that 1366 01:21:27,465 --> 01:21:32,915 are trying to work together for that, but, um, it's just too slow, Evan. 1367 01:21:33,365 --> 01:21:33,615 Evan Troxel: Yeah. 1368 01:21:33,835 --> 01:21:34,195 Yeah. 1369 01:21:34,895 --> 01:21:35,765 Well, this has been a 1370 01:21:35,765 --> 01:21:36,755 fantastic conversation, 1371 01:21:37,055 --> 01:21:37,715 Nirva Fereshetian: Thank you 1372 01:21:37,775 --> 01:21:38,015 Evan Troxel: much. 1373 01:21:38,015 --> 01:21:41,385 And I think just shifting the perspective more downstream, like you were 1374 01:21:41,385 --> 01:21:45,910 mentioning there, if we think about our work product as Think about the 1375 01:21:45,910 --> 01:21:47,050 next people who are going to get it. 1376 01:21:47,070 --> 01:21:50,800 That, that alone is, is something worth contemplating and how it might start to 1377 01:21:50,830 --> 01:21:54,090 affect what you do today to not incur 1378 01:21:54,090 --> 01:21:55,000 technical debt, 1379 01:21:55,050 --> 01:21:55,290 right? 1380 01:21:55,290 --> 01:21:59,740 Because That's if you do something now that, that just, um, benefits 1381 01:21:59,750 --> 01:22:04,470 you in the short term to meet this deadline, but it breaks 10 things 1382 01:22:04,470 --> 01:22:06,630 downstream, it's not worth it. 1383 01:22:06,660 --> 01:22:08,270 And so to be thinking about 1384 01:22:08,690 --> 01:22:09,640 and have empathy for 1385 01:22:09,640 --> 01:22:11,720 those future users of 1386 01:22:11,730 --> 01:22:12,710 that data is, 1387 01:22:12,905 --> 01:22:15,735 Nirva Fereshetian: So, the small example is within the office, but 1388 01:22:15,735 --> 01:22:19,835 the bigger example is, you know, from design phases to construction. 1389 01:22:19,835 --> 01:22:21,525 That's the, that's the small example. 1390 01:22:21,605 --> 01:22:24,675 Think about the other teams, but also think about the larger. 1391 01:22:25,540 --> 01:22:30,180 workflow of moving it from one, um, office to the other in terms 1392 01:22:30,180 --> 01:22:33,950 of making the building built at the end and, and operated. 1393 01:22:33,950 --> 01:22:34,330 I mean, 1394 01:22:34,690 --> 01:22:39,210 Digital Twins and all of this, all these conversation, um, if everything's 1395 01:22:39,210 --> 01:22:44,880 going to be starting all over again, and that's really a huge problem to solve. 1396 01:22:45,430 --> 01:22:46,000 Evan Troxel: Waste in the 1397 01:22:46,070 --> 01:22:46,760 Nirva Fereshetian: That's right. 1398 01:22:47,370 --> 01:22:47,910 Okay. 1399 01:22:48,600 --> 01:22:48,860 Evan Troxel: Thanks, 1400 01:22:49,100 --> 01:22:50,030 Nirva Fereshetian: Thank you, Evan.