See What Your Team Can Do With AI (After Training)
I teach practical patterns and guardrails so people can use AI every day with confidence. Below are simple, skimmable before→after examples—and the exact prompt patterns we practice together.
The Path: Train → Empower → Outcomes
A simple, low-risk journey from first workshop to visible results.
Train
I run a focused foundations workshop (½ day) and short enablement sessions. We cover safe use, on-brand outputs, and practical patterns.
- Foundations workshop (½ day)
- Role-based sessions
- Clear do/don’t guidelines
Empower
People apply repeatable flows: intake → draft → review → publish. I provide templates, prompt kits, and quick office hours.
- Prompt kits by role
- Checklists & SOP refresh
- Office hours for real work
Outcomes
We baseline time and quality, measure lift, and scale what works with light playbooks and simple governance.
- Tracked KPIs & adoption
- Pilot → scale plan
- Change support
Use Cases (After Training)
Each example shows a quick before → after and the prompt pattern I teach.
Operations — SOP Rewrite & TL;DR
Before: Long, outdated SOPs cause skipped steps and uneven quality.
After: Clear, concise SOP + TL;DR with a simple checklist—updated 5–10× faster.
- Impact: Quick win · Today
- Privacy: Use redacted examples
// Pattern I teach
You are an operations editor.
Goal: Rewrite the SOP for clarity and brevity.
Steps:
1) Summarize in 5 bullets.
2) Rewrite steps with numbered actions and owners.
3) Add a TL;DR and a checklist.
Return: markdown with headings.
Input: <paste SOP (redacted)>Operations — Meeting Notes → Actions
Before: Notes sit in docs; next steps get missed.
After: Action items with owners/dates + a tidy summary email.
- Impact: Quick win · Today
- Privacy: Internal only
// Pattern I teach
You are my chief of staff.
From these notes, extract:
- Decisions
- Action items (owner, due)
- Risks / blockers
Then draft a 120-word summary email.
Input: <notes>Customer Experience — Faster First Reply (On-Brand)
Before: Agents copy/paste from old emails; tone is inconsistent.
After: Draft replies from macros + your voice; agents personalize in seconds.
- Impact: Quick win · Today
- Privacy: No PII in prompts
// Pattern I teach
You write customer replies in our voice (see style guide below).
Input: macro + non-PII customer details.
Draft a reply with:
- empathy opener
- direct answer
- next step & closing
Keep it under 120 words.
Style Guide: <paste>Customer Experience — NPS Comments → Themes
Before: Free-text feedback is hard to summarize.
After: 5 themes with example quotes and suggested fixes by team.
- Impact: Quick win · Today
- Privacy: Internal only
// Pattern I teach
Cluster these comments into 5 themes with:
- theme name
- 2 example quotes
- suggested actions (owner)
Input: <NPS comments>Marketing — One Source → Many Formats
Before: Blog → social/email repurposing takes hours.
After: A short email and 5 social posts generated with your brand voice.
- Impact: Quick win · Today
- Privacy: Public content
// Pattern I teach
From the article below, draft:
- a 100-word email teaser
- 5 social posts (different angles)
- a meta title & description
Keep our brand voice: <paste style>
Input: <article or bullets>HR / People — Job Posting + Screeners
Before: Generic postings attract mismatched applicants.
After: A targeted posting with five role-specific screening questions.
- Impact: Quick win · Today
- Privacy: Do not include candidate data
// Pattern I teach
You are a recruiting coordinator.
From these role bullets, create:
- a clear job posting (practical & inclusive)
- 5 screening questions (must-have skills)
Input: <role bullets>Outcomes You Can Expect
We prioritize tasks that compound: drafting, research, responses, and summarization.
Privacy & Safe Use
I teach redaction/anonymization, permissioning, and clear “never share” rules—so your team can adopt AI confidently and ethically.
FAQ
Will outputs be on-brand?
Yes. We build a simple style guide and prompt patterns that preserve tone and formatting.
Do we need our own data?
No for quick wins; some pilots benefit from internal docs. We start with low-risk content and grow from there.
How do we measure ROI?
We baseline time-on-task and track hours saved, cycle time, and quality lift as patterns roll out.
Is this safe for privacy?
We define what never leaves your environment and practice redaction and permissioning in the sessions.
Ready to Train Your Team?
Start with a half-day workshop and see usable outcomes this week.