Technical Operations · Program Management · Solutions Design

Twelve years making creative operations smarter —
through the systems, the data, and the teams that run them.

I helped a major creative marketing organization through one of the most consequential periods in its history — as it expanded from a single broadcast network into streaming and social, with more content coming in and more places it needed to land, I owned the technology that made it run: the pipelines, platforms, workflows, and dashboards the team depended on to keep pace. My instinct is always to understand what's there before deciding what comes next.

See the work Get in touch
Bio

Who I am

My favorite work is sitting at the intersection of what a team is trying to accomplish and what the technology is actually capable of — understanding both well enough to close the gap thoughtfully.

I grew up in this work as an assistant editor and Avid technician in promo post — the person who kept the media organized, the systems running, and the editors focused on the cut. Over twelve years at CBS and Paramount Global I took on increasing ownership of the platforms, programs, and technical decisions that a major creative organization depended on. That progression matters: the judgment I bring to decisions now is built on having actually run the equipment, managed the files, and felt where the friction was.

I think in systems, and I lead them as programs. My instinct is to put data in the middle — reachable by every tool that needs it — rather than surrender it to a single platform. I buy proven tools where that's the right call, build in-house where it isn't, and spend the engineering effort on the connective tissue between them. The technology is never the goal. It's what the team can do because of it.

B.S. in Computational Media from Georgia Tech.

The Work

Digital media supply chain

This is what the work looks like at full scale — a content operation expanding in every direction, with systems that had to grow alongside it without breaking what already existed. The pipeline below evolved over years of deliberate decisions, each one made with an eye toward what the next decision would need to be possible.

Designing the flow

The acquisition pipeline I took on was functional but built around assumptions that were starting to limit us — local dependencies, siloed per-show storage, a stateless process with no persistent record of what moved or why. The redesign was less about replacing it and more about rethinking the principles underneath it: reduce ground dependencies, open the architecture for cleaner interfacing with downstream systems, and build an archive structure intuitive enough that assets land where they belong automatically — no manual transfers, no tape ceremonies, no one deciding where something goes. The result was a unified S3 schema spanning a decade of archive and live delivery, a system of record in DynamoDB that made every asset and transaction traceable, and automated processing that delivered edit media, proxies, and DAM-ready files simultaneously — each fingerprinted with show, episode, format, and a unique ID. Those early design choices are what made every subsequent phase of the modernization possible.

  • Cloud-first acquisition portal on Aspera with REST API automation
  • Unified S3 path schema spanning a decade of archive and live delivery
  • DynamoDB system of record; SQS as the cross-system message bus
  • Orchestration via CatDV, Vantage, and Marquis MEWS/Medway
  • OpenText DAM redesign — storage-in-place, title-driven navigation, 1.8M assets
  • Jira-driven media governance — flight dates, licensing windows, revision states

Instrumenting it — the part I love

A system you can't see is a system you can't improve. The work I'm proudest of is the measurement layer — turning flat, high-volume operational data into something a stakeholder can act on. Asset status, automation health, SLA tracking, cost attribution — this is where the pipeline stops being plumbing and starts being intelligence.

  • Azure cost intelligence — hierarchical VM→user→group attribution; ~20% monthly reduction
  • DAM automation health — every cross-system transaction logged, paired, and dashboarded
  • SLA tracking with automated escalation when high-priority ingests ran late
  • Source-anchored transcode chains preventing generational quality loss
  • Metadata-mismatch error analysis across Jira, acquisition, and the DAM
  • Roadmapped AI-assisted validation to resolve identifier mismatches upstream
Program Management

Program Management

I run complex technical initiatives as programs — coordinated efforts with real stakes, cross-functional teams, and enough moving parts that structure is what keeps them from drifting. That has meant owning major infrastructure transitions end to end — petabyte-scale cloud migrations, storage cutovers, platform overhauls — navigating each without interrupting active production. When the pandemic forced an overnight shift to fully remote work, it was the foundational cloud work already in place that made a working production solution possible within a week — what could have been months of scrambling became a matter of scaling what we'd already built.

My approach is to define the goal clearly, build the structure that makes progress visible, and then get out of the way of the people doing the work — stepping back in when decisions need to be made or obstacles need to be removed.

I earned my CSM and CSPO during the transition period — formalizing a practice I'd been running informally for years.

Airtable

Airtable

Airtable has become my go-to when a process needs to become a platform — when data needs to be visible, relational, and actionable without standing up a full engineering project. The built-in tools are already serious — you can get to a real, useful system without writing a line of code. Scripting, integrations, and AI are where the pace changes: data starts moving between systems, connecting across tools, compounding in ways the original requirement never anticipated. The scope tends to grow because once people can see the data clearly, they immediately want to do more with it.

Automation Health

OTMM DAM Automation Tracking

Every transaction between the acquisition pipeline and the DAM, logged and matched — SLA dashboards, automated vendor escalations, and process visibility for the teams depending on it. Anecdotal complaints became a data-backed case.

Cost Intelligence

Azure Cost Tracking

Cloud spend categorized by show, team, and workload — with automated charge attribution and exec-level visibility into trends. Found the runaway costs hiding in the noise.

Knowledge Base

ProdTech Research Platform

A cross-company vendor and technology research tool for a production technology group spanning a dozen Paramount brands — built in Airtable because the problem needed a relational platform, not a project queue.

Dig deeper into my Airtable work →

Career Timeline

Career Timeline

Thirteen years of work doesn't summarize cleanly into a job title or a bullet list. The timeline is an attempt to show it more honestly — the disciplines, the projects, the through-lines that connect them. Each event shows not just what was built, but which disciplines it drew from and how that picture expanded over time.

Explore the full timeline →

Recognition & Foundations

Recognition & Foundations

Airspace LA Build-a-Thon — Research Automation Mission Winner. Airtable's Los Angeles community conference and competitive build event, May 2026. Belt and cash prize.

The winning build was an influencer marketing dashboard built on Airtable Canvas — using AI to automatically extract payout structures, performance thresholds, and contractual terms from influencer contracts, then combining that with performance data to surface who was delivering value, who wasn't, and why. A research automation layer then found comparable influencers across platforms and geographies, giving the team a compass for where to invest next.

Certifications
  • AWS Cloud PractitionerAmazon Web Services · 2025 Microsoft Azure FundamentalsMicrosoft · 2026
  • Certified ScrumMasterScrum Alliance · 2026 Certified Scrum Product OwnerScrum Alliance · 2026
  • Airtable BuilderAirtable Academy · 2025
Education

B.S. Computational Media — Georgia Institute of Technology, 2008

Contact

Let's connect

Open to full-time, contract, and consulting work in technical program management, platform ownership, and operations technology — with deep roots in media and creative production.

[email protected]
LinkedIn