Small tools for large tables
Internal tools rarely get design attention, so they accumulate the worst UX in the company. A table with 200k rows and no filter is not a tool, it is a dare.
Three things that paid off immediately:
- Server-side sort and filter, with the current state in the URL so people can share a view
- Virtualised rows, fixed height, no measuring on scroll
- A visible row count and a real "no results" state
None of this is novel. The reason it does not get built is that nobody owns the tool. Give someone ownership and the table gets better in a week.