Ask for Help When You're Stuck

This template covers a moment where you have been blocked on a work task for most of the day and need to ask a knowledgeable peer for help. The focus is on naming the blocker, summarizing what you already tried, and making a specific request. It is not for formal escalation, performance feedback, or manager check-ins. Use it when peer-to-peer support is the fastest path forward.

A manager, team lead, coach, or the learner themselves can run it as practice. It works well for onboarding, communication training, and individual skill-building because the persona is a peer rather than a boss. The roleplay is especially useful when people hesitate to ask for help until they are already behind. A facilitator can also use it in a group setting and compare different attempts.

Use it whenever a person tends to wait too long before asking for help, or before a new hire starts handling work independently. It also works well as a short refresher after a missed deadline, a stalled project, or a confusing handoff. Because the scenario is simple and realistic, it can be repeated in a few minutes as deliberate practice. The goal is to build a habit of asking earlier and more clearly.

Ad-hoc advice usually stops at 'just ask sooner,' which does not teach the wording or structure of a good request. This template gives the learner a concrete situation, a specific persona, and scored criteria so they can practice the actual conversation. That makes it easier to notice habits like overexplaining, apologizing too much, or failing to ask a direct question. It turns a vague soft skill into a repeatable attempt with feedback.

A strong response names the blocker in plain language, briefly says what has already been tried, and asks for one specific kind of help. It should sound calm and accountable, not defensive or embarrassed. The learner should also close with a clear next step, such as asking for a quick look, a suggestion, or a short pair-debug session. That gives the peer an easy way to respond.

People often ramble through the whole backstory before stating the actual problem. Others ask for help in a vague way, such as 'Can you look at this?' without saying what kind of help they need. Some learners over-apologize, which weakens confidence, while others act like they already know the answer and only want validation. The roleplay surfaces all of those patterns quickly.

Yes. You can swap in a different work task, tool, or blocker while keeping the same communication goal. For example, the task could be a spreadsheet issue, a customer email draft, a code bug, or a policy question. You can also adjust Jordan's temperament to be more rushed, more patient, or more detail-oriented depending on the team. The rubric can stay the same as long as the learner still needs to ask clearly and specifically.

Yes. It fits well into onboarding, manager coaching, peer-feedback practice, and communication skills training because it targets a common workplace moment. It can be paired with other roleplays about status updates, feedback conversations, or escalation when a task is blocked. It also works as a warm-up before live practice because the scenario is short and easy to score. Teams can use it to standardize what a good help request sounds like.