Almost every system I've designed is still in use today. Click any theme to see the work behind it.
Client work under Grounded Systems starts with Charlie O's Bar & Grill.
Brand, website, Google Workspace, and the everyday systems behind a grand reopening, built so the owners can run it without me.
A production system that pulls community events from 45+ local sources into one searchable calendar, and runs itself every morning at 6 AM.
Each project below is real work, with real constraints and results still in use.
A neighborhood bar heading into a grand reopening with an outdated website, an unwritten brand, and accounts scattered across old vendors and staff.
The date wasn't moving, so everything had to be ready first.
A brand system, an 8-page Squarespace site, a clean Google Workspace, Canva templates, printed menus, and staff guides, all owned by the client.
Built so the owners can run it without me.
Read the case study →A nonprofit's stipend process was broken: students frustrated, staff overwhelmed, complaints constant. Everyone assumed the problem was errors.
I worked across finance, program staff, students, and families to find where it was actually falling apart.
~80% of complaints weren't errors, they were confusion about how the process worked.
A multi-channel fix: explainer video, QR-code posters, a Google Form → Asana dashboard, and weekly office hours. Complaints dropped.
Diagnose the real problem first. The solution becomes obvious.
I inherited a broken, politically charged scheduling process: department heads found it inequitable, teachers got unworkable schedules, students missed courses they'd requested.
The problem wasn't the software. Nobody had been asked what they actually needed.
I designed a new equity-centered process with 15+ department heads, iterated over three years until it became simply how things are done.
Still the standard at the school years after I left. That's the goal: a system that doesn't depend on you.
Listen deeply, co-design with stakeholders, anchor everything in equity.
Required compliance documentation that nobody read. Training that staff forgot the moment they left the room. Sound familiar?
I revised the procedures, wrote accessible handbooks, and redesigned training so frontline staff could apply it.
Documentation people would actually read and remember, with compliance met and clarity intact.
Compliance documents don't have to be unreadable. Clarity is a design choice.
I built a production system that gathers community events from 45+ local sources into one searchable calendar.
It runs every morning at 6 AM with no manual intervention.
12 custom scrapers, headless browser automation, an AI enrichment pipeline, a full admin panel, and a Supabase database with deduplication and audit trails.
Built because the problem bothered me enough to fix it.
↗ Visit rhinebeck.communityCourse registration for 2,200+ students ran on paper cards: three weeks every year, no visibility for families, plenty of room for error.
I designed and implemented a custom online registration module.
Three weeks of manual work became a real-time, self-service platform. Still the district standard over 10 years later.
"What once took three weeks of manual labor became a streamlined, transparent, self-service process."
A nonprofit needed real-time scheduling and rosters for a transient student population while its custom SIS was still being built.
I built connected tools to bridge the gap, accurate under constant change.
Accurate, real-time operations under constant change. The tools stayed in use long after they were meant to be temporary.
A good interim solution, built right, outlasts its timeline.
I joined the implementations team at a national edtech nonprofit serving 650+ school districts. The process worked but didn't scale: no playbook, no KPI framework, no consistent tracking.
I ran discovery and onboarding calls with 100+ schools and districts, scoped implementations, and guided partners through data migrations.
Built the implementation playbook, KPI framework, and partner knowledge base, and integrated Salesforce, Planhat, and Jira.
Defined the approach for a product full of unknowns, managed a vendor, and was the link across sales, CS, support, and 100+ district partners.
In everything but title, this was product management, and it connects every thread before it.
A nonprofit's off-the-shelf SIS wasn't built for afterschool programming. The team building a custom replacement needed someone who knew what it had to do.
I embedded with the development team for a year as domain expert and the link to frontline educators.
I brought real input from the eventual users back into each iteration. It launched successfully, with me as lead trainer organization-wide.
Discovery, requirements, build collaboration, launch, training, feedback loops. Product management in everything but title.
A fast-growing DEI consulting firm's shared drive had become unmanageable, and a strong presentation needed to become a reusable client asset.
Both problems were the same underneath: valuable content buried where nobody could use it.
Built a Confluence workspace for repeatable onboarding and client sharing, and turned the presentation into a brand-aligned deliverable the firm still uses year after year.
Information architecture, content strategy, and visual design — in service of equity-centered work.
When COVID-19 forced a large public high school into hybrid learning overnight, teachers with analog backgrounds had to manage in-person and remote students at once.
The barrier wasn't willingness. It was that nobody had made the technology legible to them.
I created visual blueprints that turned technical complexity into clear steps. Teachers who had never thought of themselves as tech-capable made the transition.
The barrier wasn't technology, it was confidence and clarity. The right format unlocked both.
A Boston nonprofit opening a new floor wanted a space people wanted to work in, on a real budget and with no design team.
I sourced high-quality secondhand furniture to match their design firm's existing space.
A beautiful, functional workspace and significant budget savings. Limited resources and high standards aren't mutually exclusive.
Constraints are just a different kind of design brief.
Whether your challenge looks like one of these or nothing like them, I'd love to hear about it.
Start a conversation →