Short answer: I run operations for the Experience Design team at Mayo Clinic. Long answer: it’s a little bit of everything, mostly keeping a lot of : all things AI, tooling, governance, people ops, and knowledge management. Basically, I design for designers.
I got here . I have a degree in Expeditionary Studies and Sociology, started out in the outdoor industry, then wandered into UX design, research, and product management before landing in operations. Unconventional? Sure. But the throughline never changed: people. Figuring out what they need, building it, and making sure the change actually sticks. And when it doesn’t, finding where it broke and .
Before Mayo, I spent nearly five years at . I started as a program manager and moved into running UX design and operations for an internal knowledge platform used by Microsoft’s legal and corporate affairs org (CELA). I owned the roadmap, the design, and the operating rhythm, and shipped 40+ features along the way. Midway through, I took a detour to REI as their and established the practice from the ground up.
Off the clock, I’m building KehillaHQ, congregation software for small Jewish communities. I never thought of myself as an engineer. Then I went from designing it to launching the code myself, so I may need to update that.
I’m also always experimenting with AI. The current experiment: a that helps run KehillaHQ, each with a job description and a list of things they’re not allowed to touch. I write it all up in my , partly for me and mostly so you can steal what works. And I’m helping relaunch The Den, a community for women founders.
And at the end of the day, comes first. When I get a spare minute, you’ll find me (usually in the rain; it’s Seattle), , or .
Hit reply if you want to talk AI, making change land in a big organization, building a small business, or anything outdoors. I really do answer.
Prosci-certified change practitioner
Founder, KehillaHQ · Seattle
- Outdoor education · leading groups when the plan changes
- Sociology · how people and groups actually behave
- Content strategy · saying it plainly
- UX design · humans before systems
- Research · rigor, and a little humility
- Product management · roadmaps, tradeoffs, launches
- Operations · range
- AI enablement · all of it at once
| Agent | Job | Never |
|---|---|---|
| Jim | Chief of staff, routes everything | Sets priority |
| Darryl | Product and engineering | Picks release dates |
| Dwight | Sales drafts | Sends email |
| Holly | Design system | Edits Figma alone |
| Pam | Shared memory | Takes unreviewed facts |
| Creed | Watchdog | Fixes anything |
- Nov 2026This site: an email with working partsLive
- 2026An AI dev workflow across five toolsKept
- 2026How your code goes liveShipped
- Program Manager · 2019 · document repository, research, budget
- UX Program Manager & Strategist · 2020 · platforms for 300+ in CELA
- Web UX Manager · 2021 · CSR, online safety, nonprofit, accessibility sites
- REI · 2022–23 · first DesignOps hire
- Sr. UX Design & Operations Manager · 2022–24 · roadmap, ops rhythm, first AI agent
After the AI agent launched, I pushed to pause new AI features and talk to users first. Research made the schedule.
I also led UX strategy for Microsoft’s corporate responsibility, online safety, nonprofit, and accessibility sites.
I started by asking the practice what was slowing it down. The answers became the roadmap, and the method became a published playbook.
I also led the Seattle chapter of DesignOps Assembly from 2022 to 2024.
Read the playbook →


