Transcripts
Hello and welcome to another episode of Design under influence, where Willard and I are going to break down mostly Willard gonna break down ten steps for successful conversion from AutoCad to Archicad.
Speaker A:And we are deep into this.
Speaker A:We are like, humped it last time.
Speaker A:And so right now we are over the hump and we're into step number six.
Speaker A:Willard, step number six is collaborative setup.
Speaker A:Wonderful.
Speaker A:Perfect.
Speaker A:And so, just to kind of cue this up for you listeners out there and folks who watching the video, we're going to talk about roles and permissions, access management, communication channels, coordinating meetings, file sharing protocols, and we're going to talk touch on maybe we'll spend some time on external teams and coordination with folks piping in and out of your system using newly flashy mint archicad installation you have.
Speaker A:So, Mister Willett, you're going to do most of the talking.
Speaker A:I will do some prompting, but I tell us a little bit about how your day is starting.
Speaker A:And then without further ado, let's just kind of take a dive in number six.
Speaker B:Yeah, so, yeah, day is starting.
Speaker B:Good fall is here.
Speaker B:So that's pretty exciting time.
Speaker B:And so, yeah, we're going to jump into collaborative setup.
Speaker A:So is your phone, is your phone on Sr.
Speaker A:To take you off your track right away?
Speaker A:I do that for people.
Speaker A:Is your phone on silent?
Speaker A:I mean, yeah, we got, you know, housekeeping.
Speaker B:Yeah, phones on silent.
Speaker B:I think all the distractions have been muted.
Speaker A:Eliminated.
Speaker B:Yeah.
Speaker A:All right.
Speaker B:Sorry.
Speaker B:Yeah, no, well, I think, you know, it's interesting what you said about getting over the hump.
Speaker B:I think that this chapter of kind of migrating from autocad to Archicad is unique because this represents in some ways the unique characteristics of archicad that set it apart from a lot of different other applications.
Speaker B:So I think there's a good saying that you can travel faster alone, but farther together.
Speaker B:And I think that is the theme with kind of collaboration within Archicad is that, um, you might be able to figure out how to do everything by yourself.
Speaker B:And with archicad, you know, that's definitely something that's unique because it allows you to, you know, harness both, like some of the things that we talked about, like template generation, to make you a very efficient and productive kind of individual.
Speaker B:But as with most, most things, you know, this is a team kind of exercise in some cases, whether that team is in house, you can see the people, or it's a global or national kind of team that you're working with the tools or the techniques.
Speaker B:With collaboration within Archicad, kind of set it apart from everything else.
Speaker B:We can jump into the steps of understanding some of the features and way you're going to want to approach collaboration within this tool.
Speaker A:Yeah, I think we definitely are here for that reason, but I want to do a little bit of a show off.
Speaker A:Can I show off a little bit?
Speaker A:Can I show off just a little bit and then we can go into it?
Speaker B:Yeah.
Speaker A:All right.
Speaker A:What you said was technically correct, actually correct in many ways.
Speaker A:But I know this saying by heart, so.
Speaker A:And I'm going to say it.
Speaker A:I'm going to say it the way I like.
Speaker A:I read it, I understand.
Speaker A:Then I remember I internalize it.
Speaker A:So if you want to travel fast, go alone.
Speaker A:If you want to travel far, go together, which is essentially what you said.
Speaker A:But I just wanted to show off and say, okay, this is kind of how I read this.
Speaker A:And, you know, it's worded out in a way that it's like, it's.
Speaker A:It's from times of past, you know, it's from wisdom, you know, of the past, because, you know, nobody speaks like that.
Speaker A:Go together.
Speaker A:But that's how the saying is.
Speaker A:Right?
Speaker A:That's what you were going with that?
Speaker B:Yeah, yeah.
Speaker A:And it's absolutely, it's so profound, actually, that it's.
Speaker A:That, you know, if you stop and think about this, it's, it's fascinating, but, yeah.
Speaker A:So what this does helps us travel far with our businesses, right?
Speaker B:Yep.
Speaker A:Yep.
Speaker A:All righty.
Speaker A:So show offs done now it's your show.
Speaker B:Yeah.
Speaker B:So I guess I'm going to do a little.
Speaker B:Before I jump into it, I'm going to give an example of how collaboration that I've seen.
Speaker B: te two thousands, I guess, or: Speaker B:But when I started there, they were one of the largest firms that was using Archicad in the nation, probably even globally.
Speaker B:They had 80 or 100 seats of archicad.
Speaker B:And to my understanding, when I got there, they had these individual seats, but they weren't necessarily using the teamwork tool.
Speaker B:And so teamwork is a separate kind of component to archicad.
Speaker B:So when I got there, and I had been using teamwork in a very kind of complicated manner because at the time, teamwork wasn't optimized for web usage.
Speaker B:And so you had to really build in, you had to be using specific hardware to be able to make that tool work on a more global scale.
Speaker B:But when I got to this firm, I, you know, introduced it, wanted to use it.
Speaker B:And, you know, within six months, the entire firm was leveraging this tool.
Speaker B:And one example of the, the benefits of a kind of collaborative nature was that we, at the height of it, we were using teamwork to work on a, it was roughly, I think it was like a 200,000 square foot hospital addition.
Speaker B:And so it was a new tower.
Speaker B:And I forget if there was roughly about 15 different designers and architects working on the interior kind of floor plans.
Speaker B:And then there was about a handful of architects and designers working on infrastructure and then also kind of the facade design.
Speaker B:So we were able to do, we were able to work in a parallel method.
Speaker B:So there was multiple teams working in the same file at the same time doing different aspects of the design.
Speaker B:And, you know, the ability for us to work as a team collaboratively and on our own kind of scopes of work was greatly enhanced with archicad's kind of toolset.
Speaker B:And so we were able to make changes, you know, within a couple days.
Speaker B:That was, you know, for a 200,000 square foot building that was super complex very quickly.
Speaker B:So the design iterations were much shorter and much more accurate and is a very unique tool that is unlike a lot of the tools that you would see in other applications.
Speaker B:So that's just kind of a little historical piece and gives you kind of a basic idea of what teamwork is.
Speaker B:But to kind of explain it a little bit, Archicad's teamwork, which is, I think the, the actual name of it is called the Delta server.
Speaker B:What the Delta server does is basically you create an instance of this teamwork or the delta server on a machine, and that can be in the cloud or on a server that's connected on a lan, or it can be on your own personal machine, and then it can be connected out into a more global connection.
Speaker B:And what that does is basically you do an initial setup and you put your project file into this environment.
Speaker B:And there's a little bit of a difference in terms of what we think happens versus what is actually happening.
Speaker B:And we are working in this parametric model that's a 3d based environment.
Speaker B:And we see things in that method.
Speaker B:But when we upload it to this teamwork or the Delta server, it gets parsed into basically something like an SQL or like a spreadsheet.
Speaker B:And so your file has just translated itself, even though the way that we like work with the file, it is that information.
Speaker B:But when it goes onto this server, it just represents that information.
Speaker B:And so it's kind of a reduction of the files kind of complexity in some ways.
Speaker B:And basically what that allows you to do is instead of like working with complex three dimensional data, you're working with the representation of complex three dimensional data in a kind of a spreadsheet format.
Speaker B:So this is getting into the weeds a little bit, but I like that.
Speaker A:I'm tracking with you on this one, actually.
Speaker A:I've never used it, but it actually is making sense.
Speaker A:And I have many questions, but please continue, I don't want to interrupt.
Speaker B:Yeah, so if you were to think of a cube, a cube would have like in parametric standards, would have a surface material, it would have a dimensional material.
Speaker B:So x, y and z, it would have potentially other attributes associated with both the representation, and it might have other tags that are associated with it that can be pulled from other locations.
Speaker B:But if you looked at it in a, a row of information, it would just be data numbers and potentially references or other pieces.
Speaker B:But what you're looking at is not necessarily that three dimensional representation, but it's a translation of that information.
Speaker B:What that allows users to do, who set up a teamwork instance, is that you can have multiple people all across the globe.
Speaker B:And when they sign into a file.
Speaker B:So if you have five people who sign into a teamwork file and you want, let's say, two of those people to work on a floor plan, they have the ability to reserve information.
Speaker B:And when you reserve information, you're basically reserving that object in that row of data.
Speaker B: that say, let's just say it's: Speaker B:It's only as much text as is represented by the row of information.
Speaker B:So if it has, let's just say, 25 characters that equal that value of data, then it's only sharing those 25 data across the Internet.
Speaker B:What that allows you to do is to work on super complex, super heavy files anywhere in the world with relatively low bandwidth.
Speaker B:And just to do another example, I was, when I was working in California on a, it was actually in Santa Cruz, I was working on this huge house and it was super complex, had a lot of data in the file itself.
Speaker B:I set up a server on my desktop machine in my office, and then I went on a three week trip and I brought my laptop and my iPhone one or whatever original iPhone was.
Speaker B:And I was able to tether on like a 3g or even it might have been a 2g connection through my laptop back to my, back to my desktop that was 300 miles away.
Speaker B:And I was able to make changes, update the model and do everything almost like completely off the grid kind of scenario.
Speaker B:And the only way that I able to do that was because I had shared the file and there was basically a clone of that information on my laptop.
Speaker B:And then when I made the changes to whatever objects I was changing, it was only sending the changes that were made in a textual format back to the server.
Speaker A:I have a good question here.
Speaker A:I need clarification here.
Speaker A:Your laptop, when you do the work itself, you're still working in parametric environment.
Speaker A:When you making the changes to, let's say set cube, then it translates to that spreadsheet style and then it sends it and syncs it.
Speaker A:Or are you also working in a spreadsheet style format?
Speaker B:No, you never see the spreadsheet.
Speaker A:Ah, perfect.
Speaker A:Okay.
Speaker A:I wasn't connecting that.
Speaker A:Okay.
Speaker A:Yeah, because it'd be kind of hard architect to see everything flat and just change numbers.
Speaker A:Oh, this one needs to be 6.2ft.
Speaker B:Yep.
Speaker A:It's like, okay, well what does that change?
Speaker A:I have another question.
Speaker A:Maybe you'll answer it later, but I feel like I want to, I want to shoot it now.
Speaker A:With this sort of collaboration, one thing comes to mind.
Speaker A:If you move the wall, does a conduit move with it?
Speaker A:Let's say you work on conduits, you know, whatever piping, whatever plumbing, and I work on walls.
Speaker A:If I move my wall a bit, what happens?
Speaker A:How does that connect with the other team?
Speaker B:Not necessarily.
Speaker B:I mean, if you were to reserve kind of all the elements that are associated with that wall, then it could move with it.
Speaker B:But if you were only instructed or reserved the wall, and there was pipes in the wall, then that pipe would have to be moved as well.
Speaker B:Potentially.
Speaker B:It's, it's not necessarily like pinned or like, like clipped to that set of information, but for the most part, a lot of the information would just have to be reserved as you're moving elements.
Speaker A:But is it like a real issue I'm describing or this is just in my mind something?
Speaker B:No, it is.
Speaker B:It is actually a issue that.
Speaker B:So, for instance, in this teamwork, kind of collaborative environment, one thing like teams that I've worked with are like structural engineers.
Speaker B:And so if I'm adjusting walls and, you know, locations of different things that might be only in the architectural scope, the structural team would need to go back and make adjustments to their elements because, because there is a little bit of a, you know, a division of labor.
Speaker B:But then also roles and responsibilities.
Speaker B:You know, I don't necessarily want to be moving structural elements without the structural team's awareness.
Speaker B:But then in general, I just don't want to move that because if I move it and then they don't catch that, you know, it could show up later as like an issue because maybe they didn't do the load calculations based on the location of the new wall or the new column that maybe moved because of something that I did.
Speaker B:So.
Speaker B:So in some ways, it's good that some of that information isn't hyper connected just because you want somebody to have a second eyes or the, the consultant that is responsible for that should be the one who's aware that, you know, their pipes are no longer in the wall and maybe that changes some of their, their design.
Speaker A:Got you.
Speaker A:So my other question is related to delta server functionality versus native archicad functionality.
Speaker A:Can you collaborate on a design without moving into teams in delta server?
Speaker A:I mean, is that a function?
Speaker A:Well, this is the only way to collab, to have four or five people build the thing together.
Speaker B:Yeah, yeah, this would be the only way.
Speaker B:If you were having people work inside of the file, in a live file, this would be the only way to do that.
Speaker A:Gotcha.
Speaker A:All right.
Speaker A:This is, this satisfies before now.
Speaker B:Yeah.
Speaker B:Well, and then I think that that brings up another interesting point, is there has been times and a technique that I've used personally, even though I'm not working with people, I potentially will share the file on a teamwork, in a teamwork file or on the delta server, even though I'm not working with anybody, that I potentially could access that file from different locations.
Speaker B:And there's also a component of it that creates automatic backups and different types of backups of information.
Speaker B:So that it just allows me to potentially just be a little bit more like, for instance, one thing that I often do is I'll be working on a desktop machine in my office, and then if I share the file in teamwork, I can take my laptop and then I can connect to that file remotely and not have to worry about using like a VPN or some other kind of connectivity to connect back to the server location or having to bring like a copy of that file with me.
Speaker B:So there are some benefits, even when you're working by yourself to using the teamwork feature.
Speaker A:Got you.
Speaker A:All right, well, let's go into some of the details and touch on roles and permissions.
Speaker A:Where does that come in?
Speaker A:You put that as one of the subtopics.
Speaker B:Yeah.
Speaker B:Well, let's step back a little bit and just go over the basics of the teamwork.
Speaker B:So teamwork is like a separate install that you'll need to do and set up on your machine.
Speaker B:And then there are a couple different techniques of setting it up.
Speaker B:You can set it up on your, you know, inside of your office.
Speaker B:You could also set it up on something like a cloud based server, like AWS or azure or one of these other kind of locations where it's, the install is done somewhere else, not necessarily on your lan, but in a different location.
Speaker B:And then there's like different setup configuration.
Speaker B:So you're going to go through and you're going to create a global admin user and then you're going to start to go through and set up the individual users and the roles and responsibilities for each of those users.
Speaker B:This gets into a little bit more and it's a little bit closer related to template, but then also.
Speaker B:And one of the things I really appreciate about ArchicAD is that even though we're working in this parametric environment, it's not segregated from our actual practice.
Speaker B:So it makes you think about how you are actually setting up your office, your projects, your teams, and so identifying the roles and responsibilities.
Speaker B:So inside of the teamwork kind of environment, you're going to be, or the BIM server.
Speaker B:I think I use teamwork and the BIM server and really I think teamwork is the older name and BIM server is the new name.
Speaker B:So if I, excuse me if you're getting a little confused with current terminology, but I always call it the teamwork.
Speaker B:Teamwork.
Speaker B:But one thing that is unique is the ability to restrict access to the ability for people to make adjustments.
Speaker B:And where this comes in is, I mean, it could be useful, especially if you have a very rigid kind of organizational structure and you're trying to limit the potential for team members to catastrophically mess up or adjust a file or get into areas inside the file that could pose significant changes that would need to be remediated later.
Speaker B:And so you can have roles like draftsmen, project manager, architect, different other kind of components within that, and those will adjust what people are able to manipulate within the application or kind of the environment itself.
Speaker B:And so, yeah, that I'm assuming there's.
Speaker A:Some tumblers within the roles to further define a particular role.
Speaker A:Right.
Speaker A:There's like different little things you can turn on, turn off for each role.
Speaker A:So let's say your drafter, you know, you can fine tune that access.
Speaker B:Yeah, yeah.
Speaker B:And this is a good opportunity, especially for somebody who's creating the template and then somebody who's working on kind of the server side setup is to understand what you want people to be able to do and not do.
Speaker B:And so, yeah, it is toggles or radio buttons to adjust like, what people can do.
Speaker B:And one thing I have found is that it is a very powerful tool, but sometimes it can limit your team's capabilities because if you ask somebody to do something but their role is only set to, you know, basically do floor plan work and not make details or, you know, create views or update drawings and things like that, you're going to have to go back into this server environment and, and make those changes.
Speaker B:And that could be one thing that, you know, it's good, but it can get a little bit.
Speaker B:You just have to be aware of it because it is a different environment and you have to be able to know how to get into there and make the adjustments and then you can create custom user profiles and things like that for different team members.
Speaker B:But it's a great way to.
Speaker B:The way that I've used it in the past is if I'm working with teams that are overseas and I specifically do not want manipulation of information like adjusting sheets or something of that nature or layouts, then I lock that feature so that I'm not having to worry about somebody accidentally going in there and creating 500 sheets inside of a project.
Speaker B:And if I only wanted support in one area, then I can focus the teams on that.
Speaker A:Yeah, got you.
Speaker A:Are we ready to go to access management from here or are there other things that you want to highlight in the permissions and roles setup process?
Speaker B:Well, I think, yeah, I think the roles and permissions is kind of also similar to what the access management.
Speaker B:But yeah, we can go into access management.
Speaker B:I think there's a couple different discussions that you can have.
Speaker B:Who accesses it and how do they access it inside of your operation?
Speaker B:Like, if you're just doing architectural work and then you have specific team members or roles and responsibilities that you want to disseminate that work to.
Speaker B:There's access requirements for that.
Speaker B:So setting up their usernames and emails and permissions and things like that, it's all very straightforward once you get into that environment.
Speaker B:And, you know, one thing that I, I try to, um, you know, I think it's.
Speaker B:I don't think it's a super, I don't think it's bad to, you know, kind of create a generic role and then, you know, assign the permissions and access as you go or reduce it as you go.
Speaker B:So that you're not limiting, you know, the access capabilities as you're getting started with this.
Speaker B:And then there's also kind of a component that you can allow people to see different projects on the BIM server or in the teamwork environment and reduce the visibility of certain projects or folders inside of that environment.
Speaker B:And that's pretty good too, especially if you're working on multiple different projects with multiple different teams spread out all over the place.
Speaker B:And you only want certain teams to be able to access, for instance, like the medical office team.
Speaker B:You don't want them to necessarily work on the education side of things or see those projects.
Speaker B:And then sometimes also it's nice to create kind of a sandbox or template files or things like that that everybody can see and access.
Speaker B:Sometimes I'll put like detail files or other information that I want to be globally accessible, but not necessarily projects that should be only specifically accessible to certain departments or teams.
Speaker B:And then so that, you know, it's something to dive into for sure in terms of understanding what you want accessible.
Speaker B:And then I what information you want visible, as well as what you want the roles and responsibilities for each of your members to have.
Speaker A:Gotcha.
Speaker A:We have about eight minutes, so we have to step through stuff.
Speaker B:Okay.
Speaker A:Right.
Speaker A:Like roles, I think responsibilities.
Speaker A:I think that's key because that's security.
Speaker A:That's not doing double work, trying to fix other people's stuff, trying to go back and versioning, figure it out, you know, I get that.
Speaker A:So what's the next aspect of this team server that you want to talk about?
Speaker B:Well, I think it's really getting into what I think is the more unique aspect of how this could work for your organization.
Speaker B:And I guess in some ways there is, it's kind of a paradigm shift.
Speaker B:So we're talking about access management, but really what we want is we want our consultants in these files.
Speaker B:We want our structural engineer, mechanical, electrical, plumbing guys inside of these files.
Speaker B:That's a whole different discussion.
Speaker B:But say, for instance, you are working with the structural engineer who has archicad, or if you have a client who would like to have potentially visibility inside of these applications or these files.
Speaker B:So let's just talk about a couple of things that I think are pretty interesting, and then we can relate that back to internal coordination and teamwork.
Speaker B:So kind of in the access management pool of discussion, you can also create roles and responsibilities for consultants, structural engineers, MEP.
Speaker B:And then there's the potential that you guys could be working collaboratively inside of the file.
Speaker B:So not only your architecture team, but you have your entire consultant and everybody else is also working in that environment.
Speaker B:If you're lucky enough to have a team that is leveraging the tool, and even if not, but there are ways to work around that.
Speaker B:But going further is now we are potentially integrating multiple different teams inside of this software, and then we also have our internal team.
Speaker B:So there's a lot of benefits while you're working in teamwork is that you have the ability to communicate inside the application, inside of Archicad to your other teammates.
Speaker B:You're able to assign tasks to them, you're able to see where they're working, you're able to assign areas for them to work, give them notes.
Speaker B:And so there's a lot of internal communication that can happen within the teamwork or the bimdhenness server environment that allows a really hybrid approach to coordination internally as well as externally.
Speaker B:And so what this also does is allows for meetings, coordination meetings and check ins and issue tracking to happen in a method that you wouldn't be able to do in the linear approach where one person has the file open, closes it, and somebody else opens it.
Speaker B:So there's probably, I would say, ten unique benefits of working in this environment that allow you to track progress, to communicate more efficiently so you're not using, you know, some external communication source emails or things like that.
Speaker B:You're able to open up the project, see all the notifications, see if things got done, assign information, assign tasks.
Speaker B:You're able to redline plots and insert them into the file and then assign those changes back to somebody who's inside that project.
Speaker B:So there's not only kind of the sharing of one file working in the same place, but there's also now this synergy that happens with the ability to work in a parallel method with multiple different people, with a rich, diverse kind of set of data that in terms of human progress, this would be similar to, let's see, I still go back to the Google Docs or something of that nature.
Speaker B:When you open up a document like that and you're sharing it with somebody else, and then multiple different people are writing or creating content inside of that file, you're able to both leverage the tool itself and all the inherent capabilities of it, but then you're also able to leverage kind of the group think or the hive mind kind of capabilities that in human civilization, this is a very unique kind of place for us to be able to work on the same solution at the same time with multiple different people and also control kind of how that accesses.
Speaker B:I think it's a little bit different than Google Drive because, or Google Docs because you're not able to say you are only working on page two and five and seven and then assign those pages or assign that specific thing.
Speaker B:So it gives you a little bit more nuance or granularity in terms of how and what you're allowing or wanting people to collaborate on.
Speaker B:And then the communication is more streamlined and more project focused.
Speaker B:So you're not communicating via email on a project saying go look at sheet five.
Speaker B:You're inside the software and pulling somebody's view into something that you specifically want them to look at.
Speaker B:So very unique kind of application.
Speaker B:And I've always been strongly attracted to how Graphisoft and Archicad have dealt with the communication and collaboration aspect and this literally, there's nothing else out there, probably in a lot of different softwares that has this level of collaborative capability as Archiade does.
Speaker A:I have one comment and two questions.
Speaker A:Rapid fire.
Speaker A:We have two minutes.
Speaker A:You're the master of Segues.
Speaker A:I've never seen anyone go from so micro to such macro like.
Speaker A:You start with, we talk about tumblers on the user profiles and then you go to human civilization like in one.
Speaker B:Breath.
Speaker A:It'S like, okay, profound.
Speaker A:Yes, but two rapid fire questions I really want to know.
Speaker A:Number one, very simple r1 world scenario.
Speaker A:You know how like software has lots of features and most people don't use most of it.
Speaker A:But my question in real world, do people actually use the meetings, all the collaboration, the conversations inside the tool, to have it all documented in one place and live with the project forever and ever?
Speaker A:Does this actually happen or do you see it somewhat, or give me a quick idea of the real world use case for this.
Speaker B:Yes, it does actually happen.
Speaker B:I would say that teams that are using teamwork or the BIM server are using this.
Speaker B:Yes.
Speaker A:Okay, so they're using all the features inside, tracking, communications, meetings, clash detection, whatever, documenting all those signing tasks, all that?
Speaker B:Yeah, I would say, I mean, I would say yes, but I know that it's not being leveraged completely, even throughout like the industry or within teams that are using the tool, because it's just a matter of people.
Speaker B:But I would say that, I would say a majority of people who are using the teamwork or the BIM server are using a majority of the features.
Speaker A:It sounds like you can build a big business just to be a BIm server consultant.
Speaker A:Like just that, just that aspect.
Speaker B:For sure.
Speaker B:Yeah, because that's one thing that's unique, is that once you get into this level of sophistication with leveraging the software, it almost takes.
Speaker B:Well, it definitely takes a different skill set than what most architecturally trained professionals have within their toolset.
Speaker A:One more minute, one more question.
Speaker A:This one, this one.
Speaker A:We might dedicate another episode or part of the episode too, but I want to start us off with this.
Speaker A:And this is kind of where I'm bumping up against.
Speaker A:You know, my partners don't use archicad.
Speaker A:You know, my providers don't use archicad.
Speaker A:Other, some architects, you know, that we work with don't use archicad.
Speaker A:And that's why I'm not going to use Archicad.
Speaker A:What do you say to that?
Speaker B:I think as I'm getting more seasoned in my career and profession and practice, I can understand that, but I don't agree with it.
Speaker B:So I think that it's, unfortunately, it is investment.
Speaker B:It is a time kind of thing.
Speaker B:There are some, you know, like 20, 30, 40 years worth of evolution that, you know, for somebody who has little desire or experience, kind of with parametric technology or just drafting, it could be daunting.
Speaker B:But I would suggest that everybody, you know, from the principal all the way down, should be deep, as deep as they can be comfortably within it.
Speaker B:And just to end this kind of thing is the practices that I participated in, where the principal was fluent in Archicad were the ones that I saw the most efficient leveraging of the tool, as well as the agility to make decisions in a forward movement more quickly.
Speaker B:And the project were better designed, more, just a better product in the end.
Speaker A:Gotcha.
Speaker A:All right, well, that's all the time we have, folks, as they would say.
Speaker A:I think there's more here we can unpack.
Speaker A:Let's see if we get any comments, feedback, and more questions.
Speaker A:Over time, these episodes just kind of just grow, you know, we'll start out with like 30 views and they're just like, you know, because people, you know, there's a lot of information, data here that is super valuable.
Speaker A:So will it.
Speaker A:Thank you very, very much for taking your time and breaking it down for us.
Speaker A:I know you have a lot more to give, but the time is the time.
Speaker A:Human civilization requires, you know, other meanings and, you know, substance.
Speaker A:Like, you know, maybe a donuth before next meeting.
Speaker B:Yeah, thanks, Alex.
Speaker A:Definitely not a doughnut.
Speaker A:A bagel maybe.
Speaker A:Okay.
Speaker A:Anyway, thanks a lot.
Speaker A:You guys still watching listening?
Speaker A:Check us out at get archit.com dot.
Speaker A:We really do it support for architects, but we could certainly help you think about going from AutoCaD.
Speaker A:To Archicad.
Speaker A:And then if you actually going, we can help you get there.
Speaker A:Right, Willard?
Speaker B:Yep, yep.
Speaker A:All right.
Speaker A:Cheers.
Speaker A:Always a pleasure, sir.
Speaker A:Thanks a lot for watching.
Speaker A:We'll see you all next time.
Speaker A:Cheers.
Speaker B:Cheers.
Speaker B:Bye.
