Ask for Help When You're Stuck

This template practices asking for help after you’ve been stuck on a work task for a while, without sounding defensive or ashamed. The scenario centers on a spreadsheet formula that is returning the wrong totals and a status update that is now behind schedule. You practice naming the blocker, summarizing what you already tried, and making a direct request for help. The goal is to leave with a concrete next step, not just to vent frustration.

Use it for individual contributors, new hires, or anyone who needs to ask a peer for help in a clear, professional way. It is especially useful for people who tend to over-explain, apologize too much, or wait too long before escalating. Managers can also use it in coaching or onboarding to normalize timely help-seeking. The persona is a knowledgeable peer, so it fits lateral support rather than manager escalation.

Use it whenever a learner hesitates to ask for help, or as part of onboarding and communication training. It also works well as a short refresher before a busy period when people are likely to get stuck on routine work. Because the scenario is specific, one or two attempts can reveal whether the learner can ask directly and stay composed. Repeating it with different temperaments can help build confidence.

Ad-hoc advice usually stops at “ask sooner,” but this roleplay makes the learner practice the actual conversation. They have to identify the blocker, describe prior attempts, and make a respectful request in real time. That mirrors deliberate-practice research: realistic reps with immediate, specific feedback build skill faster than passive learning. It also surfaces common habits like apologizing excessively or hiding the real problem.

Yes. You can swap the spreadsheet issue for a CRM report, a budget file, a dashboard, or another task your team actually gets stuck on. You can also change the persona’s temperament from helpful-but-busy to more direct if your learners need a harder challenge. Keep the situation concrete, the blocker observable, and the next step realistic so the practice stays believable.

A strong attempt usually starts with a clear opener, such as naming the task and the blocker in one sentence. Then the learner should briefly say what they already tried, so the peer does not repeat the same steps. The request should be direct and respectful, like asking the peer to help identify where the formula is going wrong. The close should confirm the next action, such as reviewing the formula together or sending a corrected version by a specific time.

The most common issues are waiting too long to ask, over-apologizing, and describing the whole story before naming the actual blocker. Learners also often ask vaguely for “a quick look” instead of saying what kind of help they need. Another frequent mistake is sounding defensive about the mistake rather than focusing on the work. This template makes those habits visible so they can be corrected.

Jordan is written as a knowledgeable peer who has solved similar spreadsheet problems before, so the conversation feels realistic. The persona is helpful and practical, but slightly busy, which creates pressure to be concise and clear. If the learner is vague or defensive, Jordan can push for specifics; if the learner is direct and calm, Jordan becomes more collaborative. That dynamic helps the learner practice a real workplace ask, not a scripted monologue.

Score whether the learner named the blocker clearly, shared what they already tried, asked for help directly and respectfully, stayed calm and non-defensive, and closed with a concrete next step. Those criteria reflect the actual behaviors that make help-seeking effective at work. A good attempt should make it easy for the peer to understand the problem and respond quickly. If the learner leaves the conversation vague, the template has not done its job.