Lotus Notes and the dangers of starting from scratch
Lotus Notes’ legacy as an all-in-one groupware platform—email, databases, workflow and app runtime in a single replicated system—draws both admiration and scorn from people who used it in enterprises well into the 2010s and 2020s. Many recall its powerful data model, rapid app development and built‑in PKI as years ahead of competitors, but see its nonstandard, clunky UI, difficult migrations and IBM’s strategic missteps as reasons it was eventually displaced by Outlook, SharePoint and web apps. The conversation also highlights a broader lesson: early, ambitious platforms that “start from scratch” on UX and protocols can be leapfrogged once standards, expectations and ecosystems solidify.
Overall sentiment on Lotus Notes
- Strong split between users who found Notes powerful and those who despised it.
- Common complaints: clunky, non-standard UI, confusing shortcuts, poor email UX, odd limits (e.g., window counts), and fragile local/offline sync.
- Some recall it as faster and more responsive than modern Outlook/webmail once you learned it, with email never feeling like the bottleneck.
- Many organizations stayed on obsolete versions for years, compounding UX and reliability issues.
Notes as platform vs. email client
- Multiple commenters stress that Notes was primarily an application platform with built-in replication and security, not “just an email client.”
- Praised features: document‑oriented database, rapid low‑code app development, multi‑master replication, rich ACLs/PKI, and simple backups/migrations.
- Used for helpdesk, ERP/CRM, workflow, timekeeping, wikis, and custom internal apps; many say it took decades for web tools to catch up.
- Criticism: tooling hostile to experienced developers, weak version control, replication glitches, and lots of badly built apps by “citizen developers.”
Lock-in, migration, and organizational stories
- Notes’ strength as an app platform created huge lock‑in: companies accumulated dozens to thousands of custom databases.
- Migrations to Outlook/Exchange/SharePoint or custom Java/web stacks were multi‑year efforts, often underestimated and underfunded.
- Some organizations ran Notes well into the 2010s/2020s; others aborted Notes rollouts or reverted after user revolt.
Design decisions and “starting from scratch”
- Discussion questions the article’s title; many see the real lesson as first‑mover disadvantage and non‑standard UI choices, not a later rewrite.
- Notes made its own calls on shortcuts, interaction patterns, and protocols at a time when standards were still forming.
- Once the broader Windows/Office conventions solidified, Notes’ divergence became a liability, especially when Outlook aligned with user expectations.
Competition, standards, and decline
- Debate over how much ignoring or embracing SMTP/X.400 mattered; some argue Notes wasn’t really a walled garden, others say protocol choices hurt it.
- Many see Microsoft’s integrated Office/Exchange/SharePoint stack, plus aggressive enterprise sales, as the primary competitive pressure.
- Several say the web and browser‑based tools ultimately hurt Notes more than direct product competition.