Module 6 of 7

Module 6: Bringing AI to Your Team

Why this matters

Once you’ve used AI on real work for a few weeks, your manager and teammates will notice, better drafts, faster turnarounds, more polished output. How they react depends almost entirely on how you frame it. Done well, you get credit for resourcefulness and become the person others come to for advice. Done poorly, it reads as either hiding something or offloading your job. This module is the soft-skills companion to the technical patterns in Modules 3–5.

Most managers’ real worries

Most managers aren’t anti-AI. They’re worried about three things:

Quality: will the work get worse?
Trust: is this still your work, or AI’s?
Risk: what happens if something leaks or is wrong?

Every conversation about AI use at work, whether with your manager, your team, or HR, comes back to one of those three. Address them up front and you skip 90% of the friction.

The pitch

A good intro reframes around quality, trust, and risk:

“I’ve been experimenting with [tool] on [task]. I’m using it to draft, not decide, I still review and edit everything before it goes out. It’s saved me roughly [X hours / week] on [task]. I wanted to mention it before going further so we’re on the same page about how I’m using it. Is there anything you’d want me to be careful with, or should I document the process?”

This works because:

You raised it (proactive, not caught-out)
You framed it as drafting (still your work)
You quantified the value (clear gain)
You invited their guardrails (gives them control)

What to demo

If your manager wants to see it:

Show one task end-to-end. Bullets-in, draft-out, your edits, finished output.
Don’t pick the most impressive thing AI can do. Pick the most reliable thing.
Have a “here’s what I won’t paste in” line ready, shows you understand the risk side.
If asked about a specific edge case, be honest about where AI struggles. Trust comes from showing limits, not selling.

When to stay quiet

Some workplaces aren’t ready. If your industry, employer, or specific manager treats AI use as career-affecting, take it slower:

Use AI only for personal productivity (your own notes, your own learning)
Don’t run anything through AI that ends up in a deliverable until you’ve checked the policy
If you’re unsure, ask. “Hey, just checking, is it OK if I use [tool] to help draft [thing]?” is a one-line question that protects you.

Quiet isn’t dishonest. It’s reading the room. The wrong move is using AI on real work in an environment that hasn’t approved it, that’s the path that becomes a problem.

Helping a teammate or junior

Once you’ve built the habit, you’ll be the person others ask. A few rules of thumb:

Teach the frame (Module 1’s mindset) before the prompts. Otherwise they paste sensitive data on day one.
Share one prompt at a time. People retain what they actually use.
Push back gently if they’re using it as an oracle. The “second perspective” frame is what keeps it healthy.
Don’t oversell. Show your edit-pass on a real draft, the messy part, so they see what 30% looks like.

Try It At Work: Draft the Manager Pitch

Time: 10 min

You’ll need: Your target task (from Module 1) and an honest sense of your manager’s current stance on AI.

Do this:

Use the pitch template above. Personalize it for your task and manager.
Run a tone-check: paste your draft into AI and ask, “Will this come across as proactive or as asking permission for something I’m already doing wrong?” Adjust.
Decide: send / hold / talk in person.

Done when: You have a sent message, a scheduled conversation, or a conscious decision not to raise it yet, with a reason.

Key takeaways

Manager worries cluster around quality, trust, and risk. Address them up front.
Pitch: proactive, drafting (not deciding), quantified gain, invite guardrails.
Demo the most reliable thing, not the most impressive thing. Show your edit-pass.
Some workplaces aren’t ready. Quiet is fine. Caught off-guard is not.
When you teach others, lead with the mindset frame, not the prompts.