United Indians: Operations, Grants & Process Redesign.
A community-operations role that grew into workflow redesign, grant budgeting and compliance, intern management, and a practical lesson in making work visible.
The operating context
The work was physical and administrative at the same time. I coordinated garden operations and community programming, managed a contracted intern cohort, worked with accounting and management on purchases, and had recurring grant/reporting obligations.
Turning volunteer reporting into a usable operating system
The existing volunteer reporting process was paper-heavy and slow. A full quarterly report typically took roughly 4–8 hours, often one to two shifts. I moved the workflow online and rebuilt it around required fields, validation/error flags, correction paths, Excel consolidation, and reusable reporting logic.
The important lesson was that digitization alone would not have solved the problem. The biggest gains came from removing re-entry, surfacing errors earlier, and making corrections easier.
Compare where the work happens
Choose a record condition and follow it through the old paper-heavy process versus the redesigned system. The key change was not the form itself—it was moving validation and correction earlier, then reusing one structured dataset downstream.
Paper-heavy workflow
Errors and fragmented evidence survive longer, so more work accumulates at quarter-end.
Controlled reporting system
Capture, validation, correction, and reuse happen as one connected operating flow.
Example records are illustrative. The workflow stages, controls, fallback design, and timing reflect the process I built and used.
Grant ownership under real budget constraints
I developed the proposal and budget for an awarded $73,000 King County WaterWorks grant, with a manager formally approving/submitting it. I tracked spending, coordinated purchases with accounting/management, and completed eight quarterly compliance reports across overlapping grant cycles.
From ad hoc mentoring to a repeatable internship program
I designed, onboarded, and managed an eight-person contracted intern workforce through a six-week horticulture and water-systems program. That included scheduling, expectations, structured learning plans, weekly check-ins, individualized feedback, performance tracking, and day-to-day supervision.
Feedback that changed how I worked
I also learned that delivering good work is not enough if the people around you cannot see what is happening. I received feedback that my work was getting done, but my visibility and communication were weak—especially important as a younger employee working across staff and managers.
I responded by sending concise progress updates roughly every other day and being more deliberate about checking in with employees and managers instead of assuming the finished work would speak for itself. The lesson was simple but durable: communication is part of execution because it creates trust, alignment, and a chance to correct course earlier.
What I learned
Operations problems rarely live in one tool. A reporting issue can also be a data-quality problem, a process-design problem, a training problem, and a stakeholder-communication problem. The most durable improvement came from treating the workflow as a system rather than just changing the format—and from making the work visible enough for other people to rely on it.
Related writing
Two essays grew directly out of the operating lessons from this role.