Friday, June 5, 2009

Every boss is crazy 'bout a sharp dressed intern

Summer is upon us, and nowhere is it more apparent than in the office.  Sleeves are shorter, pants go from wool to cotton, skirt hemlines are higher, boots have been traded in for sandals, and hair goes up into ponytails.  But it's summertime that highlights the importance of dressing well in the office because it's the time most interns (and office employees in general) show too much skin and make regular attire faux pas.  With a few exceptions, the workplace in general has become less formal with regards to dress code.  It's something of a carryover from making our office discourse less formal; when "Mr. Swenson" becomes "Dave", it seems odd for him to still be wearing a tie, cotton/wool slacks, and super-shined shoes.  However, less formal does not mean casual or even schleppy.  First, here is a list of things that should never be worn in an office.  Like, ever.
  • Camisoles and tank tops: ladies, if there isn't at least a cap sleeve on it, save it for after work.  And fellas, if I hear of any of you wearing a tank top outside of the gym, you will answer to my wrath.
  • Flip-flops and hiking sandals: if it's a shoe you wear while doing summer water sports, save it for those water sports.
  • Shorts: a couple of years ago, women's fashion magazines were flogging "formal" shorts to go along with those lacy camisoles-as-shirts I mentioned above.  Shorts are shorts, ladies.  No one needs to see that much of your leg.  If you wouldn't wear a skirt that short, then don't wear a pair of shorts of the same length.  And fellas, there's no reason to ever wear shorts to work unless you're only going to be there for a couple of hours, and then you're going hiking/camping/golfing, in which case just go have fun and quit rubbing it in our faces.
  • Bare tummies and cleavage: regardless of gender and physical condition, no one wants to see your bare midsection, not even a one-inch sliver of it as you walk to the copier.  And with the low-cut shirts and low-cut pants (for both genders), it's really important to think about your frontside and backside cleavage.  When you sit down, can anyone see that much of your behind?  It's not just women with the low-cut shirts, though; fellas, button every button on that shirt except for the top one or two.
The list above doesn't put that much off limits, so what should you wear? First, let's review what business casual means.  It generally indicates that you wear at least khakis or nondenim pants or skirts, shirts that usually have some kind of collar like a polo or tailored-looking shirt (mostly this rule is for men), skirts that at least touch the top of the knee when standing (that goes for women). and polished or clean shoes.  Obviously there are exceptions to these admittedly broad rules.  Here in Colorado, the combination of cold and snowy weather with an outdoorsy culture makes fleece tops and closed-toe hiking shoes acceptable workplace attire.  And granted, as architects and design professionals, we have some creative leeway with our clothing.  It's almost expected that we'll dress a little more daring or interestingly, but there's still plenty of room for creativity to coexist with some professional modesty.  It's also possible to wear jeans in a way that they look professional, or at least grown-up.  Get some that fit well and don't look like you've been working in the yard in them.  In general, whatever you wear should be clean, ironed if it looks like it even remotely needs it, and with no holes or rips or major stains.

Some interns might say, "who cares?  I never see clients, and I should be comfortable while I'm working."  Fair enough, but you can be comfortable without looking like you just rolled out of bed.  Allow me to sound a bit like your parents for a moment: you're not in college anymore.  You're a grown-up and a professional, so dress like it.  Remember, you're working with a lot of people (some of whom you're working for) who came up in a time in which you dressed nicely to go to the store, much less to go to work.  There are plenty of affordable clothing options that aren't a scruffy-looking t-shirt and jeans.  It's called Old Navy.   And regarding the I-never-go-to-meetings excuse, never say never.  One day when I was an intern about two years out of school, a mechanical consultant came to our office for a meeting that my boss had canceled and had forgotten to tell this fellow.  My boss was gone, and so I was called to the reception desk to deal with this fellow, with whom I'd spoken on the phone several times but had never met.  I was wearing a nice silk skirt and dressy shirt and heels that day, and after I informed him that the meeting had been canceled, he asked, "Well, can we meet?  You might be the person I needed to talk to about these duct layouts anyway."  Another time, I was working along when I heard a familiar voice near my desk.  Turns out that a client I had met with a couple of times was in the office to meet regarding another project, and he had stopped by my desk to say hi.  These are just two of many small and large run-ins I've had with consultants and clients for which I was fortunately prepared appearance-wise.  You never know.

But even more than this, remember what it is you do for a living.  You're an architect in an office with a bunch of other architects.  You spend eight or more hours a day in a roomful of people who have an extremely refined sense of sight.  We are a very particular bunch about how things look, about color and texture and proportion.  Add this observation to the fact that sight is thesense that takes up more of the human brain than any other sense, and you begin to understand how much your appearance matters.  Your bosses are looking.  Your colleagues are looking.  They notice if you look like you're always hung over or that you put thought into where you're going in the morning.  

(Also, because architects are good at looking at a building's exterior and postulating correctly on its interior contents and structure, this means that you don't have to dress in tight or revealing clothing in order to attract positive attention from a potential date.  He or she can already tell what you look like.  But that brings up a good topic: interoffice dating.  We'll discuss that next time.)

Wednesday, June 3, 2009

One thing that will make your job (and life) better

I just returned from a long weekend across the country, where I visited my family and gave a guest lecture for a longtime friend and colleague.  My colleague is a college English professor with a deep interest in architecture, and every spring she teaches a class on the connections between art, architecture, and literature.  And every spring, I fly to her town and give a slide show and talk even more about architecture and culture and how they influence each other.  It's nice to put on a resume, sure, but moreover, it's just fun to teach.  It's fun to talk about the things that interest me and answer questions and explain things that I take for granted but others might not understand.

Architecture is an insular profession.  We spend most of our time with other architecture majors in college because our classes, especially studio, are so time consuming that we have to make friends with the other folks in our major and classes.  By the time we get to the workplace, the habit has been ingrained--we work with almost nothing but other architects, so we seek out and hang out with more architects and do architecty things with them.  We talk about how hard we work and how little sleep we get and how do you make CAD/Revit/MicroStation do this or that or how crazy our bosses or contractors are and so on.

Do me and yourselves a favor: stop.

The best thing you can do for your mental health as an architect is to get outside of architecture.  Join some clubs, talk to your neighbors, find a volunteer activity, just do whatever it takes to do things that don't involve architecture.  Go meet people that aren't architects, that aren't even interior designers or landscape architects.  In the past nine years, my circle of friends has expanded to include a psychologist, a cardiac nurse, a physical therapist, a TSA security screener/agent, a librarian, a truck driver, a special education teacher, and two English professors.  While the majority of my friends are still in the design and construction industry, I get to hang out with people that talk about other things and broaden my horizons.  By hanging out with the psychologist, I now co-teach a communication class with her.  By hanging out with the English teacher, I started volunteering at a no-kill cat shelter.  By taking some classes several years ago, I got into stand-up and improv comedy.  Even though I occasionally lecture on architecture and I still work in architecture every day, I carve out time for non-architectural pursuits.  It does two things for me: one, it keeps me from being utterly boring (who wants to hang out with someone who only talks about one subject?); and two, it gives me a break from my passion and profession that leaves me more refreshed and motivated to get back into it.

Thursday, May 28, 2009

Back in a moment...

I'm in the process of preparing for and traveling to a guest lecture gig across the country, so AI101 is going to be quiet for a few days. In the meantime, the AIA is conducting a poll on renaming the title of "Intern" in architecture. If you think being called an "intern" after 4+ years of schooling is insulting and inaccurate, then go-go-go to the link I've provided and let your voice be heard.

Tell me in the comments as well: what would you rather be called than "intern"?

Tuesday, May 26, 2009

The art of verbal diplomacy at work: disagreeing without being disagreeable, Part 1

Let's face it: at some point at work, someone is going to say something, and you're going to think it's incorrect/slightly off-base/ridiculous.  Depending on what the issue is, you may decide to let it go; picking your battles is a huge first step in disagreeing with others.  Use your energy wisely.  It's probably not necessary to get up in arms if someone misquotes who won the NBA Finals in 1986 (it was the Celtics, by the way) or who designed the World Trade Center Towers (Minoru Yamasaki).  However, if you decide that you should call someone on a misstatement, there are a few things to keep in mind.

As we discussed last week, inappropriately framed criticism at work makes you look bad.  If you want to be heard, keep it civil and remember the following:
  1. Any statement generally falls in one of three categories: True, Partly True, or Not True.  All you have to do is address the amount of truth in the comment/statement/criticism--no more, no less.  If Patrick has a history with more than one project manager of missing deadlines, then saying "Patrick gets his work done late" is True.  If Patrick missed the last couple of deadlines but is usually on time, then saying "Patrick gets his work done late" is Partly True.  If Patrick is rarely if ever late with his work, then saying "Patrick never gets his work done on time" is Not True.
  2. Deal with the problem, not the person.  For example, your statements need to be more "when we miss deadlines, it makes us look unprofessional" versus "When you slack off and don't get your crap done, we look stupid."
  3. Keep your tone of voice even.  This can help keep the conversation from getting heated, which is when people take things personally and say things they don't mean (or do mean but aren't meant for anyone else to hear)
  4. Keep your disagreement in the service of the job (or relationship).  You want Patrick to be on time so that the project team has enough time to review everything once more before the work goes out, and that makes your office look good.
  5. Choose your words carefully.  "Always" and "never" are loaded words, so either throw them out or use them sparingly.  Very few things happen always and never.  The sun always shines during the day, and it's never out at night...unless you live above the Arctic Circle.  Also, see the statements in #2 above; words like "crap" and "stupid" have more emotional (and insulting) meanings than "miss deadlines" and "unprofessional."  Again, this is a good place to avoid profanity.
Having said all this, what do you do?  First of all, be clear as to what your objection is.  Is the other person misquoting a fact (e.g. she says that it will take a week to get the drawings done, but it will really take two weeks)?  That situation is easily resolved: a simple, "Actually, Mark, given the rest of the work we're having to do on the site plan, it's going to take us about two weeks to get all that done" will make that happen.  Some folks (more women than men, I'd say) are reluctant to correct someone in front of a group, but that is exactly where you need to disagree and set the record straight.

More difficult to deal with is when the other person makes a decision or states an opinion, and you see a better or different way of doing something.  For example, your design team is working on a restaurant located on the corner of a four-lane street and a two lane street.  Jill wants to locate the service entrance and loading dock off the four-lane street.  However, Cody believes that locating it there will put an icky blot on a major street frontage, which should be reserved for the nicest-looking facade.  

Cody could be a jerk and curtly say, "NO.  That's gonna be nasty on the main street.  We gotta put it on the back side."  He'll be much better served if he says, "Hm, the thing about that is that now we have a not-so-pretty service entrance on a major street right where we want our nicest face to be.  However, if we put it on the other side, where this two-lane street is, we can save the facade and still have street access for the delivery trucks."

Now, it's Jill's turn to disagree without being disagreeable.  It's also her turn to stick up for herself if she really believes in what she's saying.  If she realizes that Cody is right, she can utter the two sweetest words in the English language, "You're right."  If not, she needs to present her side of the situation: "Well, you make a good point, Cody.  That is the major facade, and it's the place to make the building look good.  Problem is, the owner of this restaurant gets several deliveries a week from tractor trailer trucks, and those trucks will have a hard time making this curve and parking decently on this two-lane street.  However, big trucks can come right down this major street and either use the whole street width to back into a dock or only take up one of the two lanes going south while it unloads."

What if Cody didn't know how the owner gets his deliveries, but Jill did because she gets to go to client meetings and Cody doesn't?  Jill needs to share that in the interest of having the whole team on the same page, and Cody needs to accept that information without getting all offended that he wasn't at the meeting.  What if Cody is a better designer than Jill, which always leaves her feeling a bit jealous?  Cody needs to use his good design sense to make a better project, and Jill needs to acknowledge and use Cody's abilities and observations without brushing him off or allowing him to design at the expense of function.  As long as Jill and Cody are speaking to each other without hostility, this is a chance for them to work the bugs out of a design, make a great project, and disagree with each other without later branding each other with "what a jerk".  

Be very careful in writing and emails.  I cannot stress this enough.  When you need to disagree with something that has been written or stated elsewhere, be very careful with how you go about this.  Acknowledge that the other party has made an assertion, and acknowledge any amount of truth in it that you can.  Bear in mind that most people make assertions based on something they have learned through their experience, so they're not trying to be wrong (and they may not be wrong at all).  That's why acknowledging any truth that you can is so helpful--it shows the other party that you're trying to understand how they see this.  Then, make a statement of disagreement such as:
  • "Given that, we have yet to find any evidence to support/disprove..."
  • "In light of this, we have found..."
  • "However, it has been my/our experience that..."
  • "My/Our experience of this has been different."
  • "However, we think/believe...because of...."
  • "Regardless, it is our recommendation that we...because...."
  • "After reading your email, we felt some additonal research was necessary, so we called the state inspection board/went back through the 2006 IBC/shook our Magic 8-Ball, and found that..."
The final statement in that list is especially useful.  When you disagree on a factual point, have the resources to back you up handy, and send them along with your email.  This cuts short any back-and-forth between the parties and keeps the discussion moving forward.  Be sure that you frame your disagreement in such a way that it is in the service of the job.  You want to make sure everyone's on the same page, or you know that this contractor or enegineer does great work and you want to make sure that this one little thing doesn't trip them or the design team up on the project, etc.  

It may seem like we're doing a bit of fancy footwork and almost being extra nice to others, but that's hardly the point.  Think about it: do you like being told that you're wrong?  Do you relish someone verbally gut-punching you with "No, moron, that's not how we do that"?  And do you like being told that by someone who knows less than you or is way younger than you?  Then why should it be any different for how you treat others?  Remember that as an intern, you may be disagreeing with electricians who have been wiring buildings since you were in third grade.  You'll be challenging architects who are licensed, and you're not.  You may be telling a world-class brain surgeon what he has to have in his surgery center, whether he wants it or not.  Speaking a correction respectfully to others gets you much farther than just being right ever does.

Friday, May 22, 2009

Workplace informality and the false sense of security

How many of you reading this call your boss Mr. Swenson or Ms. Patterson?  That's what I thought.  Up until the past fifteen or so years, calling your boss by their surname was the norm, while now it's the exception.  Mr. Swenson and Ms. Patterson become Dave and Joan.  Suits and hats give way to polo shirts and khakis.  The nice sit-down dinners you invited your boss to at your house (prepared lovingly by your stay-at-home wife) turns into happy hour after work or a cookout with a group of your colleagues.  Your boss is less of a stiff stranger in the office; you feel more comfortable coming to them with a problem on a project, and you don't feel like you have to hide the fact that you have a life outside of work either.  Your boss is a human, just like you.

The decrease in formality that we've seen since the 1980s is refreshing, but it has its drawbacks.  While it's helpful to remember that your boss and your colleagues are indeed human and have good days and bad days, it's important to remember that you're still at work, and at work business comes first.  That means keeping water-cooler/coffee machine chat to a minimum, providing civil but clear constructive criticism, and getting your work done comes before socializing and cutting out to do extracurricular activities.  To be sure, work is easier when you get along well with your colleagues, and it's vital to take mental breaks during the day.  It's how you go about these interactions that makes the difference.

A rule of thumb is to edit yourself on the side of caution.  Providing a few details about your hobbies or your weekend makes you human and tells your colleagues about your interests, but no one needs a five-minute description of the Star Wars theme party you held, what your cat's facial expressions mean, or just where you got sunburned at Burning Man.  And no one--no one--needs or even wants to hear how drunk you were or how hungover you are this morning.  Ever.  Please spare us all that visual.  Not only is it too much information, but it can also paint you as unprofessional.  You're 25 and you still don't know what your limits are regarding alcohol consumption?  Someone needs rehab.

In college, architecture students get really colse to each other.  You're not only classmates, but you also truly become friends.  Friends talk to each other in a different way than coworkers.  You can tell an architecture school friend, "Dude, put a sock in it--your floor plan looks like a dumpster fire."  That kind of criticism is sure to offend and/or alienate your colleagues, and forget saying something like that to a boss unless you enjoy looking for a new job.  You'll have to learn the skills necessary to disagree with others and say no with clarity and civility.

Next week: the art of verbal diplomacy at work.

Wednesday, May 20, 2009

What up, dogg? Losing the attitude in speech and writing, Part 2

Email is an easy form of communication, but that ease is a double edged sword.  Simple, one-button functions like Reply, Reply All, and Forward makes it so easy to exchanges ideas and responses with one another and keep everyone on the same page.  Each of those buttons makes these discussion easy, but they can bite you.  It's easy to see how Reply can get you in trouble.  Anytime you get an email, you have to read it and take a breath before you respond.  Even the simplest statement or request can have big repercussions, so take a moment before responding.  Take two or three moments when you get an email that sounds obnoxious or rude or seems to be asking something that you're not qualified to answer.  This is when it's especially important to forward the email to your project manager (if they weren't copied already) and ask him or her what the right course of action is.  Reply All can be a problem when you just meant to email one person.  That's usually a problem when your response was meant as a private joke to one person and suddenly everyone's wondering where the profanity or snark is coming from.  Guess who looks unprofessional?

Forward gets you in trouble not because of you forwarding something on but by someone else forwarding your email to others.  Any email you send can be forwarded on to anyone, and you should write them with that possibility in mind.  The reason people love Forward is that the recepient can send information to others without having to do a lot of typing or translation.  Back in the day, exchanging and sharing information with others was a little more arduous.  For example, with phone calls, you either had to call other people and tell them what the first person said on the phone, or you had to type up a phone memo and fax it to everyone.  Either way, it was easy to make a mistake and either mis-hear, mis-remember, or mis-translate what someone else said.  Email makes it easy to ask a question, get an answer, and then distribute that answer to all parties without losing anything in translation--that's the beauty of Forward.  The ugly side of Forward, of course, is when someone emails something unprofessional--profanity-laced, sarcastic, accusatory, whatever--to other parties, especially to those about whom the email was writted.  Yikes.  Guess who looks really unprofessional?

Every email you send is a written (albeit electronic) document that could be used against you.  Every email you send from your office email account belongs to your company, not you.  That means that your company has the right to search your email at any time, and every email you send can be used in court.  While helping with a court case about a year ago, I had to do dig through some old files from a project I worked on when I first started at my job.  I saw some faxes and emails I sent when I was only a year out of college, and I was embarassed.  I'm sure the contractor to whom I was writing found my casual, sometimes silly messages amusing, but I shuddered at the thought of any of these documents being reviewed by a jury.  What would they think as they read these documents, something like What kind of architecture firm would allow such teenage behavior out of their employees?  Where they supervising her?  How shoddy!  Would the informal, sarcastic nature of my communiques hurt us in a court of law?  Again, yikes.

Informal speech such as dude, like, yo, holla, y'know, stuff, and whatever can be misinterpreted in emails, and they can be just as bad in spoken interactions.  Every filler word in a spoken language (such as like and y'know) trips up a listener and postpones the point of a sentence.  This is the opposite goal of workplace communication.  People have things to do and places to be, so the clearer your sentences are, the better.  Workplace informality may put employees at ease, but you should never let your guard down.  Avoid filler words and profanity (even if your boss uses it constantly), and think through your statements so that when you speak them aloud they come out clearly and as quickly as possible.  Your boss, consultants, and coworkers will thank you.

Monday, May 18, 2009

What up, dogg? Losing the attitude in speech and writing, Part 1

One of the greatest struggles of the 21st-century workplace is that of good communication.  Many interns have grown up with email and PowerPoint and have spent some of their formative college years using instant messaging and text messaging.  Familiarity with these forms of high-tech communication would make one think that interns would be especially good at workplace communication--they're all good at exchanging information briefly, clearly, and quickly.  Or are they?  My experience has shown me that there's a little something to be desired in workplace communication, but with a little practice the gap can be crossed.

The thing that interns need to keep in mind is that your bosses almost invariably are old enough to be your parents, or at least a youngish aunt or uncle.  These people came up through school learning a lot more about essay writing, whereas many of you may have learned more about passing tests so that your high schools could maintain funding.  (I'm not saying you didn't learn something in English class about how to write clearly, but the input I'm getting from all the college professors I know is that the emphasis on good writing in high school isn't what it used to be.)  Also, these people didn't grow up with email--they're more accustomed to using a phone to ask someone a question or a fax to exchange information--they're not used to scanning and emailing documents.  Why is this difference important?  Not because it means that your boss is a fuddy-duddy (though they may be, I don't know your boss personally), but it means that the previous standard mode of communication has something that email does not: nuance.  When you hear someone speak aloud, you can tell if they're reticent or enthusiastic, sincere or sarcastic.  Not so with email.  You can email the words "you look nice today" to someone, and depending on the person's mood, they could read it as if it's a compliment or as a subtle jab at the new slacks they bought last weekend.  Keep this in mind in when sending an email.  Whatever you write could be read more than one way, especially depending on the words you choose.  

Let's say you need a CAD background for your project so that you can do some coordination a week before the CDs are due.  The backgrounds were due on Monday, and everyone sent them to you except for the electrical engineer.  It's now Tuesday, and you need his backgrounds, end of story.  You're annoyed, almost angry, because this guy keeps doing this to you.  So what do you do?  You could handle it by phone, but let's say you decide to use email to school this slacker.  Fair enough--you can copy your boss on the email to let her know that the engineer is underperforming and leaving you hanging.  But you still can't be a jerk.

At first, you think you should just lay it out:
Mark,
I asked for everyone's backgrounds on Monday you didn't send me yours. Where are they?  Everyone has sent theirs to me but you.  I need them now.  This is the second time you've done this.  Is there a problem?
Lulu

Okay.  That might work, but it could be construed as obnoxious and wagging a finger in Mark's face "Everyone has sent me theirs but you," like you're saying "all the other kids are good, why can't you be good?"  Please note that I'm not saying how you feel is invalid; you have every right to be annoyed with Slacker Mark.  But if you convey any attitude, Mark gets to ignore you.  No, I didn't respond to Lulu's email--she's a jerk!

So let's try again:

Mark,
I still need your backgrounds so I can do final coordination for next week's deadline.  Please let me know if you cannot get them to me by noon today.
Lulu

Better.  The request is in the service of the job--"..so I can do final coordination."  Also helpful is a finite deadline, which is now noon today. Furthermore, this email puts the onus on Mark if he can't get them to you in a timely fashion.  He has to let you know if he's going to be later than noon.  Now let's say Mark emails you back to say that Paul, his draftsman, emailed you the background yesterday afternoon.  Your email back:

Now you're just messing with me.  What email did he use?  Try it again, dude.  I'll call you at 11 if I haven't seen them yet.

Hm.  It's brief and to the point, but again it could read as a sudden attack of snarkolepsy.  "Now you're just messing with me" could be delivered with a laugh over the phone, but in email it can be read as a dig.  The same goes for "dude;" with the wrong tone of voice (spoken or interpreted), it can be snide.  Let's try it again:

What email did Paul use?  Please have him check the spelling (or forward him this email) and have him give it another shot.  I'll check my spam filter to see if it caught his email, and I'll call you at 11 if I haven't seen it again.  Thanks!
Lulu

Again, better; problem solving is combined with civility and less room for interpretation.  Whenever you write an email, pause and reread it slowly and carefully for any possible landmines.

In the next post, we'll talk some more about "dude" and why you should always write as if your email is going to be forwarded to the New York Times.