A Menu Is a Method: How Lotus v. Borland Put Command Hierarchies Beyond Copyright

The First Circuit held that the Lotus 1-2-3 menu command hierarchy is an uncopyrightable 'method of operation' under Section 102(b), a ruling left standing by an evenly divided Supreme Court.

Among the foundational software-copyright opinions, Lotus Development Corp. v. Borland International, Inc. occupies a singular place: it is the rare landmark whose reasoning the U.S. Supreme Court neither endorsed nor rejected, leaving a powerful but geographically bounded precedent. Decided by the U.S. Court of Appeals for the First Circuit on March 9, 1995 (No. 93-2214; argued October 6, 1994), the opinion held that the menu command hierarchy of the Lotus 1-2-3 spreadsheet was an uncopyrightable “method of operation” under Section 102(b) of the Copyright Act. The Supreme Court granted certiorari and then, in 1996, affirmed by an equally divided 4-4 vote with no opinion — a non-precedential outcome that left the First Circuit’s reasoning standing and the national question unresolved.

At a glance

Case: Lotus Development Corp. v. Borland International, Inc., U.S. Court of Appeals for the First Circuit, No. 93-2214.
Decided: March 9, 1995 (argued Oct. 6, 1994); on appeal from the U.S. District Court for the District of Massachusetts.
Holding: The Lotus 1-2-3 menu command hierarchy is a “method of operation” under 17 U.S.C. § 102(b) and therefore is not copyrightable.
Supreme Court: Affirmed by an equally divided Court (4-4) in 1996, with no opinion — leaving the First Circuit decision intact but non-binding nationally.
Why it matters: It carved out the means by which users operate a program — its command structure — from copyright protection, advancing interoperability and compatibility.

Background: a competitor that copied the commands, not the code

Lotus 1-2-3 was the dominant spreadsheet of the 1980s, and millions of users had memorized its menu command hierarchy — the tree of commands (such as “Copy,” “Print,” “Quit”) through which a user directed the program. Many users had also written keystroke “macros” that automated sequences of those commands. Borland released competing spreadsheets, Quattro and Quattro Pro, that included a “Lotus Emulation Interface” replicating the 1-2-3 menu command hierarchy so that experienced Lotus users could switch products without relearning commands and could keep running their existing macros.

Critically, Borland did not copy any of Lotus’s underlying source or object code. It copied the words and structure of the command menus. Lotus sued for copyright infringement. The district court ruled for Lotus, holding the menu command hierarchy copyrightable and infringed. Borland appealed, and the First Circuit reversed.

The holding: command hierarchies are how you operate the program

The First Circuit framed the dispositive question narrowly: not whether the menu command hierarchy could in some abstract sense be expressed differently, but whether it was a “method of operation” within the meaning of § 102(b), which withholds copyright from any “procedure, process, system, [or] method of operation.” The court answered yes.

A “method of operation,” the court reasoned, refers to the means by which a person operates something — and the Lotus menu command hierarchy is exactly that: the interface through which users control the spreadsheet’s functions. Just as the buttons of a video cassette recorder are not copyrightable even though they are labeled with words, the court analogized, the commands users press to operate a program are methods of operation, not protectable expression. The court invoked a now-famous hypothetical: if Lotus’s command terms were protectable, then learning to operate a program could require relearning every command tree for every competing product, and macros — sequences users had written in the 1-2-3 command language — would be stranded.

The court drew a deliberate contrast with non-literal-copying analysis. It declined to run the menu hierarchy through an abstraction-style filtering exercise, reasoning that § 102(b) supplies a categorical exclusion: once something is a method of operation, it is outside copyright entirely, regardless of how much expressive variation might theoretically be possible in labeling or arranging the commands. The existence of alternative ways to design a command menu did not, in the court’s view, transform the method of operation into copyrightable expression.

Judge Boudin’s concurrence: a functional-compatibility lens

Judge Boudin’s concurrence has arguably been as influential as the majority opinion. He approached the problem through the lens of user investment and functional standardization. Once a command set has become the way a large community of users operates a class of program — and once those users have built macros and habits around it — allowing one firm to own the command vocabulary confers a monopoly far beyond what is needed to reward the original creative effort. He suggested thinking about whether the defendant’s copying was “privileged” because it served compatibility and the legitimate interests of users, rather than appropriating the originator’s creative expression for its own sake. That framing — protecting interoperability and the value users have invested in learning an interface — has echoed through later software-interface debates.

The Supreme Court’s non-decision

The Supreme Court granted certiorari and heard argument, but ultimately affirmed by an equally divided Court, 4-4, issuing a one-line judgment with no opinion (one Justice did not participate). An affirmance by an equally divided Court resolves the case between the parties but creates no national precedent and does not adopt the lower court’s reasoning. The practical result: the First Circuit’s “method of operation” holding governs within that circuit and stands as influential persuasive authority elsewhere, but the Supreme Court has never authoritatively decided whether command structures and similar interface elements are categorically excluded from copyright.

Open questions

How far does “method of operation” extend? The opinion addresses a command menu hierarchy; its reach to richer interfaces, APIs, and declaring code has been debated ever since and remains unsettled across circuits.
Categorical exclusion versus filtration. Lotus treats § 102(b) as a clean on/off switch; other courts prefer to filter functional elements within a similarity analysis. The two methods can yield different outcomes.
The unresolved national split. Because the Supreme Court split 4-4, no binding rule emerged; later interface-copyright disputes have had to navigate around, rather than under, Lotus.
Interaction with later API jurisprudence. How Lotus’s logic coexists with subsequent decisions on interface copyrightability and fair use continues to generate scholarship and litigation strategy.

Implications

Command structures lean uncopyrightable: the means by which users operate a program are strong candidates for the § 102(b) exclusion, at least in the First Circuit.
Compatibility is protected in practice: replicating an interface so users can switch products and keep their macros found judicial shelter.
No nationwide rule: the 4-4 affirmance means Lotus persuades but does not bind outside the First Circuit.
Drafting and strategy shift: rightsholders seeking to protect interface elements must reckon with both the categorical-exclusion theory and the user-investment concerns Judge Boudin highlighted.
A touchstone for interface debates: Lotus remains a primary reference point whenever courts ask whether functional interface design is expression or operation.

Frequently asked questions

What exactly did Borland copy? Borland copied the Lotus 1-2-3 menu command hierarchy — the words and structure of the command menus — so that its Quattro products could emulate the 1-2-3 interface. It did not copy Lotus’s underlying source or object code.

Did the Supreme Court agree the menu hierarchy is uncopyrightable? The Supreme Court did not say. It affirmed by a 4-4 split without an opinion, which left the First Circuit’s ruling in place between the parties but created no national precedent and adopted no reasoning.

Is a program’s command structure copyrightable today? It depends on the jurisdiction and the specific interface. Within the First Circuit, Lotus’s “method of operation” analysis controls; elsewhere, courts may apply different frameworks, and later decisions on interfaces and APIs complicate any simple answer.