Designing Systems That Actually Help Teams Work Better

Most of my work with nonprofits starts the same way:

Too many tools.
Too many spreadsheets.
Not enough structure.

Over time, I’ve learned that the problem is usually not the people or the effort.

It’s the system.

What I focus on

When I work with teams, I try to simplify operations by building systems that are:

• Clear enough for anyone to use
• Structured enough to support reporting
• Flexible enough to grow over time

Most recently, this has included:

• Designing Airtable bases for grant tracking and program data
• Setting up Google Workspace environments with proper access controls
• Automating reports and workflows using Apps Script and integrations
• Helping teams transition from scattered files to centralized systems

A key lesson

The best system is not the most complex one.

It’s the one people actually use.

That means:

• Clear field naming
• Simple interfaces
• Thoughtful automation (not over-automation)

Where this connects to my MSIS work

As I continue in my graduate program, I’m starting to connect this hands-on experience with broader concepts:

• Data modeling and structure
• System design and scalability
• Security and access control
• AI integration into workflows

Looking ahead

I’m especially interested in how lightweight systems like Airtable can evolve into:

• AI-assisted workflows
• Smarter reporting tools
• Decision-support systems for small teams

At the end of the day, my goal is simple:

Build systems that reduce friction, save time, and help people focus on the work that actually matters.