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,277 --> 00:00:47,957 Welcome to the TRXL podcast. 14 00:00:48,047 --> 00:00:49,067 I'm Evan Troxel. 15 00:00:49,397 --> 00:00:52,607 In this episode, I welcome Parley Burnett and Chris Shafer. 16 00:00:52,967 --> 00:00:55,637 Parley is the CEO of Iconic BIM. 17 00:00:55,997 --> 00:00:56,717 Previously. 18 00:00:56,747 --> 00:01:00,927 He has led product and customer success efforts at UNIFI 19 00:01:01,167 --> 00:01:02,717 Labs.Worked as a BIM manager. 20 00:01:03,047 --> 00:01:07,367 Led large content development efforts for manufacturers and served on several 21 00:01:07,367 --> 00:01:08,897 different BIM standards committees. 22 00:01:09,184 --> 00:01:13,054 Chris has nearly 20 years of experience as an architect and leading large 23 00:01:13,054 --> 00:01:17,217 firms in their adoption of design technologies and Revvit he recently 24 00:01:17,217 --> 00:01:20,337 joined Parley .To help digital design and BIM leaders better support 25 00:01:20,337 --> 00:01:22,407 their staff in their use of Revvit. 26 00:01:22,857 --> 00:01:27,237 Previously, Chris was a senior project architect and the digital delivery leader 27 00:01:27,237 --> 00:01:33,267 for HDR Architecture, where he led global teams in north America, Australia, and 28 00:01:33,267 --> 00:01:36,807 Germany, developing and implementing firm-wide digital design technology. 29 00:01:37,557 --> 00:01:39,357 standards and processes. 30 00:01:39,727 --> 00:01:40,537 Previous to that. 31 00:01:40,537 --> 00:01:44,137 He worked with Perkins+Will and CBT Architects in Boston. 32 00:01:44,587 --> 00:01:48,817 In this episode, we discussed the hidden inefficiencies within the AEC industry. 33 00:01:49,116 --> 00:01:53,437 We discussed the automation of industry standards, educating software users 34 00:01:53,437 --> 00:01:58,237 in real time, streamlining processes, the importance of BIM model health, 35 00:01:58,447 --> 00:02:02,677 eliminating technical debt and the ROI associated with these things. 36 00:02:02,827 --> 00:02:03,457 And more. 37 00:02:03,787 --> 00:02:08,737 It was a fantastic conversation with both Parley and Chris, and I hope you'll 38 00:02:08,737 --> 00:02:10,597 not only find value in it for yourself. 39 00:02:10,896 --> 00:02:13,627 But that you'll help add value to the profession by 40 00:02:13,627 --> 00:02:15,247 sharing it with your network. 41 00:02:15,607 --> 00:02:19,627 Please give this podcast a boost in the vast media landscape out there 42 00:02:19,807 --> 00:02:21,787 by subscribing wherever you listen. 43 00:02:22,117 --> 00:02:25,597 And if you'd like to receive an email, when new episodes are published with 44 00:02:25,597 --> 00:02:31,957 all of the links and other information from the episode, sign up at trxl.co. 45 00:02:32,377 --> 00:02:37,637 You can also directly support the show by becoming a member at the site as well. 46 00:02:37,817 --> 00:02:39,587 So as always, thank you so much for. 47 00:02:39,617 --> 00:02:40,127 For listening. 48 00:02:40,487 --> 00:02:44,897 And now without further ado, I bring you Parley Burnett and Chris S 49 00:02:53,053 --> 00:02:56,533 I am joined today by Parley Burnett and Chris Shafer, and 50 00:02:56,533 --> 00:02:57,503 it's great to have you both here. 51 00:02:57,781 --> 00:02:59,413 Welcome to the TRXL podcast. 52 00:02:59,413 --> 00:03:00,023 Parley Burnett: Thank you, uh, 53 00:03:00,142 --> 00:03:01,682 Evan Troxel: Yeah, it's going to be great conversation. 54 00:03:01,962 --> 00:03:06,262 I, I am excited to hear kind of where we're going to go. 55 00:03:06,762 --> 00:03:09,332 I think of this, uh, the topic that we're going to be speaking 56 00:03:09,332 --> 00:03:12,062 about today is kind of like the industry's dirty little secrets, but 57 00:03:12,072 --> 00:03:13,932 there's other ways to, to phrase it. 58 00:03:13,932 --> 00:03:17,042 I think with waste in the industry and, and things that, 59 00:03:17,052 --> 00:03:18,692 that people actively ignore. 60 00:03:18,875 --> 00:03:23,094 The, the idea of, of Dirty Little Secrets, I think is a good enough clickbaity 61 00:03:23,184 --> 00:03:25,234 kind of, uh, title for this episode. 62 00:03:25,334 --> 00:03:27,764 So, uh, that's why I'm going with it. 63 00:03:27,774 --> 00:03:32,614 But, but before we get to that, um, because I think a lot of people will be 64 00:03:32,614 --> 00:03:36,374 able to kind of nod along in agreement, but also I'm hoping we can, we can 65 00:03:36,374 --> 00:03:41,004 really hear about some ideas to, to move forward in, in the industry. 66 00:03:42,094 --> 00:03:43,134 Let's hear your stories first. 67 00:03:43,144 --> 00:03:46,384 So Parley, why don't you kick us off and tell us how you got 68 00:03:46,394 --> 00:03:48,344 to, uh, where you are today? 69 00:03:48,644 --> 00:03:49,434 Parley Burnett: Yeah, perfect. 70 00:03:49,793 --> 00:03:51,644 try to keep it brief, I guess. 71 00:03:51,954 --> 00:03:52,454 Evan Troxel: No worries. 72 00:03:52,454 --> 00:03:53,324 This is long form. 73 00:03:53,324 --> 00:03:54,353 This is podcasting, man. 74 00:03:54,353 --> 00:03:56,774 This is where people get to get to know who you are. 75 00:03:56,774 --> 00:03:57,154 So yeah, 76 00:03:57,154 --> 00:03:58,414 don't, don't try to keep it brief. 77 00:03:58,414 --> 00:03:58,894 Just, Just, 78 00:03:58,914 --> 00:03:59,534 tell the story. 79 00:03:59,741 --> 00:04:03,561 Parley Burnett: yeah, I guess I, I usually, I, I usually say that, um, 80 00:04:03,621 --> 00:04:05,821 fundamentally I'm a Revit nerd, right. 81 00:04:05,831 --> 00:04:13,011 So just to begin with, been basically working with Revit since 2005, and I 82 00:04:13,011 --> 00:04:19,071 think I quickly gained a passion for Revit having come from AutoCAD architecture 83 00:04:19,071 --> 00:04:23,351 desktop, um, and basically kind of. 84 00:04:24,946 --> 00:04:28,476 Went into drafting, thought I wanted to be an architect, quickly changed my 85 00:04:28,476 --> 00:04:30,186 mind, thought I wanted to be a developer. 86 00:04:31,736 --> 00:04:36,396 I think I got a D in my first class of, uh, of, of that. 87 00:04:36,696 --> 00:04:37,571 Evan Troxel: D for development. 88 00:04:37,621 --> 00:04:37,891 I mean, 89 00:04:37,896 --> 00:04:38,476 Parley Burnett: yeah, D. 90 00:04:39,271 --> 00:04:39,871 Evan Troxel: sounds right. 91 00:04:40,786 --> 00:04:42,076 Parley Burnett: So I, I guess I 92 00:04:42,076 --> 00:04:45,676 was sort of not sure what to do, but I knew I had interest in the 93 00:04:45,686 --> 00:04:48,626 building industry and design industry. 94 00:04:49,306 --> 00:04:57,161 So, um, went to UNLV construction management, But really have always 95 00:04:57,191 --> 00:05:03,031 been working with Revit in one way or another and kind of had my own drafting 96 00:05:03,031 --> 00:05:08,181 service for a time there to get through school, but then really gravitated 97 00:05:08,181 --> 00:05:13,741 towards especially the content side of Revit and the content strategies, 98 00:05:13,751 --> 00:05:17,111 everything else that goes around with that created a lot of content. 99 00:05:18,261 --> 00:05:21,251 And I think perhaps most. 100 00:05:21,966 --> 00:05:26,016 impactful to my career was my time at Unifi Labs. 101 00:05:26,116 --> 00:05:29,486 So I joined up with them in the very early days. 102 00:05:29,506 --> 00:05:33,706 It was 2010, really, before it was even called Unifi. 103 00:05:34,426 --> 00:05:37,136 We went through several different names, and I was, I 104 00:05:37,346 --> 00:05:38,726 think, the third person there. 105 00:05:40,346 --> 00:05:43,826 And together with a couple of really close colleagues, kind of, 106 00:05:44,161 --> 00:05:51,061 Conceptualize the idea of cloud based content management, and, uh, that was 107 00:05:51,061 --> 00:05:53,401 a, an incredible learning experience. 108 00:05:53,631 --> 00:06:01,251 Um, it obviously kind of took hold on the industry as a, as a concept. 109 00:06:01,481 --> 00:06:05,891 Um, now there's other products, of course, and now UNIFI is acquired by 110 00:06:06,311 --> 00:06:11,811 Autodesk, as a lot of us know, but during my time there, my 7 or 8 years, 111 00:06:11,851 --> 00:06:18,766 I, I, was, uh, a manager of content creation efforts for like manufacturers 112 00:06:19,286 --> 00:06:21,116 back when Autodesk Seek was a thing. 113 00:06:21,196 --> 00:06:23,186 So we've developed a lot of content for that. 114 00:06:24,276 --> 00:06:29,596 And then I became a product manager and then near the end I was leading 115 00:06:29,596 --> 00:06:31,246 our customer success efforts. 116 00:06:32,276 --> 00:06:37,216 So, um, you know, I, I, there's been a couple stints where I was a BIM manager, 117 00:06:37,236 --> 00:06:41,166 but typically for like smaller firms where things were much more nimble. 118 00:06:41,801 --> 00:06:42,231 Um, 119 00:06:42,821 --> 00:06:47,751 but then that was kind of complimented by a lot of conversations held with 120 00:06:47,751 --> 00:06:50,341 other firms during my, my time at Unify. 121 00:06:51,511 --> 00:06:56,941 Um, so kind of to the Guardian story, I guess, um, back in 2018, 122 00:06:59,071 --> 00:07:03,461 left Unify and really wanted to do something that was 123 00:07:03,471 --> 00:07:04,841 unique for the industry. 124 00:07:05,001 --> 00:07:10,161 A lot of times I would be on the phone with, um, firms of different 125 00:07:10,161 --> 00:07:11,951 sizes, different disciplines. 126 00:07:12,546 --> 00:07:15,936 But I would always hear the same kind of problems, right? 127 00:07:15,976 --> 00:07:20,446 And a lot of them trying to address those problems in the same way. 128 00:07:20,726 --> 00:07:26,066 So, first off, it felt like an opportunity was there to kind of level 129 00:07:26,066 --> 00:07:30,126 that out a little bit and not make everybody take on so much on their own. 130 00:07:32,486 --> 00:07:37,446 but also do things in a much more, like, natural, intuitive, um, way. 131 00:07:38,376 --> 00:07:40,806 in the flow kind of process, right? 132 00:07:40,826 --> 00:07:47,496 I, I, I had seen firsthand how anytime you have software that requires user 133 00:07:47,496 --> 00:07:53,316 interaction, like, literally any buttons that you have for users to click on, 134 00:07:53,956 --> 00:07:56,086 that's a barrier for adoption, right? 135 00:07:56,086 --> 00:07:56,776 So we 136 00:07:56,776 --> 00:07:57,776 really wanted to do 137 00:07:57,961 --> 00:08:00,961 Evan Troxel: you say this and I'm like thinking about the apps that people 138 00:08:00,961 --> 00:08:04,771 use on a day to day basis and there's hundreds and hundreds of buttons, right? 139 00:08:04,771 --> 00:08:07,551 And so you're saying anytime there's a button, right? 140 00:08:08,096 --> 00:08:08,636 Parley Burnett: anytime. 141 00:08:09,641 --> 00:08:09,911 Chris Shafer: Yep. 142 00:08:09,961 --> 00:08:13,921 Evan Troxel: it's like, you pull up these, like, it just reminds me of like 143 00:08:13,921 --> 00:08:15,561 the dashboard of an aircraft, right? 144 00:08:15,561 --> 00:08:16,153 It's like, Yeah. 145 00:08:16,153 --> 00:08:16,186 Yeah. 146 00:08:16,776 --> 00:08:18,456 There's a lot of buttons here, right? 147 00:08:18,476 --> 00:08:21,596 Uh, I can, it's completely overwhelming for a lot of people. 148 00:08:21,636 --> 00:08:25,826 And, and you're talking about software that it just keeps adding buttons, like 149 00:08:25,826 --> 00:08:28,576 is, that's kind of a fundamental feature. 150 00:08:29,166 --> 00:08:31,536 It's buttons. 151 00:08:32,155 --> 00:08:33,135 We added buttons. 152 00:08:33,306 --> 00:08:33,576 Yeah. 153 00:08:34,301 --> 00:08:34,671 Chris Shafer: Yeah. 154 00:08:34,706 --> 00:08:37,686 Parley Burnett: Yeah, a feature is that we removed buttons, right? 155 00:08:37,736 --> 00:08:39,905 That's kind of the way we would like to think of it. 156 00:08:40,556 --> 00:08:43,566 Um, that just introduces more complexity. 157 00:08:43,576 --> 00:08:47,946 So we really do think hard about any time we're adding interface for the users. 158 00:08:48,346 --> 00:08:49,881 Um, that's it. 159 00:08:50,181 --> 00:08:51,781 That's almost a bad thing. 160 00:08:51,790 --> 00:08:53,991 It has to be done out of necessity. 161 00:08:54,231 --> 00:08:57,671 So, um, kind of quick profile now. 162 00:08:57,671 --> 00:08:59,341 It's been about six years. 163 00:08:59,881 --> 00:09:04,201 We work with firms all over the world now and the hundreds, and 164 00:09:04,201 --> 00:09:06,311 it's just been quite a wild ride. 165 00:09:08,231 --> 00:09:10,781 Chris has been a big part of the story actually, even though 166 00:09:11,021 --> 00:09:12,401 he's joined the team recently. 167 00:09:13,511 --> 00:09:13,821 Chris Shafer: Yeah. 168 00:09:13,821 --> 00:09:16,121 Parley and I go way back. 169 00:09:16,141 --> 00:09:20,771 Um, him and I first met, uh, during the unified days. 170 00:09:20,781 --> 00:09:25,511 So, um, he was, you know, he was our customer. 171 00:09:25,886 --> 00:09:32,856 with my previous firm and, and we just instantly, I think we instantly 172 00:09:32,856 --> 00:09:36,415 connected on a lot of things he talked about, especially when it comes to 173 00:09:36,415 --> 00:09:40,256 the content and the, and the, the problems that, that we're both seeing, 174 00:09:40,446 --> 00:09:44,056 um, and, and fundamentally understood them from, from the same perspective. 175 00:09:45,216 --> 00:09:46,626 I actually come from. 176 00:09:47,296 --> 00:09:50,806 Come from a whole different perspective and kind of path kind of getting 177 00:09:50,826 --> 00:09:54,686 to where I am here at Guardian is I actually started off as an 178 00:09:54,746 --> 00:09:56,165 engineer in the aerospace industry. 179 00:09:56,366 --> 00:10:00,446 Um, but I was really lucky early in my career, um, you know, working for 180 00:10:00,456 --> 00:10:02,246 General Electric producing jet engines. 181 00:10:02,246 --> 00:10:03,566 I was actually part of a team. 182 00:10:03,926 --> 00:10:06,216 They call them the, uh, the blue sky team because they always said 183 00:10:06,216 --> 00:10:07,436 their heads were in the clouds. 184 00:10:07,936 --> 00:10:11,126 And, but we were, we were responsible of converting the 185 00:10:11,126 --> 00:10:15,116 assembly process of jet engines from a analog one to a digital one. 186 00:10:15,941 --> 00:10:23,141 And, this was a really interesting learning development for me was we were, 187 00:10:23,491 --> 00:10:26,471 we were responsible first and foremost to solve problems that were kind of 188 00:10:26,471 --> 00:10:28,901 plaguing the assembly of jet engines. 189 00:10:29,121 --> 00:10:33,631 Um, and, but as we did that, we would introduce technology into 190 00:10:33,631 --> 00:10:36,961 solving the problems and making sure those problems don't reoccur. 191 00:10:37,871 --> 00:10:42,241 And one of the things I really learned as an engineer solving these problems was. 192 00:10:44,061 --> 00:10:47,071 At the root of every problem, there's the lowest common denominator, and 193 00:10:47,081 --> 00:10:48,901 that is the driver of that problem. 194 00:10:49,471 --> 00:10:53,451 And it's through research, it's through data analysis, and, and 195 00:10:53,451 --> 00:10:57,531 just testing to get to what is that lowest common denominator. 196 00:10:58,131 --> 00:11:02,941 And so, fast forward, always wanted to be an architect, but for 197 00:11:02,941 --> 00:11:07,421 whatever reason, at 18 years old, I chose, chose engineering first. 198 00:11:07,441 --> 00:11:11,221 Um, but then, after doing that for almost six years, I decided to go back 199 00:11:11,221 --> 00:11:12,441 to school and become an architect. 200 00:11:14,281 --> 00:11:18,961 And as soon as I got into architecture, I was like, Whoa, this, I'm, 201 00:11:19,271 --> 00:11:22,441 I'm stepping back 20, 30 years from a technology perspective. 202 00:11:23,531 --> 00:11:29,691 Um, but then Revit came out and I was like, wow, all right, this is the tool. 203 00:11:29,851 --> 00:11:33,441 And, and I started using it in about 2008, 2009. 204 00:11:33,441 --> 00:11:37,401 And I was like, this is the tool that will drive the industry to the future. 205 00:11:37,856 --> 00:11:44,866 Um, and, and I kind of fast forward, um, many years as, as being a, a project 206 00:11:44,866 --> 00:11:49,886 architect, um, leading projects, you know, make, you know, through design and 207 00:11:49,886 --> 00:11:54,415 construction, done everything from, you know, from the very beginning to the end 208 00:11:54,415 --> 00:11:56,616 of the projects, every step along the way. 209 00:11:56,626 --> 00:11:57,726 Um, and. 210 00:11:58,076 --> 00:12:02,576 I really came down to, there is a few drivers in our industry that is really 211 00:12:02,576 --> 00:12:08,216 preventing us from really maximizing the potential that's in the technology 212 00:12:08,216 --> 00:12:09,866 that we have in front of us, right? 213 00:12:10,436 --> 00:12:13,326 And one of that was, was content, and I think that was 214 00:12:13,546 --> 00:12:14,986 partly had mentioned as well. 215 00:12:15,476 --> 00:12:18,066 Um, you know, simple, simple logistics, right? 216 00:12:18,526 --> 00:12:23,736 If we are digitally building buildings, we need the parts and pieces for those piece, 217 00:12:23,816 --> 00:12:25,356 for those buildings at our fingertips. 218 00:12:25,686 --> 00:12:26,686 It's not available. 219 00:12:27,086 --> 00:12:27,696 What do we do? 220 00:12:28,796 --> 00:12:29,656 I think we all agree. 221 00:12:29,656 --> 00:12:30,676 We just kind of all make it up. 222 00:12:31,066 --> 00:12:37,786 So early on when, um, when I went to HDR, I just went back as, um, when I 223 00:12:37,956 --> 00:12:42,066 moved to HDR, I was like, all right, I'm done with the technology side of things. 224 00:12:42,286 --> 00:12:43,386 I'm just going back to architecture. 225 00:12:44,106 --> 00:12:48,726 And, and so it's been my first year there doing architecture and designing 226 00:12:48,726 --> 00:12:50,596 a building in the Boston Seaport. 227 00:12:51,196 --> 00:12:55,581 And then, um, Then I just happened to see, someone had mentioned to me, um, 228 00:12:55,591 --> 00:12:59,821 within, within the office, like, oh, I did see there's this corporate role for 229 00:12:59,851 --> 00:13:06,031 a content manager opened up, and I was like, I'll give it a go, I'll give it a 230 00:13:06,031 --> 00:13:11,526 go, and that's when I took the role, um, I met Parley and Parley had, Parley and 231 00:13:11,526 --> 00:13:15,241 I had a lot of conversations about, you know, content management and the, the 232 00:13:15,241 --> 00:13:19,876 issues that kind of plague the industry and so on and so forth, um, And then, 233 00:13:20,876 --> 00:13:22,976 then Parley went and started Guardian. 234 00:13:23,026 --> 00:13:28,806 Um, and from, from then, Parley and I spoke almost on a weekly 235 00:13:28,806 --> 00:13:32,876 basis for the last six, seven years, um, about what's happening. 236 00:13:32,876 --> 00:13:38,026 So, um, as, as my career grew at HDR, we're, um, end up leading 237 00:13:38,046 --> 00:13:40,126 our, what we call digital design. 238 00:13:40,136 --> 00:13:44,056 It was, um, digital design and delivery, which is alternative to digital practice. 239 00:13:44,446 --> 00:13:48,766 Um, you know, We were always talking about, you know, what are those 240 00:13:48,766 --> 00:13:52,756 needs and what are these fundamental problems that's, that's, that's 241 00:13:52,766 --> 00:13:58,536 limiting the industry, um, and from, from really meeting that, that 242 00:13:58,536 --> 00:14:00,246 potential that's right in front of us. 243 00:14:00,806 --> 00:14:07,261 Um, so yeah, um, after, after kind of, kind of, In my off hours helping Party 244 00:14:07,261 --> 00:14:11,831 help from time to time, uh, this past, this past spring, I finally made the 245 00:14:11,831 --> 00:14:15,341 leap and said, All right, let's give this software development thing a try. 246 00:14:15,941 --> 00:14:19,341 Um, and so it's been, it's been an interesting three months 247 00:14:19,341 --> 00:14:20,341 now since I've been here. 248 00:14:21,881 --> 00:14:22,271 Guardian. 249 00:14:22,926 --> 00:14:23,336 Evan Troxel: Nice. 250 00:14:24,326 --> 00:14:27,086 The thing that you, you mentioned about when you were, when you were working 251 00:14:27,086 --> 00:14:33,396 at GE and transitioning from analog to digital process in order to solve 252 00:14:34,026 --> 00:14:39,426 problems that were plaguing the, the process of building these engines. 253 00:14:40,206 --> 00:14:44,216 I'm curious how you, do you see an, an analogy there, I mean, 254 00:14:44,226 --> 00:14:45,566 with what you're doing now? 255 00:14:45,586 --> 00:14:49,241 I mean, the whole point of, technology implementation 256 00:14:49,261 --> 00:14:51,351 is typically process, right? 257 00:14:51,351 --> 00:14:55,831 It's, it's on the, rarely do people focus on the people side, right? 258 00:14:55,841 --> 00:14:59,391 There's, there's, which I think is, is another issue, right? 259 00:14:59,391 --> 00:15:05,081 Like you can't just put software into the pipeline and, and then just say, 260 00:15:05,081 --> 00:15:07,981 okay, check, done, solved, right? 261 00:15:07,981 --> 00:15:12,071 It's not like that at all, but working together between people 262 00:15:12,071 --> 00:15:15,441 and process is the key thing here. 263 00:15:15,571 --> 00:15:17,151 And, and I'm curious if you. 264 00:15:17,921 --> 00:15:22,451 Like you said, at some point, Revit came along, you saw that as the future, and 265 00:15:22,451 --> 00:15:27,711 you said, Okay, like this, because before that, you said we were 20 to 30 years 266 00:15:27,711 --> 00:15:29,711 behind what you had already experienced. 267 00:15:31,156 --> 00:15:31,986 Aerospace, right? 268 00:15:31,986 --> 00:15:35,836 So I, I'm just curious, like I just threw a bunch of stuff out there. 269 00:15:35,906 --> 00:15:39,006 What, what do you see as the, both of you, what do you both 270 00:15:39,016 --> 00:15:40,506 see as kind of the current state? 271 00:15:40,516 --> 00:15:46,576 You, you have your fingers at, you know, you're on tap with a lot of people in 272 00:15:46,576 --> 00:15:50,151 the industry, across the industry, you have international customers, as well as. 273 00:15:50,661 --> 00:15:54,821 You know, customers here in the US, what are you, because, because you said 274 00:15:54,821 --> 00:15:58,971 something earlier too, that, that just, all of this is just kind of firing off in 275 00:15:58,971 --> 00:16:02,581 my brain at the moment, so I apologize for it being so sporadic, but, like, you, you 276 00:16:02,591 --> 00:16:06,831 hear the same things all over the place, and I'm, same thing here, I hear the same 277 00:16:06,841 --> 00:16:10,201 things all over the place, I think a lot of people think, oh, we're, only we're 278 00:16:10,201 --> 00:16:15,061 having this problem, um, But it's not true, like everybody's having very similar 279 00:16:15,061 --> 00:16:16,801 problems, if not the same problems. 280 00:16:17,181 --> 00:16:21,631 And so, just thinking about all that, I mean, your story, the development, 281 00:16:21,651 --> 00:16:24,521 the path that you've been on, the trajectory that you've been on. 282 00:16:25,381 --> 00:16:29,741 really matters when it comes to kind of thinking about these industry wide 283 00:16:29,751 --> 00:16:34,601 issues, touching base with a lot of customers, really matters when you're, 284 00:16:34,691 --> 00:16:37,601 when you're considering how you're going to solve problems for people. 285 00:16:37,961 --> 00:16:40,951 And then there's implementation and then there's training, like there's the 286 00:16:40,951 --> 00:16:44,790 actual people side of it and getting back to Parley's initial thing about 287 00:16:45,321 --> 00:16:47,081 adding or removing buttons, right? 288 00:16:47,091 --> 00:16:52,781 That's to the actual user of, of the implementation to solve these problems. 289 00:16:53,311 --> 00:16:58,131 And, and all of this kind of ecosystem, I'm just curious, what 290 00:16:58,311 --> 00:17:01,871 are you guys hearing, feeling as kind of the pulse of the industry? 291 00:17:02,161 --> 00:17:04,111 Are we still really far behind? 292 00:17:04,461 --> 00:17:05,501 Are we not far behind? 293 00:17:05,531 --> 00:17:07,181 Are we, are we cutting edge? 294 00:17:07,181 --> 00:17:08,661 Like, where are we on the spectrum? 295 00:17:08,981 --> 00:17:12,171 And then, like, what, what are you still hearing as kind of the 296 00:17:12,191 --> 00:17:13,681 issues plaguing the industry? 297 00:17:14,810 --> 00:17:17,731 Either one of you, take, take that and run with it, 298 00:17:18,556 --> 00:17:21,376 Chris Shafer: probably if you don't mind, if I'll start off with sort of 299 00:17:21,386 --> 00:17:25,165 the analogy that you asked about that is one, it does start with people. 300 00:17:25,336 --> 00:17:28,826 Um, that is one of the things I first learned about, um, when 301 00:17:28,826 --> 00:17:32,306 solving these problems, these the majority of time, unfortunately, 302 00:17:32,336 --> 00:17:33,786 it was people problems, right? 303 00:17:34,036 --> 00:17:41,531 It wasn't, It wasn't intentional or, or, um, bad intentions, um, by anyone. 304 00:17:42,221 --> 00:17:44,851 I mean, if you think about it, it doesn't matter what you're doing. 305 00:17:45,171 --> 00:17:47,571 And I would say, especially if you're doing something where 306 00:17:47,921 --> 00:17:51,281 you're producing something, the same thing over and over and over 307 00:17:51,281 --> 00:17:53,941 again, it becomes mentally taxing. 308 00:17:54,151 --> 00:17:54,391 Right. 309 00:17:54,921 --> 00:18:01,641 And when it comes to the jet engines, one person would be responsible for fastening, 310 00:18:02,171 --> 00:18:04,971 say 700 bolts over an eight hour period. 311 00:18:05,521 --> 00:18:09,091 One of those bolts wasn't fastened to the proper torque. 312 00:18:09,411 --> 00:18:11,081 That was enough for an engine failure. 313 00:18:11,761 --> 00:18:18,771 And so like, how, how do we use technology to ensure that everything is done exactly 314 00:18:18,771 --> 00:18:20,501 the way it should be the first time? 315 00:18:20,571 --> 00:18:20,871 Right. 316 00:18:21,201 --> 00:18:24,211 So, So you don't have these downstream mistakes. 317 00:18:24,541 --> 00:18:25,621 That's just human nature. 318 00:18:25,711 --> 00:18:30,451 And, and kind of time us back to, to architecture is we are 319 00:18:30,481 --> 00:18:32,681 a, a deadline driven industry. 320 00:18:32,761 --> 00:18:37,721 Um, there's big deadlines, there's small deadlines, there's daily deadlines, right? 321 00:18:38,461 --> 00:18:42,911 Always, we're always working at 100, 110%. 322 00:18:43,231 --> 00:18:46,741 When you're working at that capacity, you're bound to make mistakes 323 00:18:47,181 --> 00:18:48,271 Evan Troxel: or take shortcuts, right? 324 00:18:48,281 --> 00:18:48,631 Like that, 325 00:18:48,641 --> 00:18:49,891 Chris Shafer: or, or take shortcuts. 326 00:18:49,891 --> 00:18:50,221 Yes. 327 00:18:50,576 --> 00:18:52,236 Yeah, that's exactly right. 328 00:18:52,606 --> 00:18:58,086 Um, and, and so, and that's where I kind of see Guardian comes along, and 329 00:18:58,086 --> 00:19:03,336 I'll let Parley kind of extrapolate on that, but it is, there's so much of what 330 00:19:03,356 --> 00:19:09,831 we do is, is really repetitive, and it is common, um, throughout the podcast. 331 00:19:10,241 --> 00:19:11,231 All of design. 332 00:19:11,611 --> 00:19:14,721 Um, you know, one may argue that when you're doing commercial construction 333 00:19:14,731 --> 00:19:19,391 versus residential, you know, the parts and pieces are a little different and 334 00:19:19,391 --> 00:19:23,591 whatnot, but if you're in commercial design, if you're designing high rises 335 00:19:23,591 --> 00:19:28,581 or whatnot, there is, there's a lot of, you're using the same kit of parts. 336 00:19:28,801 --> 00:19:29,331 more or less. 337 00:19:30,121 --> 00:19:31,261 Um, it's just the arrangement. 338 00:19:31,611 --> 00:19:35,871 So there is a lot of repetition and commonality in so much of what we do. 339 00:19:36,261 --> 00:19:40,641 Um, and I think there is a, I think there is a, 340 00:19:42,961 --> 00:19:47,406 I don't know how to phrase this, but a A thought in the industry, what 341 00:19:47,406 --> 00:19:49,796 we do each and every time is unique. 342 00:19:49,886 --> 00:19:55,536 And, and the way I see what we're doing is we're saying, well, let's 343 00:19:55,536 --> 00:20:00,586 be honest here that there, there is this thing we do over and over again. 344 00:20:01,006 --> 00:20:04,366 Let's figure out how we can apply technology to that. 345 00:20:04,836 --> 00:20:07,936 So, you know, those little mistakes aren't happening, or we're not cutting 346 00:20:07,996 --> 00:20:13,126 corners because we, to prevent those downstream impacts on, on all of that. 347 00:20:13,856 --> 00:20:15,056 And partly, if you want to. 348 00:20:15,996 --> 00:20:20,886 expand on how Guardian is, is helping, you know, solve some of those. 349 00:20:21,726 --> 00:20:21,806 Parley Burnett: Understood. 350 00:20:22,016 --> 00:20:27,106 Yeah, I think it's, those are great questions and it's true 351 00:20:27,136 --> 00:20:31,546 that we do talk with a lot of different firms every day, right. 352 00:20:31,886 --> 00:20:34,336 Um, and it's fascinating. 353 00:20:34,706 --> 00:20:39,056 It's really interesting to kind of, um, step back a little bit 354 00:20:39,056 --> 00:20:43,706 and ponder what the what's this culture at this firm look like. 355 00:20:43,796 --> 00:20:44,106 Right. 356 00:20:44,436 --> 00:20:49,396 and you and you can see a lot of themes kind of 357 00:20:52,006 --> 00:20:52,926 extend throughout. 358 00:20:53,486 --> 00:20:57,926 The entire workforce that we touch and talk with, um, 359 00:20:59,946 --> 00:21:08,196 kind of on the software side, we kind of look at ourselves as, as software, of 360 00:21:08,196 --> 00:21:13,556 course, but, but really more on the human side of things, where we're more of a 361 00:21:13,586 --> 00:21:17,156 reflection of a firm's existing culture. 362 00:21:18,206 --> 00:21:22,986 Um, basically everything in Guardian, just in case anyone hasn't seen 363 00:21:22,986 --> 00:21:27,406 it yet, everything has a setting and it's highly customized. 364 00:21:28,006 --> 00:21:28,726 that setting. 365 00:21:29,216 --> 00:21:34,756 So as you're a BIM manager, a design technologist, kind of setting 366 00:21:34,756 --> 00:21:40,726 up Guardian, it tends to reflect your own personal style, really. 367 00:21:41,296 --> 00:21:47,176 Um, we're there as a tool to kind of just allow you to scale that, right? 368 00:21:47,996 --> 00:21:53,146 Um, so I think that's, that's what we see as, um, you know, maybe 369 00:21:53,466 --> 00:22:00,126 Guardian is sort of an analog tool, basically, in that You've got the 370 00:22:00,126 --> 00:22:02,126 soft skills that are still required. 371 00:22:02,686 --> 00:22:07,506 Um, and then if you develop that, then it can be very effective to driving 372 00:22:07,506 --> 00:22:09,316 culture and change at your firm. 373 00:22:11,286 --> 00:22:13,766 Chris Shafer: I think there's one thing that's, sorry, go ahead, Evan, 374 00:22:14,136 --> 00:22:15,046 Evan Troxel: you go ahead, go for it. 375 00:22:15,366 --> 00:22:17,746 Chris Shafer: is I think that's one of the things that's, that's really 376 00:22:17,746 --> 00:22:23,946 important is when it comes to digital practice, we'll just use that as 377 00:22:23,946 --> 00:22:25,926 the kind of catch all phrase is, 378 00:22:28,496 --> 00:22:32,276 is from my role and I, you know, from my, my peers in the industry, 379 00:22:32,276 --> 00:22:36,376 a lot of conversations we've had is everything that the practice does. 380 00:22:38,126 --> 00:22:42,786 The, The crossroads of where all the, you know, the, the marketing, 381 00:22:43,146 --> 00:22:47,706 the, the sales, you know, the project management, the technical leadership, 382 00:22:47,926 --> 00:22:55,051 you know, the project delivery, it all comes to that crossroads at the, at 383 00:22:55,051 --> 00:22:58,011 the interface of people and technology. 384 00:22:58,771 --> 00:23:03,841 And, and so understanding those dynamics and understanding the people 385 00:23:04,011 --> 00:23:08,351 behind it and what their needs and how they operate is really important. 386 00:23:08,831 --> 00:23:12,421 And I think that's, um, from my own career, that's what I've seen 387 00:23:12,421 --> 00:23:15,851 is, is really understanding what are those needs of the people. 388 00:23:16,111 --> 00:23:23,061 Um, that are doing the work and making sure that all the other externalities 389 00:23:23,081 --> 00:23:28,031 within a firm and those requirements are being communicated and being, being 390 00:23:28,031 --> 00:23:30,881 adhered to throughout the process. 391 00:23:31,291 --> 00:23:34,921 Um, And because at the end of the day, when that deliverable, you know, 392 00:23:34,931 --> 00:23:40,051 when the deliverable is, is out the door or whether it's, you know, doing 393 00:23:40,051 --> 00:23:47,131 the QAQC process, you know, all that is, has to be done before that, that, 394 00:23:47,181 --> 00:23:48,911 that juncture in the project, right. 395 00:23:48,931 --> 00:23:54,711 And getting the people to start thinking about things kind of ahead of time, 396 00:23:54,841 --> 00:23:59,541 you know, before, before things become problems, before they become mistakes. 397 00:23:59,961 --> 00:24:02,831 Um, it is about really understanding. 398 00:24:03,876 --> 00:24:07,176 The people, their mindset, what they're thinking about, what their 399 00:24:07,176 --> 00:24:13,156 priorities are and how they like being communicated to as well. 400 00:24:13,516 --> 00:24:20,276 I think that's a big aspect of what we do is understanding communication in a 401 00:24:20,276 --> 00:24:22,266 firm, big and small, is really difficult. 402 00:24:22,976 --> 00:24:26,536 And how do you communicate the needs of technical leadership or design 403 00:24:26,536 --> 00:24:30,936 leadership or whatever it may be while you're in the flow of producing? 404 00:24:32,181 --> 00:24:36,471 So I think that's a really important, um, aspect of what we do is, is think about 405 00:24:36,471 --> 00:24:40,381 the people and how people communicate and how people interact with one another. 406 00:24:41,276 --> 00:24:44,086 Evan Troxel: Yeah, it's interesting for you to bring up the needs of the 407 00:24:44,106 --> 00:24:49,266 technical leadership, because I'm trying to think if I've ever heard of 408 00:24:49,266 --> 00:24:51,166 that being phrased like that before. 409 00:24:52,046 --> 00:24:57,386 I feel like the thinking in firms is that the technology is there 410 00:24:57,386 --> 00:25:02,196 to serve the people, as tools, but not to serve the people. 411 00:25:02,656 --> 00:25:04,926 Not that there's needs there that need to be met. 412 00:25:05,166 --> 00:25:08,616 It's more like, no, the function of this stuff is just to do what I tell 413 00:25:08,616 --> 00:25:10,936 it to do, however I tell it to do it. 414 00:25:11,686 --> 00:25:18,186 But you're reframing that to say, like there's a structure that is required, it's 415 00:25:18,186 --> 00:25:22,786 required that you adhere to it, so that we get the value, the benefits out of it. 416 00:25:23,536 --> 00:25:25,556 You know, probably later, right? 417 00:25:25,796 --> 00:25:33,096 But a lot of people are totally willing to hijack later for the, the, the comfort 418 00:25:33,116 --> 00:25:36,926 of like now, and by comfort, I just mean like getting something done, right? 419 00:25:36,926 --> 00:25:38,806 Like I just need it off my list. 420 00:25:38,866 --> 00:25:43,716 Um, and that's where this kind of perverse incentivization happens, right? 421 00:25:43,716 --> 00:25:46,236 Which is like, just take shortcuts now. 422 00:25:46,546 --> 00:25:52,206 The idea of technical debt creeping into projects because people aren't 423 00:25:52,206 --> 00:25:57,096 willing decisions, or they don't know what they don't know, you know, 424 00:25:57,136 --> 00:26:02,016 early on to benefit the project, to benefit the value of what technical 425 00:26:02,016 --> 00:26:04,066 leadership needs out of projects. 426 00:26:04,706 --> 00:26:11,236 Um, that, that just gets, you know, the, to use the Karate Kid metaphor, right? 427 00:26:11,236 --> 00:26:12,116 Sweep the legs, Johnny. 428 00:26:12,126 --> 00:26:15,066 Like, just, just cut the legs out from underneath, underneath 429 00:26:15,076 --> 00:26:18,986 it now, because it just, I have a deadline, like, to your point, 430 00:26:18,986 --> 00:26:20,736 Chris, I have daily deadlines, right? 431 00:26:21,226 --> 00:26:26,081 I just need it to, Kind of work now, and I'm, I'm, you know, 432 00:26:26,941 --> 00:26:28,501 screw around and find out, right? 433 00:26:28,511 --> 00:26:30,311 That, that's what ends up happening, right? 434 00:26:30,341 --> 00:26:36,701 And so, this idea of kind of, okay, so, so, okay, so here's the other 435 00:26:36,701 --> 00:26:40,041 thing that's going on in my head, based on what Parley was saying, which is 436 00:26:41,311 --> 00:26:45,031 It's every firm's the Wild West, you know, and to what you said, Chris, 437 00:26:45,051 --> 00:26:47,161 every, every project is unique, right? 438 00:26:47,161 --> 00:26:49,891 Everybody thinks their project and, and, and to some extent, yes, 439 00:26:49,911 --> 00:26:53,531 unique assemblies, unique site, unique client, um, environmental 440 00:26:53,541 --> 00:26:54,811 orientation, all these things. 441 00:26:54,811 --> 00:26:58,791 Yes, but using the same parts to put, put things together. 442 00:26:59,161 --> 00:27:04,471 And so, um, what's interesting to me is you guys are responding to. 443 00:27:05,551 --> 00:27:10,371 That situation and saying, well, your, your culture is unique 444 00:27:10,431 --> 00:27:13,181 because it's made up of individuals. 445 00:27:13,631 --> 00:27:18,051 who come together to form that culture and we want to meet you where you're 446 00:27:18,061 --> 00:27:22,411 at rather than force you to use a tool in this very specific way, which is 447 00:27:22,981 --> 00:27:24,521 big platforms kind of do that, right? 448 00:27:24,521 --> 00:27:28,301 They force people to use the software that their way. 449 00:27:28,741 --> 00:27:31,431 Um, and that's where all of this screwed up. 450 00:27:31,791 --> 00:27:32,951 Behavior happens, right? 451 00:27:32,961 --> 00:27:37,501 It's like workarounds, like that's what this is because it's complicated and 452 00:27:37,501 --> 00:27:41,421 not everybody has the same training and the same know how and, um, they 453 00:27:41,421 --> 00:27:45,111 haven't been using it as long as the person, you know, the expert over there. 454 00:27:45,431 --> 00:27:49,761 And so I don't want to ask somebody and look stupid, risk looking stupid. 455 00:27:49,761 --> 00:27:52,961 So I'm going to like YouTube it, or I'm just going to try to figure it out and 456 00:27:52,961 --> 00:27:54,841 I'm going to figure it out, not the. 457 00:27:55,351 --> 00:27:57,421 standard way that the technical leadership needs. 458 00:27:57,421 --> 00:28:00,361 Like we've seen all of this happen all the time, right? 459 00:28:00,711 --> 00:28:03,441 And I think it's really interesting that you're approaching this problem 460 00:28:03,451 --> 00:28:09,921 from a different perspective, which is, okay, your firm culture is unique 461 00:28:09,931 --> 00:28:13,171 in what you're doing and how you're delivering it and how you're using the 462 00:28:13,171 --> 00:28:14,521 tools because you have different people. 463 00:28:14,521 --> 00:28:16,331 You've got different standards than that firm. 464 00:28:16,331 --> 00:28:18,161 You've got different content than this firm. 465 00:28:18,621 --> 00:28:21,271 You've got different market segments and different project 466 00:28:21,301 --> 00:28:22,491 types and all these things, right? 467 00:28:22,491 --> 00:28:23,821 Those are, those are differences. 468 00:28:24,311 --> 00:28:29,021 And you're saying like, we tailor it to you rather than forcing you 469 00:28:29,021 --> 00:28:30,801 to use it a very specific way. 470 00:28:31,641 --> 00:28:32,651 When I. 471 00:28:33,251 --> 00:28:34,321 Throw all this at you. 472 00:28:34,331 --> 00:28:35,261 I, I apologize. 473 00:28:35,271 --> 00:28:38,171 Like, I feel like super unstructured about how I'm, how I'm talking about 474 00:28:38,171 --> 00:28:42,581 this, but this is very much like, Oh, I'm working all this out in my head. 475 00:28:42,591 --> 00:28:45,451 And I, and you prompted it, Chris, by saying, you know, what technical 476 00:28:45,451 --> 00:28:48,241 leadership needs and, and based on some other things that they came 477 00:28:48,241 --> 00:28:52,581 up before that, like, this is the kind of stuff that I think lots 478 00:28:52,581 --> 00:28:53,791 of people are struggling with. 479 00:28:54,116 --> 00:28:54,396 Right. 480 00:28:54,416 --> 00:28:57,586 And, and I know firm leaders out there who have just said, like, we 481 00:28:57,586 --> 00:29:01,066 just declared digital bankruptcy and we let the teams figure it out. 482 00:29:01,126 --> 00:29:01,466 Right. 483 00:29:01,896 --> 00:29:05,446 And, and then we're just there to put out fires and we're there to kind of 484 00:29:05,456 --> 00:29:10,516 smooth over the road bumps and we're just trying to just keep it going. 485 00:29:10,566 --> 00:29:10,916 Right. 486 00:29:10,916 --> 00:29:13,376 Just keep the tire, keep the wheels on. 487 00:29:13,456 --> 00:29:13,616 Right. 488 00:29:14,601 --> 00:29:15,301 Chris Shafer: Exactly. 489 00:29:15,326 --> 00:29:17,776 Evan Troxel: and there's another, there's the other side of that coin, 490 00:29:17,786 --> 00:29:19,246 which is like, it's super structured. 491 00:29:19,246 --> 00:29:20,726 You have to do it this way. 492 00:29:21,136 --> 00:29:26,271 Um, and, and I mean, You know, trying to limit technical debt buildup. 493 00:29:26,331 --> 00:29:31,771 So if I throw all this out there, I mean, I'm really interested in how you're kind 494 00:29:31,771 --> 00:29:37,101 of approaching this from a different angle than like the big platforms even can. 495 00:29:37,121 --> 00:29:37,291 Right? 496 00:29:37,291 --> 00:29:37,641 You can't. 497 00:29:37,661 --> 00:29:42,681 And so what you're saying is like, Guardian is super customizable to the way 498 00:29:42,701 --> 00:29:46,671 firm cultures and people use the software and what their technical leaders need 499 00:29:46,671 --> 00:29:47,991 to get out of it and all these things. 500 00:29:49,631 --> 00:29:55,081 Um, I, I just imagine that, like, at some level, and maybe I'm wrong, 501 00:29:55,111 --> 00:29:57,761 that's got to be a little hard to manage because everybody's doing it a 502 00:29:57,761 --> 00:29:59,101 little bit differently still, right? 503 00:29:59,141 --> 00:30:02,441 Um, there's no industry standard here, right? 504 00:30:02,451 --> 00:30:06,151 Like, this is still kind of firm culture, firm standard kind of stuff. 505 00:30:06,151 --> 00:30:08,461 So, I mean, what does that trigger for you guys? 506 00:30:08,541 --> 00:30:11,541 Kind of, like, me bouncing this back at you. 507 00:30:12,341 --> 00:30:17,981 Chris Shafer: One of, one of the things, hearing, hearing that is, take a simple 508 00:30:17,981 --> 00:30:19,701 thing, say, browser organization. 509 00:30:20,676 --> 00:30:21,356 is 510 00:30:22,371 --> 00:30:23,591 Evan Troxel: You're talking about the Revit, like, 511 00:30:23,676 --> 00:30:26,206 Chris Shafer: the Revit browser, Project Browser Organization, right? 512 00:30:26,206 --> 00:30:27,606 Something as simple as that, right? 513 00:30:28,076 --> 00:30:31,756 All that is, is an, is organizing of your views and sheets. 514 00:30:32,151 --> 00:30:32,551 Evan Troxel: Mm hmm. 515 00:30:32,636 --> 00:30:37,611 Chris Shafer: Um, Especially early on in, in, in my career and using, using Revit. 516 00:30:38,151 --> 00:30:40,271 And this happens with everyone in architecture. 517 00:30:40,291 --> 00:30:42,391 You kind of bounce from project to project, right? 518 00:30:42,951 --> 00:30:44,841 And you go from one project to the next. 519 00:30:45,261 --> 00:30:47,881 And the browser organization is completely different than the other. 520 00:30:48,251 --> 00:30:49,221 There's a learning curve. 521 00:30:49,281 --> 00:30:52,191 And there's just, you know, talking about waste in the industry, right? 522 00:30:52,551 --> 00:30:53,976 That's, that's just waste. 523 00:30:54,416 --> 00:30:54,706 Evan Troxel: Yeah. 524 00:30:55,236 --> 00:30:59,706 Chris Shafer: And then you would have, then you would have, say, you hire a 525 00:30:59,706 --> 00:31:02,676 new architect or a new architect or a junior architect and like, well, my 526 00:31:02,676 --> 00:31:04,326 last firm, we organized it this way. 527 00:31:04,546 --> 00:31:08,006 And they go in there and start changing their organization right within that 528 00:31:08,006 --> 00:31:10,146 active project to that organization. 529 00:31:10,586 --> 00:31:15,916 And then you have just, Layers and layers of all these other standards, and at the 530 00:31:15,916 --> 00:31:17,666 end of the day, you've got nothing, right? 531 00:31:18,006 --> 00:31:21,096 Everyone's just confused and I think we've all been there. 532 00:31:21,356 --> 00:31:23,586 We spend 20 minutes just looking for a view. 533 00:31:24,676 --> 00:31:28,786 And so with, you know, one of the things with Guardian is we're 534 00:31:28,786 --> 00:31:32,496 not saying what that browser organization should or shouldn't be. 535 00:31:32,496 --> 00:31:35,756 We're just saying, hey, this is something that is set up by the 536 00:31:35,756 --> 00:31:37,456 company as a company standard. 537 00:31:37,856 --> 00:31:44,181 Those, you know, the administrators, the digital, digital design leaders 538 00:31:44,191 --> 00:31:47,661 in the firms, they're the ones who's responsible for setting that up. 539 00:31:48,741 --> 00:31:52,891 But Guardian just ensures whatever was set up by those leaders that is 540 00:31:52,891 --> 00:31:57,431 being adopted and adhered by all the team, all teams and everyone on there. 541 00:31:57,901 --> 00:32:03,631 And if, if the Guardian administrator chooses to do so, people are 542 00:32:03,631 --> 00:32:05,411 prevented from changing it, right? 543 00:32:05,411 --> 00:32:08,621 So they're being asked to kind of follow the rules and there's a lot of layers 544 00:32:08,621 --> 00:32:12,261 of tools that make sure that, you know, those, you know, those standards are set. 545 00:32:12,806 --> 00:32:14,946 And they're easily adhered to. 546 00:32:14,946 --> 00:32:18,106 And I think that's something that's really important is it's one thing to 547 00:32:18,106 --> 00:32:23,066 say, Hey, here's your standards, but it's another thing to say, say, well, 548 00:32:23,076 --> 00:32:28,066 we're making it easier for you to do your job by the standards are kind of set. 549 00:32:28,126 --> 00:32:29,316 You don't have to think about it. 550 00:32:29,536 --> 00:32:30,246 They're there. 551 00:32:31,576 --> 00:32:36,356 And whenever there's something that is not meeting the standards, we're, 552 00:32:36,386 --> 00:32:37,486 we're just going to change it for you. 553 00:32:37,496 --> 00:32:39,096 We're going to change it to the standard. 554 00:32:39,506 --> 00:32:41,526 Um, but partly actually has a really. 555 00:32:42,036 --> 00:32:48,716 Um, cool history on, on where he ran into a situation where, um, someone wasn't 556 00:32:48,716 --> 00:32:55,396 a big fan of, of the standards or lack thereof, and, and how, how a simple 557 00:32:55,396 --> 00:32:59,396 interaction, and again, come back to communications and people, um, how that 558 00:32:59,406 --> 00:33:02,256 led to, um, actually winning someone over. 559 00:33:04,361 --> 00:33:06,281 Parley Burnett: Yeah, yeah, it's a fun one. 560 00:33:06,471 --> 00:33:11,691 Um, but, and I'll share it, but Evan, I think you said it better than I did. 561 00:33:11,871 --> 00:33:16,991 You know, we, we do try to arrive at where they're at from the beginning 562 00:33:18,091 --> 00:33:24,151 and we kind of view our role in, in the lifespan of our relationship with a firm 563 00:33:24,271 --> 00:33:27,251 as consulting them and guiding them. 564 00:33:27,811 --> 00:33:31,691 And taking the good parts that we see at other firms and kind 565 00:33:31,691 --> 00:33:35,871 of allowing them to kind of morph into a more positive culture. 566 00:33:37,161 --> 00:33:42,541 Um, and technical debt for sure is a, is a concept that as, as software developers, 567 00:33:42,541 --> 00:33:44,321 we're, we're well familiar with, right? 568 00:33:44,471 --> 00:33:50,481 Um, and, and the reality is like, we are technology people. 569 00:33:51,211 --> 00:33:55,261 And so sometimes we're not aware of the technical debt that we're accumulating. 570 00:33:56,001 --> 00:33:57,621 Now, think about Revit, right? 571 00:33:58,071 --> 00:34:02,021 We're working with artists and designers who, who may not be as 572 00:34:02,021 --> 00:34:06,491 technically minded, they don't even know they're creating that technical debt. 573 00:34:06,871 --> 00:34:07,221 Right. 574 00:34:07,301 --> 00:34:11,791 And so, so we kind of see that as our role is to kind of bring that to light as well. 575 00:34:12,371 --> 00:34:19,110 And the story that Chris is talking about, um, in software, we, we often 576 00:34:19,110 --> 00:34:23,201 say, or there's this phrase, you know, we need to eat our own dog food. 577 00:34:23,351 --> 00:34:23,721 Right. 578 00:34:24,061 --> 00:34:28,286 And so, um, early in the development of Guardian. 579 00:34:28,726 --> 00:34:32,815 We put it into practice with a close firm here locally, um, 580 00:34:33,016 --> 00:34:34,556 kind of in partnership with them. 581 00:34:35,036 --> 00:34:38,906 We deployed it to the users and, you know, we, I think we had a 582 00:34:39,206 --> 00:34:44,005 prompt show up to users when they went to the line styles management 583 00:34:44,005 --> 00:34:48,596 dialogue, um, that basically said like Chris was saying with the project 584 00:34:48,606 --> 00:34:50,835 browser, okay, this is our standard. 585 00:34:51,311 --> 00:34:53,880 If you're going to make a change, tell us what you're changing. 586 00:34:54,661 --> 00:34:58,461 And, and we had a user there that was like, well known for being 587 00:34:58,471 --> 00:35:00,291 the bull in the China shop, right? 588 00:35:00,301 --> 00:35:02,151 Just kind of go, go, go. 589 00:35:02,791 --> 00:35:06,641 Um, very quick, um, not really caring about 590 00:35:06,996 --> 00:35:08,366 Evan Troxel: Move fast and break things. 591 00:35:08,386 --> 00:35:08,696 Right. 592 00:35:08,726 --> 00:35:08,936 Yeah. 593 00:35:08,986 --> 00:35:10,756 Parley Burnett: Just break everything. 594 00:35:11,296 --> 00:35:11,756 Yeah. 595 00:35:12,006 --> 00:35:13,126 Notorious for this. 596 00:35:13,126 --> 00:35:16,376 And he sent me this message of the guardian dialogue. 597 00:35:16,396 --> 00:35:18,346 Like, Hey, how do I get rid of this? 598 00:35:18,876 --> 00:35:19,246 Right. 599 00:35:19,666 --> 00:35:21,886 He's, he was quite adamant about this. 600 00:35:22,536 --> 00:35:26,036 And I basically had a conversation with him. 601 00:35:26,036 --> 00:35:27,596 I was like, well, why do you want to get rid of it? 602 00:35:27,656 --> 00:35:30,156 Well, I'm, I see it every time I go to Align Styles. 603 00:35:30,156 --> 00:35:33,326 And then I asked, well, What are you trying to do there? 604 00:35:33,846 --> 00:35:37,456 And he's like, well, I, I'm trying to make a red line style that I can mark 605 00:35:37,456 --> 00:35:42,106 my plans up with so I can come back later and make changes as like, well, 606 00:35:42,226 --> 00:35:46,776 sounds like that's something that you're doing on every project, right? 607 00:35:46,856 --> 00:35:48,386 It's like, Oh yeah, for sure. 608 00:35:48,536 --> 00:35:52,446 It's like, well, now that I know this, I can add that line style to the template 609 00:35:52,496 --> 00:35:54,116 and you'll never have to do this again. 610 00:35:54,296 --> 00:35:54,636 Right. 611 00:35:55,266 --> 00:35:58,216 And that's when the, the light bulb went off to that user. 612 00:35:58,736 --> 00:36:03,256 Um, and became almost the biggest advocate for it at the firm. 613 00:36:04,825 --> 00:36:07,465 Evan Troxel: This episode is made possible with support from Guardian 614 00:36:07,465 --> 00:36:11,325 for Revit; because even superheroes need sidekicks in the BIM world. 615 00:36:11,824 --> 00:36:15,124 Are you ready to say goodbye to the model headaches and hello 616 00:36:15,154 --> 00:36:16,684 to a smoother BIM management? 617 00:36:16,984 --> 00:36:19,744 Meet Guardian, a revolutionary Revit add-in. 618 00:36:19,924 --> 00:36:22,444 That's like a command center for your BIM strategy. 619 00:36:22,814 --> 00:36:26,234 Guardian is dedicated to helping teams protect their models, automate 620 00:36:26,234 --> 00:36:30,074 consistency, and ensure a standard of quality in their Revit projects. 621 00:36:30,324 --> 00:36:34,734 With Guardian you'll save time, avoid mistakes and build trust in your system. 622 00:36:35,164 --> 00:36:38,674 Guardian takes a holistic approach to improving the user experience 623 00:36:38,674 --> 00:36:42,754 by providing the data and solutions you need to address issues quickly 624 00:36:42,964 --> 00:36:44,494 before they become a problem. 625 00:36:44,774 --> 00:36:48,404 Through actionable insights, you can customize the Guardian settings to 626 00:36:48,404 --> 00:36:52,514 reflect your firm's standards and best practices with in-the-moment, user 627 00:36:52,514 --> 00:36:54,794 education and project protections. 628 00:36:55,094 --> 00:36:58,351 , , Guardian ensures your teams can focus on what they do best: 629 00:36:58,591 --> 00:37:01,051 building, designing and engineering. 630 00:37:01,421 --> 00:37:06,531 Trusted by firms worldwide since 2018, Guardian is your go-to add-in 631 00:37:06,581 --> 00:37:08,141 for the complex world of BIM. 632 00:37:08,561 --> 00:37:13,541 With immediate and measurable ROI, firms have saved thousands of hours by 633 00:37:13,541 --> 00:37:15,431 preventing mistakes before they happen. 634 00:37:15,801 --> 00:37:18,111 Are you ready to elevate your team's Revit experience? 635 00:37:18,411 --> 00:37:22,731 To learn more or take advantage of a free 30 day trial visit 636 00:37:22,731 --> 00:37:28,601 www.getguardian.tech/trxl. 637 00:37:29,001 --> 00:37:33,531 Together, let's take a stand in the new, proactive era of BIM management. 638 00:37:33,948 --> 00:37:37,518 My thanks to Guardian for supporting this episode of the TRXL podcast. 639 00:37:37,908 --> 00:37:40,158 And now let's get back to the conversation. 640 00:37:42,288 --> 00:37:45,828 Something you mentioned earlier, Chris, was the 20 minutes that 641 00:37:45,828 --> 00:37:49,518 somebody could spend just kind of learning how to navigate a project. 642 00:37:49,538 --> 00:37:52,038 And this is, I guess, what I was alluding to in the very beginning 643 00:37:52,048 --> 00:37:53,438 about like these dirty little secrets. 644 00:37:53,468 --> 00:37:56,248 It's like nobody really wants to recognize that this happens 645 00:37:56,268 --> 00:37:59,968 all in many different forms. 646 00:38:00,538 --> 00:38:06,278 with, right, it is not always just the inexperience of, of a user, right? 647 00:38:06,508 --> 00:38:11,458 It is, it is often because we are, you know, ad hoc, you know, as 648 00:38:11,778 --> 00:38:15,528 a previous title of an episode, AEC is an adhocracy, right? 649 00:38:15,528 --> 00:38:19,688 It's like this idea that every team we disperse, we come back 650 00:38:19,688 --> 00:38:21,378 together in a different form. 651 00:38:21,843 --> 00:38:25,093 Uh, different phase of a project, different project type, different 652 00:38:25,103 --> 00:38:28,903 template maybe for that project, different project leaders, different technical 653 00:38:28,903 --> 00:38:33,413 advisors, uh, different structures in these files, these giant databases that 654 00:38:33,413 --> 00:38:35,763 we all get into to work on a project. 655 00:38:36,573 --> 00:38:41,613 And, okay, so what we've buried so far is just like what Guardian does, and you've 656 00:38:41,613 --> 00:38:46,158 mentioned a few things about it, but I think from a, I, I would like to, uh, to 657 00:38:46,158 --> 00:38:50,108 set this up so that you can talk about what Guardian does in a more comprehensive 658 00:38:50,108 --> 00:38:53,668 way so that people can get like, they can actually say, Oh, okay, I get it now. 659 00:38:54,128 --> 00:38:58,458 Um, but using this as like the way to get into there, which is like this 660 00:38:58,488 --> 00:39:02,908 20 minutes that somebody spends just learning how to navigate through the 661 00:39:02,908 --> 00:39:06,828 views, how to find a view that they're looking for in a, in a project browser. 662 00:39:07,338 --> 00:39:08,728 That's one example. 663 00:39:09,168 --> 00:39:12,488 And you've talked about line styles and you've talked about content and you've 664 00:39:12,488 --> 00:39:17,028 talked about kind of these, these pop ups that happen that You know, maybe they give 665 00:39:17,028 --> 00:39:20,958 somebody information, maybe they ask them to make a decision, maybe they're, you 666 00:39:20,958 --> 00:39:23,038 know, they're these prompts that happen. 667 00:39:23,078 --> 00:39:27,388 Um, so all of this has, has been stated, but now I, I want you to kind 668 00:39:27,388 --> 00:39:31,248 of give a, a, a broad overview because I know we can't get into the specifics 669 00:39:31,248 --> 00:39:34,458 of every single thing that Guardian does because it's so comprehensive. 670 00:39:34,458 --> 00:39:36,778 It's like as comprehensive as Revit is itself, right? 671 00:39:36,798 --> 00:39:41,758 It's like, Yep, it does everything, um, but, but at the same time, like, 672 00:39:41,758 --> 00:39:44,918 I want you to give it, give people an idea, like, why is it called Guardian? 673 00:39:44,978 --> 00:39:46,208 Like, what is it guarding? 674 00:39:46,238 --> 00:39:47,928 What, what is going on here? 675 00:39:47,958 --> 00:39:52,408 Um, and, and how is it addressing, um, The dirty little secrets of 676 00:39:52,508 --> 00:39:56,888 every single project that people get into and how nobody wants to 677 00:39:56,888 --> 00:40:02,198 actually say that time matters and it adds up and it is worth something. 678 00:40:02,658 --> 00:40:03,808 What can we do about it? 679 00:40:03,828 --> 00:40:04,048 Right? 680 00:40:04,048 --> 00:40:06,698 Like to me, that's, that's really what we're talking about here. 681 00:40:06,818 --> 00:40:11,448 And we're talking about a tool that kind of helps us address those issues. 682 00:40:11,448 --> 00:40:12,538 I 683 00:40:14,228 --> 00:40:15,908 Chris Shafer: Yep, Parlec. 684 00:40:17,628 --> 00:40:18,148 Yeah, I'll take that. 685 00:40:18,518 --> 00:40:18,818 Yeah. 686 00:40:18,818 --> 00:40:23,988 So, Guardian, um, at its core, what it does, it automates 687 00:40:24,388 --> 00:40:29,208 consistency across standards and processes and best practices. 688 00:40:29,608 --> 00:40:33,993 It educate users in the moment of, you know, what are those best practices? 689 00:40:34,563 --> 00:40:38,473 that firm's standards, best practices and, and, and processes. 690 00:40:39,073 --> 00:40:42,643 Um, but then also provides, you know, actionable insights on how 691 00:40:42,643 --> 00:40:47,273 people are actually utilizing for, to actually execute their projects. 692 00:40:47,773 --> 00:40:54,923 And so we really see that, that standards and process is, is such important 693 00:40:54,923 --> 00:40:56,553 to the culture of what a firm is. 694 00:40:57,023 --> 00:41:02,653 And, and so what Guardian really does is, does it kind of on a almost a 695 00:41:02,653 --> 00:41:10,823 command by command basis under tries to figure out to how are your users 696 00:41:10,843 --> 00:41:15,213 utilizing that command and how does your digital practice, your digital delivery 697 00:41:15,213 --> 00:41:20,373 leaders, how are they working to make sure that everyone understands what are 698 00:41:20,373 --> 00:41:23,663 those standards around those with the process around each and every command. 699 00:41:24,183 --> 00:41:31,353 Um, and in addition to that, you know, it, having the, the 700 00:41:31,353 --> 00:41:33,903 data behind all that, it helps. 701 00:41:34,203 --> 00:41:40,323 It helps the digital practice leaders to understand with this particular 702 00:41:40,323 --> 00:41:43,613 command, and we can just go down the list there of, of all the 703 00:41:43,613 --> 00:41:48,163 different features, um, and commands that, that Guardian is addressing. 704 00:41:48,453 --> 00:41:51,563 By providing that data, it gives them the opportunity to say, well, 705 00:41:51,593 --> 00:41:55,583 I see this amount of people are using this command incorrectly. 706 00:41:55,883 --> 00:41:58,673 Maybe I need to focus our training this week on that. 707 00:41:59,168 --> 00:42:03,928 on that command or, or that process or that best practice. 708 00:42:04,378 --> 00:42:06,598 So fundamentally it's a way of 709 00:42:08,798 --> 00:42:13,678 providing consistent standards process and, and communications around that. 710 00:42:13,918 --> 00:42:20,038 Um, I, I think what most people know Guardian about is, is the command prompts. 711 00:42:20,068 --> 00:42:25,373 When a user goes to execute a command, rather than instantly, Going into that 712 00:42:25,373 --> 00:42:31,273 command, Guardian will prompt the user a customizable message by the firm, which 713 00:42:31,273 --> 00:42:37,543 can also be customized at the project level as well, um, of how, how this 714 00:42:37,543 --> 00:42:41,433 command is to be used, the best practice, the process, and so on and so forth. 715 00:42:41,573 --> 00:42:46,823 And so it's a great tool of just communicating standards, 716 00:42:46,863 --> 00:42:48,333 processes, and best practices. 717 00:42:49,618 --> 00:42:53,918 Evan Troxel: want to raise my hand here and say, okay, that sounds, and I'm no, 718 00:42:53,948 --> 00:42:56,598 no offense, Chris, that sounds terrible. 719 00:42:56,648 --> 00:42:57,498 That sounds terrible. 720 00:42:57,538 --> 00:42:59,608 And because I think people are going to hear that and be like, what do 721 00:42:59,608 --> 00:43:03,038 you, now it sounds like everything's going to take twice as long, right? 722 00:43:03,038 --> 00:43:06,398 Because every time I click on a tool, it's going to prompt me. 723 00:43:06,608 --> 00:43:07,888 And I know that's not how it works. 724 00:43:07,968 --> 00:43:13,593 So I want, I want you guys to, to, to, to, Take that little bit of feedback 725 00:43:13,593 --> 00:43:17,063 right there in the way that you talk about your tool and talk about that because, 726 00:43:17,153 --> 00:43:20,993 because addressing that is definitely going to be a concern for people. 727 00:43:20,993 --> 00:43:24,563 It's like, because I mean, one thing is as a former digital 728 00:43:24,563 --> 00:43:25,913 practice leader myself, right? 729 00:43:25,913 --> 00:43:30,833 It's like, we talk about the difference between handcuffs and freedom 730 00:43:30,853 --> 00:43:32,423 when it comes to standardization. 731 00:43:32,638 --> 00:43:34,368 of processes, right? 732 00:43:34,398 --> 00:43:36,198 And, and the way that we use things. 733 00:43:36,198 --> 00:43:38,848 It's like, some people say, that sounds terrible. 734 00:43:38,848 --> 00:43:40,218 That sounds like handcuffs. 735 00:43:40,468 --> 00:43:44,218 And at the same time, we're, we're saying, okay, but if we reframe it 736 00:43:44,228 --> 00:43:46,808 to say like, okay, now you don't have to think about that stuff anymore 737 00:43:47,038 --> 00:43:49,078 because we've taken care of it. 738 00:43:49,088 --> 00:43:51,168 And now you can go focus on stuff that really matters. 739 00:43:51,358 --> 00:43:53,918 Like that's one, one example, right? 740 00:43:54,058 --> 00:43:56,258 But the things that you're talking about here, it's like, it's not, 741 00:43:57,758 --> 00:44:00,868 It's not slapping you on the hand every time you do something, right? 742 00:44:00,888 --> 00:44:04,638 It's, but, but it is a training tool in the moment. 743 00:44:04,678 --> 00:44:07,988 And I love how you said that, where it's like, it's in the moment. 744 00:44:08,238 --> 00:44:11,808 And it says to, to Parley's point earlier, all I wanted to 745 00:44:11,808 --> 00:44:13,338 do is create a red line, right? 746 00:44:13,338 --> 00:44:15,888 So that I could mark up my, my drawing so that I wouldn't 747 00:44:15,898 --> 00:44:17,178 forget what to come back to. 748 00:44:17,468 --> 00:44:20,368 And it's like, well, and then it, then it enables. 749 00:44:20,398 --> 00:44:25,278 It's a communication to happen for people to understand because what's the ratio 750 00:44:25,278 --> 00:44:27,278 of BIM managers to users out there? 751 00:44:27,318 --> 00:44:28,268 Like what are you guys seeing? 752 00:44:28,268 --> 00:44:29,568 Is it like 50 to one? 753 00:44:29,578 --> 00:44:30,258 Is it bigger? 754 00:44:30,258 --> 00:44:33,118 I don't even, I don't even know where it is, but it doesn't scale. 755 00:44:33,148 --> 00:44:37,038 Everybody knows it doesn't scale to all the problems that happen on a 756 00:44:37,038 --> 00:44:38,908 daily basis with all the team members. 757 00:44:39,248 --> 00:44:41,768 And this is another dirty little secret in the industry, right? 758 00:44:41,768 --> 00:44:43,348 It's like it, that it doesn't scale. 759 00:44:43,678 --> 00:44:48,988 And so we need tools like this to automate that process of. 760 00:44:49,583 --> 00:44:54,593 Engagement and not accruing technical debt over time so that we can get the 761 00:44:54,593 --> 00:44:59,783 value out of these exquisite models that people craft on a daily basis. 762 00:45:00,733 --> 00:45:04,743 And so I, I want you to speak to that point about like, okay, it's not like 763 00:45:04,743 --> 00:45:08,533 just, it's not gonna take twice as long to do this stuff because it's actually 764 00:45:08,563 --> 00:45:12,703 training people to not have to worry about doing it like the wrong way again, right? 765 00:45:13,268 --> 00:45:14,478 Chris Shafer: Yeah, exactly. 766 00:45:14,568 --> 00:45:16,638 Parley Burnett: Chris has some good experience implementing 767 00:45:16,938 --> 00:45:17,908 Chris Shafer: Yes, yes. 768 00:45:17,908 --> 00:45:21,838 Um, you know, having implemented to over 1000 users, I've seen 769 00:45:21,848 --> 00:45:23,198 and heard it all over the years. 770 00:45:23,248 --> 00:45:29,188 Um, but just from my own personal experience, um, you know, I having 771 00:45:29,738 --> 00:45:34,838 been a Revit user, a Guardian user for years, I developed a little saying. 772 00:45:35,188 --> 00:45:37,368 I don't get in a car without fastening my seatbelt. 773 00:45:37,418 --> 00:45:43,523 I don't get into Revit, without having Guardian, um, even as a power user myself, 774 00:45:44,033 --> 00:45:51,653 I've experienced where, hey, our natural tendency is to, you know, to just, to cut 775 00:45:51,713 --> 00:45:56,373 corners sometimes or, you know, I can, I can, I can get away with this, right? 776 00:45:56,413 --> 00:45:57,253 I'll come back to it. 777 00:45:57,633 --> 00:46:01,953 And sometimes those gentle reminders are like, Hey, you're, you know, 778 00:46:01,963 --> 00:46:06,433 we're all prone to making mistakes, especially when we're in a hurry 779 00:46:06,433 --> 00:46:07,723 or under the gun of a deadline. 780 00:46:08,353 --> 00:46:14,593 Um, I actually have a, an interesting, my very first project utilizing Guardian, 781 00:46:14,653 --> 00:46:18,863 um, we, this was a developer driven. 782 00:46:19,073 --> 00:46:22,853 building in, in Boston, you know, very fast pace and whatnot. 783 00:46:22,933 --> 00:46:26,133 And just, just five, you know, 400, 000 square feet. 784 00:46:26,853 --> 00:46:31,113 And we were, it was a really interesting case study here 785 00:46:31,333 --> 00:46:36,403 where, where we had the team. 786 00:46:36,808 --> 00:46:41,098 all operating, um, in the same direction, rowing in the same direction. 787 00:46:41,098 --> 00:46:41,378 Right. 788 00:46:41,888 --> 00:46:47,308 And, and another saying I have said over my career is, you know, Revit's 789 00:46:47,378 --> 00:46:49,128 like death by a thousand cuts, right? 790 00:46:49,388 --> 00:46:52,068 It's never this big thing. 791 00:46:52,278 --> 00:46:55,268 It's always this one little thing, but over the course of a 792 00:46:55,268 --> 00:46:58,918 project, you know, all these little cuts add up to something big. 793 00:46:59,578 --> 00:47:04,648 And what we saw with this project, with the help of Guardian, is we stopped. 794 00:47:04,918 --> 00:47:08,068 Cutting those, those cuts never happened, right? 795 00:47:08,498 --> 00:47:12,258 And so what you saw was you're constantly just moving the 796 00:47:12,258 --> 00:47:13,738 ball down the field, right? 797 00:47:13,738 --> 00:47:17,848 You're going towards your project deadlines more efficiently and you're 798 00:47:18,068 --> 00:47:21,148 in many ways you weren't, you know, fixing mistakes along the way, right? 799 00:47:21,148 --> 00:47:23,408 You weren't being that firefighter that you had mentioned earlier. 800 00:47:24,198 --> 00:47:29,878 It was all about just moving that project forward, everyone in the same direction, 801 00:47:30,328 --> 00:47:36,823 and it And that in the day, um, it was a very tight schedule, a very tight budget. 802 00:47:36,853 --> 00:47:39,533 Being developer driven project is always a tight budget. 803 00:47:40,173 --> 00:47:43,773 We ended up making 17, 17 percent profit on that given 804 00:47:43,773 --> 00:47:46,493 project, which was unheard of. 805 00:47:47,453 --> 00:47:53,023 You just stop doing the little things, the little things that set you back and moving 806 00:47:53,023 --> 00:48:00,263 it forward, that's when you start seeing the real value that That not only Guardian 807 00:48:00,263 --> 00:48:02,553 provides, but also Revit provides, right? 808 00:48:02,583 --> 00:48:06,573 Is, is coming, we talked earlier about the potential that Revit has. 809 00:48:06,973 --> 00:48:09,333 When you're actually getting that potential out of it, some 810 00:48:09,333 --> 00:48:10,653 great things can really happen. 811 00:48:12,568 --> 00:48:17,288 Parley Burnett: And, uh, yeah, I think it's definitely a case of like 812 00:48:17,748 --> 00:48:21,938 how you message that too, right, Chris, like sharing the wins with 813 00:48:21,938 --> 00:48:28,228 the users, um, can really build that consensus, that, that kind of mentality 814 00:48:28,258 --> 00:48:29,808 that this is a good thing for us. 815 00:48:30,638 --> 00:48:32,168 We do talk a lot about, um. 816 00:48:33,088 --> 00:48:33,948 communication. 817 00:48:34,008 --> 00:48:38,558 So like before you put out a dialogue that you kind of communicate to users, 818 00:48:39,138 --> 00:48:40,918 but what that's going to look like. 819 00:48:42,298 --> 00:48:46,028 Um, and then the other thing is, um, 820 00:48:48,448 --> 00:48:52,418 just to shed a little bit of light on some other aspects of Guardian too, because 821 00:48:52,418 --> 00:48:54,228 it's not just like workflow prompts. 822 00:48:54,228 --> 00:48:55,348 It's also like, Hey, 823 00:48:57,508 --> 00:49:01,168 somebody else is syncing their model right now, right? 824 00:49:01,288 --> 00:49:01,708 Evan Troxel: Mm-Hmm. 825 00:49:02,048 --> 00:49:05,178 Parley Burnett: Just, and so users appreciate knowing that so that they can 826 00:49:05,208 --> 00:49:07,008 add themselves to the Guardian queue. 827 00:49:07,818 --> 00:49:13,698 without having to face that like 2x sync time that they would have faced otherwise. 828 00:49:13,838 --> 00:49:17,688 So like, over time they really start to see the benefits of that. 829 00:49:17,848 --> 00:49:22,698 And there's other things behind the scenes like works at automation, things get 830 00:49:22,698 --> 00:49:26,508 put on the work set just automatically as things are placed or drawn. 831 00:49:28,203 --> 00:49:29,323 Parameter prompts. 832 00:49:29,573 --> 00:49:32,443 There's a lot of like automations behind the scenes. 833 00:49:32,463 --> 00:49:37,723 That's, that's what I would like to say is that it's not always a prompt and there's 834 00:49:37,723 --> 00:49:39,443 a reporting component to it as well. 835 00:49:40,283 --> 00:49:42,883 Chris Shafer: One thing I would like to add regarding the prompts and that you 836 00:49:42,883 --> 00:49:46,213 had alluded to, Devin, is like, oh, I'm being slowed down, but that's prompt. 837 00:49:46,913 --> 00:49:51,693 Um, and one of the things, and who I heard this mostly from was the power users. 838 00:49:52,423 --> 00:49:56,123 And, you know, as, as someone who was leading. 839 00:49:57,338 --> 00:50:00,688 You know, the whole firm of, of Revit users is. 840 00:50:01,593 --> 00:50:04,183 I would always remind them, I'm like, well, usually as the power 841 00:50:04,183 --> 00:50:08,393 user, you're the person responsible for fixing the mistakes of others. 842 00:50:09,053 --> 00:50:17,173 And so while, yes, you may have a prompt that, that pops up once every, you know, 843 00:50:17,683 --> 00:50:21,433 two hours when you're working in the day and that prompt takes you five seconds 844 00:50:21,433 --> 00:50:24,123 to read and go and to clear and whatnot, 845 00:50:26,473 --> 00:50:30,133 that is much less time it takes than cleaning up the 846 00:50:30,133 --> 00:50:31,423 mistakes of others on your team. 847 00:50:31,523 --> 00:50:34,433 As the power user, you're the one who's responsible for. 848 00:50:34,698 --> 00:50:38,728 doing the cleanup, doing the fixing, and that takes a lot more time. 849 00:50:38,768 --> 00:50:43,798 And so the peace of mind knowing that the others on your team who are 850 00:50:43,968 --> 00:50:48,428 prone to making mistakes just from inexperience or not knowing or knowing 851 00:50:49,378 --> 00:50:54,438 your firm standards or whatever it may be, you know, just that actually 852 00:50:54,438 --> 00:50:57,228 creates more time for you and whatnot. 853 00:50:57,658 --> 00:51:01,343 Um, but then ultimately there are tools within Guardian to you 854 00:51:01,343 --> 00:51:03,893 know, for your power users saying, well, you know what you're doing. 855 00:51:03,893 --> 00:51:05,843 You don't, you know, you don't need this as well. 856 00:51:05,893 --> 00:51:12,283 So, you know, there's coming back to finding that balance of how do you 857 00:51:12,293 --> 00:51:15,983 communicate, but not over communicating or being too much of a burden on this user. 858 00:51:15,983 --> 00:51:18,953 So, you know, there's something as party alluded to earlier that we're always 859 00:51:18,963 --> 00:51:24,633 striving for is, is how do we, how do we figure out how to lessen that impact 860 00:51:26,183 --> 00:51:28,953 Evan Troxel: Yeah, I think part of this is, you have to communicate this 861 00:51:28,973 --> 00:51:31,493 to all the different levels, right? 862 00:51:31,493 --> 00:51:35,543 You've got, you've got the user level, like, and then there's a spectrum there, 863 00:51:35,543 --> 00:51:37,933 beginner to expert, um, user level. 864 00:51:38,593 --> 00:51:41,363 Then there's technical management leadership, and then 865 00:51:41,363 --> 00:51:42,933 there's, like, firm leadership. 866 00:51:43,263 --> 00:51:48,423 And just talking about the value proposition at every one of these 867 00:51:48,423 --> 00:51:53,083 levels has got to be, you know, I mean, I'm interested to hear from 868 00:51:53,083 --> 00:51:56,913 you guys how you do that because I think a lot of technology vendors 869 00:51:56,973 --> 00:51:58,713 need to do the same thing, right? 870 00:51:58,743 --> 00:52:06,133 Um, and, and I'm just curious how you do it because I'm reading this book by Cal 871 00:52:06,133 --> 00:52:11,293 Newport and, and the idea, like he's, he's had a few different topics kind of all 872 00:52:11,293 --> 00:52:17,408 around this idea of, Pseudo productivity, uh, and doing deep work, right? 873 00:52:17,428 --> 00:52:19,978 Like, like our life is full of distraction. 874 00:52:20,368 --> 00:52:22,868 We've got teams or Slack running all the time. 875 00:52:22,868 --> 00:52:24,098 There's constant messaging. 876 00:52:24,108 --> 00:52:26,088 There's email, there's notifications. 877 00:52:26,088 --> 00:52:27,148 There's all these things. 878 00:52:27,708 --> 00:52:28,848 And yeah, I'm busy. 879 00:52:29,248 --> 00:52:30,378 I'm busy doing email. 880 00:52:30,388 --> 00:52:33,098 Like nobody became an architect to do email. 881 00:52:33,208 --> 00:52:33,568 Right. 882 00:52:33,658 --> 00:52:38,968 Um, but that is what, how much of our day is spent like just. 883 00:52:40,183 --> 00:52:42,003 Addressing the inbox, right? 884 00:52:42,103 --> 00:52:43,133 New things to do. 885 00:52:43,173 --> 00:52:44,583 Like that's what your inbox is, right? 886 00:52:44,583 --> 00:52:47,933 It's new things for you to do given by somebody else who didn't have permission 887 00:52:47,973 --> 00:52:49,253 to tell you to do something, right? 888 00:52:49,253 --> 00:52:52,783 It's just like, but that, that's what it becomes, right? 889 00:52:52,783 --> 00:52:55,403 And, and firms don't address like firm leadership. 890 00:52:55,413 --> 00:52:59,703 If they, if they actually counted how much time people spent in Outlook 891 00:52:59,743 --> 00:53:01,623 every single day, they'd be like, what? 892 00:53:02,133 --> 00:53:04,833 We're not doing projects when we're, when we're doing Outlook. 893 00:53:04,843 --> 00:53:09,713 Like you may be addressing a client's concerns, or you may be kind In a 894 00:53:09,713 --> 00:53:14,313 roundabout way, you know, getting something done by assigning somebody a 895 00:53:14,313 --> 00:53:18,003 task or, you know, consult, you're talking to a consultant or something like that. 896 00:53:18,013 --> 00:53:23,893 But in an inordinate amount of time gets spent doing email, which 897 00:53:23,893 --> 00:53:25,923 is not doing architecture, right? 898 00:53:25,933 --> 00:53:29,593 So if, and we don't talk about that, like we don't talk about how 899 00:53:29,593 --> 00:53:31,123 much time people are just spending. 900 00:53:31,988 --> 00:53:35,478 Chatting, which is, you know, maybe it is project oriented when they're 901 00:53:35,598 --> 00:53:39,988 chatting on teams or slack or something, but a lot of times it isn't right. 902 00:53:39,988 --> 00:53:43,698 And so, and it's not like we need to be 100 percent productive all the time. 903 00:53:43,708 --> 00:53:47,148 That's not what I'm saying, but there is a huge amount of like, we just don't 904 00:53:47,148 --> 00:53:49,188 address the waste that's going on here. 905 00:53:49,558 --> 00:53:53,428 And so from a leadership, like people who do the work know 906 00:53:53,458 --> 00:53:54,858 exactly what I'm talking about. 907 00:53:54,888 --> 00:53:56,178 It happens all the time. 908 00:53:56,228 --> 00:53:57,408 We're all guilty of it. 909 00:53:57,528 --> 00:53:59,458 Um, and at the same time, we're, we're. 910 00:53:59,648 --> 00:54:02,518 Quote unquote using these tools to get work done, but we're kind 911 00:54:02,518 --> 00:54:03,998 of not at the same time, right? 912 00:54:04,008 --> 00:54:08,748 And so from a messaging to the leadership standpoint when you guys talk about 913 00:54:08,878 --> 00:54:12,293 addressing Waste that's going on. 914 00:54:12,313 --> 00:54:15,863 And what is the return on that investment of getting that time back? 915 00:54:15,863 --> 00:54:17,493 How do you communicate to those people? 916 00:54:17,493 --> 00:54:20,603 Because to me, like they're the decision makers in the firms, like 917 00:54:21,303 --> 00:54:24,523 users of any level can go say, Hey, like I heard about this thing. 918 00:54:24,533 --> 00:54:29,703 It sounds incredible to actually get us all on the same page and, and, and 919 00:54:29,703 --> 00:54:33,123 enable us to get more value out of these intricate, incredible models 920 00:54:33,133 --> 00:54:37,983 that we're building over many years and it's standardizing our data and it's 921 00:54:37,993 --> 00:54:39,623 standardizing, you know, when, when. 922 00:54:40,868 --> 00:54:43,088 Sally goes from this project to that project. 923 00:54:43,108 --> 00:54:45,938 She's going to know right where to pick up because we're developing these 924 00:54:45,938 --> 00:54:49,028 with the same standards and there's lots of value to be gained in that. 925 00:54:49,038 --> 00:54:51,958 How do you communicate that to leadership so that they actually understand that? 926 00:54:52,758 --> 00:54:57,158 Chris Shafer: So I'm going to provide a little antidote here to start 927 00:54:57,168 --> 00:55:04,628 answering that question is when when I first implemented our model health 928 00:55:04,628 --> 00:55:09,848 strategy and Guardian was a vital tool in that process with my previous firm. 929 00:55:09,848 --> 00:55:10,533 It. 930 00:55:12,613 --> 00:55:18,523 In my role, and I guess my, my boss who I reported to, we never felt like we had 931 00:55:18,523 --> 00:55:22,123 the, the authority to actually require it. 932 00:55:22,903 --> 00:55:27,603 And then after a couple of years of doing this on a, I wouldn't say a 933 00:55:27,603 --> 00:55:32,223 voluntary basis, but we were, we were really focused on our largest projects, 934 00:55:32,583 --> 00:55:37,033 um, getting the teams to utilize, uh, utilize the model health strategy. 935 00:55:37,033 --> 00:55:38,823 Again, Guardian was a critical part of that. 936 00:55:39,413 --> 00:55:45,383 And, um, And that equate that covered about 60 percent of our firm and and as 937 00:55:45,383 --> 00:55:51,103 we are wanting to do and grow and, you know, ask for for for more money to do 938 00:55:51,213 --> 00:55:56,563 other things as well, we were presenting the savings that we were seeing with. 939 00:55:57,003 --> 00:55:59,923 And with our model health strategy and one of the things that we were 940 00:55:59,923 --> 00:56:04,863 presenting was just say sync times party had mentioned earlier is we were 941 00:56:05,213 --> 00:56:06,783 through that model health strategy. 942 00:56:06,783 --> 00:56:12,813 We were able to reduce our sync times by over a minute across the firm. 943 00:56:13,323 --> 00:56:14,873 Um, and when. 944 00:56:15,153 --> 00:56:15,433 each 945 00:56:15,593 --> 00:56:15,853 Parley Burnett: sync. 946 00:56:16,243 --> 00:56:16,923 Chris Shafer: each sync. 947 00:56:17,613 --> 00:56:24,063 And so when you look at that across the board, you know, that equated 948 00:56:24,063 --> 00:56:27,023 to almost a 600, 000 a year savings. 949 00:56:27,063 --> 00:56:31,483 Just, you know, obviously not all that is seen or gained or whatnot. 950 00:56:32,753 --> 00:56:36,193 The reality and coming back to dirty little secrets, everyone knows as 951 00:56:36,193 --> 00:56:41,053 well, people kick sync and then they go check their Outlook or they go to their 952 00:56:41,053 --> 00:56:42,893 IMs or they go get a cup of coffee. 953 00:56:42,893 --> 00:56:43,123 Right. 954 00:56:43,453 --> 00:56:43,763 So. 955 00:56:44,488 --> 00:56:46,168 That two minute, right? 956 00:56:46,188 --> 00:56:51,328 So that two minute syncs ends up being 10, 15, even longer, right? 957 00:56:51,528 --> 00:56:52,758 It becomes a distraction. 958 00:56:53,478 --> 00:56:54,128 And so 959 00:56:54,358 --> 00:56:55,538 Evan Troxel: doing something else, right? 960 00:56:55,848 --> 00:56:57,358 Chris Shafer: exactly, exactly. 961 00:56:57,358 --> 00:57:03,088 So how do you eliminate the simple setbacks, the simple distractions 962 00:57:03,358 --> 00:57:05,348 that lead to larger distractions? 963 00:57:05,368 --> 00:57:13,663 And one is, is, is, is quite, I'm going to say, you go down the list of so much 964 00:57:13,663 --> 00:57:19,603 of what Guardian does and you start looking at how, how much this actually 965 00:57:19,603 --> 00:57:26,113 costs a company by not preventing, you know, mistakes or misuse or, or whatever 966 00:57:26,113 --> 00:57:27,993 it may be, or the lack of standards. 967 00:57:28,493 --> 00:57:32,943 And, And on its surface, the ROI is just instant. 968 00:57:33,033 --> 00:57:36,393 It, you're just like, wow, you know, this, this pays for itself 969 00:57:36,503 --> 00:57:38,483 in a matter of weeks here. 970 00:57:39,293 --> 00:57:45,043 But then the layer of additional waste that comes out of this, you know, 971 00:57:45,053 --> 00:57:49,483 the, the secondary, the tertiary, um, downstream impact, you know, 972 00:57:49,493 --> 00:57:51,463 that's not really accounted for that. 973 00:57:51,533 --> 00:57:56,063 Um, and, and a lot of times making this argument to leadership and say, 974 00:57:56,063 --> 00:58:01,973 Hey, having everyone operating in different ways And we're not even, 975 00:58:02,203 --> 00:58:04,653 don't even have the word to bring up the word standards, because even a lot 976 00:58:04,653 --> 00:58:09,543 of leadership, they start to like, Oh, here goes the standards thing again. 977 00:58:09,543 --> 00:58:09,833 Right? 978 00:58:10,153 --> 00:58:16,623 Um, just saying, Hey, just, just having people just all operating in the same 979 00:58:16,623 --> 00:58:21,253 direction and doing things really in the same way, really being a team and 980 00:58:21,253 --> 00:58:26,273 the way that they do things and making sure the needs and the of the project 981 00:58:26,373 --> 00:58:29,943 and the needs of the team are being met throughout the course of the project. 982 00:58:30,663 --> 00:58:34,713 That alone has tremendous value and it's measurable value. 983 00:58:35,023 --> 00:58:41,323 Um, and And when you see it in the profitability, um, on projects, you 984 00:58:41,323 --> 00:58:44,423 know, that makes it, you know, makes it an easy, sometimes an easy sell. 985 00:58:45,688 --> 00:58:47,788 Parley Burnett: And Chris, you even got your hand slapped a 986 00:58:47,788 --> 00:58:50,278 little bit by leadership once they understood that, right? 987 00:58:50,308 --> 00:58:50,618 They're like, 988 00:58:50,653 --> 00:58:51,043 Chris Shafer: Yeah. 989 00:58:51,303 --> 00:58:51,683 Yes. 990 00:58:52,223 --> 00:58:52,663 Yes. 991 00:58:52,798 --> 00:58:54,838 Parley Burnett: why aren't we using this on every project? 992 00:58:55,463 --> 00:58:55,783 Chris Shafer: yeah. 993 00:58:55,883 --> 00:58:59,453 Um, where, like I said before, I never felt in my role that I had the 994 00:58:59,453 --> 00:59:04,013 authority and, and, and my boss, who I directly reported to didn't have the 995 00:59:04,023 --> 00:59:06,163 authority to say, no, this is mandatory. 996 00:59:06,673 --> 00:59:10,383 And the president was like, why aren't we doing this on? 997 00:59:10,423 --> 00:59:14,863 This is such, this provides such tremendous value to the company. 998 00:59:15,343 --> 00:59:17,673 Why aren't we doing it on every project? 999 00:59:17,673 --> 00:59:19,443 Why isn't everyone following this? 1000 00:59:20,213 --> 00:59:24,893 And I think that's something a lot of people in that digital practice role. 1001 00:59:25,703 --> 00:59:29,793 They're kind of caught between right there They're given this tremendous 1002 00:59:29,793 --> 00:59:34,973 responsibility to make sure the firm the fundamentals of the firm 1003 00:59:35,003 --> 00:59:39,463 are being Executed but they're not given the authority to do so 1004 00:59:40,078 --> 00:59:40,348 Evan Troxel: Yeah. 1005 00:59:40,998 --> 00:59:43,468 Chris Shafer: And, and what Guardian does is, 1006 00:59:45,848 --> 00:59:51,238 is it ensures that the best practices, the standards, but more importantly, the 1007 00:59:51,238 --> 00:59:56,858 knowledge and experience of your digital practice people are being, being gained by 1008 00:59:56,868 --> 00:59:59,908 everyone, all the time, by every project. 1009 01:00:00,678 --> 01:00:06,258 And, and there's a tremendous value about having that knowledge and expertise right 1010 01:00:06,268 --> 01:00:08,208 there as people are doing their work. 1011 01:00:08,668 --> 01:00:11,088 And not being, and not being the firefighters, right? 1012 01:00:11,098 --> 01:00:14,618 You know, preventing mistakes before they happen versus being the 1013 01:00:14,618 --> 01:00:16,608 person for cleaning up the mistakes. 1014 01:00:17,198 --> 01:00:17,668 Evan Troxel: Right. 1015 01:00:18,958 --> 01:00:24,978 It seems like that kind of just in time methodology of of providing. 1016 01:00:25,673 --> 01:00:30,213 Insight prompts, um, you know, action items, training. 1017 01:00:30,333 --> 01:00:33,283 There's a lot of different ways you could kind of categorize these things 1018 01:00:33,303 --> 01:00:38,993 is so important because I mean, to your point earlier about kind of, you 1019 01:00:38,993 --> 01:00:41,943 know, technical debt and just saying, you know, I'm incentivized to figure 1020 01:00:41,943 --> 01:00:45,023 out a work around right now and I'll come back and I'll fix it later. 1021 01:00:45,433 --> 01:00:48,423 And then you get distracted and you're doing a bunch of other stuff. 1022 01:00:48,453 --> 01:00:48,963 And then. 1023 01:00:49,768 --> 01:00:51,298 It's, it snowballs, right? 1024 01:00:51,308 --> 01:00:54,758 Like you forget about this one and then somebody builds on top of that, 1025 01:00:54,758 --> 01:00:57,488 which relies on what was already done and it was already done wrong. 1026 01:00:57,488 --> 01:01:00,178 So now we have to do it a little bit wrong, some more, right? 1027 01:01:00,788 --> 01:01:03,528 And then, and that, that just keeps snowballing. 1028 01:01:03,538 --> 01:01:07,798 And at some point it's like, who's going to fix this and what do we do? 1029 01:01:07,798 --> 01:01:12,708 I mean, how many times early on in those, in those early days, Chris, 2008, 2009, 1030 01:01:12,718 --> 01:01:17,038 right, did you say, okay, export to AutoCAD right at this point, because we 1031 01:01:17,038 --> 01:01:19,533 just can't We can't deal anymore, right? 1032 01:01:19,543 --> 01:01:21,933 Like everybody's, everybody who's been doing this a while 1033 01:01:21,933 --> 01:01:24,003 has lived through that, right? 1034 01:01:24,433 --> 01:01:27,433 And at some point, like now, now that's not an option, right? 1035 01:01:27,433 --> 01:01:33,453 It's like now we just are completely weighed down for the rest of the 1036 01:01:33,453 --> 01:01:35,463 project because it gets so bad. 1037 01:01:35,483 --> 01:01:40,313 And I'm, I'm just curious, like what other kinds of examples you have besides like 1038 01:01:40,313 --> 01:01:46,483 sync times when it comes to communicating, you know, so, so a more fundamental 1039 01:01:46,483 --> 01:01:50,953 question is like, Are architects very good at like, valuing their own time? 1040 01:01:51,053 --> 01:01:54,413 And I, I tend to think no, because we're all trained to like, just solve 1041 01:01:54,413 --> 01:01:56,103 the problem, no matter what it takes. 1042 01:01:56,123 --> 01:01:57,483 Like we're up for the challenge. 1043 01:01:57,953 --> 01:01:59,233 We know that there's an answer. 1044 01:01:59,233 --> 01:02:01,763 We'll figure it out if we just try hard enough. 1045 01:02:02,588 --> 01:02:06,708 And everybody, like to your point earlier, Chris, like everybody goes to 1046 01:02:06,708 --> 01:02:08,628 work wanting to do a good job, right? 1047 01:02:08,638 --> 01:02:11,808 Like they don't, they're not going in saying, man, I'm going to take a bunch 1048 01:02:11,808 --> 01:02:13,188 of shortcuts and leave early today. 1049 01:02:13,198 --> 01:02:15,428 Like that doesn't, doesn't really happen, right? 1050 01:02:15,438 --> 01:02:17,378 So, so people want it there. 1051 01:02:17,388 --> 01:02:18,578 They want to do the right thing. 1052 01:02:18,578 --> 01:02:22,068 But at the same time, like they do have the real constraints of deadlines 1053 01:02:22,088 --> 01:02:24,488 and, and sync times is one example. 1054 01:02:24,498 --> 01:02:25,028 But like. 1055 01:02:26,108 --> 01:02:30,438 When it comes to learning how to value our own time, let's put some values 1056 01:02:30,438 --> 01:02:34,108 on that right now and like, what are some other kinds of qualitative or 1057 01:02:34,108 --> 01:02:39,708 quantitative metrics, either category there that you're really seeing that 1058 01:02:39,848 --> 01:02:44,928 tools like this can, can provide to the users and the firm leadership alike. 1059 01:02:46,638 --> 01:02:47,078 Chris Shafer: Yeah. 1060 01:02:47,158 --> 01:02:50,738 Um, one of the things I would just quickly hit on, we have a feature 1061 01:02:50,738 --> 01:02:56,198 called delete protections, um, where, so for instance, is when someone goes 1062 01:02:56,198 --> 01:03:00,028 to delete something and there's a, an item that is hosted to that element. 1063 01:03:02,098 --> 01:03:05,388 Well, everyone has conditioned themselves to ignore the yellow 1064 01:03:05,388 --> 01:03:06,898 warning box that Revit produces. 1065 01:03:07,278 --> 01:03:08,428 And just hit delete, right? 1066 01:03:08,698 --> 01:03:10,398 Evan Troxel: even sees that corner of the screen. 1067 01:03:10,663 --> 01:03:11,493 Parley Burnett: If it shows up. 1068 01:03:12,353 --> 01:03:12,703 Yeah. 1069 01:03:13,228 --> 01:03:13,588 Chris Shafer: Right. 1070 01:03:14,288 --> 01:03:15,378 Evan Troxel: Complete blind spot. 1071 01:03:16,578 --> 01:03:22,358 Chris Shafer: and, and so, so what Guardian has done is provided a prompt 1072 01:03:22,378 --> 01:03:26,448 that shows you everything that's being deleted and all it does, and, 1073 01:03:26,448 --> 01:03:30,378 and, and I've heard you mentioned this another podcast, you have to 1074 01:03:30,378 --> 01:03:32,618 go, you have to go slow to go fast. 1075 01:03:33,078 --> 01:03:38,538 This is slowing people down just enough to say, yes, I intentionally. 1076 01:03:38,833 --> 01:03:42,583 want to delete all this other stuff that I don't see in front of me, right? 1077 01:03:42,688 --> 01:03:43,268 Evan Troxel: You're right. 1078 01:03:44,253 --> 01:03:46,193 Chris Shafer: Um, and, and 1079 01:03:46,328 --> 01:03:49,528 Evan Troxel: think I shared a story with you where every day I'd come into work, 1080 01:03:49,538 --> 01:03:54,238 and the main stair in a three story school classroom building was gone. 1081 01:03:54,448 --> 01:03:54,988 Every day. 1082 01:03:55,998 --> 01:03:58,308 And it was like, somebody was deleting something. 1083 01:03:58,308 --> 01:04:01,118 They had no idea that somebody else had pinned another out 1084 01:04:01,178 --> 01:04:02,608 the stair to that element. 1085 01:04:02,708 --> 01:04:06,168 And they were like, this, this element does not need to be in here. 1086 01:04:06,178 --> 01:04:09,858 Like it, but, and so, so every day we'd roll that model back 1087 01:04:09,888 --> 01:04:13,098 to grab that piece out of it and bring it back into the new model. 1088 01:04:13,628 --> 01:04:15,928 And then the next day it'd be gone again, because somebody would be 1089 01:04:15,928 --> 01:04:18,638 like, what, what I thought I'd delete, I'm going to delete it again. 1090 01:04:18,818 --> 01:04:19,098 Right. 1091 01:04:19,108 --> 01:04:19,938 And, and it's gone. 1092 01:04:20,198 --> 01:04:23,953 And so to your, to your point, it's like, if you don't know, You're, you're not 1093 01:04:23,953 --> 01:04:27,673 doing it wrong on purpose, but if you don't know, I mean, all you're doing is 1094 01:04:27,673 --> 01:04:31,293 saying like, Hey, here's some additional context you might want to be aware of. 1095 01:04:32,213 --> 01:04:32,983 Chris Shafer: that's exactly right. 1096 01:04:33,033 --> 01:04:36,393 And, and it is just communication, right? 1097 01:04:36,393 --> 01:04:36,973 Communication. 1098 01:04:36,983 --> 01:04:41,638 Hey, these are, these are the things, because we, we understand, Many of 1099 01:04:41,638 --> 01:04:45,048 us understand with Revit, I, I call it the butterfly effect, right? 1100 01:04:45,048 --> 01:04:48,438 You touch one thing and something on the other side of the model is, is impacted. 1101 01:04:48,448 --> 01:04:51,938 A lot of people just fundamentally don't understand that about Revit, right? 1102 01:04:52,238 --> 01:04:55,538 There are things outside of your immediate view that you're impacting. 1103 01:04:56,068 --> 01:04:58,988 And, and all we're doing is bringing awareness to that. 1104 01:04:59,488 --> 01:05:05,158 And we're seeing that in the data, how, how frequent people are actually saying. 1105 01:05:05,483 --> 01:05:07,733 No, I don't want to delete all this. 1106 01:05:07,733 --> 01:05:08,043 Right? 1107 01:05:08,373 --> 01:05:15,763 Um, and so when we, so I don't have the exact numbers off the top of my head on 1108 01:05:15,773 --> 01:05:19,733 how much this is being used, but this is one of the most common data points that 1109 01:05:19,733 --> 01:05:23,683 we see is people just have stopped, um, 1110 01:05:23,833 --> 01:05:25,993 Evan Troxel: Well, and if you use my story as an example, like 1111 01:05:26,003 --> 01:05:29,053 every single day, we're going back and opening the old model. 1112 01:05:29,083 --> 01:05:30,233 We're pulling that piece out. 1113 01:05:30,243 --> 01:05:30,833 We're copying it. 1114 01:05:30,833 --> 01:05:32,923 We're pasting it into every single day. 1115 01:05:32,933 --> 01:05:35,873 And then somebody else is finding that element and deleting it every 1116 01:05:35,873 --> 01:05:37,903 single day for a week, right? 1117 01:05:37,913 --> 01:05:41,863 And it's like, okay, well, there's, that's just one version of, of. 1118 01:05:42,408 --> 01:05:44,698 you know, why this kind of thing exists, right? 1119 01:05:44,728 --> 01:05:48,288 And it's like, it is, it is an actual amount of time. 1120 01:05:48,288 --> 01:05:49,388 It is not incidental. 1121 01:05:49,963 --> 01:05:50,223 Chris Shafer: right? 1122 01:05:50,223 --> 01:05:56,638 And coming back to your example is, is And why does someone keep on repeating that? 1123 01:05:56,658 --> 01:06:00,418 Because they don't know that they're, they're deleting the entire 1124 01:06:00,418 --> 01:06:01,638 stair while we're at it, right? 1125 01:06:02,058 --> 01:06:09,228 And so, having the information about who deleted it, when, and where, and 1126 01:06:09,228 --> 01:06:16,458 what not, provides the BIM manager, the model manager, to, hey, this so and so 1127 01:06:16,458 --> 01:06:21,248 went and deleted the stair, let's go have a conversation with them about, 1128 01:06:21,258 --> 01:06:24,948 hey, I understand that you're just, you weren't trying to delete the stair, 1129 01:06:24,948 --> 01:06:26,688 you're only trying to delete this, right? 1130 01:06:27,608 --> 01:06:31,468 This provides an opportunity to have an educational moment and say, well, 1131 01:06:32,388 --> 01:06:37,368 by not knowing that they're deleting this shows a, a, a fundamental 1132 01:06:37,378 --> 01:06:41,508 misunderstanding of how Revit works and also opens the opportunity to have 1133 01:06:41,508 --> 01:06:45,418 a teaching moment and say, Hey, this is, this is the way, say, annotation 1134 01:06:45,418 --> 01:06:47,328 and Revit work and so on and so forth. 1135 01:06:47,338 --> 01:06:47,588 Right? 1136 01:06:47,938 --> 01:06:51,288 Um, you know, annotations, views, specific, well, model elements 1137 01:06:51,288 --> 01:06:52,773 is, You know, in every view. 1138 01:06:52,813 --> 01:06:57,423 Um, and you know, those type of things, you know, a lot of that is, is missed. 1139 01:06:57,433 --> 01:07:00,803 You know, those simple opportunities to teach are missed. 1140 01:07:01,143 --> 01:07:06,163 Um, and by not knowing and kind of sweeping it under the rug 1141 01:07:06,183 --> 01:07:07,583 actually doesn't really help. 1142 01:07:09,113 --> 01:07:12,643 Anyone in that situation, and especially the person, um, the person 1143 01:07:12,643 --> 01:07:13,953 who's deleting the stare, right? 1144 01:07:13,973 --> 01:07:16,913 No one, no one wants to make that mistake, right? 1145 01:07:17,283 --> 01:07:21,823 Um, and so have an opportunity to, to help people before they get 1146 01:07:21,823 --> 01:07:25,813 into that situation is, we feel is like the, the better opportunity 1147 01:07:25,813 --> 01:07:27,263 or the better position to be in. 1148 01:07:27,668 --> 01:07:27,948 Evan Troxel: Yeah. 1149 01:07:28,383 --> 01:07:32,063 Parley Burnett: We've, we've heard from a lot of interns and that junior 1150 01:07:32,063 --> 01:07:38,213 level of designer, Brevitt user, um, appreciate the fact that the 1151 01:07:38,213 --> 01:07:41,053 guardrails are up right to that point. 1152 01:07:41,083 --> 01:07:42,563 Nobody wants to make the mistake. 1153 01:07:43,503 --> 01:07:47,233 Um, on that feature, the number, Chris, is about 50 percent of 1154 01:07:47,263 --> 01:07:49,423 the time users are canceling. 1155 01:07:49,683 --> 01:07:55,803 So, so we do track, um, the cancel rate on every kind of prompt, um, which is 1156 01:07:55,803 --> 01:07:58,753 incredible information to show leadership. 1157 01:07:58,763 --> 01:08:03,153 That's another way that we kind of go up there, Evan, and kind of inform 1158 01:08:03,153 --> 01:08:04,743 them about what Guardian's doing. 1159 01:08:05,883 --> 01:08:09,243 Um, yeah, 50 percent and the numbers aren't small too. 1160 01:08:09,283 --> 01:08:13,563 We're seeing a lot of cancels and it does track the actual elements 1161 01:08:13,723 --> 01:08:15,083 that would have been deleted. 1162 01:08:15,848 --> 01:08:19,868 So when you see that, there's a lot of work product that 1163 01:08:20,127 --> 01:08:21,337 would have gone out the window. 1164 01:08:21,848 --> 01:08:22,228 Evan Troxel: Right. 1165 01:08:22,608 --> 01:08:23,497 Parley Burnett: Um, another 1166 01:08:23,698 --> 01:08:29,798 Evan Troxel: gotta be, I'm interested how you talk to firm leaders who say, what do 1167 01:08:29,827 --> 01:08:34,778 you mean I have to get another piece of software to plug all these holes in the 1168 01:08:34,778 --> 01:08:37,207 main software we use to deliver projects? 1169 01:08:37,238 --> 01:08:42,603 Like, I mean, that's gotta be a sentiment of, you know, You know, I've I don't 1170 01:08:42,603 --> 01:08:46,863 know what, you know, we've got to be frustration there for sure, right? 1171 01:08:47,143 --> 01:08:50,513 But, I mean, it's great, great for you to be able to create a business out of 1172 01:08:50,513 --> 01:08:55,783 all the holes that do exist, but the, the platform is not solving these problems. 1173 01:08:55,813 --> 01:08:58,582 And that's got to be a little disheartening for, for people to say 1174 01:08:58,582 --> 01:09:03,403 what, you know, we already spend probably the biggest chunk of our software budget 1175 01:09:03,702 --> 01:09:07,872 on this platform that everybody uses differently in very different ways, you 1176 01:09:07,983 --> 01:09:10,042 know, and, and, and there's all these. 1177 01:09:10,743 --> 01:09:14,903 potential problems that just creep up here and there. 1178 01:09:15,403 --> 01:09:18,002 And now I've got to get this other thing to help do that. 1179 01:09:18,103 --> 01:09:21,093 I mean, what, what do you, how's the story go? 1180 01:09:21,443 --> 01:09:22,823 How's the communication go around that? 1181 01:09:26,138 --> 01:09:33,028 Parley Burnett: I mean, back to that example of, um, CAD and, you know, like, 1182 01:09:35,068 --> 01:09:37,728 Let's, let's just print this all to CAD, right? 1183 01:09:37,948 --> 01:09:39,268 And kind of scrap it, 1184 01:09:39,573 --> 01:09:39,943 Evan Troxel: Right. 1185 01:09:40,358 --> 01:09:41,318 Parley Burnett: export to CAD. 1186 01:09:42,077 --> 01:09:47,198 I think there's been enough of that in the past that, um, a lot of 1187 01:09:47,218 --> 01:09:51,917 leadership does feel like the promise of Revit hasn't been realized, right? 1188 01:09:52,728 --> 01:09:54,108 And it's unfortunate. 1189 01:09:54,288 --> 01:09:56,348 I wish it wasn't like that. 1190 01:09:57,528 --> 01:10:03,138 Um, I think we, we try to convey that we're a complement to the tool and 1191 01:10:03,148 --> 01:10:07,723 providing a level of customization that, like, Um, a company like 1192 01:10:07,723 --> 01:10:13,702 Autodesk isn't likely to, um, who knows, um, seek, seek after providing. 1193 01:10:15,553 --> 01:10:16,873 What's your take on that, Chris? 1194 01:10:17,023 --> 01:10:17,393 Chris Shafer: Yeah. 1195 01:10:17,763 --> 01:10:23,728 And, and if you think about it, is Revit's designed to, to the 1196 01:10:23,798 --> 01:10:26,448 tallest skyscrapers in the world to 1197 01:10:26,663 --> 01:10:26,913 Evan Troxel: Yeah. 1198 01:10:27,178 --> 01:10:28,658 Chris Shafer: residential sheds, right? 1199 01:10:28,698 --> 01:10:34,028 Um, and, and, and a little inside joke. 1200 01:10:34,068 --> 01:10:38,848 Um, um, and, and everything in between, right? 1201 01:10:38,868 --> 01:10:44,088 And, and how do you, how do you create a tool that has to work? 1202 01:10:44,378 --> 01:10:45,348 that broadly. 1203 01:10:46,008 --> 01:10:52,248 And, but then so specifically for a firm that does a residential versus a firm 1204 01:10:52,248 --> 01:10:54,658 that does healthcare specifically, right? 1205 01:10:54,978 --> 01:11:02,528 Um, I don't know how Autodesk, um, could do it, um, in a single platform. 1206 01:11:02,548 --> 01:11:06,788 And then I think that's where Guardian really comes in is like, well, Guardian 1207 01:11:06,788 --> 01:11:12,103 is really providing that layer of your firm's culture, your standards, your 1208 01:11:12,103 --> 01:11:17,973 processes to that where you can customize basically how your users are using Revit 1209 01:11:18,313 --> 01:11:23,863 to deliver projects in the way that you want to, um, and, and not have this 1210 01:11:23,863 --> 01:11:27,863 sort of open, open book or open process. 1211 01:11:28,083 --> 01:11:33,213 Um, so in, in many ways, and this is something that I've heard over the, 1212 01:11:33,313 --> 01:11:37,403 over the years, um, whether it was in my previous firm or, you know, 1213 01:11:37,952 --> 01:11:41,903 here with Guardian is, is there's a, there's a level of comfort and you, 1214 01:11:41,903 --> 01:11:43,413 you had mentioned freedom, right? 1215 01:11:43,423 --> 01:11:45,643 There's a level of comfort knowing that. 1216 01:11:47,968 --> 01:11:53,558 A lot of this has already been figured out you, you have the 1217 01:11:53,558 --> 01:11:56,818 runway to focus on your job, right? 1218 01:11:57,008 --> 01:12:01,538 You know, the standards, the processes, everyone doing the things in the 1219 01:12:01,538 --> 01:12:03,768 same way that's taken care of. 1220 01:12:03,818 --> 01:12:06,068 And then you can focus on doing your job. 1221 01:12:08,058 --> 01:12:08,358 Evan Troxel: Yeah. 1222 01:12:08,588 --> 01:12:09,188 Interesting. 1223 01:12:09,708 --> 01:12:14,138 I, I know that this, this is sounding, I don't know, maybe people think 1224 01:12:14,138 --> 01:12:15,238 it sounds too good to be true. 1225 01:12:15,258 --> 01:12:17,708 I mean, everybody has that story. 1226 01:12:17,738 --> 01:12:22,608 I have this, I hear this story from my wife all the time who literally 1227 01:12:22,608 --> 01:12:25,068 hates using Revit every single day. 1228 01:12:25,418 --> 01:12:28,488 And, and I know not every, there's a lot of people who love using 1229 01:12:28,488 --> 01:12:31,363 Revit every single day, but I, I do want to, like, to your point. 1230 01:12:31,363 --> 01:12:35,513 I saw a comment earlier, Parley, about, about junior architects or 1231 01:12:35,513 --> 01:12:38,813 graduates coming into firms and saying, because every one of them, 1232 01:12:38,833 --> 01:12:41,693 I guarantee you is coming with bad habits to your firm, right? 1233 01:12:41,713 --> 01:12:42,403 100%. 1234 01:12:42,473 --> 01:12:46,273 Like this, the, the training that people get in school when it comes 1235 01:12:46,273 --> 01:12:52,933 to digital tools is probably zero and they're learning it on their own from 1236 01:12:53,463 --> 01:12:55,293 their friends and the internet, right? 1237 01:12:55,333 --> 01:12:59,533 And so when they come in, like, I guarantee you they're doing it. 1238 01:13:00,273 --> 01:13:01,053 Wrong, right? 1239 01:13:01,073 --> 01:13:05,603 In air quotes, because they're not doing it to your standards, your firm standards. 1240 01:13:06,023 --> 01:13:09,343 And I mean, you mentioned it also from people coming from other firms and how 1241 01:13:09,343 --> 01:13:12,673 we did it there is how I want to do it here, because that's my experience 1242 01:13:12,673 --> 01:13:14,143 and that's, I'm comfortable with that. 1243 01:13:14,443 --> 01:13:18,113 And so I want to implement that on my project and bringing that 1244 01:13:18,113 --> 01:13:23,513 consistency back to the firm's, you know, culture, technical 1245 01:13:23,513 --> 01:13:27,783 leadership requirements, you know, profitability, like all of these things. 1246 01:13:28,158 --> 01:13:32,468 It's a really big deal, like in, in, in, in, or we mentioned earlier, like 1247 01:13:32,468 --> 01:13:37,928 this stuff just doesn't scale with a per at the personal level because the 1248 01:13:37,928 --> 01:13:39,848 technical staff, there's just not enough. 1249 01:13:39,858 --> 01:13:40,738 There's never enough. 1250 01:13:40,818 --> 01:13:41,088 Right? 1251 01:13:41,098 --> 01:13:44,858 And, and these tools are table stakes. 1252 01:13:44,888 --> 01:13:45,848 They're just a guarantee. 1253 01:13:45,848 --> 01:13:47,768 We're going to use these tools on every single project. 1254 01:13:47,768 --> 01:13:49,158 This is how we deliver projects. 1255 01:13:49,158 --> 01:13:50,678 We don't deliver projects any other way. 1256 01:13:50,678 --> 01:13:52,048 We're not going back to hand drafting. 1257 01:13:52,048 --> 01:13:53,428 We're not going even back to CAD. 1258 01:13:53,428 --> 01:13:54,848 We're not doing any of that stuff anymore. 1259 01:13:55,438 --> 01:13:55,678 Right? 1260 01:13:55,698 --> 01:13:58,368 And so to not understand that, that. 1261 01:13:58,663 --> 01:14:04,233 This has a huge business impact, as well as a culture and training and 1262 01:14:04,233 --> 01:14:09,143 professional development impact, like you have to realize that in leadership 1263 01:14:09,553 --> 01:14:14,483 at these levels to understand why any of this matters, um, and, and to 1264 01:14:14,483 --> 01:14:18,523 me, like, I know at some level, maybe this does sound too good to be true, 1265 01:14:18,523 --> 01:14:19,933 but at the same time, like, it's not. 1266 01:14:20,843 --> 01:14:21,543 You guys have done it. 1267 01:14:21,653 --> 01:14:25,843 And, and that's why I wanted to highlight it on the podcast, because when I 1268 01:14:25,853 --> 01:14:30,023 saw what this is, like, I have all of these scenarios and I started out this 1269 01:14:30,023 --> 01:14:34,108 whole rant right here about what I hear from my wife, which is like, I've, Why 1270 01:14:34,138 --> 01:14:36,138 doesn't it do what I want it to do? 1271 01:14:36,528 --> 01:14:40,688 And like, she's working for very small architects here and there doing modeling 1272 01:14:41,208 --> 01:14:43,588 and every one of them does it differently. 1273 01:14:43,878 --> 01:14:47,948 And, and so constant battles, constant internet searches on 1274 01:14:47,948 --> 01:14:49,028 how to figure this stuff out. 1275 01:14:49,458 --> 01:14:52,228 And so Chris, like you bring it up, like somebody's already figured 1276 01:14:52,228 --> 01:14:54,138 this out so that you don't have to. 1277 01:14:54,218 --> 01:14:58,238 And having a way to convey that to staff who doesn't know what they don't know. 1278 01:14:58,693 --> 01:14:59,553 is huge. 1279 01:14:59,643 --> 01:15:02,143 Like it's just absolutely huge. 1280 01:15:02,163 --> 01:15:08,483 And so kudos to you guys for, for doing the work and, and plugging a 1281 01:15:08,483 --> 01:15:10,193 lot of these holes that do exist. 1282 01:15:10,202 --> 01:15:13,202 And, but, but also like educating people through the process and 1283 01:15:13,202 --> 01:15:14,433 meeting them where they're at. 1284 01:15:14,463 --> 01:15:14,723 Right. 1285 01:15:14,723 --> 01:15:18,743 Because it's not just handcuffs and it's not just slaps on the, on the 1286 01:15:18,753 --> 01:15:21,673 back of the hand or on the back of the head as sometimes it might be. 1287 01:15:22,033 --> 01:15:22,293 Right. 1288 01:15:22,343 --> 01:15:25,648 But it's like, That you're, you're taking a different approach to it. 1289 01:15:25,668 --> 01:15:29,678 And I think it's a, it is a very personal approach, uh, and it's a very 1290 01:15:29,678 --> 01:15:32,738 human approach because those are the people who are actually using these 1291 01:15:32,738 --> 01:15:34,408 tools to deliver these projects. 1292 01:15:34,428 --> 01:15:38,628 And so it's worth highlighting, like absolutely worth highlighting. 1293 01:15:38,648 --> 01:15:42,898 And, and so I appreciate you guys coming on the show to talk about that today. 1294 01:15:43,208 --> 01:15:46,343 And I want to give you the opportunity, if there's anything that I've missed 1295 01:15:46,343 --> 01:15:47,883 here that we, we need to talk about. 1296 01:15:47,883 --> 01:15:50,143 I think we've, we've talked about a lot of the problems, but we've also 1297 01:15:50,143 --> 01:15:51,733 talked about ways to handle that. 1298 01:15:51,763 --> 01:15:55,173 And, and some interesting ways to handle these things through, through the 1299 01:15:55,173 --> 01:15:57,113 people approach to the culture approach. 1300 01:15:57,173 --> 01:16:00,543 Um, is there anything that we missed that you guys want to bring up 1301 01:16:00,543 --> 01:16:02,423 before we, we call it quits here? 1302 01:16:02,443 --> 01:16:04,263 Yeah, 1303 01:16:05,543 --> 01:16:07,083 Parley Burnett: It's been fun to talk about it with you. 1304 01:16:07,303 --> 01:16:10,553 I think I, um, I would just say that we're not done yet. 1305 01:16:10,813 --> 01:16:11,223 Right. 1306 01:16:11,933 --> 01:16:14,393 It does a lot for sure. 1307 01:16:14,853 --> 01:16:19,623 It does a lot, but the, the challenges there in Revit are quite many. 1308 01:16:19,833 --> 01:16:23,823 So we look forward to continuing the path. 1309 01:16:23,823 --> 01:16:27,083 Evan Troxel: I don't hear the same rant from my wife every time. 1310 01:16:27,213 --> 01:16:30,093 It's always a different thing, to your point, right? 1311 01:16:30,093 --> 01:16:32,493 It's like there's, there's a lot more work to do. 1312 01:16:32,673 --> 01:16:37,313 So, uh, and, and I, I appreciate that you're up for it because I know obviously 1313 01:16:37,313 --> 01:16:41,633 there's a business case for it, but at the same time, like you're interested in. 1314 01:16:42,258 --> 01:16:46,028 Firms getting better at what they're doing, delivering better products 1315 01:16:46,028 --> 01:16:49,758 to their clients, because I know you guys as, as people, right? 1316 01:16:49,758 --> 01:16:51,858 And these are the things that, that you're passionate about. 1317 01:16:51,858 --> 01:16:56,418 So, um, yeah, so thanks for bringing that up because I, yeah, like it's not over. 1318 01:16:56,418 --> 01:16:58,848 It's, and, and software is never done, right? 1319 01:16:58,848 --> 01:17:03,698 You, there's, there's, I'm sure you've got a roadmap that, that, that's enormous. 1320 01:17:03,698 --> 01:17:05,338 So, um, that's cool to see. 1321 01:17:05,338 --> 01:17:09,538 It's cool to see things coming out, new ways to address these problems. 1322 01:17:09,538 --> 01:17:12,748 And, and, uh, thanks for taking the time to talk about it today. 1323 01:17:14,168 --> 01:17:14,458 Chris Shafer: Yeah. 1324 01:17:14,498 --> 01:17:16,238 We really appreciate the opportunity, Evan. 1325 01:17:16,308 --> 01:17:17,758 Um, this has been, it's been fun. 1326 01:17:18,243 --> 01:17:19,202 Parley Burnett: Yes, it has. 1327 01:17:19,213 --> 01:17:19,543 Thank you.