When will we fix the tools that run the world?
Legacy software underpins critical sectors like healthcare, aviation, banking, and government, yet attempts to replace it with “modern” systems often lead to slower workflows, usability failures, or even patient harm. Commenters argue that old, text-heavy and keyboard-driven interfaces can be far more efficient and reliable for expert users than sleek web apps, and that the real bottlenecks are economic incentives, risk of migration, and loss of embedded domain knowledge rather than a lack of newer technology. Many conclude that tools will only improve when organizations value domain-appropriate, fast, and predictable systems over aesthetics and minimal training costs.
Legacy vs “sleek” modern software
- Many argue that “sleek” modern UIs often hide fragile, complex stacks (Angular/React/SPAs) that are slower and less reliable than older tools.
- Old-looking systems can be fast, stable, and well-tuned to workflows; appearance is a poor proxy for quality.
- Some see modern redesigns as prioritizing aesthetics and “novice friendliness” over speed and power for expert users.
Expert, keyboard-driven interfaces
- Multiple comments praise 80s–90s TUIs and dense GUIs: full keyboard control, instant response, high information density, and input buffering (typing ahead while screens load).
- Modern web apps often discard buffered input, lack shortcuts, have unpredictable focus, and rely on tooltips/search instead of discoverable accelerators.
- There’s interest in new frameworks explicitly designed for expert use, with queued input and systematic shortcut discoverability.
Healthcare and EMR case studies
- Several examples (Norway’s “Health Platform,” Swedish regional systems, VA’s Cerner rollout) are cited as disastrous replacements of old health software, allegedly degrading care and even causing harm.
- Others note that leading EMR vendors employ many domain experts and extensive QA; many issues stem from local misconfiguration and attempts to preserve idiosyncratic processes.
- There is concern that health IT optimizes for billing, monitoring, and management metrics rather than clinical workflows.
Economics, incentives, and replacement risk
- A recurring theme: organizations won’t fund major rewrites unless they clearly generate revenue (e.g., an MRI machine beats IT upgrades in hospital budgets).
- Legacy systems encode vast domain knowledge; rewriting them is risky, costly, and often attempted by teams without that expertise.
- Managers frequently undervalue UX and productivity gains for frontline staff, constraining efforts to “fix” tools.
Paper-like flexibility vs rigid digital systems
- Digital forms/databases bring searchability, backups, and automation, but often remove paper’s flexibility (leaving fields blank, writing in margins, attaching arbitrary documents).
- Many enterprise UIs mirror rigid database schemas and reporting needs instead of real-world workflows.
- Some argue we could design systems that preserve paper’s adaptability while leveraging digital strengths.
“When will we fix it?” and systemic constraints
- Several comments challenge the framing of “we”: there is no unified actor, only many agents with misaligned incentives.
- Fixing foundational tools requires long timelines, substantial resources, and the ability to “change engines in flight,” which few organizations possess.