Back to 044. Our First Big M&A Deal (Beating Netscape)
Please keep the feedback rolling in. This post concludes with shipping Office 97. It represents the end of the first era of the PC, where the focus was on features, retail consumers, tech enthusiasts, and mostly just getting stuff to work and shipping. The next couple of chapters represent a major shift in the PC as the focus turns to the enterprise business and the primary customer the business itself and professional IT.
Office96 was quickly becoming the biggest slip to an Office or Apps release in years, and that was extraordinarily disappointing. We reached our Zero Bug Bounce milestone (ZBB, because for a brief moment the product would bounce around a mythical zero bug count) in July 1996, and that was great. We were also behind our original schedule by months, and we knew there was no way to catch up. We needed more time. We felt like s**t.
I did not always go to lunch in the building 17 cafeteria but happened to go one summer day. I was waiting to pay, holding my two slices of Marriott cheese pizza, when I heard, “SINOFSKY! SINOFSKY! WHAT DO YOU MEAN YOU ARE CHANGING THE FILE FORMATS?? WE CAN’T DO THAT!”
SteveB was yelling across the cafeteria at me, and all of a sudden, I felt like a few hundred people got quiet and were watching to see how I reacted. His voice seemed to come from everywhere, so it took me a moment to locate him. A 10-minute conversation followed that started in earnest as he made his way toward me about the reality that Office 97, as it had been officially named, had a whole new architecture with loads of new features for document creation like drawing and fancy Word tables, animations in PowerPoint, and new charts with top-notch graphics in Excel. Word and Excel changed the file formats to support these features. A changed file format meant a customer file such as FOO.DOC or FOO.XLS on disk was only compatible with the version of the app that created the file, or a newer version. Trying to open FOO.DOC created with Word 97 on a Word 6.0 setup would give an inscrutable error message. This message would often terrify the user into thinking they had a corrupt file or the computer had eaten all their work. This horrible experience was perfectly normal for state-of-the-art software. I kid you not.
Well, it turned out that the strategy of not changing the file formats in Office 95 (at least for Word and Excel) was a huge hit with the field sales force. So much so that they thought it was our new strategy to maintain the same file formats forever. When, in fact, we thought of 95 as the exception and only way to sync up with Windows 95—we had spent a ton of creative energy arriving at sellable features that did not require a file format change but were severely constrained in doing so.
I never really thought of mentioning this because it was so obvious, or so I thought. Steve thought we were totally screwed and had misled his sales team.
The file format changed probably within the first weeks of the project and was standard industry practice. The success of Office 95’s unchanged file formats caused a bit of a crisis as we were working on Office96. It was obviously both too late and impossible, regardless, to reverse course. HeikkiK coordinated what could best be described as a crisis mitigation plan involving format converters for existing applications and Save As capability within the new versions to produce down-level files (with the risk of losing new features). This was a reasonable solution but would require organizations to install software on every PC, whether it was just a converter for existing computers or the whole new Office 97 on new PCs. In other words what we thought was reasonable was a huge pain. SteveB was right.
The Apps culture was tuned to avoiding crisis moments, usually by rewarding prevention, and a low tolerance for avoidable drama. When a crisis did hit, self-inflicted or otherwise, the Apps approach aimed for cool, calm, collected. ChrisP often described this like listening to the cockpit recordings of Naval aviators landing jets in difficult circumstances. That calm was accompanied by an executive team that did not view a crisis as an opportunity to micro-manage or upend existing processes.
As a result, we thought this through in excruciating detail. All of the test managers and PMs from each team had developed a complete plan to support the new file formats in old products and deliver product updates to existing products, even using the novel approach of internet downloads. This did not solve the physics problem that we could not make the new features of Office96 show up in Office 95 or Office 4.3, but we could ease the pain and prevent people from being unable to open files they received due to the growing use of email.
One bit of good news was that the biggest motivator for changing the file format was to support the new world-wide standard for representing text in computers, called UNICODE, that Microsoft had contributed a huge amount to. Up until then, PCs had a difficult time representing many of the world’s languages and mixing several languages at once was almost impossible. UNICODE was a major step forward and for multinational corporations, the ones complaining loudly to SteveB, easing the pain of multilingual documents was a significant win. A decade later, UNICODE would become familiar to everyone as it supported Emoji.
This was a rare crisis for the team and a good learning experience to the degree that foisting incompatible files across a corporation could be called a learning experience. As an organization this did bring us into the modern, Office-focused world in two ways. First, the crisis created a new muscle, which was driving change to core behavior across all the products. That had to happen. It was the first of what could be called suite-first problem-solving and coordination.
Second, this was such a pain for every team that it served to be an early dose of the enterprise business and what would be different for the team. The needs of enterprise customers became paramount as we moved to future releases, and the solutions to those needs were addressed across the entire team.
Still, this was my first of many, many lessons in the difference between consumer products and enterprise products, between selling at retail and selling through account managers. Because every product always changed file formats, this should have been viewed as routine. But the world had changed—seemingly overnight documents were being emailed around, and all of a sudden it was all too common to get files that could not be opened. In a sense this was really a crisis for the Office business and one that would cause a sea change in how we viewed files. It also happened to be the strength of the internet and the World Wide Web—one single format that could be read by any browser, and soon one language that could be used to write a program once and run it anywhere.
Beyond that it was a lesson in how Microsoft’s customers were changing. The technology enthusiasts who embraced changes and had a high threshold for the pain that random changes caused…