Showing posts with label Collaboration. Show all posts
Showing posts with label Collaboration. Show all posts

Wednesday, July 24, 2013

It is a Training Problem

I frequently get involved in conversations that start with someone wishing Revit would help resolve "x" problem. The essence of "x" is that somebody on the team keeps doing something that the team wishes they wouldn't. So we want Revit to fix a user, or make it impossible for a certain user to do something.

Usually it is just growing pains and those WILL subside after enough time is invested and experience is gained. That's the purpose of training, we can shorten the time required with training. Yes, I do work as a trainer but I'm not just saying that because I'm a trainer (the carpenter thinking every problem needs a hammer). The whole point of hiring a training consultant or going to classes (for anything) is to reduce the time it takes to become productive or knowledge.

    We SPEND money to SAVE time and invest in our skills.

Too many firms don't invest in their staff (or if they do, they don't do it effectively). They expect or assume that their staff will just manage to get by on their own. Give them a book, they're smart, they'll figure it out. They probably are smart and they will figure it out...eventually. How long can you wait for that to happen? They might pay for training but then after three days in a class they've been trained and therefore are experts! At least that's the perceived expectation or assumption. After all, that's why architecture is such a easy degree to get and getting licensed is a snap, right?

Getting training is a piece of the puzzle. Putting that training to work is how experience is gained. The training makes it possible to shorten the learning curve toward experience. No matter which way you approach the learning don't underestimate the importance of the experience of doing the job, the project. You'll just enjoy the job or project more if you get some good training and spend less time getting frustrated.

If a firm really keeps track of how much time is lost to inefficient task completion and inexperience leading to rework. They'd find out eventually that hiring that consultant or training facility would have been a bargain. If we don't treat "time lost" as "money spent" we don't realize how much it really cost. So many firms behave this way, they don't pay attention to the money going out the door the slow and "invisible" way. It goes out so slowly they convince themselves it isn't happening. If you are serious about seeing a return on investment (ROI) you need to know what it costs to do everything now (the established or "old way") and then later after becoming proficient with Revit. As they say, you can't manage what you don't measure. Keep in mind that lots of data doesn't necessarily mean it is useful.

A senior architect mentoring an intern architect is the same thing, your experience helps the future senior architect become one. You can be a mentor in your office for Revit and bring people up to speed sooner too! So it's not just about hiring a great trainer, it's also about striving for better continuously.

    We sprung for training and people are still making mistakes and they've been warned repeatedly!

Mistakes are one thing, we all make them. If people know better but keep doing the same thing over and over again you now know what they really think of you and the firm. They don't care! They don't care enough to "play along", be a "team player" (OMG, holy catch phrase Batman). Sorry but AEC is a team sport.

    Messing up other people's work IS a training issue, until it ISN'T anymore.

If people are trained and continue to be RUDE and refuse to work well with others it is no longer a training issue. It's a HR (Human Resources) problem, yeah I mean "possibly cost them their job". A firm (and it's staff) shouldn't have to tolerate people refusing to work together well. That's easy to write, not as easy to work through, I know that. Someone once said to me, "Yeah we have a few people who should work for our competition". So I say, "why aren't they?" (big grin)

Ignoring the problem, yeah how's that working?

Plaaaaay BALL!

Wednesday, April 11, 2012

Wall Floor Interaction and Linked Models

When we have architecture and structure in separate Revit models we end up with somewhat clumsy graphics in wall sections. This is more pronounced if the structural slab is in the structure model only. It could look like this.


The wall continues past the floor as if it isn't there. One possible solution that allows us to keep the structural slab in the separate file and avoids the copy/monitor scenario is to place a Reveal on the interior side of the wall. The profile needs to be equivalent in size to the slab thickness and the wall thickness (inside surface plus however far the slab extends toward the exterior). This approach creates a bit better result.


I should mention that this works the other direction too, since the reveal is part of the wall it will leave a "hollow" space for the structural model's floor slab to occupy.