Systems design
I start with the operating problem. I gather input, define ownership, map decisions, and test the model before I build the sheets.
About Anthony Garcia
I build the operating systems behind marketing work.
My career started in graphic design. Over time, I became the person teams turned to when the problem was bigger than a deliverable: work had no clear owner, approvals lived in email, leadership could not see capacity, or reporting took more effort than the decisions it was meant to support.
Today, I design the data models, workflows, dashboards, automations, and governance that let marketing and project leaders run on current information instead of manual status updates.
My AI partnership
I am the thought leader. AI is the thought partner.
I maintain dedicated AI project environments with organizational context, system architecture, governance standards, known technical patterns, and project history. That shared context lets us continue complex work instead of starting from a blank prompt every time.
I lead the problem definition, stakeholder decisions, operating model, tradeoffs, validation, and rollout. AI helps me challenge assumptions, connect information, translate conversations into build plans, write and review code, and get past technical barriers that would otherwise slow the work down.
What I actually do
The platform is part of the work. It is not the work.
Automation
I build the scripts and scheduled workflows that keep reporting, budgets, and historical data current without someone maintaining them by hand.
Stakeholder-facing product thinking
I design each view for the person using it. A VP sees the six fields needed for a decision. A facilitator sees metrics in presentation order. A contributor sees only what they own.
Cross-organization ownership
I think beyond one sheet or one team. Naming, governance, automation, and migrations have to hold together across Ott, Kipp & Zonen, and Shared Services.
How I work
Useful systems earn trust by being clear, accurate, and easy to live with.
A workshop or survey comes before the build when the team needs to agree on the model.
I dry-run automations against real data and review the output before they write to production.
If a required field solves the problem, I do not add a fragile formula just because I can.
A system that needs constant babysitting is not finished.
I use AI to accelerate scripting, debugging, and analysis. I own the operating decisions, validation, and final result.
My transition
I did not leave design thinking behind. I applied it to how work operates.
Design taught me to understand the person on the other side of the work, make complexity easier to navigate, and care about whether something is actually usable. Those instincts now show up in intake forms, capacity models, approval paths, executive dashboards, and the way I lead stakeholders through change.
The four case studies in this portfolio are proof that I am already doing project and operations work. The next step is giving that work the title, scope, and room to grow that it deserves.
See the case studies →Current focus