There was a birthday celebration of sorts last week. From the October 29th edition of ABC News Science & Technology:
While the actual date of the Internet’s birthday is somewhat debated, many say that the Internet was born 40 years ago today at the University of California, Los Angeles, when a computer to computer message was sent for the first time from the UCLA campus to Stanford.
At the time, Leonard Kleinrock and his colleagues were charged with developing the Advanced Research Projects Agency Network (or ARPANET), a government-funded research project in global computer communications that eventually grew into the Internet.
I thought it would be a good occasion to reflect on how easy it is for Loose Cannons to get smashed by colliding worlds.
In the days before ARPANET, computer-to-computer communications were homogeneous, and computer manufacturers liked it that way. The very idea of not owning every aspect of a technology stack seemed to be ridiculous. Where’s the value if you can get critical components from anywhere? What if competitors start using the same suppliers? Heads of business units hated the idea, but Loose Cannons kept proposing technical architectures that looked, well, open. The idea was playing out in many ways in many companies.
At IBM, two architectural revolutions were simultaneously underway. We now know that they were related. In the summer of 1980, IBM executive Bill Lowe prepared to brief the company’s Management Committee on development plans for a personal computer:
It was a dangerous place to be. The Management Committee — or, given IBMers’ fondness for acronyms, the MC — ruled on issues that couldn’t be resolved at lower corporate levels, so going before the committee was, to IBMers, like going before the Supreme Court. It was actually rougher because the top IBM executives who sat in judgment were known to be brutal, especially if they thought someone was wasting their time.
Bill Lowe had been beaten up by the MC before, but this time Lowes’ plan to use outside suppliers drew polite questions from MC members who expressed some concern about turning over even partial control of any of their businesses to “outsiders.” What Lowe and the vast majority of IBM engineers didn’t know was that earlier in the year the MC had received a forecast for global PC sales that showed a peak market of 80,000 units in that began to rapidly decline in 1984 as the specialized customer need for computers was satiated:
IBM had already been embarrassed by early missteps in the PC market but the corporate culture was focused on mainframes and services. Problems might be created by opening up the hardware and software architecture of personal computers, but
The general attitude…was that you don’t have big problems in small markets, and we thought the personal computer was a very small market.
The MC might have been more inclined to turn its attention to a market that had real legs. Like, say, networking. Ed Hendricks was an engineer at IBM’s Federal Systems Division in San Diego. Hendricks had helped design VNET, at that time the largest computer network in the world. VNET was IBM’s internal corporate network, linking IBM mainframes at scientific data centers. By 1980, VNET was a global asset with hundreds of hosts in North America, Europe and Asia.
Meanwhile, ARPANET was growing into the Internet, and Ed Hendricks was interested in how IBM’s technology would continue to prosper when the world started connecting IBM mainframes to large UNIVAC computers, HP mini-computers, PC’s, and supercomputers from Cray or Control Data. Hendricks became an industry player in this arena, collaborating with my colleague Larry Landweber at the University of Wisconsin as the expansion of the ARPANET began in earnest. Ed Hendrick’s IBM Internet Gateway Project was aimed squarely at insuring that IBM mainframes would not be stranded in a world in which they could only talk to each other:
The objective of this project is to begin to bridge the gap between IBM computer systems and network technology predominant among government agencies, conractors and universities. More specifically, we are working to develop according to DOD standards the technical capacity to interconect networks of IBM computers and systems to similar but different computer networks used by government agencies and their affiliates.
Hendrick’s website preserves the sometimes heated but thoughtful and deep technical discussions — involving Hendricks, the legendary Jim Gray, and MIT’s Jerry Saltzer, among others — that took place througout 1980 about the relative merits of ARPANET and IBM’s networking strategy. For reasons that are still unclear, IBM decided to move the Internet Gateway Project to IBM Research in Yorktown Heights, New York, an effort that Hendricks calls “screwy.” Hendricks along with team members Gerot “Mike” Engel and Dale Johnson planned to spend a week at Yorktown Heights, getting comfortable with IBM Research’s Systems Laboratory, their proposed new home:
…the Systems Laboratory was created to focus more directly on perceived business needs. Consequently, Systems Laboratory projects are evaluated and prioritized on the basis “leverage” they exert on the software product line…by design, ninety-five percent of the work carried out in the Systems Laboratory is so closely related to strategic product development that it cannot be discussed outside IBM.
Shocked, the Internet Gateway team concluded:
…a project such as ours which is intended to establish internet communication compatible across differing systems…could not be carried out under such guidelines. Our overall reaction…was that the ARPANet Internet Gateway project could not have been started within the Systems Laboratory.
They concluded that if the project was to have any chance at all of success, there would need to be a formal review of management decisions, what IBM called the “Open Door” process.
March 14, 1981
John R. Opel, President IBM Corporation
Dear Mr. Opel,
This letter is intended to invoke the IBM Open Door Policy. My purpose in requesting this Open Door is to seek clarification of the decisions which led to a situation where a project which is clearly critical to IBM’s future posture in the data communications industry cannot be pursued…Bureaucratic accomodation for only that which is in the strategic plan is a very dangerous posture to be in while the data processing and communication industry is rapidly evolving.
[My team and I] have been working to carry out a project to establish a capacity…to cooperate with the U.S. Government and University Computer Science departments in the evolution of techniques to interconnect dissimilar computer networks…There is essentially unanimous agreement that this activity promises important advances for IBM and for computer technology in general.
In September 0f 1980 we were notified by our management that this work could not be carried out…On each occasion when this qustion [of where the work could be carried out in IBM] was being escalated to the proper level, my management would insist that I leave the management issue to them and to concentrate my own efforts of the technical work.
Last week I was informed verbally that no sponsorship for this project could be found. My manager asked where hie should look to find me a job. My position was…that inability to find organizational sponsorship for the project is not equivalent to a decision that IBM should not be involved in developing the capacity to interconnect IBM networks to government and university networks…to look for other professional opportunities now and give up attempts to pursue this technology…would be to let the company down….
19 March 1981
Mr. Thomas J. Watson, Jr., Chairman Emeritus
Dear Mr. Watson,
My employment with IBM has been terminated as a consequence of recent management decision which are incompatible with my professional goals…I believe I am justified in requesting more thorough and explicit responses to the following questions:
- What “business needs required the termination of our ARPANET Interconnection Gatweway Project and the abandonment of the…professionals we had been dealing with?
- What factors prevented alternative organizational arrangements that would have allowed our group to continue its work within IBM?
- What is IBM’s posture regarding professional cooperation with the computer scientists working in association with DARPA…to establish mutual techniques for interconnection of dissimilar computer networks?…
May 15, 1981
John R. Opel, President IBM Corp.
Dear Mr. Opel,
On March 4, 1981 I sent a letter to your office requesting clarification of a decision which cancelled the internet gateway project…Your office’s attempt to analyze the internet decision appears to be stalled because it was handed back to middle management….I can only conclude in this instance the Open Door Policy has failed. My recommendation to salvage the situation is that you give fifteen minutes of your time to receive a presentation on the internet project and attempt to evaluation for yourself the value of this project to IBM’s future.”
May 19, 1981
Dear Mr. Engel,
I have reviewed the results of [the] investigation into your concerns. Your disappointment with the decision to terminate the VNET/ARPANET project is understandable; however, I conclude the decision was properly based on the need to fund other Ad Tech projects with greater business potential…
I understand you are currently considering a return to IBM, and I hope you choose to do so.
John R. Opel
Number 1-81: September 11, 1981 MANAGEMENT BRIEFING
TO ALL IBM MANAGERS:
Organizations seem to have an irresistable tendency to codify successful practices in rules, instructions and controls which soon begin to take the place of judgement. When that happens, the result is bureaucracy.
IBM is not immune. Earlier this year, reports from many sources indicated to me that a growing bureaucracy is affecting the performance of our business…corporate staff heads, group executives, and the division presidents are exploring ways to reduce unnecessary controls, rules and approvals in their areas of responsibility…We will succeed in that effort only if you managers, at every level of the business,k are willing to stand up and fight bureaucracy wherever you find it…If you have all the information to make a decision, make it…
[signed by John Opel, president]
John Opel stepped down as IBM president in January 1985 and chairman in May 1986. He was succeed by John Akers, and he was succeeded by Lou Gerstner in 1993. Gerstner, the former CEO of RJR Nabisco, described his transformation of IBM in “Who Says Elephants Can’t Dance?”. Most observers agree that critical to IBM’s turnaround that took it from a free fall in the early 1980’s to unquestioned market leadership in computers, software and services was the dismantling of a remote, hierarchical management culture that squeezed innovation in political pincers. By the time I took over the computing research directorship at the National Science Foundation in the late 1980’s, IBM had become a major player in the growth of the Internet :
In the mid-1980s, NSF decided the time was right to try to link its regional university networks and its supercomputer centers together. This initial effort was called NSFNET.
By 1987, participation in the new NSFNET project grew so rapidly that NSF knew it had to expand the capacity of this new network. In November of that year, it awarded a grant to a consortium of IBM, MCI, and a center at the University of Michigan called Merit to create a network of networks—or inter-net—capable of carrying data at speeds up to 56 kilobits a second. By July, 1987, this new system was up and running. The modern Internet was born.
1. Paul Carroll, Big Blues: The Unmaking of IBM, Crown Trade Paperbacks, 1994
2. Louis V. Gerstner, Who Says Elephants Can’t Dance? Inside IBM’s Historic Turnaround, Collins, 2002
3. National Science Foundation, NSF and the Birth of the Internet, http://www.nsf.gov/news/special_reports/nsf-net/textonly/index.jsp