Gather Training Examples While Protecting Employee Information

A manager walks into your office with a great story, a real email chain, a real coaching conversation, a real performance review that shows exactly the mistake you want the next cohort to avoid. The material is vivid and true, which is exactly why it works so well in a workshop. It is also attached to one specific person, and the moment it lands on a slide or in a role play script, you have turned a private situation into shared knowledge that person never agreed to share. As a talent development leader, you need real patterns without real people attached to them, and that means having a plan for this conversation before a manager ever offers you the material.

Why This Conversation Goes Wrong

Managers offer real examples because they want training to feel true. A generic case study about a missed deadline does not land the way an actual, specific story does, so a manager who cares about the workshop will naturally reach for the most memorable thing that happened on their team. The problem is that memorable usually means identifiable. A detail as small as a project name, a client, a shift schedule, or a job title can be enough for other employees to guess who the story is about, even after you remove the name.

The conversation also goes wrong because the request usually shows up fast and informally, in a hallway or a quick message, not as a planned handoff. You get asked to say yes or no on the spot, before you have had a chance to think about whether the situation involves an active complaint, a medical accommodation, or a disciplinary record. If you say yes too quickly, you inherit a compliance problem. If you say no bluntly, the manager stops offering examples at all, and your training material gets weaker over time. The goal is a process that lets you say yes to the pattern and no to the private details, every time, without making the manager feel shut down.

How To Prepare Before You Ask

Build the filter before you need it. Set up a short intake form or a standard set of questions you ask any contributor, covering the skill the example teaches, the general work context, the decision point the learner needs to practice, and who owns the underlying process if it touches a people matter. Having this ready means you are not improvising boundaries in the moment, which is when mistakes happen.

Decide in advance what you will never ask for. Names, medical information, case notes, complaint details, and anything pulled from an employee file are off limits, full stop. You do not need them. What you need is the shape of the situation, the behavior that went wrong or right, and the outcome that made it worth teaching. If a manager mentions that a situation came from an active review or an open complaint, treat that as a stop sign. Ask the authorized process owner, usually someone in HR, whether the pattern can be used for learning at all, and wait for an answer before you build anything.

It also helps to have a short answer ready for why you are doing this. Managers respond better to a clear reason than to a flat refusal. Telling someone you need a fictional version because real details can be traced back to a person and could put both of you in a bad spot is a reason people accept. Comparing this to how you would Give a Process Update Without Sharing Another Person's Information can help you frame it, since the same instinct, protect the person while keeping the useful information, applies in both conversations.

What To Say

Picture a manager named Priya stopping by your desk. She says, "I have a whole thread from last month that would make a perfect example for the feedback workshop. It shows exactly how not to handle a missed handoff."

You ask, "What skill do you want managers to practice from it?"

Priya says, "How to raise an incomplete handoff without sounding like you are accusing the person of doing it on purpose."

You reply, "That is a great skill to build a scenario around. Do not send me the thread or any names. Describe the sequence of events in general terms, what was missed, what happened next, and how the conversation actually went, and I will turn that into a fictional exchange between a supervisor and an analyst. If this touches an open review or a complaint, I will need to check with HR before we use it at all."

Priya says, "It is not part of any complaint, it just did not go well. The short version is that a checklist step got skipped and a client update went out late."

That last line is the useful part. You now have a skill, a decision point, and a consequence, with nothing that identifies a real person, a real client, or a real date. That is enough to build a strong scenario.

Mistakes That Undermine The Conversation

A few habits cause this process to fail even when everyone means well.

1. Accepting the raw material first and planning to scrub it later. Once you have the email thread or the case notes, the specific details tend to stay in your head and leak back into the scenario even after you think you removed them.

2. Assuming a first name change is enough. Job title, department, shift pattern, and timeline often identify someone just as clearly as a name does, so change all of them, not just the obvious one.

3. Skipping the check with the process owner because the manager assured you it was fine. Managers are not always aware of what is active in HR or legal. When a situation touches a formal process, that owner makes the call, not you and not the manager.

4. Treating this as a one time judgment call instead of a repeatable process. Without an intake form or a standard set of questions, every request gets handled differently, and inconsistency is where sensitive details slip through.

5. Letting workshop participants ask follow up questions that pull the conversation back toward real details. If a learner asks whether the scenario is based on someone specific, redirect to the skill being practiced, not the source.

Practice And Score The Conversation

This is a conversation worth rehearsing, not just planning on paper. Run it as a role play where you play the talent development leader and someone else plays a manager pushing to use a real, specific example. Notice where you feel pressure to say yes quickly, and practice the redirect that asks for the pattern instead of the details.

DealSpeak lets you rehearse this exact exchange with an AI counterpart that plays the manager, pushes back the way a real one would, and scores how well you protected the person's information while still getting a usable scenario out of the conversation. Score yourself on whether you asked for the skill before the story, whether you named the specific details you needed removed, and whether you held the line when the manager offered a shortcut. You can find this scenario and others built for your role among the HR and Leadership practice conversationsincluding one on Help a Leader Notice When Urgency Prevents Reflectionwhich covers a related instinct to slow down before acting on a compelling story.

Real examples make training better, and protecting the people behind them makes training sustainable. Build the intake habit once, and every future offer of a great story becomes a quick, comfortable conversation instead of a judgment call under pressure.