--- title: "AI workshops for operations teams · OneTwo Growth Studio" description: "Hands-on AI workshops for operations teams, built on the reports, case work and handoffs they run every week. The team learns to question how its work gets done, rebuild it with agents, and put the time into work that moves the numbers." url: "https://onetwogrowth.com/teams/operations" canonical: "https://onetwogrowth.com/teams/operations" --- # AI workshops for operations teams Hands-on AI workshops for operations teams, built on the reports, case work and handoffs they run every week. The team learns to question how its work gets done, rebuild it with agents, and put the time into work that moves the numbers. ## Where it starts Operations teams are often the go-between for systems that don’t talk to each other. The work runs across a CRM, an order system, spreadsheets and email, and someone on the team carries it from one to the next. What leaders of these teams tend to see: - the same report rebuilt by hand every week from several exports - tasks that have built up over the years and that nobody has stopped to question - knowledge that sits in one person’s head - people trying AI on their own, with results that don’t add up to a different way of working ## What teams like this work on Operations teams already think in processes. Mapping a process step by step, deciding where a person checks the work, and writing down the rules the team follows is most of what it takes to work well with agents. The sessions start there. Each workshop runs on the team’s own work. From operations teams so far: **Case inquiries** A workflow that pulls an inquiry’s history from several systems, runs the analysis and posts a recommendation in Slack. Each one used to take about 20 minutes of digging. **Exception checks** Order lines checked against the team’s rules, so a person reviews the few that are wrong instead of every line. **Weekly reporting** One weekly view built from four system exports, in place of a dashboard rebuilt by hand. **Follow-ups** A tracker that reads the team’s email each morning and lists what has been missed. **A time audit** The team sorts its own work into what should stop, what’s necessary but low value, and what matters most, then builds for the middle. ## What stays human Operations teams keep the judgment calls and the customer. - The exception that doesn’t fit a rule, and the call on what happens next. - Messages to customers and partners, which the team still writes or approves. - Changes to systems. Connections start read-only, and anything that changes a record waits for a person to approve it. ## What changes The team changes how it works, not only how fast. At Flare, one ops leader audited how her team spent its time: about 30% legacy tasks, 30% necessary but low value, and 40% the work everyone wished they had more time for. The next day she built an app to take on part of the middle 30%. Within three weeks of the first session, the team was working in a new way. > “The team is working in an entirely new way. We’re saving time and automating necessary but low value add tasks with agents and reallocating that time to other activities that can move the metrics for the business.” > > Rachel Horowitz, COO, Flare > “Harry understands what operators live and breathe every day, which makes the experience more relevant than general AI workshops and courses.” > > Seth Greenberg, VP Learning Experience, Springboard [Read the Flare case study](https://onetwogrowth.com/results/flare) ## Questions ### **Our systems don’t connect to AI tools. Does this still work?** Yes. Teams start from exports and the files they already have, then add connections where they exist. Operations teams have run the whole workshop on exports. ### **How do we know the output is right?** The sessions teach the checks. The agent works from the source files, does the math in code and shows where each number came from, and a person reviews what matters before it’s used. ### **Won’t explaining a task take longer than doing it?** The first time, sometimes. The sessions turn a task the team repeats into a saved skill with its rules written down, so the explaining happens once. ### **Who keeps it going after the workshop?** Someone on the team, often the leader who brought it in. Teams that kept going shared what they built in a channel and kept trying the next thing. ## Other teams [People and HR](https://onetwogrowth.com/teams/people) · [Finance](https://onetwogrowth.com/teams/finance) · [Go-to-market](https://onetwogrowth.com/teams/gtm) · [Leadership](https://onetwogrowth.com/teams/leadership) ## Start with a call. Thirty minutes about your team and its work. If a workshop would help, Harry would be glad to put one together. [Book a call](https://cal.com/harry-onetwogrowth/discovery-conversation) · [Meet Harry](https://onetwogrowth.com/about) OneTwo Growth Studio is Harry Siggins' AI enablement practice in Seattle, WA, running hands-on AI workshops for teams. [harry@onetwogrowth.com](mailto:harry@onetwogrowth.com) · [LinkedIn](https://www.linkedin.com/in/harrysiggins/) · [Harry on AI](https://harrysiggins.substack.com) · [Privacy](https://onetwogrowth.com/privacy)