Corporate Training e-learning & explainer scripts

[On screen: Module 3 - Giving Feedback That Lands] Most managers don't avoid feedback because they don't care. They avoid it because they care, and they're worried about getting it wrong. This module gives you a simple way to get it right more often. We call it See, Say, Ask. [On screen: See] First, See. Start with something specific you observed. Not a label, not a personality trait. An action. "You're disorganized" is a label. "The report came in two days after the deadline, and the numbers in section two didn't match the summary" is an observation. One starts an argument. The other starts a conversation. [On screen: Say] Second, Say. Say what the impact was. Keep it short and honest. "Because it came in late, the client meeting was pushed, and I had to explain the numbers on the spot." You're not piling on. You're connecting the action to what it caused, so the other person can see why it matters. [On screen: Ask] Third, Ask. Then stop talking and ask a real question. "What got in the way?" or "What would help next time?" This is where most feedback goes wrong. We deliver the message and then keep explaining, softening, or repeating ourselves. Instead, let the silence sit. The answer is usually more useful than anything you'd have added. [On screen: See. Say. Ask.] A quick note on timing. Feedback works best close to the moment, and in private. Waiting until a formal review turns a small fix into a big surprise. And a note on tone. Some people think being kind means being vague. It doesn't. Kindness is being clear. Vague feedback leaves people guessing, and guessing is stressful. In the next activity, you'll read three short situations and write a See, Say, Ask for each one. There are no perfect answers. Just practice.

[On screen: New Managers Programme - Module 2] If you've just become a manager, your first proper one-to-one can feel a bit odd. Last month, this person was your peer. Now you're meant to be asking about their goals. Take a breath. It gets easier quickly, and there's a simple structure that helps. [On screen: Before the meeting] Before the meeting, book thirty minutes, not fifteen, and keep it in the diary every fortnight. Moving it at the last minute sends a message, even if you don't mean it to. Ask them to bring two or three things they'd like to talk about. That small request does a lot of work. It tells them this meeting is for them. [On screen: During the meeting] During the meeting, let them go first. Listen more than you speak. A good rule of thumb is that they should be talking for about two thirds of the time. Useful questions include: What's going well at the moment? What's getting in the way? Is there anything you need from me? Resist the urge to fix everything on the spot. Sometimes the most helpful thing you can say is, "Let me think about that and come back to you by Thursday." Then, of course, actually come back by Thursday. [On screen: After the meeting] Afterwards, jot down two or three notes. What you discussed, what you agreed, and who's doing what. Share them if that suits your team. Look at them before the next session so you can pick up where you left off. One last thought. A one-to-one isn't a status update. You can get project news from a tracker. This is time to understand the person, what they care about and what would help them do their best work. It's their meeting, not yours. If you remember nothing else, remember that.

[On screen: Brookfield Distribution Center - Site induction] Welcome to the Brookfield Distribution Center. Before you start work on the floor, we're going to walk through the building together, zone by zone. This induction takes about fifteen minutes, and you'll need to complete it before your badge will open the warehouse doors. [On screen: Map of the site, entrance highlighted] Let's start at the staff entrance. Every shift, you'll badge in here and pick up your high-visibility vest from the rack on your right. Vests are required anywhere past the yellow line. No exceptions, even if you're just grabbing something quickly. [On screen: Zone A - Receiving] Zone A is Receiving. This is where trucks unload at the dock doors. When a door is open, a truck may be backing in, even if you can't see it yet. Stay behind the painted safety line unless you're assigned to that door. And never stand between a truck and the dock. [On screen: Zone B - Storage racking] Zone B is Storage. The racking here runs up to thirty feet. Never climb the racking, and never stand under a load being raised or lowered. If you notice a bent upright, a missing safety pin, or a pallet hanging over the edge, report it to your shift lead straight away. Damaged racking can fail without warning. [On screen: Pedestrian walkways in green] You'll notice green walkways painted throughout the floor. These are for people on foot. Forklifts and pallet jacks use the gray lanes. Where the two meet, you'll see a crossing marked with white stripes. Stop, look both ways, and make eye contact with any driver before you cross. If you can't see the driver's eyes, assume they can't see you. [On screen: Zone C - Picking and packing] Zone C is Picking and Packing, where most new team members start. Workstations are set up so the items you handle most sit between your waist and shoulders. If your station isn't set up that way, tell your lead. Small changes to height and reach add up over a ten-hour shift. Box cutters here have self-retracting blades. Always cut away from your body, and put the cutter back in its holder when you're done. Don't leave it on the bench. [On screen: First aid stations and fire exits] As you walk the floor, look for the red signs. They mark fire exits, extinguishers, and first aid stations. There's one of each within fifty feet of every workstation. Take a moment on your first shift to find the nearest ones to where you'll be working. [On screen: Break room] Finally, the break room. Eat and drink only here, never on the warehouse floor. And please take your breaks. Rested people make fewer mistakes, and fewer mistakes mean fewer injuries. That's the walkthrough. In the next section, you'll answer five questions about what you've seen. You need four out of five to pass, and you can retake it as many times as you like.

[On screen: Scenario - It's Wednesday afternoon] It's Wednesday afternoon. You've promised your manager, Dana, a draft of the quarterly summary by end of day Thursday. But two of your data sources are late, a customer issue ate your whole morning, and you now realize there's no realistic way to finish by Thursday. What do you do? [On screen: Three options] Option one. Keep quiet, work late tonight and tomorrow, and hope you make it. Option two. Send Dana a quick message Thursday afternoon explaining it'll be a day late. Option three. Talk to Dana today. Explain what's happened, and suggest what you can deliver by Thursday and what will need until Monday. Take a moment and choose. [On screen: Learner selects option one] You stay late both nights. On Thursday at six, the summary is still missing a section, and you're exhausted. Dana finds out it's incomplete when she opens it Friday morning, right before her own meeting. It's a common choice. Most of us want to avoid disappointing people. But silence usually turns a small problem into a surprise, and surprises are harder on everyone. [On screen: Learner selects option two] Dana gets your message two hours before the deadline. She's already told her director the summary is coming. Now she has to walk that back. Letting someone know is better than not letting them know. But timing matters. The earlier you raise it, the more options everyone has. [On screen: Learner selects option three] Dana isn't thrilled, but she's glad you said something. Together you agree that you'll send the main numbers on Thursday and the full write-up on Monday. She adjusts her meeting plan. This is the strongest choice. You raised the problem early, you came with a proposal, and you let your manager make an informed decision. [On screen: Key takeaway - Early, honest, with a plan]

[On screen: Writing emails people actually read] The average person at work gets well over a hundred emails a day. Yours is competing with all of them. So let's make it easy to read. Here's a typical email. "Hi team, I hope everyone is doing well. I wanted to follow up on the conversation we had last week about the new scheduling process, and I've been thinking about some of the concerns people raised, and after talking to a few people I think it might make sense to maybe push the launch, though I'm open to other ideas. Let me know your thoughts." What does it want you to do? It's hard to tell. Now here's the same email, rewritten. "Subject: Decision needed by Friday - move scheduling launch to June 3? Hi team, I'd like to move the launch of the new scheduling process from May 13 to June 3. That gives us time to fix the two issues raised last week. Please reply by Friday if you have concerns. If I don't hear any, I'll confirm the new date on Monday." [On screen: Ask first. Be specific. Give a deadline.] The second version does three things. It puts the ask first. The subject line tells you exactly what's needed and when. It's specific. Real dates, the actual number of issues, a clear proposal. And it gives a deadline, plus what happens if nobody replies. That keeps things moving. A few more quick habits. Keep paragraphs to two or three lines. Use a short list if you're asking for more than one thing. And read it once from the reader's point of view before you hit send. Your turn. In the next screen, you'll rewrite a sample email using these three steps.

[On screen: Leading your team through change] Reorganisations are unsettling, even when they're well planned. People worry about their jobs, their teams and their routines. And as a manager, you're often expected to reassure everyone while you're still working out what it means for you. This module won't make that easy. But it will give you a few principles that tend to help. [On screen: 1. Communicate early and often] The first principle is to communicate early and often. When people don't have information, they fill the gap themselves, and the stories they tell are usually worse than the truth. You won't always have the full picture. That's all right. A useful pattern is this: say what you know, what you don't, and when you'll know more. For example: "Here's what I know. Our two teams will merge in October. Here's what I don't know yet: who'll lead the combined team. I expect to hear by the end of the month, and I'll tell you the same day." That's honest, it's specific, and it gives people a date to hold on to. [On screen: 2. Make room for reactions] The second principle is to make room for reactions. Some people will be angry, some anxious, some quietly relieved, and a few won't seem bothered at all. All of those are normal. Resist the temptation to talk people out of how they feel. "I understand this is frustrating" is more helpful than "Honestly, it'll be fine." You don't know that it'll be fine, and neither do they. Hold one-to-ones as soon as you can after an announcement. Some people won't say much in a group but will tell you plenty on their own. [On screen: 3. Keep what you can steady] The third principle is to keep what you can steady. When a lot is changing, the things that stay the same become more important. Keep your regular meetings. Keep your usual standards. Keep celebrating good work. Small routines tell people that the ground beneath them is still solid, even while the walls are being moved. [On screen: 4. Look after yourself] And finally, look after yourself. Leading through change is tiring, and you may have your own worries about it. Find someone you can talk to honestly, whether that's your own manager, a peer, or our employee assistance service. You don't have to have all the answers. You just need to be the person your team can rely on to tell them the truth, as soon as you know it. In the next section, you'll hear three short messages from managers announcing a change. You'll decide which one follows these principles best, and why.

[On screen: Sample pay stub] Your first pay stub can look like a wall of numbers. Let's go through it line by line, using this sample. [On screen: Top section highlighted] At the top, you'll see your name, employee ID, and the pay period. This one covers the first through the fifteenth. You're paid twice a month, on the twentieth and the fifth. [On screen: Gross pay highlighted] Next is gross pay. That's what you earned before anything is taken out. In this example, it's two thousand, four hundred dollars. If you worked overtime, you'll see it here as a separate line. [On screen: Taxes highlighted] Below that are taxes. These are required by law, and they include federal income tax, state income tax, and payroll taxes for Social Security and Medicare. The amount depends on your earnings and the tax form you filled out when you started. If you want to change how much is withheld, you can update that form in the HR portal at any time. [On screen: Deductions highlighted] Then come deductions. These are things you chose, like your medical plan, dental, and retirement contributions. In this sample, the retirement contribution is five percent, or one hundred and twenty dollars. [On screen: Employer contributions highlighted] You might also see a section called employer contributions. This is money the company pays on your behalf, like our retirement match. It doesn't come out of your pay, but it's good to know it's there. [On screen: Net pay highlighted] At the bottom is net pay. That's what lands in your bank account. Here, it's one thousand, seven hundred and six dollars. [On screen: Year to date column] Finally, the column on the right shows year-to-date totals. That's handy when you're budgeting, or doing your taxes. If anything on your stub looks wrong, contact the payroll team within thirty days, so they can correct it on your next check.

[On screen: Deciding when you don't have all the facts] As a leader, you'll rarely have all the information you want before you have to decide. The data is late, the forecast is uncertain, and two smart people on your team disagree. Waiting for certainty feels safe. Often it isn't. Delay is a decision too, and it has its own costs. This module offers a practical way to make good decisions when the picture is incomplete. We'll use four questions. [On screen: 1. How reversible is this?] First, how reversible is this decision? Some decisions are like a door you can walk back through. Trying a new meeting format, testing a different supplier for one order. If it doesn't work, you change it. Others are like a door that locks behind you. Signing a five-year lease. Closing a product line. For reversible decisions, move faster. You'll learn more from trying than from debating. Save your deep analysis for the doors that lock. [On screen: 2. What would change my mind?] Second, what information would actually change your mind? It's easy to ask for more data out of habit. Instead, ask: if I had this piece of information, would I choose differently? If the answer is no, you don't need to wait for it. [On screen: 3. What's the cost of waiting?] Third, what does waiting cost? Put it in concrete terms. A week's delay might mean a missed shipping slot, a frustrated client, or a team stuck in limbo. Sometimes waiting is cheap. Often it's more expensive than it looks. [On screen: 4. How will we know if we're wrong?] And fourth, how will you know if you're wrong? Decide in advance what signal would tell you to change course, and when you'll check. That turns a risky bet into a managed experiment. [On screen: Example] Here's how it looks in practice. Jonah manages customer support at a regional bank. Call volumes have jumped, and he's considering adding weekend hours. He doesn't know whether the spike will last. Is it reversible? Mostly, yes. He can staff weekends for a trial period. What would change his mind? A clear drop in volume in the next two weeks. He'll have that data soon, but not before the next busy weekend. What does waiting cost? Two more weekends of long hold times and complaints. How will he know if he's wrong? If weekend calls stay under a set level for a month, he'll end the trial. So Jonah decides to run weekend hours for six weeks, tells his team it's a trial, and sets a date to review. [On screen: Reflect] Before you move on, think of a decision you've been putting off. Run it through these four questions. You may find it's smaller, or more reversible, than it felt.