2/ From the earliest days the company was uniquely focused on a breadth product line, and only on software. Those were both unique compared to single-product companies or to the vertically integrated likes of IBM captured by this classic video (c. 1981).
3/ As technical assistant I was there to help with product reviews and serve as a form of connective tissue or glue between product groups executing on Bill's vision. In 1993 Microsoft just launched the 'year of Office' and had started the pivot from apps to the suite.
4/ Managing each large group as a portfolio of "features" and the company as a portfolio of products was key to the approach of both having high standards while also making big bold bets, leaving room for not every bet having to be a hit.
5/ Three next posts detail specific projects kicked off during this time along 3 axes:
* Innovation versus Shipping: Cairo
* Expanding Breadth versus Coherency: EMS
* New Ideas and IQ for the Information Superhighway
Please consider subscribing and join over 9000 others. //
• • •
Missing some Tweet in this thread? You can try to
force a refresh
A topic I end up talking about quite a bit is how org structures evolve. In today's "Hardcore Software" I discuss origins of Microsoft's two main cultures--Systems and Apps. "018. Microsoft’s Two Bountiful Gardens" in Hardcore Software on @SubstackInc…rdcoresoftware.learningbyshipping.com/p/018-microsof… 1/
2/ Mike Maples Sr (then head of all World Wide Products) explained the origin of each culture using a folksy story about "two bountiful" gardens at Microsoft. Apps was 58% of revenue but Systems was top of the food chain, so to speak.
3/ Many are familiar with this image of different tech company org charts. It always drove me bonkers because I felt it did little to understand how or why companies are structured like they are and presumes it is just lunacy. Yes, I get it was to be funny.
Climate of 'fear' prevents experts fro questioning the handling of the pandemic. express.co.uk/news/uk/141589… // this is super interesting and not at all obvious for a true pandemic in a democracy. 1/
2/ WHO has studied pandemics and worked tirelessly for decades in many countries. They serve in an advisory capacity with varying degrees of involvement depending on country. Lots of history going way back, smallpox, HIV, flu, ebola, SARS, etc.
3/ In 2008 a few years after SARS they published an updated Outbreak Communication and Planning Guide. apps.who.int/iris/bitstream…
016. Filling the Void Left by IBM …rdcoresoftware.learningbyshipping.com/p/016-filling-… // Over 5000 have signed up. Please join in, it is great fun. Many stories--history & strategy. Microsoft is transitioning to enterprise products and building "Chicago", oh and the internet.
Also, my first exec offsite.
2/ The offsite was the first time I was at a meeting with a bunch of executives from across the company. There were 9 execs out of the 25 or so worldwide at the company at the time. Attending scored us a wonderful acrylic block. Microsoft loved acrylic blocks.
3/3 Our breakout had to come up with an answer to "Filling the Void Left by the Demise of IBM" which was days away from insolvency and will appoint a new CEO the following week. This was the earliest days of Microsoft's transition to selling enterprise as discussed. Weird slide🤣
Just posted "Every Group Is Screwed Up" in _Hardcore Software_. This is my interview with billg to become his technical assistant. 👇that's the old fountain you could see outside from our office windows. 1/ …rdcoresoftware.learningbyshipping.com/p/015-every-gr…
2/ Check out the post for the adventure (including me humiliating myself). The most interesting thing though was how the previous technical assistant warned me about the job.
Also, he told me to start looking for my next job right away!
3/ He told me that every group is "screwed up" and that becomes readily apparent as you cycle through meeting after meeting. Projects are late, buggy, missing features, and more. I was intrigued by the idea everything was messed up.
The most recent post is the end of "16 bit" era c. 1992-3. Join me as I learn about naming a product and reviews.
2/ PC sales had been slow due to global economic stuff, but the Mac had really slowed (you can see why in one of the magazines below). But recently sales had gone vertical with the success of Windows 3.x
At the same time developers all moved to focus on "Win32" the 32bit world.
3/ That's the market we launched Visual C++ into. Talk about tailwinds. We had a Windows-based development environment that was "object oriented" just in time for this massive uptick.
Windows NT was in beta. The successor to 3.x was under development. Momentum built.
Ever wonder when and how Microsoft made a big bet on Windows? Today’s Hardcore Software shares what it was like to have a bunch of existing confusion clarified by the CEO in a memo. 1/5 …rdcoresoftware.learningbyshipping.com/p/011-a-strate…
2/ The memo was from Bill Gates and detailed a “A Strategy for the ‘90s Windows”. Seems kind of obvious now. But then the company was deep in a partnership with IBM to develop OS/2, the successor to MS-DOS. Windows was a side project.
3/ But Windows 3.0 was selling super well—sales of Windows 3.0 exceeded that if Macintosh by a huge amount, selling over 4M copies in the first year (2.5M Macs were sold that year). OS/2 was not selling well, nor was it making progress in product development that was needed.