AI for the Workplace with Claude: Complete Online Course Guide
Live online, 2 days, instructor-led. $799 with free retake within one year. Pro-level Claude subscription recommended. No prior AI experience required.
Claude model tiers at a glance
| Feature | Model | Best for | When to use |
|---|---|---|---|
| Haiku | Fast, affordable | Quick questions, simple drafts, high-volume tasks | |
| Sonnet | Balanced default | Everyday writing, analysis, and research | |
| Opus | Max capability | Complex reasoning, nuanced writing, hard multi-step problems |
Context window vs. books of text
Weak prompt vs. strong prompt — same task, very different results
| Feature | Weak prompt | Strong prompt |
|---|---|---|
| The ask | "Write a summary of our project." | "I'm a PM at [org]. Summarize our Q3 website redesign for my director. Include timeline status, budget variance, and two key risks. Under 250 words. Professional, direct tone." |
| What's missing | No audience, no format, no length, no tone — Claude has to guess at all of it. | All five prompt parts are present: context, task, format, constraints, examples (the constraints serve as the pattern). |
| Typical result | A long, generic paragraph you'll rewrite. | A tight, on-tone draft that's 80% of the way to final. |
The five prompt patterns drilled in Module 2
Writing & drafting
Emails, memos, reports, briefs, talking points. Start with role and audience, then content, then constraints.
Summarization
Long docs, meeting notes, data pulls — with a structured output (main conclusion, supporting points, open questions).
Analysis
Identify patterns, compare options, evaluate arguments. Ask for reasoning, not just a verdict.
Research
Gather information, explain concepts. Use web search deliberately — it's a quota eater.
Creative problem-solving
Brainstorming, reframing, generating alternatives. Role prompts shine here.
Day 1 agenda (6.5 hours + lunch)
Module 1 — Getting Started with Claude
Mental model, model tiers, interface tour, first prompt.
Module 2 — Prompting Fundamentals + Files
Anatomy of a prompt, five use cases, working with PDFs and images.
Module 3 — Projects
Custom instructions + knowledge base. Set context once.
Module 4 — Artifacts, Styles, Memory
Deliverables, voice control, persistent context.
Lunch
60 minutes.
Module 5 — Advanced Prompting
Role-based, chain-of-thought, multi-step, 'You Ask Me'.
Module 6 — Claude vs. Other AI Tools
Honest comparison. Pick the right tool for the job.
Module 7 — Day 1 Wrap-Up
What to install before Day 2.
Four features, one system
Projects
Dedicated workspaces with custom instructions and a knowledge base. Every conversation inside inherits the setup.
Artifacts
Standalone deliverables Claude produces alongside conversation — docs, tables, visualizations, code.
Styles
Encode your voice once (concise, data-driven, no jargon) and reuse across every chat and Project.
Memory
Persistent context about you — role, preferences, terminology — editable from settings.
Set up your first Project in five steps
New Project
Sidebar → Projects → New Project. Give it a specific name ("Q3 Performance Report", "Hiring — Data Analyst").
Write custom instructions
Who you are, what the project is, and how Claude should respond. Three to five sentences is plenty to start.
Upload the knowledge base
Reports, guides, data, templates, prior deliverables. Paid plans use RAG so you can reference far more than fits in a single chat.
Start a conversation
Your first chat inherits every instruction and reference doc automatically. Iterate on the instructions as you go.
Save Artifacts back
When Claude produces a useful deliverable, save it to the Project's knowledge base so future chats match the style.
Day 2 agenda (6.5 hours + lunch)
Module 8 — Claude Cowork Intro
Desktop agent that reads and writes your files.
Module 9 — Your Context System
about-me, brand-voice, working-style — the real multiplier.
Module 10 — Guardrails & Safe Use
Permissions, network egress, privacy, prompt injection.
Module 11 — Connectors + Office Add-Ins
Slack, Drive, Gmail, Notion, Excel, PowerPoint.
Lunch
60 minutes.
Module 12 — Plugins + Scheduled Tasks
Role-specific expertise + recurring automation.
Module 13 — Industry Applications
Data, marketing, HR, ops, PM, finance — pick two.
Module 14 — Capstone
Build your personal Claude system end-to-end.
Module 15 — Wrap-Up
Week 1 action plan + honest limitations.
Cowork conversation history is stored locally on your computer — it is NOT captured in Audit Logs, the Compliance API, or Data Exports. Do not use Cowork for HIPAA-covered, export-controlled, or classified data. The course covers this in detail in Module 10.
Three files that compound in value every session
about-me.md
Who you are, what you do, what success looks like in your role. Five to ten sentences to start.
brand-voice.md
How you communicate: signature phrases, tone rules, vocabulary, preferred structure, words to avoid.
working-style.md
How you want Claude to behave: ask questions first, default to markdown, lead with the conclusion, no padding.
In your Global Instructions, add one line: "Always ask me clarifying questions before starting any non-trivial task." Brian calls this the single most impactful instruction you can set — it turns vague prompts into guided conversations, and replaces a lot of prompt engineering with a simple interview.
Seven steps to your personal Claude system
Audit your work
Write down every task you do in a typical week. Be specific: "write weekly status report for director", not "write reports".
Ask Claude where it fits
Paste the list and ask: "Which of these can you help with most — and why?" Let Claude triage for you.
Gather the inputs
For your top three to five tasks, ask Claude: "What information do you need from me to do these well?"
Configure your instructions
Refine Global and Folder Instructions based on Claude's feedback. Encode the rules it would otherwise re-ask every time.
Connect your tools
Wire up the connectors most relevant to your top tasks — Slack, Drive, Gmail, Notion, Excel, PowerPoint.
Schedule recurring work
Create at least one Scheduled Task. Weekly status summary. Daily briefing. Friday presentation prep.
Run it end-to-end
Execute your highest-impact task through the full workflow: AskUserQuestion → clarifying questions → finished deliverable. This is what you'll use Monday morning.
One real task per day
Monday
Use Claude for one real task — keep it low-stakes. Something you'd do anyway in your first 90 minutes.
Tuesday
Refine your context files based on yesterday's friction points. Add rules where Claude asked you something you don't want to be asked again.
Wednesday
Try a task with a Plugin active — compare the output with and without. Notice where domain-specific instructions change the answer.
Thursday
Connect one more tool. Try a multi-tool workflow: pull data from a Connector, produce a deliverable, save it back.
Friday
Review your Scheduled Task's output. Adjust the prompt. This is the compounding step — small weekly tweaks pay off for months.
What Claude does well today — and what it doesn't
If you find yourself re-prompting Claude three or four times to get what you want, the problem usually isn't Claude — it's the original prompt. Spend the extra 30 seconds upfront.
Four techniques, drilled until they're automatic
Structured prompts
Context, task, format, constraints, examples. One consistent pattern for every use case.
You Ask Me
Give Claude the goal, ask it to interview you. The single most important technique in the course.
Chain-of-thought
Ask Claude to walk through its reasoning before recommending. Higher accuracy + easier to audit.
Multi-step prompting
Break any task that would take you an hour into three to five verified steps.
Quick check: which technique fits?
Question 1 of 2
You need Claude to draft a 500-word policy memo with a specific audience, format, and tone. Best technique to lead with?
A structured prompt up front beats iterating from a vague one. Set the role, task, format, and constraints once and you'll get a draft that's close on the first try.
You'll get the most out of this course if…
Analyst, manager, IC, ops — any knowledge-work role.
You're past novelty; you want a system.
The capstone targets exactly this.
Module 10 covers guardrails, data privacy, prompt injection.
Every module ends hands-on, on your own files.
A running, personalized Claude system — context files, Global Instructions, connected tools, at least one scheduled task, and a Week 1 action plan locked in for Monday morning.
Key Takeaways