Office9 (aka Office 2000) was the very first release of Microsoft Office built by a team that began the project and ended the project as one. Well, almost as there was that pesky Outlook challenge. That said, the project was coming to a close by the end of 1998 and it was late. It was not terribly late or out of control as I reflected on my 1:1 with SteveB, but late nonetheless. The way old-timers would talk about projects to me was that product development slogs “really sucked” and then you ship and that is the “best feeling ever” and it is worth it. I was hoping to feel that way soon. The last month of 1998 would be eventful for me personally and the team in ways that were unexpected, both happy and tragic, and a reminder of the scale at which we worked.
Back to 054. Steve and Steven Get New Jobs
Not only were we five months late by the end of 1998, we also faced the lag time that would happen on the other side of our pending a holiday break. It became clear our end-of February completion date for Office9 was going to be a challenge.
At least we were on the glide path to completing the product before we left for the holidays. As far as the enterprise sales team was concerned, we were going to finish in the first quarter, which was important for customers buying or renewing volume license contracts. Office 2000 was shaping up to be a significant release for the end of the millennium. And yes, Office 2000 was Y2K ready.
As I prepared to head to Florida for holiday vacation to see family, JonDe let me know that I was being promoted to corporate vice president. This was truly a big deal personally, and as I look back I realize it was a big deal for the company. Along with BrianV leading Exchange a press release would go out announcing our promotions in about a week—the ranks of executives were small enough then that not only did we do press releases for promotions, but we became named officers in the company and the two latest additions from the product development teams. If you’ve ever been part of a rocket ship, what you experience is growth in executive promotions when you start to wonder if this is a worthy promotion or will people outside your immediate group roll their eyes. NatalieY, the spiritual and cultural leader of the company in human resources, sent me an incredible note telling me how “real” the promotion was which meant everything. These insecurities come with what does seem like one of the most significant milestones in a career and for me, I will always think of this as the most significant, owing much to JonDe and all of the Apps people before him.
While everything was the same organizationally, what was simply a title change in the Exchange address book was the start of being treated differently, particularly by those I did not yet know, especially in the field sales org, and, perhaps even more entertaining, by the various Microsoft systems and services.
In short order, Colleen Johnson (CollJ) was being briefed on the exec travel desk (EXTRAVEL), executive tech support (EXECSUPP, yes, there was special on-call PC and tech support for executives), executive shuttle (sort of an Uber for VPs to go between buildings that I almost always walked anyway), and even the special team that helps make PowerPoint slides for execs, and so on. I knew these existed, but I thought they were for Bill, Steve, the CFO, and Board, not all the VPs. Oh, and my card key worked in all sorts of places it used to not work, like weekend access to the Executive Briefing Center! I did have mixed feelings about special treatment for run of the mill execs in product groups. The teams were all incredibly nice, but this felt like excess to me.
CollJ was a key addition to our team who had an outsized impact on our operational excellence and culture. Hired as an administrative assistant, she quickly and quietly assumed the role of indirectly managing the dozens of administrative/group assistants across the team (on average one for every 100 people) which was the front line of our culture of careful management of resources. She also took on the role of formalizing all our headcount tracking which was a key enabler for how I would manage the team. A dumb example was instituting a code in our SAP-based system for what individuals worked on (Word, Excel, Office shared, etc.) and what functional group they were in (dev, test, program management). Amazingly our systems did not track that and yet it is all that mattered in managing a significant team. For decades neither she nor I managed to coach other teams into managing this way, even after the yearly visits from teams being told to learn a best practice from how we managed things. There’s a lesson in there—you can’t manage a big team at scale if you don’t know what people are working on and how humans (not dollars) are allocated!
Colleen also led our efforts at developing a new more scalable Office culture. Too much of Microsoft was still acting like it was college when it came to team outings or now operating like a fancy Wall Street bank when it came to using company resources for events. From figuring out how to get a huge discount on team movies by renting all the theaters for morning shows and offering family friendly and alternatives to the current sci-fi release, to helping teams to know about $250/day offsite locations (including a stop at Fred Meyer for snacks) instead of the $2,500 locations (before the required hotel catering), Colleen instilled a broad sense of fiscal and cultural responsibility across the team of admins. She helped to create whole classes of events such as our product vision meetings, the “tradeshow”, and especially our launch events. As the team grew, the tradeshow became a hallmark event where every member of the team had a chance to experience all the other teams building Office as though we were at a tradeshow. Years later, Microsoft Research would adopt this format for what became the Microsoft TechFest event.
As a VP I quickly learned people I did not know would no longer email me directly and even people I did know would soon also employ the level of indirection afforded by CollJ. The Microsoft culture had developed an arm’s length VP culture, where contacting a VP meant going to the Exchange address book and looking up the direct reports of a VP to find their Executive Assistant to contact about “getting time with” or “what is the best way to email them”. Exchange had a unique feature where you could offer an assistant direct access to an email account as a delegate. Suddenly VPs were having admins screen email and even respond on their behalf. How quickly we became “big”. Along with helping people to email me directly, Colleen had to remind people of one other quirk of mine I insisted on, which was I managed my own calendar. I was hardcore about this because of what I’d gone through in terms of the ripple effect of scheduling. A meeting was scheduled with an exec, the executive assistant moves the meeting for something important, then everything dependent on that moves as well. Soon the one person who needs to get out of the way, the VP, is the barrier to making progress as a routine course of business.
I think I spent the rest of my years trying to hold on to a feeling of small, and avoiding the distant feeling new hires (and we had hundreds every year) would have towards execs. I think I had varying degrees of success at doing so and certainly made my mistakes at trying, but with Colleen’s help I worked hard at that for my run, even as we scaled.
The press release went out while I was on the way to Miami…