onEnterFrame/FULL-course1-ai-tools-at-work.md

Created March 16, 2026 01:57

Star (0) You must be signed in to star a gist
Fork (0) You must be signed in to fork a gist

Select an option

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/onEnterFrame/e4fc5d99b25d7c545005b48e8f424c08.js"></script>
Save onEnterFrame/e4fc5d99b25d7c545005b48e8f424c08 to your computer and use it in GitHub Desktop.

Download ZIP

FULL Storyboards with Prompts, Triggers & Variables — CoursePipelines Demo

Raw

FULL-course1-ai-tools-at-work.md

STORYBOARD: AI Tools at Work — What Every Employee Should Know

Variables

Row ID | On-Screen Content / Prompt | Rise Block | Trigger / Logic / Notes ▶ LESSON 1 — Why This Matters | ▶ LESSON 1 — Why This Matters | ▶ LESSON 1 — Why This Matters | ▶ LESSON 1 — Why This Matters 1 | AI Tools at Work: What Every Employee Should Know | heading | Course title slide. Display company logo if available. No interaction required — Next button advances. 2 | AI tools are everywhere — and your organization is paying attention to how they're used. This course takes about 8 minutes and covers what's approved, what's not, and how to stay on the right side of both your company policy and your clients' trust. | paragraph | Intro paragraph. Font: body. No interaction. 3 | PROMPT: "Before we get started, here's why this matters to you."

The Opportunity The Risk Your Responsibility | accordion | TRIGGER: Learner must expand all 3 items before Next button activates (if Rise supports gating — otherwise leave open).

Item 1 — The Opportunity: AI tools can cut hours off routine tasks — drafting emails, summarizing documents, generating first drafts. When used correctly, they make you faster without replacing your judgment.

Item 2 — The Risk: The same tools that help you work faster can expose confidential data, generate inaccurate information, or create legal liability if used without guardrails. One copy-paste into the wrong tool can be a serious problem.

Item 3 — Your Responsibility: You don't need to become an AI expert. You do need to know which tools are approved, what data you can put into them, and when to ask before you act. ▶ LESSON 2 — Approved vs. Unapproved Tools | ▶ LESSON 2 — Approved vs. Unapproved Tools | ▶ LESSON 2 — Approved vs. Unapproved Tools | ▶ LESSON 2 — Approved vs. Unapproved Tools 4 | Approved vs. Unapproved Tools | heading | Section header. No interaction. 5 | Not all AI tools are created equal — and not all of them are safe for work use. Your organization has reviewed and approved specific tools based on data privacy terms, security standards, and vendor agreements. | paragraph | Intro paragraph. 6 | Approved Tools: • Microsoft Copilot (via company license) • ChatGPT Enterprise (company account only) • Grammarly Business • [Add your organization's approved tools here] | list | VARIABLE: Display green checkmark icon next to header if possible. No interaction — informational list. 7 | Not Approved: • Personal ChatGPT accounts • Google Gemini (personal accounts) • Any AI tool not on the approved list • Browser-based AI add-ons not vetted by IT | list | VARIABLE: Display red X icon next to header if possible. No interaction — informational list. 8 | ⚠️ Using a personal AI account — even for a quick work task — means your input may be used to train that company's models. That data doesn't come back. | quote | TRIGGER: Display as warning callout (orange or red accent). No interaction — learner reads and continues. ▶ LESSON 3 — What Data Can You Share? | ▶ LESSON 3 — What Data Can You Share? | ▶ LESSON 3 — What Data Can You Share? | ▶ LESSON 3 — What Data Can You Share? 9 | What Data Can You Share? | heading | Section header. No interaction. 10 | Even with approved tools, not everything belongs in a prompt. Here's how to think about it. | paragraph | Intro paragraph. 11 | PROMPT: "Select each category to see what's allowed."

Always Okay to Share | Ask Your Manager First | Never Share | accordion | TRIGGER: Learner clicks each item to reveal content.

Item 1 — Always Okay: Generic business writing (email drafts, agenda templates), publicly available information, your own original ideas and outlines, anonymized or fictional examples.

Item 2 — Ask Your Manager First: Internal strategies or roadmaps, customer names or company names, financial projections or forecasts, any document marked "Internal" or "Confidential."

Item 3 — Never Share: Client data or PII (names, emails, addresses, SSNs), passwords or access credentials, documents marked "Restricted" or "Proprietary," personal health or HR information. ▶ LESSON 4 — Getting AI Results You Can Trust | ▶ LESSON 4 — Getting AI Results You Can Trust | ▶ LESSON 4 — Getting AI Results You Can Trust | ▶ LESSON 4 — Getting AI Results You Can Trust 12 | Getting AI Results You Can Trust | heading | Section header. 13 | AI is a first-draft machine, not a fact machine. Everything it produces needs a human review before it goes anywhere — to a client, a manager, or a customer. | paragraph | Intro paragraph. 14 | PROMPT: "Follow these three steps every time you use AI for work."

Step 1: Prompt with Context Step 2: Review Before You Use Step 3: Own the Output | process | TRIGGER: Learner clicks through steps in sequence.

Step 1 — Prompt with Context: The more specific your prompt, the better the output. Vague in = vague out. Include your role, the purpose, the audience, and any constraints.

Step 2 — Review Before You Use: Check for accuracy, tone, and anything that sounds too confident. AI can hallucinate facts with complete authority. Never forward AI output without reading it.

Step 3 — Own the Output: You're responsible for what you send, post, or submit — regardless of whether AI wrote the first draft. ▶ KNOWLEDGE CHECK — 5 Questions | ▶ KNOWLEDGE CHECK — 5 Questions | ▶ KNOWLEDGE CHECK — 5 Questions | ▶ KNOWLEDGE CHECK — 5 Questions 15 | PROMPT: "Let's see what you've learned. You need 80% to pass. You have 2 attempts."

Q1: Which of the following is the safest way to use AI for a work task?

A) Use any free tool that gives the best results B) Use only company-approved tools with non-confidential inputs C) Use your personal account because it's more private D) Avoid AI entirely to stay safe | knowledge_check | CORRECT ANSWER: B

CORRECT FEEDBACK: "Right! Approved tools with appropriate data = the safest combination. Your company has vetted these tools for security and privacy compliance."

INCORRECT FEEDBACK: "Not quite. Free or personal tools may use your inputs to train their models. Always use company-approved tools — even for tasks that seem harmless."

TRIGGER: On submit → show feedback → Next button activates. 16 | PROMPT: "Q2 of 5"

A coworker pastes a client's full name and email into a personal ChatGPT account to draft a follow-up email. What's the problem?

A) Nothing — ChatGPT is always safe B) The email might sound too robotic C) Client PII may be used to train the model and is no longer controlled by your organization D) The email won't be personalized enough | knowledge_check | CORRECT ANSWER: C

CORRECT FEEDBACK: "Exactly. Once client data enters a personal AI account, your organization loses control of it. That's a data privacy violation — and potentially a legal one."

INCORRECT FEEDBACK: "The real issue is data privacy. Client PII entered into a personal AI account may be used to train that company's model. Your organization — and your client — never agreed to that." 17 | PROMPT: "Q3 of 5"

You receive an AI-generated summary of a research report. What should you do before sharing it with your manager?

A) Send it immediately — AI is fast and accurate B) Review it for accuracy, tone, and any errors before sharing C) Add a disclaimer that AI wrote it and send it anyway D) Ask IT to approve it first | knowledge_check | CORRECT ANSWER: B

CORRECT FEEDBACK: "Correct. AI output always needs a human review pass. A confident-sounding wrong answer is still wrong — and now it has your name on it."

INCORRECT FEEDBACK: "AI can generate inaccurate or misleading content that sounds completely authoritative. Always review before sharing — you're responsible for what goes out under your name." 18 | PROMPT: "Q4 of 5"

Which of the following types of content is generally safe to share with a company-approved AI tool?

A) A spreadsheet containing customer SSNs and account numbers B) Your company's unannounced Q3 product roadmap C) A generic email draft requesting pricing from a new vendor D) An employee's HR performance review | knowledge_check | CORRECT ANSWER: C

CORRECT FEEDBACK: "Right. Generic, non-sensitive business communication is exactly what approved AI tools are designed to help with. No confidential data, no problem."

INCORRECT FEEDBACK: "Options A, B, and D all contain sensitive or confidential information that should never enter an AI tool — even an approved one — without explicit guidance from your manager or IT." 19 | PROMPT: "Q5 of 5 — Last one!"

Who is ultimately responsible for AI-generated content that you send to a client, a coworker, or a manager?

A) The AI tool's company B) Your IT department C) No one — it's AI-generated, so there's no liability D) You | knowledge_check | CORRECT ANSWER: D

CORRECT FEEDBACK: "Correct. You own everything you send — regardless of how it was created. AI is a tool, not a shield."

INCORRECT FEEDBACK: "You are responsible. The fact that AI generated the first draft doesn't transfer accountability. Always review, always own the output."

TRIGGER ON PASS (score >= 80): Display success screen → "You passed! Score: [score]%. Course complete." → Set quiz_passed = true → SCORM reports completion + passed.

TRIGGER ON FAIL ATTEMPT 1: Display retry screen → "You scored [score]%. You need 80% to pass. Review the lessons and try again — you have 1 attempt remaining." → Return learner to beginning of knowledge check.

TRIGGER ON FAIL ATTEMPT 2: Display final screen → "You scored [score]%. Please review this course with your manager." → SCORM reports completion + failed. Set quiz_passed = false.

Raw

FULL-module1-setting-expectations.md

STORYBOARD: New Manager Essentials — Module 1 of 3: Setting Expectations

Variables

Variable | Type | Description module1_complete | Boolean | Set to True when learner reaches final slide. Triggers SCORM completion status = completed.

Row ID | On-Screen Content / Prompt | Rise Block | Trigger / Logic / Notes ▶ LESSON 1 — The Cost of Unclear Expectations | ▶ LESSON 1 — The Cost of Unclear Expectations | ▶ LESSON 1 — The Cost of Unclear Expectations | ▶ LESSON 1 — The Cost of Unclear Expectations 1 | New Manager Essentials Module 1 of 3: Setting Expectations with Your Team | heading | Title screen. Display module progress indicator: "Module 1 of 3". No interaction — Next advances. 2 | Most early management mistakes don't come from bad intentions. They come from assumptions. You assumed they knew the deadline. They assumed "done" meant something different. Unclear expectations are the root of most team friction — and they're almost always fixable before they become a problem. | paragraph | Intro paragraph. No interaction. 3 | 57% of employees say unclear priorities are their top source of stress at work.

2× more likely — teams miss deadlines when success criteria aren't defined upfront.

10 minutes is all a good kickoff conversation takes to prevent hours of rework. | numbered_list | TRIGGER: Display as 3 stat callout cards side by side (or stacked on mobile). Each stat appears with bold number and supporting text. No interaction required. ▶ LESSON 2 — What Good Expectations Look Like | ▶ LESSON 2 — What Good Expectations Look Like | ▶ LESSON 2 — What Good Expectations Look Like | ▶ LESSON 2 — What Good Expectations Look Like 4 | What Good Expectations Look Like | heading | Section header. 5 | PROMPT: "Before you assign any meaningful work, you should be able to answer these four questions. Click each one to see why it matters." | paragraph | Instructional prompt above accordion. 6 | What | When | Why | How | accordion | TRIGGER: Learner clicks each item to expand. All 4 should be opened before Next activates (gate if Rise supports it).

Item 1 — WHAT: What exactly needs to be done? What does "done" look like? Be specific enough that a reasonable person could evaluate whether it's complete without asking you.

Item 2 — WHEN: What's the deadline — and are there milestones before it? If the work has dependencies, name them. "ASAP" is not a deadline.

Item 3 — WHY: Why does this matter? What decision or outcome depends on it? People work differently when they understand the stakes.

Item 4 — HOW: Are there constraints on approach, format, tool, or process? If you have a preference, say so upfront — not after they've already done it another way. 7 | If you can't answer all four of these yourself before assigning the work, spend 5 minutes getting clear before you hand it off. Confusion travels downstream — and gets more expensive the further it goes. | quote | TRIGGER: Display as tip callout (blue or teal accent). No interaction. ▶ LESSON 3 — The Kickoff Conversation | ▶ LESSON 3 — The Kickoff Conversation | ▶ LESSON 3 — The Kickoff Conversation | ▶ LESSON 3 — The Kickoff Conversation 8 | The Kickoff Conversation | heading | Section header. 9 | PROMPT: "Use this four-step structure every time you assign meaningful work. It takes 10 minutes. It saves hours." | paragraph | Instructional prompt above process block. 10 | Step 1: State the task and outcome Step 2: Confirm the deadline and constraints Step 3: Ask the right question Step 4: Agree on a check-in point | process | TRIGGER: Learner clicks through steps in sequence. Each step reveals detail text.

Step 1 — State the task and outcome clearly: One or two sentences. What needs to happen and what success looks like. Avoid jargon — if you can't state it plainly, the task isn't clear enough yet.

Step 2 — Confirm the deadline and constraints: State the hard deadline. Name any dependencies. If there are constraints on format, tools, or process, state them now — not after they've submitted the work.

Step 3 — Ask the right question: "What questions do you have?" — not "Does that make sense?" "Does that make sense?" is a yes/no trap. It invites nodding, not honest confusion.

Step 4 — Agree on a check-in point: Before the deadline, not after. A 5-minute midpoint check-in prevents a last-minute surprise. Make it explicit — put it on the calendar if needed. ▶ LESSON 4 — When Expectations Shift | ▶ LESSON 4 — When Expectations Shift | ▶ LESSON 4 — When Expectations Shift | ▶ LESSON 4 — When Expectations Shift 11 | When Expectations Shift | heading | Section header. 12 | Priorities change. Deadlines move. When they do, don't assume your team will figure it out — tell them explicitly, and reset the expectation the same way you set it the first time. | paragraph | Body paragraph. 13 | Silence is not an update.

If something changes, say so immediately. The fastest way to lose a team's trust is to let them work hard toward a target that's already moved — and find out at the deadline. | quote | TRIGGER: Display as warning callout (orange or amber accent).

COMPLETION TRIGGER: This is the final block in Module 1. When learner clicks Continue/Next from this screen: → Set module1_complete = true → SCORM reports: completion status = "completed", success status = "passed" → Display brief completion message: "Module 1 complete. On to Module 2: Running Effective 1:1s."

Raw

FULL-module2-running-11s.md

STORYBOARD: New Manager Essentials — Module 2 of 3: Running Effective 1:1s

Variables

Variable | Type | Description module2_complete | Boolean | Set to True when learner reaches final slide. Triggers SCORM completion.

Row ID | On-Screen Content / Prompt | Rise Block | Trigger / Logic / Notes ▶ LESSON 1 — What 1:1s Are Actually For | ▶ LESSON 1 — What 1:1s Are Actually For | ▶ LESSON 1 — What 1:1s Are Actually For | ▶ LESSON 1 — What 1:1s Are Actually For 1 | New Manager Essentials Module 2 of 3: Running Effective 1:1s | heading | Title screen. Module progress indicator: "Module 2 of 3". No interaction. 2 | A 1:1 is not a status update meeting. Status updates can happen in Slack. A 1:1 is your team member's meeting — it exists so they have a dedicated space to raise blockers, talk about their work, and hear from you in a way that a group meeting doesn't allow. | paragraph | Intro paragraph. No interaction. 3 | PROMPT: "Click each tab to understand the purpose of a 1:1."

What 1:1s Are For | What They Are Not For | How Often | accordion | TRIGGER: Learner expands each item.

Item 1 — What 1:1s Are For: Blockers the team member can't solve alone. Feedback — both directions. Career development conversations. Relationship-building. Coaching moments that don't fit in a group setting.

Item 2 — What They Are Not For: Reading a task list back to each other. Quick status updates that could be a Slack message. Topics that require the whole team to be present. Performance documentation (that's a separate conversation).

Item 3 — How Often: Weekly for the first 90 days with a new team member. Bi-weekly once trust and rhythm are established. Never cancel — reschedule if needed. Consistency signals that you take the relationship seriously. ▶ LESSON 2 — A Simple Structure That Works | ▶ LESSON 2 — A Simple Structure That Works | ▶ LESSON 2 — A Simple Structure That Works | ▶ LESSON 2 — A Simple Structure That Works 4 | A Simple Structure That Works | heading | Section header. 5 | PROMPT: "This four-part structure fits a 30-minute meeting. Use it every time until it becomes habit." | paragraph | Instructional prompt above process block. 6 | Their agenda first | Blockers | Your updates | Close with one action | process | TRIGGER: Learner clicks through steps in sequence.

Step 1 — Their Agenda First (10 min): Open with: "What's on your mind?" Then stop talking. Let them lead. If there's silence, wait — don't fill it. The most important thing on their agenda usually takes a minute to surface.

Step 2 — Blockers (5 min): Ask: "What's slowing you down that I can help remove?" This reframes your role from manager-as-judge to manager-as-resource. You're here to clear the path.

Step 3 — Your Updates (5 min): Anything they need to know: priority changes, org news, timeline shifts, feedback on recent work. Keep it relevant to them — this isn't a company all-hands.

Step 4 — Close with One Action (2 min): End with: "What's your one next step?" and state yours too. Both of you leave knowing what happens next. Even a small, clear action beats a vague "let's keep talking." ▶ LESSON 3 — Questions That Actually Work | ▶ LESSON 3 — Questions That Actually Work | ▶ LESSON 3 — Questions That Actually Work | ▶ LESSON 3 — Questions That Actually Work 7 | Questions That Actually Work | heading | Section header. 8 | PROMPT: "Generic questions get generic answers. Click each swap to see a better version." | paragraph | Instructional prompt above accordion. 9 | Instead of "How's it going?" | Instead of "Any blockers?" | Instead of "Are you okay?" | Instead of "Good job on that" | Instead of "What are your goals?" | accordion | TRIGGER: Learner clicks each item to reveal the better question and why it works.

Item 1 — Instead of "How's it going?": Try: "What's been the hardest part of your week?" Why: "How's it going?" almost always gets "Fine." Asking about difficulty gives people permission to be honest.

Item 2 — Instead of "Any blockers?": Try: "What's the one thing slowing you down most right now?" Why: "Any blockers?" gets a no. Asking for the single biggest obstacle gets a real answer.

Item 3 — Instead of "Are you okay?": Try: "What would make next week better than this one?" Why: It's forward-looking and solution-oriented. It also reveals what wasn't working this week.

Item 4 — Instead of "Good job on that": Try: "When you [specific action], that made a real difference because [specific impact]." Why: Vague praise is forgotten in minutes. Specific recognition tied to impact is remembered for years.

Item 5 — Instead of "What are your goals?": Try: "What kind of work do you want to be doing more of?" Why: "Goals" triggers a performance review mindset. The second question opens an honest conversation about what energizes them. ▶ LESSON 4 — When Someone Goes Quiet | ▶ LESSON 4 — When Someone Goes Quiet | ▶ LESSON 4 — When Someone Goes Quiet | ▶ LESSON 4 — When Someone Goes Quiet 10 | When Someone Goes Quiet | heading | Section header. 11 | Not everyone will show up to a 1:1 ready to talk. That's fine. Your job is to make it safe to be honest — not to perform engagement. | paragraph | Body paragraph. 12 | If someone consistently has "nothing to discuss," that's a signal — not a relief.

It might mean they don't feel safe raising issues. It might mean the meetings feel pointless to them. It might mean something is wrong that they don't know how to bring up.

Try asking: "Is there anything that would make these conversations more useful for you?" That question alone often opens the door. | quote | TRIGGER: Display as tip callout.

COMPLETION TRIGGER: Final block in Module 2. On Continue click: → Set module2_complete = true → SCORM reports: completion status = "completed" → Display: "Module 2 complete. Final module: Giving Feedback That Sticks."

Raw

FULL-module3-giving-feedback.md

STORYBOARD: New Manager Essentials — Module 3 of 3: Giving Feedback That Sticks

Variables

Variable | Type | Description module3_complete | Boolean | Set to True on final slide Continue click. SCORM reports completion. Full series complete.

Row ID | On-Screen Content / Prompt | Rise Block | Trigger / Logic / Notes ▶ LESSON 1 — Why Feedback Often Misses | ▶ LESSON 1 — Why Feedback Often Misses | ▶ LESSON 1 — Why Feedback Often Misses | ▶ LESSON 1 — Why Feedback Often Misses 1 | New Manager Essentials Module 3 of 3: Giving Feedback That Sticks | heading | Title screen. Module progress: "Module 3 of 3 — Final Module". No interaction. 2 | Most feedback fails not because the message was wrong, but because of how it landed. Too vague, too late, too personal, or buried in so many qualifiers that the actual point got lost. Good feedback is a skill — and it's learnable. | paragraph | Intro paragraph. No interaction. 3 | PROMPT: "Click each failure mode to recognize it — and avoid it."

Too Vague | Too Late | Too Personal | accordion | TRIGGER: Learner expands each item.

Item 1 — Too Vague: "You need to communicate better." Better says nothing. Communicate what? With whom? In what format? On what timeline? Feedback without specifics leaves people guessing — and usually guessing wrong.

Item 2 — Too Late: Feedback delivered three weeks after the event has no useful connection to the behavior. The person can barely remember what you're referring to. The moment matters. Feedback within 24–48 hours is dramatically more effective.

Item 3 — Too Personal: "You're disorganized" attacks character. "The last three deliverables came in without a summary — here's why that creates a problem downstream" addresses behavior. One creates defensiveness. The other creates clarity. ▶ LESSON 2 — The SBI Framework | ▶ LESSON 2 — The SBI Framework | ▶ LESSON 2 — The SBI Framework | ▶ LESSON 2 — The SBI Framework 4 | The SBI Framework | heading | Section header. 5 | PROMPT: "SBI is a three-part structure that keeps feedback specific, observable, and actionable. Click through each step." | paragraph | Instructional prompt. 6 | Situation | Behavior | Impact | process | TRIGGER: Learner clicks through steps.

Step 1 — SITUATION: Describe the specific context. When and where did this happen? Be precise enough that both of you are picturing the same moment. Example: "In Tuesday's client presentation..."

Step 2 — BEHAVIOR: Describe what you actually observed — not your interpretation, not your conclusion about their character. Just the observable action. Example: "...you interrupted the client twice before they finished their question."

Step 3 — IMPACT: Describe the actual consequence — on the client, the team, the project, or the relationship. Example: "...The client looked frustrated and ended the call 15 minutes early. We lost the follow-up meeting." 7 | "Good job" is forgettable. SBI makes recognition stick.

Instead of: "Good job on that presentation."

Try: "In Thursday's board presentation, when you caught that revenue discrepancy before the CFO saw it — that saved us from a serious credibility problem. That kind of preparation matters, and I want you to know it was noticed." | quote | TRIGGER: Display as highlighted positive example callout (green or teal accent). Shows SBI applied to positive feedback. ▶ LESSON 3 — Delivering It Well | ▶ LESSON 3 — Delivering It Well | ▶ LESSON 3 — Delivering It Well | ▶ LESSON 3 — Delivering It Well 8 | Delivering It Well | heading | Section header. 9 | PROMPT: "Knowing what to say is half the job. Here's how to say it in a way that actually lands." | paragraph | Instructional prompt. 10 | Do it soon | Do it privately | Make it a dialogue | Follow up | accordion | TRIGGER: Learner clicks each item.

Item 1 — Do It Soon: Feedback within 24–48 hours of the event is most effective. After a week, it's historical. After a month, it's a surprise. Don't let "finding the right moment" become an excuse for delay.

Item 2 — Do It Privately: Corrective feedback in front of others is not feedback — it's punishment. Always find a private moment, even if it's a brief hallway conversation. Public praise is fine; public correction is not.

Item 3 — Make It a Dialogue: After you deliver the feedback, stop and ask: "What's your take on that?" You might learn context that changes the picture. You might learn the problem is upstream of the person. Either way, you've made them a participant, not a recipient.

Item 4 — Follow Up: One conversation rarely changes a pattern. Check back in at the next 1:1. If things improved, say so specifically. If not, have the conversation again — earlier, not later. ▶ LESSON 4 — Receiving Feedback | ▶ LESSON 4 — Receiving Feedback | ▶ LESSON 4 — Receiving Feedback | ▶ LESSON 4 — Receiving Feedback 11 | Receiving Feedback | heading | Section header. 12 | Managers need feedback too. And how you receive it sends a louder signal than anything you say about psychological safety. | paragraph | Body paragraph. 13 | PROMPT: "The next time someone gives you feedback, follow these three steps." | paragraph | Instructional prompt above process. 14 | Listen without interrupting | Ask a clarifying question | Thank them | process | TRIGGER: Learner clicks through steps.

Step 1 — Listen Without Interrupting or Defending: Your first instinct will be to explain. Resist it. Let them finish completely. Your explanation — even if valid — signals that you're defending, not listening.

Step 2 — Ask One Clarifying Question: "Can you give me a specific example?" This isn't a challenge — it's a genuine attempt to understand the behavior they observed, not just their interpretation of it.

Step 3 — Thank Them — Even If You Disagree: "I appreciate you telling me that" is not agreement. It's an acknowledgment that it took something to say it. People stop giving feedback when receiving it feels risky. Your response in this moment determines whether they'll do it again.

COMPLETION TRIGGER: Final block in the full series. On Continue click: → Set module3_complete = true → SCORM reports: completion status = "completed" → Display series completion screen: "🎉 New Manager Essentials — Complete! You've finished all 3 modules: ✅ Setting Expectations ✅ Running Effective 1:1s ✅ Giving Feedback That Sticks Great managers aren't born — they're built. You're already doing the work."

onEnterFrame/FULL-course1-ai-tools-at-work.md

Select an option

No results found

Select an option

No results found