
Douglas Engelbart pursued a research program to augment human intellect with interactive computing and better ways of working together. His 1968 demonstration showed an online text system with flexible views, linking, multiple input devices and remote collaboration. — Engelbart — 1968 Demo Transcript.
Part 1: The Core Mission & Urgency
- Augment Human Intellect: Engelbart defined augmentation as increasing a person’s ability to understand complex problems and develop solutions suited to the situation. — Engelbart — 1962 Framework.
- Address Growing Complexity: In 1962, Engelbart argued that social and economic activity was expanding while the complexity of human problems was increasing even faster. — Engelbart — 1962 Framework.
- Match the Urgency of Interconnected Problems: Engelbart also argued that faster activity and broader global connections made timely problem-solving increasingly urgent. — Engelbart — 1962 Framework.
- Choose a Long-Term Research Mission: Engelbart recalled that, within weeks of envisioning interactive computers and collaborative work, he committed his career to augmenting human intellect. — Engelbart — Workstation History.
- Look for Multi-Payoff Capabilities: Rather than optimize one task in isolation, Engelbart asked whether improving a shared set of knowledge capabilities could strengthen both an organization’s daily work and its ability to improve that work. — Engelbart — 1992 Groupware Paper.
- See the Revolution as Unfinished: Engelbart described the transformation he sought as only beginning, with much broader participation still needed before its promise could be realized. — Engelbart — Unfinished Revolution Colloquium.
- Look Beyond Fixed Intelligence: Engelbart argued that the effectiveness people exercise is unlikely to be limited chiefly by innate intelligence, because the surrounding system of tools and methods can improve. — Engelbart — 1962 Framework.
- Expect Large Gains from Systemic Improvement: Engelbart saw no reason to rule out large improvements in intellectual effectiveness from a coordinated system approach, drawing an analogy to gains in personal mobility. — Engelbart — 1962 Framework.
- Respond to Problems Faster Than Coping Capacity: In his account of the original vision, Engelbart said human problems were growing in complexity and urgency faster than society’s ability to cope; this led him toward computer-supported augmentation. — Engelbart — Workstation History.
Part 2: The Meaning of Augmentation
- Improve More Than Speed: For Engelbart, increased capability included not only faster comprehension but also deeper understanding of situations that had previously been too complex. — Engelbart — 1962 Framework.
- Make Hard Problems Solvable: Engelbart included the possibility of finding useful solutions to problems that had previously seemed insoluble among the aims of augmentation. — Engelbart — 1962 Framework.
- Support Human Judgment: Engelbart described an integrated way of working in which human hunches and feel for a situation coexist with electronic aids, rather than treating the computer as a substitute for the thinker. — Engelbart — 1962 Framework.
- Use Interactive Displays to Explore Designs: Engelbart envisioned a computer-supported workspace where a person could inspect, change and compare developing ideas on a visual display. — Engelbart — 1962 Framework.
- Make the Computer Responsive: At the start of the 1968 demo, Engelbart asked what an intellectual worker could accomplish with an always-available display and computer responsive to each action. — Engelbart — 1968 Demo Transcript.
- Preserve Work in an Online System: In the 1968 demo, Engelbart showed how an online file could record its name, creator, date and subsequent changes while remaining available for further editing. — Engelbart — 1968 Demo Transcript.
- Externalize a Thought Structure: Engelbart envisioned interlinked design notes and lists that could be stored, navigated, revised and shared as the thinking behind a project matured. — Engelbart — 1962 Framework.
- Work with Symbols Interactively: Engelbart treated language and symbol manipulation as central to thought, and designed the computer as a tool for handling those symbols in richer ways. — Engelbart — 1962 Framework.
- Keep Working Material Revisable: Engelbart’s augmented-architect example keeps specifications, considerations and interlinked notes outside the person’s head so they can be revisited and modified. — Engelbart — 1962 Framework.
- Design the Whole Human–Tool Interface: Engelbart emphasized that the interface includes language, methods, conventions and learned practices as well as the immediate technology. — Engelbart — 1962 Framework.
Part 3: The H-LAM/T Framework
- Treat Capability as a Whole System: Engelbart called the relevant unit an H-LAM/T system: a human using language, artifacts and methodology in which that person has been trained. — Engelbart — 1962 Framework.
- Do Not Isolate the Artifact: Engelbart treated computers and other artifacts as one class of augmentation means, alongside language, methodology and training. — Engelbart — 1962 Framework.
- Include Language in the Design: Engelbart included the concepts and symbols people use to model the world among the means through which their intellectual work can be improved. — Engelbart — 1962 Framework.
- Improve Work Methods with Tools: Engelbart argued that improving an organization’s capability requires coordinated changes to its procedures and methods as well as to its tools. — Engelbart — 1992 Groupware Paper.
- Train for New Capabilities: Engelbart treated training as the conditioning that makes language, tools and methods operationally effective for a person. — Engelbart — 1962 Framework.
- Count the Human System: Engelbart described the human side of an organization’s capability as including paradigms, procedures, methods, language, skills and training, not simply its devices. — Engelbart — 1992 Groupware Paper.
- Let Practices Change with Tools: Engelbart urged explicit co-evolution of the Tool System and Human System rather than dropping a new device into unchanged work practices. — Engelbart — 1992 Groupware Paper.
- Avoid Single-Component Fixes: Because organizational capability depends on interacting human and tool elements, Engelbart argued for an evolutionary, multi-element improvement strategy. — Engelbart — 1992 Groupware Paper.
- Build a Conceptual Framework First: Engelbart began with a framework for identifying the factors and relationships that limit human problem-solving before designing an improvement program. — Engelbart — 1962 Framework.
Part 4: Bootstrapping & Continuous Improvement
- Bootstrap the Researchers’ Own Work: Engelbart’s research group developed tools and techniques that increased its own capacity to develop and study augmentation systems. — Engelbart — 1968 Research Center.
- Improve the Improvement Capability: Engelbart proposed concentrating early improvement efforts on an organization’s ability to improve itself. — Engelbart — 1992 Groupware Paper.
- Compound Gains Across A, B and C: Engelbart distinguished one-time gains in core work from investments that improve the rate of improvement—and even the rate at which that rate can grow. — Engelbart — 1992 Groupware Paper.
- Let Researchers Use Their Own Tools: Engelbart chose his own researchers as early users of the systems they were developing, so the research process itself could benefit from the tools. — Engelbart — 1968 Research Center.
- Co-Evolve Human and Tool Systems: Engelbart called for a long-term evolution of work practices and tools together, rather than a one-pass redesign of either. — Engelbart — 1992 Groupware Paper.
- Plan for Evolution Rather Than a Final Blueprint: Engelbart argued that a complex organization’s capability infrastructure was too interdependent for a complete one-pass redesign, favoring guided evolution instead. — Engelbart — 1992 Groupware Paper.
- Learn Through Instrumented Pilots: Engelbart proposed pilot applications whose scope and results could be examined before broader changes to improvement work. — Engelbart — 1992 Groupware Paper.
- Feed Improvements Back into the Process: In Engelbart’s model, some outputs of the B and C improvement activities can strengthen those activities themselves, creating a bootstrap feedback path. — Engelbart — 1992 Groupware Paper.
- Connect Improvement Communities: Engelbart proposed C Communities in which organizations collaborate on shared improvement capabilities while continuing their separate core work. — Engelbart — 1992 Groupware Paper.
- Make Improvement Work Explicit: Engelbart wanted organizations to give improving their improvement process an explicit role, with attention to its staffing, funding, methods and pilots. — Engelbart — 1992 Groupware Paper.
Part 5: The ABC Model of Organizational Work
- Define A as Core Work: In Engelbart’s ABC model, A is an organization’s core business activity, such as product development, manufacturing, marketing, sales or operations. — Engelbart — 1992 Groupware Paper.
- Make B a Continuous Improvement Function: B is the continuing activity of improving A’s human–tool augmentation system and the way core work gets done. — Engelbart — 1992 Groupware Paper.
- Use C to Improve B: C activity improves the capability of the B improvement function—for example, by strengthening its skills, methods or pilot operations. — Engelbart — 1992 Groupware Paper.
- Give C an Explicit Role: Engelbart argued that improving B is important enough to warrant an explicit C activity rather than leaving the organization’s improvement capability unattended. — Engelbart — 1992 Groupware Paper.
- Recognize Different Leverage Levels: Engelbart described investment in A as a one-time boost, in B as improving A’s growth rate, and in C as improving the rate at which that growth rate increases. — Engelbart — 1992 Groupware Paper.
- Budget Improvement Work Deliberately: Engelbart urged organizations to distinguish the functions and budgets of B and C, and to examine funding and staffing for their improvement capability. — Engelbart — 1992 Groupware Paper.
- Treat Improvement Capacity as Strategic: Engelbart saw the capability to improve an organization’s own human–tool system as a strategic response to growing complexity. — Engelbart — 1992 Groupware Paper.
- Look Beyond Core Operations: The ABC model separates an organization’s core work from the dedicated work of improving that work and improving the improvement process. — Engelbart — 1992 Groupware Paper.
- Institutionalize Improvement Capabilities: Engelbart proposed permanent B activity and explicit C activity, including ways to assess and improve pilot operations. — Engelbart — 1992 Groupware Paper.
Part 6: Collective IQ & Collaboration
- Define Collective IQ by Joint Capability: Engelbart used collective IQ for a group’s ability to address complex challenges together, including the capabilities needed to perceive, reason and act across a shared knowledge environment. — Engelbart — Unfinished Revolution Colloquium.
- Solve Important Problems Collectively: Engelbart emphasized that large social challenges require many people and communities to work together, not just an isolated team. — Engelbart — Unfinished Revolution Colloquium.
- Aim to Raise a Group’s Capability: Engelbart urged organizations to examine how well they harness individual talents and increase their collective ability to handle difficult work. — Engelbart — Unfinished Revolution Colloquium.
- Match Collective Capacity to Global Problems: Engelbart argued that global challenges need a scalable increase in collective problem-solving capacity because solutions involve many communities. — Engelbart — Unfinished Revolution Colloquium.
- Treat Collective IQ as Improvable: Engelbart proposed boosting collective capability through evolving tools, methods and organizational practices, rather than treating a group’s effectiveness as fixed. — Engelbart — Unfinished Revolution Colloquium.
- Invite Dialogue About the Framework: Engelbart said he needed more direct dialogue about how the concepts in his augmentation framework fit together, instead of merely presenting them in sequence. — Engelbart — Unfinished Revolution Colloquium.
- Make Collective IQ a Societal Concern: Engelbart wanted people to improve their collective ability to face complex, urgent problems at a scale larger than a single company or team. — Engelbart — Unfinished Revolution Colloquium.
- Maintain Shared Working Knowledge: Engelbart’s improvement-community design called for a dynamic knowledge repository and shared tools that let participating organizations pool and reuse what they learn. — Engelbart — Unfinished Revolution Colloquium.
- Collaborate in a Shared Workspace: The 1968 demonstration showed participants working across locations with a shared computer display and live video, rather than only passing completed documents. — Engelbart — 1968 Demo Transcript.
- See Potential for Much Stronger Collective Work: Engelbart regarded better networked tools and improvement communities as a path to markedly stronger collective capability. — Engelbart — Unfinished Revolution Colloquium.
Part 7: Tool Co-Evolution & The Mother of All Demos
- Introduce the 1968 Demo Through the Medium Itself: Engelbart opened the 1968 presentation seated, addressing the audience largely through the display medium used to demonstrate his research. — Engelbart — 1968 Demo Transcript.
- Explain the Mouse Name: During the demonstration, Engelbart said the team had started calling the pointing device a mouse and never changed the name. — Engelbart — 1968 Demo Transcript.
- Credit the Remote Team: Engelbart told the audience that a substantial staff in Menlo Park was supporting the live demonstration. — Engelbart — 1968 Demo Transcript.
- Let Tools and Practices Co-Evolve: Engelbart’s strategy called for changes in the human system—skills, methods and conventions—to evolve alongside changes in the tool system. — Engelbart — 1992 Groupware Paper.
- Integrate NLS Functions: NLS combined pointing, structured text, alternate views and links in one working environment for composing and exploring complex material. — Engelbart — 1968 Demo Transcript.
- Use Links to Navigate Specific Material: Engelbart demonstrated links that could open another file at a specified location and in a specified view. — Engelbart — 1968 Demo Transcript.
- Switch Views of Structured Material: In NLS, Engelbart could change the view of a structured file to expose different levels and parts of the same working material. — Engelbart — 1968 Demo Transcript.
- Bridge Distance With Shared Displays: The 1968 demo connected Engelbart with colleagues in Menlo Park through live video and a computer-mediated shared work surface. — Engelbart — 1968 Demo Transcript.
- Pursue the Exciting Possibility of Augmentation: In a Stanford oral history, Engelbart recalled being excited by the possibility of helping people work and think more effectively, a memory that fed into his later augmentation framework. — Stanford — Engelbart Oral History.
Part 8: Difficulty, Expertise, and Learning Cliffs
- Balance Learnability Against Long-Run Efficiency: Engelbart argued that an interface used constantly may justify extra training if its sophisticated commands enable more efficient work. — Engelbart — Knowledge Workshop Terminals.
- Expect Practice for Powerful Tools: Engelbart compared learning a powerful computer-interaction system with learning to drive: useful mastery takes deliberate training. — Engelbart — Knowledge Workshop Terminals.
- Develop a Sophisticated Command Vocabulary: For frequent operations, Engelbart favored a sophisticated, sometimes abbreviated command vocabulary over controls designed only for immediate ease of learning. — Engelbart — Knowledge Workshop Terminals.
- Invest in Useful Operating Skill: Engelbart reported that users could gain practical value from the chorded keyset after a few hours of practice and improve further with use. — Engelbart — Knowledge Workshop Terminals.
- Design for Proficient Users: Engelbart designed frequently used controls around the needs of practiced knowledge workers, including keeping their eyes on the display while entering commands. — Engelbart — Knowledge Workshop Terminals.
- Combine the Mouse and Chorded Keyset: The five-key handset let one hand enter short strings and commands while the other used the mouse, avoiding repeated hand movement for some tasks. — Engelbart — 1968 Research Center.
- Allow Skilled Users More Powerful Interaction: Engelbart argued that limiting a system to controls learned in minutes could sacrifice flexibility and speed for serious, repeated knowledge work. — Engelbart — Knowledge Workshop Terminals.
- Use Richer Languages for Complex Work: Engelbart anticipated specialized computer-interaction languages that knowledge workers would master to control more powerful functions. — Engelbart — Knowledge Workshop Terminals.
- Treat Training as Part of the System: Engelbart included training in the human–tool system and expected serious knowledge workers to invest in methods and operating skills to use its capabilities well. — Engelbart — Knowledge Workshop Terminals.