Systems Thinking Across Projects & Portfolio

I didn’t just list my experience, I built my portfolio inside Figma to show how I actually think and work in operations and enablement.

Through reflection, I realized I’ve been doing ops work throughout my career — turning ambiguity into scalable systems, tooling, and self-serve workflows — whether in classrooms, for nonprofits, consulting, or global SaaS-like environments. The common thread has always been designing for reuse, measuring adoption, and creating single sources of truth that help internal teams and users move faster.

I started with Figma Make and Figma’s built-in AI to rapidly ideate early design directions. Then I stepped back, researched modern web design principles for professional ops audiences, and deliberately applied restraint to keep everything clean, scalable, and focused on clarity over flair.

The result is a living system: a published design system + library, static resume in Figma Design, a full CMS-powered site in Figma Sites with custom domain, and a system for LinkedIn carousels to share my portfolio's projects over the coming weeks. It mirrors exactly how I approach support scalability, cross-functional programs, and user enablement in Product Support operations. 

The highest-leverage work in support ops is often fixing root causes.

One of the highest-leverage projects I led was a full 500+ page global documentation overhaul. Through rigorous information architecture and cleanup, we reduced the content by 33% while turning it into a true single source of truth.

This enabled AI-powered support directly in GitBook and Discord, significantly reduced product support load, and served as the foundation for early draft access and Notion tooling that kept staff, partners, and UAT participants aligned, leading to smoother launches and far less post-launch rework. 

A single source of truth isn’t just organization, it’s a force multiplier that turns chaos into clarity.

At The Sandbox, visual effects (VFX) behaviors had exploded in number, but their attributes (sub-settings like size, color, frequency, etc.) were completely unstandardized. Same functionality had different names, same names had different behaviors, and value ranges were inconsistent (e.g., float4 vs large integers). This created confusion, false bug reports, and made creators avoid using VFX altogether — a missed opportunity for easy game polish.

I built a comprehensive living system in Notion that became the single source of truth for development and best practices: a dashboard for Art to track status across versions, a gallery-style compendium of every VFX, detailed per-VFX pages, and a sub-database of data for all modifiers to begin comparing. Level Design contributed real use cases, while Art used the data to guide standardization and outsourced development.

This created a clean knowledge pipeline from feature development → internal best practices → improved public documentation and creative tools for users.