I pioneered an agentic workflow that empowers the design team to create and ship to sweetgreen.com, with ownership from end to end.

I turned a bottleneck into a publishing capability that the business now runs on — from a crisis op-ed shipped in a weekend to a repeatable launch engine.

Since July we've shipped five pages across five different use cases.

From July, I led and owned a project to enable non-engineers to publish web pages agentically. Collaborating with our AI Transformation & Data Principal, I designed a path connecting tools we already use — Claude Code, Figma, GitHub — from design to a live page, with no engineering required to stand it up. For lower-stakes pages, design could go concept to production on its own.

When the 2026 cyclospora outbreak hit, leadership needed to make a public statement within a single weekend — this workflow is what made "yes, by Monday" possible.

Sweetgreen wasn't linked to the outbreak, but trust in fresh produce dropped and consumers pulled back. With intentional sourcing as a real differentiator, leadership moved to elevate that story: OOH billboards ("Fight for Fresh") pointing to an op-ed from our co-founder and CEO.

The ask landed Thursday: get the op-ed page live by Monday. Because the workflow already existed, I could commit on the spot — no eng to scope, no queue — and launched the page in the window we had.

Since July, the workflow has shipped five live pages — and their range is the point. Each does a distinct job, which is what proves this is a repeatable capability, not a one-off.

• Op-ed — protects trust. A credible CEO message to customers within days of impact.
• ‍30 Days of Sweetgreen — drives activation. Jumped on an organic trend to funnel challenge entries.
  
• Fall menu drop — drives orders. The repeatable template — the recurring launch case we can now execute fast, for any drop.
  

‍Next: discoverability. I'm partnering with Tech and Creative to pair back-end sitemapping with SEO-optimized copy, so these pages get indexed and capture organic search demand — instead of relying on us to route traffic to them.

‍Also next: an intake form. As demand grows, I'm building a request intake to field these asks consistently — capturing scope and priority up front, and setting the guardrails that protect both our bandwidth and the quality of what we ship.

The capability I’d built quietly over a month became the reason the company could move at the speed its most urgent moment demanded — turning “we’d need engineering for that” into “design can ship this now.”