Operational systems
Two systems I specified, built and deployed solo, for teams that until then ran on chat groups and scattered files.
Logistics Data Collector · 2026
Operational teams submit supply requests and recurring data. When that runs through chat groups and files, it's hard to track each request, assign it to a department, change its status and get a picture of the whole.
- Mobile-first web appQuick request entry in the field, departments and sub-departments
- AuthenticationGoogle sign-in, user data in Firestore, field validation
- AdminUsers, permissions and departments; creating and merging segments
- Request managementEdit, block, statuses, consistency when permissions change
- SummariesPer-unit summary and PDF export for managers
- active users
- 50
- place for every request
- 1
What broke along the way
Deployment surfaced build failures: a missing collection definition and an invalid useSearchParams call. I fixed them until the image built, then re-checked the whole production chain.
| Alternative | Limit |
|---|---|
| Google Forms + Sheets | Easy to set up, hard to manage requests, permissions and lifecycle |
| Airtable / Smartsheet | Powerful, but need setup and training |
| WhatsApp + Excel | Accessible, but split decisions, data and tracking |
Shift Manager · 2025
Shift and guard-duty scheduling for teams working under constraints of posts, people, time and qualifications. One source of truth instead of versions of spreadsheets and messages.
| Persona | Need | UX answer |
|---|---|---|
| Scheduler | Build, assign, fix and send a plan | Overview of hours × posts × people |
| Supervisor | See what's covered, who swaps and when | Statuses, overlaps, exceptions, summary |
| End user | See when and where they're on duty | A simple mobile view |
The problem that interested me most: time clashes, unavailable people and last-minute swaps. The system has to surface them before they happen, not after. About 60 users.