The work
Fifteen years of making the operating model change, not just the tooling.
Ten of those applying AI, starting with Salesforce Einstein and Service Cloud chatbots, then enterprise GenAI, RAG, governance, and agentic automation.
Timeline
Roles and scope.
Remote, Seattle based. Full employment history, with company names, on LinkedIn.
Speaking
Where this gets said out loud.
Translating GenAI, agentic automation, governance, and change management into operating models that executives, product leaders, and delivery teams actually use. Keynoted the same annual portfolio conference twice, two years apart.
Keynote — annual enterprise portfolio conference, Copenhagen, 2026
Operationalizing agentic AI platforms: moving from experimentation to execution. Agent loops, planning, tool use and retrieval. Multi-agent workflows coordinating specialized roles. MCP connectivity across enterprise systems, with human review and governance checkpoints in the path. Evaluation, monitoring and production readiness — the parts that decide whether a demo becomes a dependency.
The through-line: turning service platforms from systems of record into systems of action. Worked examples across intelligent triage, case summaries, root-cause analysis, bug creation and knowledge generation, spanning the ticketing, issue-tracking and knowledge systems a support organization already runs on. Then scaling those patterns as reusable assets across business units, and measuring adoption, throughput, quality, customer impact and ROI.
Keynote — annual enterprise portfolio conference, Cancun, 2024
Real-World AI Adoption: Transforming Customer Support with Augmented Intelligence. Augmented intelligence rather than replacement: AI supporting human judgment across transcription, case summaries, and email drafting. Covered early experimentation, measured business impact, why grounding and retrieval matter when hallucination is the failure mode, and the SPARK adoption framework — Start small, Pilot, Analyze, Refine, Keep growing.
UC Berkeley Executive Education — guest lecture and fireside chat
From AI Experiment to Operating System. The catalyst for changing the first question from what can AI do to what business problem is worth solving. Then the pilot, frontline adoption, the shift from chat to systems of action, spec-driven engineering, and the four-gate executive playbook.
SEE 2026 — Southeastern Electric Exchange, Grapevine, Texas
2026 Trends and Best Practices in Fleet Software. Co-presented on the Transportation track: how AI and agentic AI are reshaping utility fleet operations, moving past predictive maintenance to the unglamorous part — getting data and workflows ready before anyone presses automate.
EDGE 2025, Oceanside, California
Smarter, Faster, Better: Using AI to Redefine Customer Support. Customer support at a turning point: AI augmenting human connection rather than replacing it, cutting backlogs and response times while letting teams deliver a more empathetic experience at scale. Presented to leaders across vertical market software.
Enterprise virtual innovation summit, 2025
Scaling AI adoption through governance frameworks, ROI measurement, executive sponsorship, and repeatable operating models.
AI Champion Enablement Programs, 2024–2025
Executive workshops and maturity model sessions building AI literacy, champion networks, change readiness, and sustained adoption capability.
The champions shipped, under a problem-first rule: start from a real pain point or do not start. A retrieval chatbot over internal documentation, multi-agent infrastructure automation, an AI-powered hosted operations suite, a release-note generator, and DevOps automation over MCP servers — built by engineers and by colleagues who do not write code, and demonstrated at a GenAI at Work: Real Projects, Real Impact showcase.
Viva Engage AI enablement community, 2026
Published Microsoft 365 Copilot and Copilot Cowork content, helping employees build project context, reusable references, prompting skills, and responsible AI habits.
What I speak about
- Moving AI from experiment to operating system
- Operationalizing agentic AI platforms
- Frontline adoption and building trust
- Agentic workflows and human oversight
- The executive four-gate playbook
- Spec-driven engineering when code gets cheap
- Knowing when not to use AI
Case studies
Four things I have actually run.
Building the intake and prioritization machinery for an enterprise AI CoE
Global enterprise software portfolio. Founding member of the group. Built the intake and prioritization machinery first: discovery workbooks, maturity assessments, prioritization models, governance guidance, ROI dashboards, implementation playbooks, reusable templates.
Helped move leaders from experimentation to structured execution through phased roadmaps, prioritized use cases, named executive sponsorship, and quarterly accountability. Enablement reached 40+ business units via executive workshops, role-based learning, AI literacy programs, and champion networks.
Transforming customer support with AI in the workflow
The failure mode is starting with an enterprise programme. Established the baseline first, then picked the single workflow where the pain was already measurable — knowledge research and customer email drafting — and tested whether AI improved it before touching anything else. Measured against the baseline, not against expectations.
From there, agentic workflows took load off the queue rather than just speeding up typing. The part that compounds: every closed case now produces a knowledge article, which feeds the retrieval layer, which makes the next case faster to resolve. The system improves by being used instead of decaying between refreshes.
That loop is the difference between a support team with an AI tool bolted on and a support operation whose workflow has actually changed shape.
Onboarding 80+ engineers to AI tools in one week
Amazon Q Developer, now Kiro, and Microsoft Copilot, across engineering and QA. Run with the engineering managers and team leaders who owned those teams, on groundwork already laid: those managers had been through AI workshops first, which is why one week was even possible.
Four things did the work: real engineering problems that already mattered, low-risk starting points where mistakes were easy to catch, respected engineers sharing wins with their own peers, and office hours to remove friction as it appeared.
The goal was never blind trust. It was safe, informed challenge. Adoption is not a communications problem. It is a product experience problem — and not a one-person problem either. Managers who already believed it carried it further than any programme could push it.
On the harder question underneath it: rather than promising the team that AI would not change their jobs, which would not have been honest, we hired a college intern supported by AI tools and showed a different entry point into the role. Faster onboarding, meaningful entry-level work, a new talent pathway. AI lowered the experience barrier without lowering the quality standard.
Designing the human-authority model for a risk-scoring product
Traditional reporting shows the data. The product connects fragmented operational sources into one decision context, detects meaningful signals, and scores risk so teams know where to focus first. A product and engineering team built and shipped it.
My contribution was the shape of the decision: domain professionals set the scoring weights, validate the score, and choose the action. AI prioritizes attention. People decide what happens next. That constraint is what separates a risk score people act on from one they learn to ignore.
Scope and accountability
What I own, stated plainly.
Decisions
Owns go, defer, and stop decisions where the workflow keeps a human in the loop and the blast radius is contained.
Escalates through governance review when autonomy, data exposure, or customer impact crosses the line. The gate is a judgment about risk, not a spend limit.
Financial accountability
Owns the business case. Builds and defends the investment case, tracks realized value, and reports on it. Spend sits with function leaders.
People
Leads the agentic AI and automation function across six areas, with a direct team and extended delivery capacity. Coaches eight professional services teams on solution design, workflow fit, feasibility, governance, and output quality.
Previously hired, built, and led a 16-person organization.
Earlier leadership
Before AI was the headline.
Director, Customer Support — regulated healthcare SaaS, 2021–2023
Led post-sales transformation for a HIPAA and PHI regulated platform. Hired and built a 16-person organization, establishing operating rhythms, KPI accountability, coaching practices, and escalation ownership.
Led the build of a self-service knowledge and triage platform, delivered in six months by the team.
Manager, Technical Support — cybersecurity SaaS, 2017–2021
Led global technical support for an enterprise platform covering network security, risk analysis, and compliance. Took the organization to a 24x5 follow-the-sun model through workflow redesign, automation, and portal modernization, with the team producing 200+ knowledge base articles along the way.
Executive education
Where the operating discipline came from.
- University of Chicago Booth — Chief AI Officer ProgramExpected Nov 2026
- Stanford Graduate School of Business — Digital Transformation and AI PlaybookJan 2026
- UC Berkeley Haas — Technology Leadership ProgramDec 2025
- UC Berkeley Haas — Data StrategySep 2025
- UC Berkeley Haas — Digital TransformationDec 2024
- UC Berkeley Haas — AI Business Strategies and ApplicationsJun 2024
Returned to UC Berkeley Executive Education as a guest speaker and fireside chat participant: From AI Experiment to Operating System.
Get in touch
Conversations I am always open to.
- Conference talks, panels, and fireside chats
- Executive education and workshop sessions
- Advisory conversations on AI adoption, governance, and operating models