Yes. I wear many hats. I am referring to my job…not a physical hat.
But first. I would just like to say, I love Maria Sharapova. Well…ok. I don’t know her so thus I do not truly love her. But from a pure visual sense, she is one hot woman. All 6′ 2″ of her. My god… I am not ashamed to say that I have stopped fast forwarding on my DVR when I see her Powershot commercial. What I would do to be her pet dog like in that commercial… (^_^)
I mean…sure, back in the day Anna Kournikova was attractive but she has got NOTHING on Sharapova. She’s hot on TV. She’s hot on interviews. She’s hot with no makeup on and sweaty while totally concentrating on the tennis court. Am I obsessed? No. Or at least I don’t think so. But…yeah…yum…
How can you NOT say she’s a hottie? Hm? HMMM???? (Oh, and for anyone in the market for a camera, the Powershot is a really nice one!)
…ok ok. Back to what I was going to write about. I apologize for going off on a tangent.
So yes…hats. I assume you’ve all heard the expression “wearing many hats”. Basically, my job has me doing many things and dealing with many responsibilities. Why am I bringing this up? Because today was one of those days when I must have worn at least 6 hats. Also because the phrase “…so…what DO you do??” has been asked a few times again to me from various people. That question seems to come up in waves of about every 5 months.
You see…my “official” title is “Director of International Product Development”. This was given to me so I have a title when I started to do the work that I do now opening up the Japanese and later the Asian market. It also made sense back then since I really was working closely with Development to make our software international. These days though, I am still officially in the Development department though I no longer code. That is mainly because I am more of a technical resource for the company. I am a freelancer. I do what needs to be done and when and if something has to be done outside of the standard procedure, I also get to be one of the ones picked only because my time is not charged to the customer or partner and I am not in the typical departments like technical services that has to account for their member’s time and work. There are a few other people like me. It’s an interesting job…
But for me, since I focus on mainly the Japanese market and I tend to be the driving force behind it that is directly dedicated to it (as opposed to, say, our CTO who is all for it, gives me 100% support, but has millions of other things to deal with too) there are days, like today, where I need to deal with multiple departments and make decisions or steer decisions or at least help come to a decision on various aspects…thus the multiple hats.
So for anyone curious, come with me to a fun review of my hectic day…and for all of you who know me from work…why most of the time I am nowhere near my desk…
Hat #1: Project Manager - We are doing a custom integration project with a partner. There are various aspects of it that makes it very very very tricky to not just program it but also to test it and, when problems arise, debug it. And since this partner is in Japan, the e-mail is in Japanese, and the sentiment and the procedures and the information needed is…well…very Japanese. So, I get to translate the e-mail. Understand the e-mail. Help the tech guys who are working on this understand why I am asking so many detailed questions that they really don’t want me to ask (”…so why did we mess this up?” “So, can you say for certain that this is indeed the problem?” “…why?? Why can’t it be this?” “You’re sure?” etc…). Unlike many times in the US, the Japanese customer wants details. Ridiculous details. And they are very direct in terms of what they want to know. And as usual, they want it yesterday. So I get to oversee it all respond diplomatically and with tact in Japanese via e-mail and, if I need to, jump departments to get resources, I do. Which brings me to #2…
Hat #2: Quality Assurance - In today’s case, I look at the issue and listen to the programmer and realize that there is something more to this. I can’t test it since I don’t have the code or the environment but by looking at the logs, I can ask the right questions to get things rolling. Having a background in this helps as well since I can look at the logs and the various information handed to me and start to think about how it can be replicated or what has to happen for this to be replicated here. I also know just the right question and wording to use when talking to Development (coming up next) to get the answer that I need or to get them to understand what I’m looking for.
Hat #3: Development - Then, due to the fact that I have been here for 11 years (well, 11 years next Monday) and I have a more direct relationship with the VP’s and managers, I can speed things up like I did today by directly going to the person responsible for the portion of the product that I have a question on and ask him directly. The other programmers may not have a direct line or it will be difficult for them to escalate the question to this point. Most of the time I don’t do this. In this case, the issue was hot and time was short, and so I acted alone and decided to get the ball rolling a bit faster. Of course, they will respond to me at a very detailed level so having 8.5 years of experience writing this product helps.
Hat #4: Sales - Meanwhile, while all of this is happening, I am getting frequent phone calls from the first floor where our sales people are. We have 2 great Japanese women downstairs in sales doing all the stuff necessary for us to succeed selling our software in this sometimes incredibly difficult country. Whenever they want an opinion on what to do or what course of action to take, they will involve me. Not because they have to but because I have been involved in this from the beginning and I can at least bring some insight into this. Also as I am outside of their department, I can then say things or ask for things from other departments such as technical resources that may be difficult for them. Throughout the day, I am also dealing with actual sales decisions and reading and filling out RFP’s and finding out what solutions work best and if we should pursue certain opportunities. But all from a technical bent. Ask me about contracts or our P.O. procedure and you will get a sad blank look from me…
Hat #5: Marketing - Of course, in the end, to sell, we need to advertise and make collateral. Everything from a 20 page main product catalog all the way down to a 2 page slick with a whitepaper thrown in there for fun. Not only do we need to come up with the content in Japanese but we need to work on presentation too. It has to LOOK Japanese after all and this is not easy. At all. Where do I fit in? I work to make sure that various aspects of marketing and sales are communicating and making sure that things are moving along smoothly. Making sure that the whitepaper is being designed with the correct thought in mind and even going so far as approving design choices…which to be honest…is the hardest thing for me to do as I don’t have a degree in marketing or design work. But I can at least say what looks good or what doesn’t and ultimately (and thankfully) the marketing guys realize that no matter what they think, me and a few others are the ones that has to personally hand out these marketing materials so, if we don’t like it, it has to be changed. But yeah…marketing.
Hat #5.5: Marketing pt. 2 - Of course it’s not just pamphlets and catalogs. We have events coming up that we need to decide what to do. I am not directly involved in this myself but I do make myself available to give comments and suggestions and also to help in making sure that, if we have speakers, they know what they are going to say and are ready since, 9 times out of 10, I get to be the interpretor on stange with them…
Hat #6: Translator / Interpretor - This is self explanatory but I do also deal on a slight basis with our translator to make sure that we are getting what we really need translated first and that the information on our web page and such are correct. I used to be more involved in this back in the day when we were deciding for example, how in the hell to say “Rendition” in Japanese. These days though, I tend to be more involved from a “stay on top of the development’s effort to get the things ready for Arabic (right to left)” type situation. I also do field questions from translators doing new languages like Chinese on how we translated certain words in Japanese and such and also how to decide how to say certain words when those words do not exist in their native tongue. Fun stuff…
Hat #7: Travel Agent - Yup. For example…today I get a panicked phone call from downstairs because a key person for our next trip to Japan just informed us that she is coming in not on Sunday but on Monday at 7am since she has to make a brief stop at a different country. But we have a meeting at 10am in Tokyo Monday morning that is very difficult for us to reschedule. But Narita Airport is pretty far away from Tokyo. And it’s rush hour. And we have no idea how long it will take her in immigration or customs. AAAAA. So I had to pull out my train schedules and such (all online thankfully) and figure out if she gets in at this time then what train she needs to take and to where to transfer to what so as long as she is in business attire when she lands in Narita, we can do a luggage transfer to someone else at this station and she goes on to her meeting just in the nick of time at 10am and so on with other contingency plans in case that train is full or she comes out late or there is a delay in the trains and so forth. …yeah… Fun stuff….
So this was just today. Other days I am also doing voice overs for our online demonstrations or doing web demos from home at the wee hours of the morning. At times at a trade show, I’m the chump outside of our booth bowing to everyone walking buy and sticking out our marketin slick in front of them hoping they will take one and maybe read it later. Or I’m doing an interview to see if someone is a good candidate for a position with us. Or I’m talking directly with a VP to tell them that I found someone for a different international market and that we need to give the person a chance. Or sometimes my past catches up with me as I get a phone call about an old program I last touched 4 years ago that a customer has a question on. Then I’m in a different meeting trying to coordinate communication among multiple departments since we don’t have that one true overseer (which I also don’t want). And then I’m in Japan or elsewhere in the world doing techincal training with their tech guys and sometimes even sales training. Then I’m the complaint department while I’m in Japan and also a mediator. I try to explain to the Japanese in a way that they will understand and vice versa for the US since business practices can be so different it’s scary.
Back when we were a small company and I was 1 programmer out of just 10 or 11 or us, the term “this is not my job” never came up. We did what we had to do to succeed. And not always programming either. If it had to be done, there was no question. It was done. And now, as a company of over 700 with close to (or maybe we’ve gone over already) 90 programmers, once again, I do what needs to be done. I can’t say “this is not my job” since…well…my job is to do what needs to be done…
And throughout it all, I try…oh I try….to remain as positive and as upbeat as possible. If I freak out or if I get negative or if I get emotional, then it’s over. I have to keep my cool just so things go smooth. Just so everone involved in this effort can also keep moving forward and keep driving this towards eventual success.
And through all of this, not one grey hair.
COME ON!!!
I want that cool grey hair man. Just to PROVE that I am doing something. Just so people can go “wow…Tim must be pretty stressed out.”
…instead I get the occasional, “…you’re kind of like a rougue employee….what do you really do?”
I do lots of things kid. Lots of things……….
Fun times…fun times…
(^_^)