09.20.09

Microsoft Compares Its Monopoly to the Older Telephone Monopoly

Posted in Antitrust, Bill Gates, Microsoft at 10:04 am by Dr. Roy Schestowitz

Old phone

Summary: Political acceptance using the company’s image — a debate from within Microsoft

TODAY’s Comes vs Microsoft exhibit is Exhibit px09509 (1991) [PDF], which we already have in the Wiki. It shows just to what degree Microsoft perceives itself as a political movement.

This document is titled “Managing the Microsoft Image for Public and Political Acceptance”. Mike Hall and Bill Gates were sent this by Richard B, whose surname we were unable to determine. Here is the opening paragraph:

The position of Microsoft in the market has grown rapidly; today, it has an impact on the economy, the information infrastructure of business, and the public that is reminiscent of the situation of AT&T in the early nineteen hundreds when telephones had been widely accepted, but not yet become ubiquitous.

This happens to relate to this week’s news. In news of interest, here is Microsoft recruiting people along with oil giant Exxon on campus. Microsoft’s co-founder has also just given more wireless control to AT&T, whose many offences we wrote about here.

Microsoft co-founder Paul Allen has made a deal with AT&T to sell the carrier several licenses for wireless spectrum in the Pacific Northwest, according to Bloomberg. The deal was exposed in government documents, although the agreed price has not been disclosed by either party.

Anyway, Richard carries on by stating:

Peter Drucker has written an account if how AT&T recognized the implications of its position at the time, and how it responded successfully. I would like to recount that story and then suggest how Microsoft’s situation is similar, and how it can and should apply the lessons of our predecessor in order to be equally successful for the long term (25 to 50 years).

“One of the earliest and most answers (to the question ‘what is our business’) was worked out by Theodore N. Vail (1845 – 1920) for the American Telephone and Telegraph Company almost seventy years ago: “Our business is service.” This sounds obvious once it has been said. But first there has to be a realization that a telephone system, being a natural monopoly, was susceptible to nationalization and the privately owned telephone service in a developed and industrialized country was exceptional and needed community support for its survival.

Here is the part which relates to our earlier post about the "Microsoft Hater" label:

Second, there has been the realization that community support could not be obtained by propaganda campaigns or by attacking critics as “un-American” or “socialistic”. It could be obtained only by creating customer satisfaction. This realization meant radical innovations in business policy. It meant constant indoctrination in dedication to service for all employees, and public relations which stressed service.

Kind of like “People-ready”? Or the illusion of “charity”, as illustrated this morning?

Microsoft speaks about “constant indoctrination” and “radical innovations in business policy”. How about “radical innovations” in technology rather than in marketing (“constant indoctrination”)?

Microsoft continues to defend some sort of a communist vision, wherein Microsoft ought to be at the centre of computing for the betterment of society. Their real reason for bringing up the subject is that even back 1991 — well before the USDOJ vs Microsoft case — the FTC called Microsoft “anticompetitive” and actually took action:

Win32 is an alternative standard architecture defined by Microsoft. It is our challenge to alternative standards, and we stand a chance of making it stick because of our dominance in the market. The biggest obstacles to making this happen are probably political rather then technical or business related. This standard is only one of a series we contemplate which lead to a new component architecture and true IAYF.

The recent FTC probe of Microsoft is a symptom of this coming challenge. The probe may fail, and I’m sure there is no basis for it. But it should be interpreted as the warning shot of a war that we will lose if we don’t recognize the danger and take actions now.

The recent letter from Senator Metzenbaum (from OHIO of all places) telling the FTC to pursue this case vigorously because Microsoft clearly has been ‘anticompetitive’ is an example of the kind of political forces that will rise against us as our success and dominance increase, unless we turn this feeling and win support.

Microsoft wants to be treated as though it is a privileged “chosen one” which controls the ‘standards’ and eliminates competition in platforms, supposedly for the benefit of ISVs (current accounts seem to suggest otherwise). It’s very selfish and egocentric, especially given the fact that by this stage, Microsoft had committed crime to get where it was.

We must make it clear that our business is providing the framework and standards for building apps and integrating them into a common framework where they work well together and get the benefits of synergy. We must make it clear that what we do is for the benefit of the majority of ISVs and businesses, and thus for the country, and that it is in their interest to help us succeed. We must set this as our goal.

To accept this goal means to provide leadership for apps other ways besides delivering software such as Windows. We must do other (perhaps less profitable) tasks which contribute to the same goal.

For example, we should take the lead in establishing a common approach to UI and to interoperability (of which OLE is only a part). Our efforts to date are focussed too much on our own apps, and only incidentally on the rest of the industry. We want to own these standards, so we should not participate in standards groups. Rather, we should call ‘to me’ to the industry and set a standard that works now and is for everyone’s benefit. We are large enough that this can work.

Here is the part about “evangelism” and such things:

We should develop spokespeople who can establish themselves as effective advocates for the enablement of a large software industry build on wide standards.

Here is one part about using the education system/s to indoctrinate people while young, having them become mere clients of Microsoft.

We should become actively involved in education in order to enable people to use software – i.e. we should solve the usability problem by attacking both ends of the problem (UI complexity and user experience). We might do this through local schools, teachers, colleges where they prepare teachers for local schools, through universities, etc.

Microsoft then talks about influence in government:

A significant investment is required to do this task effectively. It should be done by a separate group and not by product groups that make their numbers by delivering specific apps. The group should have sufficient talent and experience to deal with engineers in MS and other companies, to deal with the press, with business people, and with politicians.

They should be committed to enabling applications to reach ever wider markets and providing more value by working together. We are too big to treat our business as strictly business – it is a matter of public affairs.

Finally it says:

If we are successful, we will be asked/encouraged/led to extend the reach of our architecture to mainframe and mini computer platforms. Our architecture will achieve the goal that IBM set for SAA. The difference will be that we own it.

“The difference will be that we own it,” concludes this man from Microsoft. Just as Microsoft broke the law to “own” more people’s documents.


Appendix: Comes vs. Microsoft – exhibit px09509, as text


From richardb Thu Oct 31 16:04:39 1991
To: billg
Subject: Managing the Microsoft Image for Public and Political Acceptance
Date: Thu Oct 31 16:59:01 1991
Status: RO

Daryl suggested that I should copy you on this:

> from: From richardb Thu Oct 31 12:22:15 1991
To: mikehal
Subject: Managing the Microsoft Image for Public and Political Acceptance
Date: Thu Oct 31 12:22:11 1991

The position of Microsoft in the market has grown rapidly; today, it has an impact on the economy, the information infrastructure of business, and the public that is reminiscent of the situation of AT&T in the early nineteen hundreds when telephones had been widely accepted, but not yet become ubiquitous.

Peter Drucker has written an account if how AT&T recognized the implications of its position at the time, and how it responded successfully. I would like to recount that story and then suggest how Microsoft’s situation is similar, and how it can and should apply the lessons of our predecessor in order to be equally successful for the long term (25 to 50 years).

“One of the earliest and most answers (to the question ‘what is our business’) was worked out by Theodore N. Vail (1845 – 1920) for the American Telephone and Telegraph Company almost seventy years ago: “Our business is service.” This sounds obvious once it has been said. But first there has to be a realization that a telephone system, being a natural monopoly, was susceptible to nationalization and the privately owned telephone service in a developed and industrialized country was exceptional and needed community support for its survival.

Second, there has been the realization that community support could not be obtained by propaganda campaigns or by attacking critics as “un-American” or “socialistic”. It could be obtained only by creating customer satisfaction. This realization meant radical innovations in business policy. It meant constant indoctrination in dedication to service for all employees, and public relations which stressed service.

It meant emphasis on research and technological leadership, and it required financial policy which assumed that the company had to give service wherever there was a demand, and that it was management’s job to find the necessary capitol and to earn a return on it. The United States would hardly have gone through the New Deal period without a serious attempt at telephone nationalization but for careful analysis of its own business that the Telephone Company made between 1905 and 1915.

Microsoft’s position is not exactly the same, but there are strong parallels.

The establishment of a universal platform upon which to build software applications is in the interest of the general public, and of most ISVs, unless they are in the business of supplying competing platforms.

The explosion of new software applications and ISVs after the market for them was increased by a common PC platform is analogous to the growth in the telephone business as the number of callable subscribers increased. Software system platforms define communities that can purchase software, analogous to the communities served by competing telephone networks of the early 1900′s

Just as the nation needed a common carrier for telephony, this nation needs a single common platform upon which to build software, so that the energies of our software engineers can be applied to building new products at a higher level, rather then systems that duplicate work already done by competing platforms. Multiple system architectures exist today, because the technology is relatively new, and we are still learning what works, but we will converge on a common solution (for example, consider the multiple window systems starting from Xerox Parc’s Star that have appeared). As that happens, competition will be of less value, and the advantages of a tolerated monopoly will be greater. I believe convergence will take place in this decade.

The industry has recognized the value of such a monopoly and has attempted to create one without creating a competitor by establishing committees and standards groups (e.g. POSIX, Xwindows). Unfortunately, such standards are defined by the groups who build systems, and thus will not in fact establish a standard. For telephones, the analogy would be of individual telephone companies which establish interface standards to switch calls between systems. It will work only as wee as such standards – which is to say not as well as a true monopoly where the single vendor could apply more global optimizations and apply larger advantages of scale.

Win32 is an alternative standard architecture defined by Microsoft. It is our challenge to alternative standards, and we stand a chance of making it stick because of our dominance in the market. The biggest obstacles to making this happen are probably political rather then technical or business related. This standard is only one of a series we contemplate which lead to a new component architecture and true IAYF.

The recent FTC probe of Microsoft is a symptom of this coming challenge. The probe may fail, and I’m sure there is no basis for it. But it should be interpreted as the warning shot of a war that we will lose if we don’t recognize the danger and take actions now.

The recent letter from Senator Metzenbaum (from OHIO of all places) telling the FTC to pursue this case vigorously because Microsoft clearly has been ‘anticompetitive’ is an example of the kind of political forces that will rise against us as our success and dominance increase, unless we turn this feeling and win support.

We must make it clear that our business is providing the framework and standards for building apps and integrating them into a common framework where they work well together and get the benefits of synergy. We must make it clear that what we do is for the benefit of the majority of ISVs and businesses, and thus for the country, and that it is in their interest to help us succeed. We must set this as our goal.

To accept this goal means to provide leadership for apps other ways besides delivering software such as Windows. We must do other (perhaps less profitable) tasks which contribute to the same goal.

For example, we should take the lead in establishing a common approach to UI and to interoperability (of which OLE is only a part). Our efforts to date are focussed too much on our own apps, and only incidentally on the rest of the industry. We want to own these standards, so we should not participate in standards groups. Rather, we should call ‘to me’ to the industry and set a standard that works now and is for everyone’s benefit. We are large enough that this can work.

We can take some simple initial steps such as publishing, publish books and articles about existing standards for GUI Interfaces, for apps, and a guide to solving frequent UI issues in a common way. These may be as useful and enabling for our ISVs as the software itself. We can back this up with sample code and tools (such as additional standard Win controls) that simplify building apps according to these guidelines.

We should develop spokespeople who can establish themselves as effective advocates for the enablement of a large software industry build on wide standards.

We should become actively involved in education in order to enable people to use software – i.e. we should solve the usability problem by attacking both ends of the problem (UI complexity and user experience). We might do this through local schools, teachers, colleges where they prepare teachers for local schools, through universities, etc.

A significant investment is required to do this task effectively. It should be done by a separate group and not by product groups that make their numbers by delivering specific apps. The group should have sufficient talent and experience to deal with engineers in MS and other companies, to deal with the press, with business people, and with politicians.

They should be committed to enabling applications to reach ever wider markets and providing more value by working together. We are too big to treat our business as strictly business – it is a matter of public affairs.

If we are successful, we will be asked/encouraged/led to extend the reach of our architecture to mainframe and mini computer platforms. Our architecture will achieve the goal that IBM set for SAA. The difference will be that we own it.

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

What Else is New


  1. Team UPC Keeps Pretending That UPCA Can Still be Resurrected (Even Without the UK, Which is Strictly a Requirement)

    The latest distortion of facts regarding the Unified Patent Court (UPC) Agreement (UPCA) as seen from the lens of people who seek to profit from such distortion



  2. 'Ethical Source' is Not Ethical and Not a Movement But a Misguided Self-Serving PR Stunt

    Something which is neither enforceable nor ethical is being promoted by profoundly unethical media in the pockets of large corporations



  3. InteLeaks – Part XXI: Intel Seeking Advice From a Bunch of Clowns (Harbor 'Research')

    A firm called Harbor 'Research' is making dubious recommendations to Intel; as shown in the above video, there's also an obsession with buzzwords (typically suggestive of a lack of technical grasp/understanding)



  4. IRC Proceedings: Monday, January 18, 2021

    IRC logs for Monday, January 18, 2021



  5. The US Election Was Not Rigged, But the Nomination Process Was (Undermined to Maintain Control by Oligarchy)

    Cheating/driving the left out of the Democratic Party seems like a longstanding tradition and we know who stands to gain from it; moreover, problems remain in the voting process because it's controlled by secret code of companies like Microsoft (in spite of the openwashing)



  6. InteLeaks – Part XX: Redacted (for Names Only) Release of Intel File About Developer eXperience (DX) Meddling in GNU/Linux

    Today (or tonight) we release the first 'phase' of InteLeaks in a sensibly redacted form; coming up next is a surprise from Team Microsoft



  7. Sites in Bed With the EPO and UPC 'Covering' the 'News' Without Mentioning Any of the Overt Abuses

    It is rather sad that blogs like IP Kat have turned into proponents of abusive EPO management and Team UPC increasingly resorts to lying using pseudonyms (to avert criticism and accountability); much of the rebuttal or response that’s hinged on reality/facts can only be found in comments, which are still subjected to a face-saving moderation process (conducted by Team UPC)



  8. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part IV: Stories From the Depths of the Free Software Foundation (FSF)

    To reduce or alleviate suspicions and a potential of mistrust the FSF needs to become more transparent and liberate information (such as the real reason Bradley Kuhn left, as noted in the previous part)



  9. Links 18/1/2021: GNU Radio 3.9, Wikipedia at 20

    Links for the day



  10. InteLeaks – Part XIX: Intel's Web 'Experts' Seen as Microsoft Champions Dealing With the Platform Microsoft is Looking to Destroy

    Things aren't rosy at Intel because the hires aren't suitable for the job of documenting and/or presenting GNU/Linux-centric products (whose target audience is Free software developers)



  11. Adding Images as Characters to the Daily Bulletins of Techrights

    Our daily bulletins now have inside them coarse graphics, depicted using characters alone, and the tool used to generate them announced a new release earlier today; we showcase some of its features (in a new video)



  12. Links 18/1/2021: Weekly Summaries and Linux 5.11 RC4

    Links for the day



  13. IRC Proceedings: Sunday, January 17, 2021

    IRC logs for Sunday, January 17, 2021



  14. The Oligarchs' Parties Will Never Choose the Side of Software Freedom Because Free Software Cannot Bribe Officials

    The tough reality is that next week's (or this coming week's, depending on what Sunday counts as) inauguration ceremony is partly symbolic as all the same and important issues remain largely untouched, for corporations control almost everything of significance



  15. COVID-19 Has Actually Helped Software Freedom Due to Financial and 'Spare Time' Factors

    Developers and users are increasingly exploring what the Free software world has to offer; this is actually measurable and it contradicts claims to the contrary



  16. Future Plans and Using Videos to Complement Text

    Remarks on recent and impending site changes; We are not replacing text with video, we're just trying to enhance the presentation a bit, especially where visuals help make a point or where browsing through Web sites (or leaks) is more suitable than static, linear presentation



  17. InteLeaks – Part XVIII: Intel Does Not Know How to Properly Do Research and It Seems Apparent Unscientific Methods Are Used to Justify Poor Documentation

    There appears to be a severe crisis at Intel; they cannot recruit scientists (or those whom they recruited are walking away) and as a result the company produces bad products with poor documentation (or highly defective chipsets that top-notch marketing cannot compensate for); in this video we walk through some examples of how studies are being conducted (as already noted in Part XVII)



  18. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part III: The Free Software Foundation (FSF) Seems More Like a Victim of Destabilisation Campaigns

    The Free Software Foundation (FSF), which turns 36 later this year, is looking to raise money that helps support the GNU Project, soon 38 years old and likely the most important Free software project to exist (ever)



  19. Links 17/1/2021: EasyOS on Raspberry Pi and GNU libsigsegv 2.13

    Links for the day



  20. InteLeaks – Part XVII: The High Cost of Microsoft Windows Users in GNU/Linux Development Teams

    A look inside Intel explains what holds back the technical team, which bemoans the lesser technical people getting in the way and not even using the product that they are writing about



  21. IRC Proceedings: Saturday, January 16, 2021

    IRC logs for Saturday, January 16, 2021



  22. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part II: Why Bradley Kuhn Left the Free Software Foundation (FSF)

    The founder of the FSF is still at the FSF (albeit not publicly) and the person who lobbied to oust him has basically been 'banished' by the founder



  23. Links 16/1/2021: LibreOffice 7.1 Release Candidate, Zeroshell 3.9.5, FreeBSD Report, and GhostBSD 21.01.15

    Links for the day



  24. Free Speech on the Web Not Respected by Companies That Used to Support Software Freedom

    Mozilla does not have to make its Web browser about politics; it can just make an excellent piece of software that is neutral about the Web pages that it renders, based on the user's personal preferences



  25. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part I: We Are Under Attack by Corporations and Their Salaried Facilitators

    The corporate takeover (taking over the Commons, produced by volunteers who are motivated by altruism) is a subject we must speak about and somehow tackle; this series will highlight uncomfortable or difficult truths



  26. InteLeaks – Part XVI: Intel Cannot Do Command Line, Even When It's Vastly Simpler and More Suitable for Development

    The Developer eXperience (DX) team at Intel seems to be full of Microsoft drones instead of developers and/or mildly technical people; this has not only harmed the quality of documentation but also upset staff, alienating people who actually understand what developers need (more than buzzwords like "DX")



  27. IRC Proceedings: Friday, January 15, 2021

    IRC logs for Friday, January 15, 2021



  28. Links 15/1/2021: KaOS 2021.01, Whisker Menu 2.5.2, Istio 1.8.2

    Links for the day



  29. InteLeaks – Part XV: Intel is Blind to Blind and Colour-Blind People

    Intel does not seem to grasp very basic concepts associated with accessibility; nevertheless, Intel shamelessly tries painting itself as "woke" and a "justice warrior" (policing speech while overlooking much-needed practical work)



  30. Links 15/1/2021: GStreamer 1.18.3 and Proton 5.13-5

    Links for the day


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts