Friday, October 2, 2009

"Estimate your time and then double it."

An intern and I were recently estimating how much time it would take us to do certain tasks on a master planning project, and it was proving a bit harder than it would seem to be. We had to consider the time it would take to visit and review the existing facility, conduct staff interviews, go back to the office and produce the drawings and images and site assessment...oh, but we should sit down before we ever go to the site and talk about what we want to look at, measure, take pictures of...and perhaps we should allot some time and fee for an engineer and a landscape architect to survey the site and provide some input.... Like I said, the more we thought about the time and effort involved, the more we realized that it wasn't as simple as just saying "three weeks."

As the intern and I bounced ideas and timelines off each other, a well-meaning manager within earshot said half-jokingly, "Figure out the time it'll take, then double that. That's what should be on your proposal to the client." We all laughed and commiserated the way that projects seem to always take more time or be more involved than we originally thought. The manager then corrected himself a bit and said, "Actually, you should add about another 20% to 30% onto the time you think it'll take."

The intern and I did just that, and then we presented our estimate to our project manager, who was writing the proposal. His estimate was even higher than our 125% estimate, maybe even more like 150% of our guess. He took an average of the two estimates and wrote that into the proposal. What struck me was how, even though the intern and I are the ones that do this work on a regular basis and know how long it takes to do, the boss thought we needed longer to do it. Strangely enough, it is often those very bosses and managers that will push us to do whatever the task at hand is in less time that it truly takes to do a good job.

Estimating how long it takes to do a job or a task gets easier as your career progresses, then it gets harder again. After you have a few years of experience, you have a really good idea of how long it takes to do something. You're familiar with the software, you know the consultants pretty well and how long it takes to get back to you, and you know your way around a project. But then, your success gets in your way. By being good at your job, you get put on more than one project at a time, and maybe you even get more involved with the project by working with consultants on a regular basis and trading emails and taking phone calls. You become known in your office for being good at this or that--codes, Revit, equipment clearances, etc. So suddenly, what used to take you two hours now takes you three because as you were drawing this or putting together that, someone asks you what's the ADA clearance at the pull side of a door (18", you say, but 12" at the push), and then as you start working again, someone else asks you how to fix this stupid error message in Revit (split the wall, then demo the part you don't want, then align the part you do want with the door frame, etc.), and then you start working again, and then someone else...you get the picture.

Granted, there are some tasks that you can truly say, "That will take me ten minutes." But as you get better at your job, I urge you to consider lightly padding the estimated time it takes to complete more complex tasks. If it takes you that long or a bit longer, then at least you prepared them for it, and if it takes you less time than you said, then fantastic--overpromise and underdeliver, I always say. At the very least, be aware of what it takes to complete even the seemingly simplest requests.

A project manager in my office recently asked me to make a phone call to a local code official for him, knowing that I was on professional but good terms with this official (she seems to always call me back within a few hours of leaving her a message, and she answers my questions and explains things patiently). I was in the middle of assembling a program for a master plan (a different one than the one I described above), and I knew I really couldn't help this manager. I can hear you asking, "But why, Lulu? It's just a question!" Ah, but it's not. This particular manager has a very specific way he wants things done--everything--and he has a need to know the why beyond the why beyond even that why. Despite the fact that I was accustomed to this fellow and would try to ask questions of various code officials and consultants and product reps that I know he would ask, I would invariably not think of one or two questions for which he would want answers. So, his "just a question" would be me on the phone with the code official for ten minutes, then I would take five minutes to email him an answer, then an hour later when he finally read my email and I was working on something else, he would interrupt me and interrogate me on my conversation for ten minutes, then I'd have to call the code official back but this time I'll have to leave her a message, and then fifteen minutes later she calls me back and I stop what I'm doing for another ten minute conversation...again, you get the picture.

So I said that I was unable to help him at that moment, that I could make the call for him tomorrow, when I'd gotten somewhere with my master plan program. He pushed back, insisting that "it was only a couple of phone calls." I finally had to call my own project manager in to back this fellow of off me, but it was worth it. If had given in, my primary project (and frankly, a little of my sanity) would have been compromised, and I wouldn't have done as good of a job as I could have for that manager, knowing that I had a bunch of other work waiting on me. Having worked with that fellow enough, I knew that I had to estimate the time it took to do "a few phone calls"...and then double it.

I'd love to hear about phrases or habits/behaviors that make you curious or crazy. And it seems I may have a couple of managers reading the blog. If so, welcome! Feel free to ask questions or make suggestions for future posts, either in the comments on via email in the sidebar. Thanks!

Wednesday, September 30, 2009

"I've been doing this a long time."

In your job and career, you'll ask generally honest questions about how something looks or why it's being done the way it's being done, and the response you'll get ranges from straightforward and curt to pleasant and pensive--someone may realize that you've brought up a good point that they've never considered. Occasionally, though, you'll get today's post title as a response to your questioning or challenging of an idea or method for doing or designing something. And I'm here to tell you: don't take "I've been doing this for a long time--trust me, this way is right" as an acceptable answer.

I'm sure some if not most people mean well when they tell you that sentence. They want to reassure you that the project and/or detail is not going to hell in a handbasket. They want you to know that whatever this decision is to be made, it's been thought through before now so that we don't have to reinvent the wheel on every project. So good on them. But while it's meant to reassure you, the intern, the newbie (as it were), it's not a very educational or informative answer, is it? Understanding why we do what we do--why we put the vapor barrier on this or that side of the insulation, why we show the doors swinging like this or that into the exam rooms, why we indicate control joints in the brick exterior every X or Y feet--is one of the vital essences of being an architect. It does no one in any profession any good to simply copy details and methods as rote gospel. The understanding of what we're doing and why makes it easier to remember what to do next time, and it gives us an understanding that helps us deal with unusual situations (the doors swing like this in the exam rooms for privacy, but it can't because of the column here, so perhaps this should be an office instead).

So instead of shrugging and mumbling, "oh, okay" when someone feeds you this line, ask "Why is it right? Can you explain it to me? If you can't, then who should I ask?" Or, if you think they very well could be wrong, ask "Well, I found this thing in the code/facility standards/meeting notes/whatever, and it seems to contradict that--can we go over this together for a few minutes? If you can't, who should I review it with? Can you look at it with me later?" If you're still getting pushback, then push right back (I'm officially giving you permission to be a pain, if only for a moment): "Perhaps it is right, but I'm not seeing how that's possible given what I've found here...would you mind explaining it to me?" Or even "I'm sure you're right about this, but I need to understand what the reasoning is behind this detail--this isn't the only detail I'll be doing on this project."

Questioning the reasons for doing things they way someone tells to do it is important, because they may not realize--innocently enough--that they're wrong. They may have been following some superbasic rule of thumb ("the vapor barrier always goes on the warm side of the insulation!!!!") without realizing that the correct answer is either different or more complicated that they originally thought. Asking them to explain the reasoning behind their response gives everyone one more chance to check their assumptions and see if they're still correct. A corollary to this is that people may do things the way they've always done it and not realized that technology has made their way of doing things obsolete or more trouble than they're worth. For example, a lot of our interns are having to confront the older project managers in my office with how Revit changes the old way of setting up a set of drawings and indeed a project. Because we're building in 3D, there's no more fudging details and just saying, "oh, we'll fix it later." 3D software platforms like Revit and ArchiCAD tend to require longer SD and DD phases and a shorter CD phase, and we who deal with the software are having to challenge our bosses' assertion that "we've been doing this a long time and it works" still applies (when it doesn't). So challenge someone when you have done the research and really believe you've found a better way.

I'm giving you permission to push on this because there are a few people who use the above sentence as a way to shut you up. By asking them why something is the way it is or by disagreeing with their decision or direction, they view this as some iPod-wearing, text-message-sending, baggy-pants-wearing whipper-snapper punk challenging their authority. How dare you insinuate that they're wrong? You're an intern, for crying out loud! And they're an architect/ engineer/interior designer/whatever! These are the people you especially need to push back on, because they're wrong at least half the time, and all you're really doing is saving them from themselves.

About a year ago, I was helping an interior designer in my office by checking her floor plans for compliance with various codes, including ADA and ANSI (the two major codes that govern disabled accessibility). I noticed in the code that a clear space of 36" wide by 48" long was required at all 3' by 3' transfer showers, instead of the usual 30" x 48" clear space required just about anywhere and everywhere else in ANSI. I brought it to her attention, almost in passing, and she corrected me, "Oh no, it's 30" by 48"." I disagreed politely, saying that it was 30x48 everywhere but at 3' by 3' showers, where the code pretty clearly said 36" by 48", but I would check one more time. (After all, I too could be wrong.) She asked me to do that to be sure. When I checked again, sure enough--36" by 48" at all transfer showers. I mentioned it to her again when she walked by my desk to talk to someone sitting near me, and she said, "I've been doing this a long time, and it's always 30-by-48."

That threw up a red flag for me, knowing that the code was very clear on this. It further threw up a red flag because of her tone of voice and body language--all that was missing was a Beyonce-style Z-snap when she finished her sentence. She was about ten to fifteen years older than me, and I know that interior designers catch heat sometimes from architects because they may not always understand all the ins and outs of building and accessibility codes. Perhaps some of her attitude was coming from a feeling of being challenged by someone younger, or by someone who thought she was "smarter" than this interior designer. However, some of my fellow architects in the office had bumped heads with her on code issues before, and I felt this was no different.

"Here, let me show you the piece of code; perhaps I'm reading it wrong and you can help me," I said. I had already marked the page in the code book, and I showed it to her. She read it...and was beside herself.

"Well," she said, putting on an air of sophistication, "what made you judge this shower room as a 'Type A' residence?"

"I didn't," I replied calmly and pointed to the section number by the code paragraph. "This is in section 6, which is just plain old plumbing fixtures."

She was stunned for a response, and it took her a moment to recover and then thank me for finding this bit of code for her. I checked the rest of her floor plan, fixed anything that was noncompliant, and went on my way. I was polite and considerate as I showed this interior designer the error in her understanding, which is important. No one wants to be told they're wrong, then be proved wrong, then get made fun of. I was clear, nonaccusatory, and civil. But I didn't buy her excuse of "doing this a long time." That's a lazy and condescending excuse, and there's no reason you should ever accept that as a good reason.

On Friday, we'll talk about estimating the time it takes to get work done. In the meantime, if you have something you'd like to see discussed or a question to ask, feel free to do so in the comments or via email in the sidebar. Thanks!

Monday, September 28, 2009

"We can't afford for interns to go to meetings."

I thought I might take this week to talk about a few sayings I've heard time and again in the architectural profession, and this is one of them that I've heard recently (and about which I asked in a past last week). I've heard it said more than once that a firm cannot afford to have interns at meetings, and I cannot entirely agree nor disagree.

Why aren't you being taken to meetings with clients, consultants, and contractors? There may be many reasons, but ultimately it boils down to a relationship between money and skill. Drawing takes a long time, and interns are not only good at it but also don't cost a lot in the eyes of the owner/client, the folks paying the bill. If the hypothetical architect of an earlier post charges the owner $85/hr for an intern's time and $100/hr for a licensed architect's time, and drawing takes a lot of time, then it makes sense to have the intern do the drawings while the architect does the meetings. And not to diminish what you do with a mouse, but my own mother went back to college and gained an associate's degree in computer drafting and design at the age of 51. I mention that because a professor of mine once said that he could teach anyone to use CAD, but he can't teach just anyone to think architecturally. Hence, you only need a certain amount of experience and skill to do the drawings.

The architect has generally spent more time working on projects than an intern, and s/he generally has more experience with projects and will know the kind of information to gather, questions to ask, red flags to raise, etc. in a meeting. She will know enough about construction administration to discuss RFI procedures with the job superintendent; he will know enough to ask a client about workflow and staffing in a department that's being renovated; she will know enough to push back on the engineer who insists that the electrical room "just can't get any smaller" (or to know when the engineer is telling the honest truth about that room size).

But how is that architect's experience gained? By doing, of course. And sometimes that doing involves going to meetings. I learned some about what it takes to put together a hospital by doing the redlines that were brought back to me from meetings, and I filled in that knowledge by reading the AIA's healthcare guidelines, but what really solidified my education was going to client meetings with my boss and watching and listening to him ask questions and pull information out of these nurses and doctors and administrators, who knew plenty about replacing a hip or administering chemotherapy but who had a hard time understanding what our 2D plans and elevations meant in terms of real space.

The biggest thing you learn by going to meetings is a skill that college really has a hard time teaching you (if it does at all) and that is how to (and how not to) communicate. There is a science and an art to listening, to reading people's verbal and nonverbal cues, to saying 'no' to a client when they're asking for something that they'll hate in less then a year and then helping them understand why you're saying 'no' to them when they're paying your fee. I recently got the chance to lead one of these user group meetings with a hospital, and while I was a bit clumsy at first, I got better as I went. When the conversation got off track and the users started wondering about things that would have no real effect on the project, my boss was able to pull the conversation back to the plans and elevations that I was trying to walk them through. I filed his words and approach in my head, knowing that it was okay for me to use such words to guide folks back to the task at hand without offending my clients. That sort of skill must be modeled, not dictated. While I try to outline those skills here, it's really more helpful if you see someone do it in real life--it really makes a difference.

On the one hand, it seems indulgent that architects would budget in time for a "lowly" intern to go to meetings, but to me it makes sense, at least a couple of times. I know that when I've been present at meetings and looked back at my boss' notes or at the redlines generated from those meetings, they make way more sense. By hearing the conversations that led to the decisions that have been transcribed or redlines, I also had an overarching idea of why we're doing what we're doing and how to solve problems in the future on this project. If you're in a meeting with some user groups, and the head of accounting bristles at the idea of having his department near plant operations, then you know in the future not to locate those departments near each other under any circumstances. Furthermore, you've internalized that knowledge in a way that no meeting note saying "Accounting should not be near plant ops" ever could convey. If I ran the zoo, I'd make time for interns to make at least two meetings on a decently-sized project. And they'd get at least two site visits after construction commenced, if not more. Interns need to see who they're working for and how the things they draw get built. It makes your work more concrete and make sense. And you deserve to learn on the job--that's the whole point of internship.

On Wednesday, we'll be talking about one of my least favorite phrases ever, which is mostly used by lazy people. In the meantime, if you have a phrase you've heard over and over and love or hate it, mention it in the comments or via an email to me from the sidebar. Thanks!

Friday, September 25, 2009

So, what *is* an architect?

Eric over at BlueArchitecture has a great post about the legalities of calling oneself an architect, whether one is licensed or just in posession of an architectural education. It's important to remember that in the eyes of the design and construction industry, one has to be licensed to say "I'm an architect," but Eric (rightfully so) gives us some food for thought on that narrow definition.

Thursday, September 24, 2009

Do you get to go to meetings?

Before I get too far into my next post, I should ask: how many of you now or in the recent past get to/got to go to meetings? Did you go to meetings with the clients? The engineers? The contractors? Anyone? Ever? It's usually been my experience that interns rarely if ever get to go to meetings for the projects on which they work, and while I understand the reasoning behind not sending you, I don't always agree with that reasoning.

Sound off in the comments or even in an email in the sidebar and share your experiences with project meetings (or your lack of experience thereof). Thanks!

Tuesday, September 22, 2009

The power of the list

Some of us are natural born listmakers; I am among those people. I regularly make lists of what needs to be done on my project(s) so that I can cross tasks off and add new ones on, and it also helps keep me organized. Listmaking doesn't come naturally to everyone, and if you have a solid, proven way to keep track of everything you need to do that doesn't involve a list, then don't sweat it. But if you find that you're forgetting to get things done or you're missing deadlines or major details, then I encourage you to give it a try.

The real power of the list is when it is shared. When you deal with other team members in your office, emailing out or tacking up a list of who's doing what and when it's due is a good, clear way to keep everyone accountable and make sure your team is on the same page. That goes doubly for dealing with consultants that aren't in your office, like engineers or various other design professionals like interior designers or landscape architects. Back in the day, when iPods were just coming out, I used lists to keep everyone on track when I was doing CA on a hospital in the next state over. On Friday afternoons, I sent out a list of the upcoming deadlines and issues of the next week, and I sent out a list of outstanding RFIs and whose court they were in. Years after the project was over, one of the engineers told me how handy that was to have once a week. (I realize this sounds like you're doing a bit of parenting, or at the very least you're kinda doing other people's jobs for them, but remember: architects are the ultimate coordinators on a project, especially up until the contractor starts building the project. You will have to look at everyone's stuff before it goes out to make sure it jives with what you've drawn/designed. Therefore, you occasionally will have to remind people of deadlines and commitments.)

Some project management software will do some of this coordination and listmaking for you, but sometimes it's good just to remember what all you have to do yourself. I recently began making a list of everything that still needed to be done on my two projects, and it hit me: I'd been incredibly busy for the past month. I'd been feeling tired, and no wonder given the tasks I had left to do and the deadlines to do it in. Making lists for yourself can help ease your weary burden when you show them to your boss. When they ask you to do yet one more thing, you can show them the list and ask, "what would you like for me to move down the list so I can do that for you?" Remember the boss' paradox: they don't always know what you're doing, but they know how well you do it. Lists remind them of the first part.

Sunday, September 20, 2009

Back shortly...

I've received some good input and questions in the few short months that I101 has been on the internet, and I appreciate every email, comment, question, and correction. All the input I've received has been useful and informative, and I will be addressing those ideas in the next couple of weeks. I try to make sure I've posted something well-thought out and decently researched on Mondays, Wednesdays, and Fridays, but the last half of my week last week had me working 13-hour days full of back-to-back meetings and even having to go in for half of Saturday (which I haven't done in a while). Hence, it's left me with low energy and the desire to sleep in and shuffle around in my jammies.

You'll have days, weeks, and perhaps even months like this in your professional career. Maybe not so much now, but when the economy and the workload comes back, those days of overwork shall return. When they happen, make sure you're good to yourself when you're not at work. Get some sleep, forego that third drink at happy hour for a good dinner and some rest, go for a walk or a bike ride or a yoga class. Do what you need to do to get recharged...which is what I'm doing. My posts for this week will be a little late, but they'll be done. I really appreciate y'all continuing to visit the site, and feel free to share your own stories of overwork in the comments on via email from the sidebar. Thanks!