This is the kind of spreadsheet architecture that deserves more respect. A seven-sheet restaurant P&L tracker with 2,257 formulas, zero macros, and cross-platform compatibility isn't a project that got out of hand, it's a masterclass in designing for real people. The builder chose formula-only because the end users are restaurant managers, not Excel experts, and that single constraint drove every smart decision in the file.
What this teaches us is that accessibility isn't about dumbing down. It's about removing fear. When a manager opens a workbook and sees a wall of #DIV/0! errors because someone left a cell blank, the tool has failed. Wrapping every division in IFERROR and showing a clean zero or dash isn't a technical shortcut; it's a trust-building measure. The same goes for color-coding inputs blue and locking formula cells. These aren't aesthetic choices, they are behavioral guardrails that let non-experts interact with complex logic without breaking it. Named ranges, conditional formatting order, and SUMPRODUCT as a multi-condition workhorse all serve the same goal: make the machine invisible so the human can focus on the numbers that matter.
We also appreciate the cross-platform discipline. Building for Excel, Google Sheets, and LibreOffice means testing every formula against the lowest common denominator. That's harder than picking one ecosystem and optimizing for it. But it's the right trade-off when your users don't control their software environment. The builder learned that TEXTJOIN with arrays works in Excel but breaks in Sheets, so they rewrote those formulas using simpler functions. That kind of constraint breeds creativity, not compromise.
The most practical takeaway is this: your spreadsheet's architecture is a user interface. Every named range, every conditional formatting rule, every IFERROR wrapper is a design decision that either empowers or frustrates the person on the other end. If you are building complex workbooks for people who are not spreadsheet nerds, let this project be your reference. Start with the constraint of zero macros. Test on every platform your users might open. And when you think you're done, hand the file to someone who has never seen it and watch where they hesitate. That hesitation is your next improvement.