My first week at Microsoft
Wow. It’s over. Finally. And now I can reflect back on my first week as a member of the collective. Here’s some photos of the campus back when there was snow:
Here’s Mt. Rainier towering over Building 42:

Here’s the mountains behind 156 Ave:

The implant didn’t hurt all that much. My first couple of days at Microsoft involved signing up for various things like benefits, payroll, and parking. It also involved going through New Employe Orientation, where you get to find out some more things about the history, size, and ‘diversity’ at the company, as well as things that you can and cannot (well more about the cannot part) do as a Microsoft employee – essentially your responsibilities as a corporate citizen.
Here’s a photo of Building 122:

Jon Udell was in my orientation class, and he had a great observation about just how confusing the benefits presentation was, and how it can be improved using social networking technology. The idea is to hook up people with similar life circumstances with each other so that they can discuss these things. For example a benefit like the flexible spending account is important to me since Matthew’s in preschool, but that same benefit would be unimportant to the new college hires that were in my orientation class because of their differing life situation.
I believe that some of this stuff can be answered using some of the internal mailing lists at Microsoft. As a new hire, I’m wary about drowning in email, so I’ve avoided (so far) signing up for those distribution lists. Instead, I’m relying on the ‘hallway advisors’ to help me out. There are a remarkable number of folks that I have met / know that have been out on paternity leave over the past year or so, so there’s no shortage of people in similar ‘family situations’ to me.
I managed to accidentally score a window office as my team is in the middle of an office move. I’ll enjoy it while it lasts – I suspect my new office will be next to the boiler room in the basement :)
One example of the sheer size of Microsoft involved getting my alias setup. The seven letters of my name (John Lam) are not unique enough to generate me an alias that would not be ambiguous or just outright silly (and I didn’t get an ambiguous alias). Thanks to some lobbying on the part of my manager’s manager, we fought the IT policy … and won!
I attended my first few team meetings as well, experienced the joys of observing a re-org that I wasn’t a part of (or frankly could really understand), as well as getting the experience of being the dumbest guy in the room. There’s an enormous amount of information overload as you walk into a world that, while somewhat familiar from the outside, is very different since everyone here is focused on what the outside world would call a ‘future release’.
I’m also spending time figuring out what it means to be a ‘Program Manager’. I suspect that will take the longest amount of time to figure out. But as far as I can tell, it involves an awful lot of meetings :)

















Recent Comments