Over a weekend I shipped eight focused pull requests to polish an admin dashboard for a task seeding platform. None of them fixed a broken feature. Every one removed friction that had accumulated while the product grew: crowded toolbars, hardcoded filter lists, search that fired on every keystroke, internal jargon on buttons, missing navigation cues. Core functionality was already solid. The dashboard was just harder to use than it needed to be.
This post walks through each PR—what changed, why it mattered, and the patterns worth reusing. The through-line is simple: polish is not a big redesign. It is a series of small, intentional improvements that respect the user's time and compound into a dramatically better experience.
The context
The admin panel had grown organically over several weeks. Operators could list tasks, filter by status, drill into batches, and run bulk actions. But the UI showed its age. Five separate filter dropdowns sat inline on the toolbar next to sort controls and a search box. Filter options were hardcoded in component files, so adding a new status meant touching multiple places and hoping string literals stayed in sync. One action button still used an internal slot code instead of the human label the rest of the app used. Task tables showed a redundant arrow column even though the whole row was clickable. Search re-filtered the list on every character, including single-letter queries that matched half the database.
