Master First Circuit held that the Lotus 1-2-3 menu command hierarchy is an uncopyrightable method of operation under 17 U.S.C. § 102(b). with this comprehensive case brief.
Lotus Development v. Borland is a foundational software copyright case that sits at the intersection of user interfaces, interoperability, and the limits of copyright protection in functional works. At stake was whether a software developer can use copyright to control the command structure that users employ to operate a program—here, the hierarchical menu of commands in Lotus 1-2-3, then the market-leading spreadsheet. Borland's competing product, Quattro/Quattro Pro, included a mode that replicated Lotus's menu command hierarchy to allow users to transition easily and run existing macros.
The First Circuit held that the Lotus command hierarchy is an uncopyrightable "method of operation" under 17 U.S.C. § 102(b), a conclusion the Supreme Court left undisturbed by affirming the judgment via a 4–4 split. The decision remains a touchstone for understanding how copyright law draws a line between protectable expression and unprotectable functionality in software, and it foreshadows later debates about the copyright status of interfaces and APIs.
49 F.3d 807 (1st Cir. 1995), aff'd by an equally divided Court, 516 U.S. 233 (1996)
Lotus Development Corporation created Lotus 1-2-3, a dominant spreadsheet program in the 1980s. The program's user interface featured a hierarchical system of menus and submenus composed of command names and a specific organizational structure (the "menu command hierarchy"). Users invoked functions—such as copying, printing, graphing—by navigating that hierarchy or by using keystroke equivalents. Importantly, 1-2-3 users could write macros that automated sequences of commands by referencing these very command names and their arrangement. Borland International developed competing spreadsheet programs—Quattro and later Quattro Pro—that contained a feature (often described as a Lotus-emulation interface or mode) that replicated Lotus's command hierarchy so that 1-2-3 users could seamlessly transition, preserve their workflow, and run existing macros within Borland's software. Lotus sued in the District of Massachusetts for copyright infringement, asserting rights in the menu command hierarchy (including its structure, sequence, and organization) and certain keystroke labels. The district court ruled for Lotus, holding the menu hierarchy copyrightable expression and that Borland's replication infringed. Borland appealed. The First Circuit reversed, concluding that the menu command hierarchy was a "method of operation" excluded from copyright protection by § 102(b). The Supreme Court granted certiorari but affirmed by an equally divided Court, leaving the First Circuit's judgment intact without creating nationwide precedent.
Is the Lotus 1-2-3 menu command hierarchy—the arrangement of command names used by users to operate the program—copyrightable expression, or is it an uncopyrightable "method of operation" under 17 U.S.C. § 102(b)?
Under 17 U.S.C. § 102(b), copyright does not extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described. Expression that is the means by which users control or operate a functional system is a method of operation and is not protectable by copyright, even if the developer had some creative latitude in choosing labels or arranging commands.
The Lotus 1-2-3 menu command hierarchy is a method of operation and therefore not copyrightable; Borland did not infringe by replicating the command hierarchy to allow users to operate Borland's program and run 1-2-3 macros.
The First Circuit grounded its analysis in § 102(b) and Baker v. Selden's core insight that copyright cannot be used to monopolize functional systems or methods of use. The court defined a "method of operation" as the means by which a person operates something—in this context, the set of commands and their organization that users employ to make the spreadsheet perform tasks. The menu hierarchy was not merely a descriptive literary work; it was the user's interface to the program's functionality. Just as the arrangement and labeling of buttons on a device are part of the method by which a user operates that device, the Lotus commands were the method by which users operated the spreadsheet and executed macros. Because the command hierarchy was the mechanism of control, it fell squarely within § 102(b)'s exclusion. Lotus argued that creative choices in command names and hierarchical arrangement reflected protectable expression and that alternative ways of organizing commands existed (so protection would not grant a monopoly over the underlying ideas). The court rejected this reasoning, emphasizing that the existence of alternative designs does not transform a method of operation into protectable expression; the key inquiry is whether the expression is the means of operating the program. Protecting the command hierarchy would impede interoperability and lock in users by preventing competitors from enabling use of existing macros and learned keystrokes—precisely the type of functional control copyright is not meant to secure. The court distinguished protectable program code and audiovisual displays from the unprotectable command structure itself. Because the hierarchy was uncopyrightable as a method of operation, the court did not reach merger or fair use defenses. On the macro issue, the court noted that users wrote macros referencing Lotus command names; Borland's compatibility features allowed those user-authored macros to run. Granting Lotus exclusive rights in the command hierarchy would effectively confer control over user-created works and the functional means of invoking program operations. That outcome would contravene copyright's purpose and the explicit statutory exclusion in § 102(b). Accordingly, the court reversed the district court and directed judgment for Borland on the copyrightability question. The Supreme Court's later 4–4 affirmance left the First Circuit's judgment intact without endorsing a nationwide rule.
Lotus v. Borland is a leading case on the boundary between protectable software expression and unprotectable functional interfaces. It is frequently cited for the proposition that user interfaces that function as the method of operating a program—such as command hierarchies and, by analogy, certain APIs—are excluded from copyright by § 102(b). The decision preserves interoperability and user transition by preventing copyright from locking up control mechanisms, while recognizing that underlying code and expressive screen displays may still be protected. Although the Supreme Court's evenly divided affirmance limited national precedential effect, the reasoning has been influential in later software-interface disputes and remains essential reading for understanding how copyright interacts with functionality in software.
No. The court focused on the menu command hierarchy because it is the mechanism by which users operate the program—i.e., a method of operation under § 102(b). The court did not hold that all UI elements are uncopyrightable; screens, icons, and other audiovisual displays may be protectable if they are not themselves the method of operating the program.
No. The case does not authorize copying of source code or other protectable expression. Borland independently wrote its code; it replicated only the command names and their hierarchical structure to allow users to operate the program similarly and to run existing macros.
The ruling permits a competitor to replicate the command structure necessary for users to operate the program and run existing macros, promoting interoperability and easing user migration. It prevents a copyright holder from using copyright to control the functional interface and thereby lock in users' investments in macros and learned commands.
No. The Supreme Court affirmed by an equally divided Court, issuing no opinion. That left the First Circuit's judgment in place but without creating binding nationwide precedent. Still, the decision has been influential and is often cited persuasively in other jurisdictions.
The case's reasoning—that an interface used to operate a system is a § 102(b) method of operation—has been invoked by courts and commentators in API disputes. While APIs raise distinct issues, Lotus is often cited to argue that functional interfaces necessary to invoke software functionality are not protectable by copyright, or that copying for compatibility may be noninfringing.
Lotus v. Borland draws a principled line between expression and functionality in software. By holding that a program's command structure—the mechanism by which users control the software—is a method of operation, the First Circuit prevented copyright from encroaching on functional control schemes better left to patent law. The decision underscored the importance of user expectations, legacy investments in macros, and industry-wide interoperability.
For law students, the case is a core authority on § 102(b) in the software context and a vital complement to Baker v. Selden, Apple v. Microsoft, and Computer Associates v. Altai. It provides a clear analytical framework for evaluating when a software interface crosses from expression into unprotectable method and remains an influential touchstone in contemporary debates over interface and API copyright.
Need to cite this case?
Generate a perfectly formatted Bluebook citation in seconds.
Use our Bluebook Citation Generator →