see you when we see you
Yesterday we held a farewell party for Glenn, my operations manager, and Vlam, my buddy. Glenn was the third operations manager I've been under the supervision of in two years (yes they do seem to come and go fast); and I was assigned to be Vlam's buddy when he was a new hire. Actually the party yesterday was centered on Glenn, since Vlam's "surprise" despedida party was held last Thursday at my pad, plus we have a farewell outing at Fontana tomorrow c/o Vlam. Anyway, yesterday was their last day in the office, and the farewell party made it seem so final. Well, granted it was final, and I just felt an overwhelming sense of sadness especially watching my buddy pack his stuff from his trolley and back up his files (thanks for the MDO/ISIS files Vlam) and wrap up his laptop and seeing the white clearance checklist. At the same time, I am glad for new opportunities that come their way, and I have only happiness and success to wish them in their new endeavors.
Here's the poster/collage we made for Vlam (acknowledging James' help with the creation). As a farewell gift, we gave him two framed 8x10 photos.
It's actually two images combined into one. To check out the individual posters in their original size and complete version, click here and here.
Other Work Ramblings:
1. Our team is expanding, and so is the floorspace we're occupying. Soon our team will be all over the 35th floor, and it's back to 1 WFH day a week, instead of two. I've always thought the rate of accepting new work is faster than the rate of hiring and ramping up resources to take the additional work on, which causes a strain on existing trained people. I think everyone thinks so. But it never changes. It just goes on and on. When I was hired, there were only about 30 people in the team. Now there's 150. Big difference, huh? And it's hard to get to know everyone anymore. Actually, it's impossible.
2. I am the owner of this beauty care reporting application, and given that my operational background is more on processing, I reeeaaally struggle when I am asked with data quality issues. I try, nangangapa, sometimes not able to interpret the results of my investigations... it's frustrating, but I have no choice, since I'm supposed to be the global application owner and I'm supposed to know almost everything about it. But I don't. Far from it. That's why it's such a pressure. That's why I don't want to take another GAO role again, even when they thrust it to me. I do learn from the experience...but the pressure (and the tears) is so not what I need.
[added September 4]
Thank God for kindhearted souls like Ben who took the time to help check on my application's issue on top of his hectic schedule, especially with various projects keeping him busy.
3. Yesterday was my technical assessment with Bartosz, one of the Warsaw managers, and I guess I was so rattled that in one of my answers I got it the other way around. But I swear I knew the correct answer :p Anyway he asked me how I could balance operations work and GAO work and I...well... I just said I tried to manage. And he asked, what happens when there's an issue with my application and I'm on duty? See that's the hard part when having a 9-hour shift a day during my DM week - I don't have time for anything else. Well I have to make time if my application calls for my assistance. So I do it on top of my shift. As if I have any choice. There's a good side to it, being on the operations team as a GAO - I can take care of the application and be more on the loop on its processing, though I wouldn't be able to monitor it everyday of course. But I don't know. I never dreamed or aspired to be a GAO. Any takers on the role? :p
4.
jimbart used to want a laptop as a workstation, but then changed his mind when he realized that having a desktop means not taking your work home and not being expected to work at home off-office hours because you're not provided when a mobile computer and DSL connection. And he has a point. I like being able to control my time and work whenever I want, but the downside is taking the work home and continuing to work after office hours because you're expected to finish your deliverables, and sometimes the customers can be so demanding. And it also means that Philippine holidays are just work-from-home days for us. Our manager spelled it out to us some time ago. Of course we could choose not to work, IF there wasn't any pressing issue we need to look at or IF we didn't have a duty manager shift. Sometimes I even have to do some work even when I'm on CDO (compensatory day off) because I can't really take my mind off work when there's an issue with my application. It's really not fun.
5. The resignation bug is back. No team is immune.
Like Mike's forwarded email read, "I love my work... I love my work... I love my work."
Here's the poster/collage we made for Vlam (acknowledging James' help with the creation). As a farewell gift, we gave him two framed 8x10 photos.
It's actually two images combined into one. To check out the individual posters in their original size and complete version, click here and here.
Other Work Ramblings:
1. Our team is expanding, and so is the floorspace we're occupying. Soon our team will be all over the 35th floor, and it's back to 1 WFH day a week, instead of two. I've always thought the rate of accepting new work is faster than the rate of hiring and ramping up resources to take the additional work on, which causes a strain on existing trained people. I think everyone thinks so. But it never changes. It just goes on and on. When I was hired, there were only about 30 people in the team. Now there's 150. Big difference, huh? And it's hard to get to know everyone anymore. Actually, it's impossible.
2. I am the owner of this beauty care reporting application, and given that my operational background is more on processing, I reeeaaally struggle when I am asked with data quality issues. I try, nangangapa, sometimes not able to interpret the results of my investigations... it's frustrating, but I have no choice, since I'm supposed to be the global application owner and I'm supposed to know almost everything about it. But I don't. Far from it. That's why it's such a pressure. That's why I don't want to take another GAO role again, even when they thrust it to me. I do learn from the experience...but the pressure (and the tears) is so not what I need.
[added September 4]
Thank God for kindhearted souls like Ben who took the time to help check on my application's issue on top of his hectic schedule, especially with various projects keeping him busy.
3. Yesterday was my technical assessment with Bartosz, one of the Warsaw managers, and I guess I was so rattled that in one of my answers I got it the other way around. But I swear I knew the correct answer :p Anyway he asked me how I could balance operations work and GAO work and I...well... I just said I tried to manage. And he asked, what happens when there's an issue with my application and I'm on duty? See that's the hard part when having a 9-hour shift a day during my DM week - I don't have time for anything else. Well I have to make time if my application calls for my assistance. So I do it on top of my shift. As if I have any choice. There's a good side to it, being on the operations team as a GAO - I can take care of the application and be more on the loop on its processing, though I wouldn't be able to monitor it everyday of course. But I don't know. I never dreamed or aspired to be a GAO. Any takers on the role? :p
4.
jimbart used to want a laptop as a workstation, but then changed his mind when he realized that having a desktop means not taking your work home and not being expected to work at home off-office hours because you're not provided when a mobile computer and DSL connection. And he has a point. I like being able to control my time and work whenever I want, but the downside is taking the work home and continuing to work after office hours because you're expected to finish your deliverables, and sometimes the customers can be so demanding. And it also means that Philippine holidays are just work-from-home days for us. Our manager spelled it out to us some time ago. Of course we could choose not to work, IF there wasn't any pressing issue we need to look at or IF we didn't have a duty manager shift. Sometimes I even have to do some work even when I'm on CDO (compensatory day off) because I can't really take my mind off work when there's an issue with my application. It's really not fun.
5. The resignation bug is back. No team is immune.
Like Mike's forwarded email read, "I love my work... I love my work... I love my work."