Moving Offices

 

Unfortunately I've been bad at writing Blog entries the last two weeks.  :-( 

 

One of the distractions has involved moving my office again.  This is a standard event at Microsoft, and happens regularly as different product teams grow or reorg in size.  According to a recent MicroNews chart (our weekly Microsoft newsletter) there were 25,155 office moves at the Microsoft Redmond/Issaquah buildings alone over the last year (which translates into a lot of packing/unpacking).

 

This particular move was a very welcome one for my team -- since prior to it we were distributed over two wings of a large building.  I find proximity one of the key things to building team focus and energy, and so jumped at the chance to consolidate all of us in one place (we now own an entire south wing floor of the same building). 

 

At Microsoft, we use the word "campus" to describe where we work -- since the buildings are spread out somewhat like a university setting.  The campus includes a baseball diamond and soccer field, various outdoor basketball courts, and a small pond (appropriately nicknamed "Lake Bill") which is nice to lunch next to in the summer.  Various senior execs have either been dumped into the pond, or forced to swim across it, by cheering employees to celebrate key moments during the company's history.

 

All but two of the buildings on campus are new ones that have been built by Microsoft over the last 20+ years we’ve been headquartered in Redmond.  The location before Microsoft arrived was a sparse forest primarily used by people doing dirt-bike racing on the weekends – although you’d never guess that if you saw the sprawling campus today.

 

Building numbers at Microsoft are based on the order in which the company received planning permission to build them – not the order in which they were actually built or the numbers of their surrounding buildings.  This tends to confuse the heck out of people who expect that Building 25 would be next to Building 26 – when in reality they are on completely opposite sides of the campus from each other (Building 25 non-intuitively sits between Buildings 20 and 21).

 

One of the fun games that used to be played with new hires was to have an anonymous person call them late in the day telling them that they had to pick up a new security badge in Building 7 – and that they had to hurry because they closed in 20 minutes.  The poor person would then frantically run around campus trying to figure out where the building was (usually expecting it would be in the vicinity of buildings 4, 5, 6 or 8, 9, 10).  After getting very lost, confused and anxious, someone would finally take pity on them and explain that there was no Building 7.

 

Building 7 was originally slated to be next to 6 – but was never built.  Because the company was expanding so quickly, it was decided to make Buildings 8, 9 and 10 twice the size of the previous ones (which involved using up most of the space originally intended for Building 7).  Sticking to the building permission naming pattern, the new buildings were named 8, 9 and 10.  Building 7 lives on only in mythology (it was a location in the fictional MicroSerfs book).   Sadly – the increased prevalence of campus maps in every building lobby prevents this game from working as effectively in recent years. :-(

 

Different buildings at Microsoft tend to have slightly different atmospheres depending upon their size, shape, and the era in which they were built.  The original 1-6 buildings tend to be laid out a little more close and intimate (they also only have two floors).  Buildings 25 and higher are a little more corporate and spacious.  I’ve worked in 5 different ones over my career at Microsoft: Buildings 26, 6, 31, 10 and 42.  With the exception of Building 10 (whose mirrored double X wing layout scheme was so hopelessly confusing I sometimes had trouble finding my own office), they’ve all been great.

 

Building 42 has been my home for last 4 ½ years, and is probably my favorite (lots of space, tons of conference rooms, and a great view of the Cascade Mountains).  It is also a little unique in that it straddles the line between the cities of Redmond and Bellevue.  This was apparently something of a challenge when getting planning permission – since Redmond had a town ordinance that prevented buildings from being more than three stories tall, while Bellevue allowed an unrestricted number of building floors to be built.   

 

Microsoft wanted the new Building 42 to be a nice four stories tall -- but despite the fact that 2/3rds of it would have lived in Bellevue, the planning permission folks in Redmond apparently insisted that it not be more than three.   After a lot of wrangling, they finally reached a compromise whereby the 1/3rd of the building that lived in Redmond was built to be 3 stories tall – and the 2/3rds of the building which lived in Bellevue was built to the full 4 stories in height.

 

If you are ever driving past campus on 156th Avenue, you can spot the exact Redmond/Bellevue city border by seeing where an otherwise normal, professional looking building suddenly changes height. 

 

As of last weekend, I now live in the part of it which is 4 stories tall….

 

Published Saturday, March 15, 2003 6:27 PM by ScottGu

Comments

# re: Moving Offices

Saturday, March 15, 2003 10:49 PM by G. Andrew Duthie
GREAT blog entry, Scott!

Even though it had nothing really to do with .NET, the history lesson on how buildings are numbered, and the history of building 42 was well worth the read. I shall indeed look for the change in height in your building the next time I'm in town.

# re: Moving Offices

Sunday, March 16, 2003 8:28 AM by Tomas Restrepo
Cool Story. It's funny, but I've been down in building 42 a few times and had *never* noticed that :-)

# re: Moving Offices

Sunday, March 16, 2003 10:02 AM by Hanan Cohen
I hope MS have an Intranet. If not, searching Google for "microsoft campus map" gets the work done. No building 42 on this map but no. 7 is clearly missing.

# re: Moving Offices

Sunday, March 16, 2003 1:03 PM by William Tell
sounds like MS designs its campus like it designs its software

# re: Moving Offices

Sunday, March 16, 2003 2:25 PM by Anonymous
It's actually a wonderful thing that Building 7 was never built. The site, just south of Building 5 and 6, was landscaped into one of the prettiest parks on campus. There are 15 or so Douglas Firs larger than 100 feet tall, remnants of the forest that fringes campus, that gave the surrounding suburb the name Sherwood Forest. The Teufel Landscape company (Teufel means devil in German), Microsoft's landscapers, maintains a nice grass lawn, walkways and picnic tables in there.

It was our favorite place to practice during nice weather when a group of us MSFT employees learned to play hand drums (congas and djembes mostly) out on Building 7 in the early 90s. We hired teachers to come in once a week on Wednesdays to help us learn new things.

# re: Moving Offices

Sunday, March 16, 2003 2:26 PM by David Luebbert
It's actually a wonderful thing that Building 7 was never built. The site, just south of Building 5 and 6, was landscaped into one of the prettiest parks on campus. There are 15 or so Douglas Firs larger than 100 feet tall, remnants of the forest that fringes campus, that gave the surrounding suburb the name Sherwood Forest. The Teufel Landscape company (Teufel means devil in German), Microsoft's landscapers, maintains a nice grass lawn, walkways and picnic tables in there.

It was our favorite place to practice during nice weather when a group of us MSFT employees learned to play hand drums (congas and djembes mostly) out on Building 7 in the early 90s. We hired teachers to come in once a week on Wednesdays to help us learn new things.

# re: Moving Offices

Sunday, March 16, 2003 4:11 PM by Danny
Another piece of brilliant user interface design!

# re: Moving Offices

Sunday, March 16, 2003 6:02 PM by Me
Who cares?! What's yor next entry gonna be? An explanation of why there's blue & orange badges? Only a Microsoftie cares about this meaningless stuff.

# re: Moving Offices

Sunday, March 16, 2003 9:29 PM by Charles Nadeau
"Building numbers at Microsoft are based on the order in which the company received planning permission to build them "
This is almost exactly the way the Japanese system works. It drove me crazy when I arrived but now I am used to it... But it is still illogical by "western" standard.

# re: Moving Offices

Sunday, March 16, 2003 9:43 PM by me
Argh... urban ledgend. Building 40-43 or whatever are entlrely in Redmond, as are 116 and so on. They are in a different zoning district however, like Group Health. (The border is Bel-Red road behind the campus until it hits Northup, then 148th straight north 'til around 60th, where Kirkland is.)

Personal favorite: 31-32.

# re: Moving Offices

Monday, March 17, 2003 3:28 AM by Scott Knaster
I always heard that building numbers in the 40s were in Bellevue -- that's why 40 et al were built before the 30s were finished.

# Bldg 7

Tuesday, March 18, 2003 4:46 AM by /cco
Actually, building 7 wasn't built because of fire code restrictions. Until relatively recently, there was no access to that part of campus from Bel-Red rd (it was too narrow to get permission for a driveway), which made the Bldg 7 site too far from the entrance for timely access by emergency equipment. MS wouldn't pay to widen Bel-Red, so the city wouldn't let them build on the site.

# re: Moving Offices

Saturday, March 22, 2003 2:01 PM by Jim Ross
Hi Scott,

Moved offices eh? Hope you got one with a window this time, and maybe enough room to at least swing a cat.

# re: Moving Offices

Monday, March 24, 2003 10:17 AM by Dave
Funny about the campus map being online. I was on campus last week and having left my map in the car, asked one of the receptionists for one. I was told they weren't allowed to give them out for security reasons.

And yes Scott does have a window. But the office is only big enough to swing a mouse.

# re: Moving Offices

Thursday, March 27, 2003 12:07 PM by anonymous
this page is completely unviewable using mozilla. please test in more than one browser.