Why I Teach Copilot Instead of ChatGPT in Enterprise Workshops

When companies hire me as an AI workshop facilitator, most expect me to open ChatGPT on day one. I don't. For enterprise workshops, I almost always start with Microsoft Copilot -- the tool already inside their security boundary, already paid for, and already approved by IT.

This is a deliberate choice, and it changes everything about how adoption plays out.

The Shadow IT Problem

Every enterprise I've worked with has the same dirty secret: employees are already using AI. They're just using it on personal phones, with personal accounts, uploading company data into consumer-grade tools with zero data protection.

When I start with ChatGPT in a corporate workshop, I accidentally validate this behavior. I'm teaching people to use a tool that IT might block tomorrow. When I start with Copilot, I'm teaching within the security fence. There's no debate about "is this allowed?" It's already allowed. It's already paid for. It's already integrated with their email, their documents, their calendar.

The Adoption Curve Is Steeper With ChatGPT

ChatGPT is a standalone tool. You have to open a new browser tab, context-switch, copy-paste data in, and copy-paste results out. Copilot lives inside the tools people already use -- Word, Outlook, Excel, Teams. The friction to adoption is dramatically lower.

When I helped PolyU's finance team build AI workflows, the breakthrough came when AI stopped being a "separate activity" and became part of their existing Excel and email workflow. That integration is what turns occasional users into daily users.

When I Do Teach ChatGPT

I'm not dogmatic about this. ChatGPT and Gemini are genuinely better at certain tasks -- creative brainstorming, complex analysis, image generation. At Chow Tai Fook's design workshop, we used four different AI tools because jewelry design requires capabilities that Copilot doesn't have.

The principle is: start with the tool that has the lowest barrier to sustained daily use, then expand to specialized tools for specific workflows. For most enterprises, that starting point is Copilot.

The Real Lesson

The tool choice isn't really about the tool. It's about designing for adoption, not demonstration.

A workshop where everyone leaves saying "wow, ChatGPT is amazing" but nobody uses it next week has failed. A workshop where everyone leaves with Copilot integrated into their actual email workflow -- even if it's less flashy -- has succeeded.

As an AI workshop facilitator, my job isn't to show people the most impressive AI demo. It's to make sure they're still using AI a month later. Starting with the tool that's already in their ecosystem is the single biggest predictor of long-term adoption.