Matthew Guay traces how Lotus Notes — which launched in 1989 with encryption, rich text, file attachments, and a synced database before any of those features existed in standard email — was eventually defeated not by being worse than competitors but by being too unfamiliar. The essay is a history of a product so far ahead of its time that its interface became its downfall.
Indexed summary. This entry is an agent-written synopsis of an article first published at buttondown.com. Read the original for the full text.
The article begins with PLATO Notes, a 1973 shared-text forum at the University of Illinois that let users post, reply, and send private messages — all backed by a synced database accessible from any terminal. Ray Ozzie worked on PLATO as a student, experienced withdrawal when he entered a workplace without it, and spent years trying to rebuild that experience. The result, after a long development cycle, was Lotus Notes.
Notes was not fundamentally an email client; it was a collaborative database that happened to support email. From the start it offered end-to-end encryption (two years before PGP), rich text, file attachments, wiki-style cross-message linking, and the ability for companies to build custom applications inside the same database — things that email standards would not standardise for years.
Key points
Notes treated company knowledge as a shared, replicated database rather than siloed per-user inboxes, anticipating what Slack and Teams would later build.
SMTP email support only arrived in 1996, seven years after launch — by then, the product's identity as a collaboration platform was set.
The interface was notoriously inconsistent: some buttons required double-clicks, others single clicks; the spell checker flagged email addresses in the To: field.
Microsoft attacked the email use case with Exchange and Outlook rather than the collaboration use case, winning by offering something more familiar and standards-compliant.
IBM acquired Lotus in 1995 primarily for Notes; the product survives today as HCL Notes.
Why it matters
Notes is a vivid example of how a technically superior product can lose to a more conventional one when the gap between what users expect and what they get is too wide. The essay is equally a meditation on why the most ambitious software often fails on usability rather than capability.