Team GSD: AI-Enabled Workflow Transformation
Standing up a cross-functional AI transformation effort across five departments — turning the repetitive operational work that bogs teams down into systems that just run.
Problem
Operational teams across Finance, Customer Success, Catalog, Fulfillment, and Support were spending huge portions of their week on repetitive, low-leverage work — copy/paste between systems, manual reconciliation, drafting the same email a hundred different ways. Traditional automation projects were too slow and too narrow to keep up.
Context
A People First, AI Empowered philosophy: AI is leverage for the humans doing the work, not a replacement for them. Five departments, dozens of distinct workflows, and a strong cultural appetite to experiment if the path was made safe and clear.
What changed
- Stood up Team GSD as a cross-functional unit chartered to find and ship AI-enabled wins — staffed across engineering, ops, and the partner departments.
- Defined a three-tier operating model with the team: Easy Wins (ship in days), Initiatives (ship in weeks), and Reworks (rethink the workflow end-to-end).
- Stood up a tooling stack — n8n, Cursor, ChatGPT Enterprise, NotebookLM — that let small teams move fast without breaking governance.
- Embedded alongside each department to pair on the first few automations, then handed ownership back so they could build their own.
Systems introduced
- Easy Wins / Initiatives / Reworks triage and intake model
- n8n-based workflow automation platform for non-engineers
- ChatGPT Enterprise rollout with documented prompting patterns
- NotebookLM-backed institutional knowledge surfaces
- Cursor-based AI-assisted development standards
Measurable impact
- 40%+ — Operational time reduction across departments
- 5 — Departments onboarded
- 0 — Headcount added to deliver this
Lessons learned
- Trust is the bottleneck — if the humans doing the work don't trust the tool, the workflow dies.
- Easy Wins build the credibility that buys you the right to attempt the Reworks.
- The biggest unlock isn't the model, it's the operating model around the model.
Scaling BSE Project Throughput by ~300%
How we tripled what the Business Systems Engineering org could ship without adding headcount — by fixing the operating model, not the people.
Building Asynchronous Information Flow with Asana
Replacing status meetings and Slack archaeology with a single async source of truth across five business divisions.