The short version
This is a generalized write-up of internal tooling work: taking a process that lived in spreadsheets and copy-paste, and turning it into a dashboard with automations behind it.
The interesting part wasn't the code — it was mapping how the work actually happened, then removing the steps nobody needed to be doing by hand.
The problem
Manual processes don't fail loudly. They just quietly eat hours every week and produce small errors that someone has to catch later.
The goal was to make the process visible in one place, automate the repetitive parts, and keep humans on the judgment calls.
What I built
- internal dashboard for process visibility
- automated data collection and syncing
- reporting and status tracking
- alerting on the cases that needed a human
Design decisions
Internal tools get skipped if they're slower than the old way, so the bar was: faster than the spreadsheet on day one, or it fails.
Technical decisions
Automation handled the collection and syncing; the dashboard focused on making state obvious. The system was designed so a failure meant falling back to the manual process, never silent bad data.
Challenges
The hard part was trust. People keep using spreadsheets they trust over tools they don't — the rollout mattered as much as the build.
The outcome
Hours of weekly manual work went away, errors dropped, and the process became something a new person could understand by looking at one screen.
What I'd improve next
More of the alerting could become self-serve configuration, so process owners can tune it without a developer.