This module equips coaches with practical strategies for navigating difficult coaching situations, supporting learners through frustration, and understanding when it is appropriate to escalate an issue. Effective coaching involves not only technical knowledge, but also emotional awareness, communication skills, and clear boundaries. This module helps you coach confidently, even when things get messy.
Demonstrate how to break down a problem logically rather than relying solely on knowledge recall.
Feel comfortable saying “I don’t know” and use it as a learning moment.
Show learners how to identify credible resources and verify information.
Collaboratively investigate solutions to promote shared discovery.
Recognise early signs of overwhelm, such as withdrawal, agitation, or self-blame.
Validate emotions and normalise that struggle is part of learning technical skills.
Teach coping strategies like stepping away briefly, reframing the problem, working in smaller chunks or Rubber Duck Debugging
Support learners in building resilience and persistence.
Clearly communicate session expectations, availability, and what support you can reasonably provide.
Manage time effectively during sessions, especially with multiple learners.
Know when to refer learners to additional support.
Recognise red flags indicating the need for escalation, such as safeguarding concerns, repeated distress, or technical issues that require specialised help.
Follow your codebar’s escalation pathway or referral process. Reach out to Charlene or Kim.
Communicate escalation reasons and benefits to learners.
Even experienced coaches encounter unfamiliar questions. Rather than seeing this as a barrier, treat it as an opportunity to model curiosity and strong problem-solving skills.
Break the problem down with the learner.
Ask questions such as: “What have you tried?” or “What does the error message tell us?”
Look up documentation, examples, or resources together.
Show learners how to fact-check online answers or AI-generated suggestions.
Emphasise the value of learning how to learn, rather than memorising solutions.
This approach builds learner confidence and avoids creating dependence on the coach.
Learning technical topics can be emotionally challenging. When learners feel stuck, they may become quiet, apologetic, or visibly frustrated.
Effective coaching includes:
Validating feelings: “It makes sense that this feels difficult. Many people struggle at this stage.”
Normalising the learning curve: Mistakes and confusion are signs of progress, not failure.
Offering strategies:
Break the task into smaller steps
Encourage short mental breaks
Use diagrams or alternative explanations
Compare the issue to something they already understand
Your calm, steady presence can prevent frustration from becoming disengagement.
Healthy boundaries ensure sustainable, high-quality coaching.
Clearly communicate available time and support. Protect your time, both in sessions and outside them.
Clarify what you can help with and what you cannot.
Be honest when a topic is outside your expertise rather than guessing or over-extending.
By setting boundaries, you encourage learners to take ownership of their progress and avoid unrealistic expectations.
Some challenges require additional support or intervention.
Reasons you may need to escalate include:
A learner becomes distressed or expresses wellbeing concerns
A technical issue is beyond your training or role
A learner demonstrates repeated difficulties that require specialist help
Safeguarding, harassment, or discrimination concerns emerge
How to escalate effectively:
Follow the organisation’s agreed escalation procedure
Document what happened if required
Explain to the learner why escalation is in their best interest
Reassure them they are not “in trouble”—escalation is about support, not punishment
Clear, timely escalation protects learners and ensures they receive the right help.
Make sure you have read and understand the code of conduct
Read the codebar code of conduct
Read each scenario and categorise the coach’s response into one of the following:
Solve Together
Emotional Support Needed
Set a Boundary
Escalate
| # | Scenario | Response Category |
|---|---|---|
| 1 | A learner loudly says, “This platform is broken!” and looks to you to fix the error, but it is a common issue you can troubleshoot together. | |
| 2 | A learner becomes upset, says “I’m just too stupid for this,” and stops interacting with their computer. | |
| 3 | A learner messages you late at night saying, “Can you review my code quickly before tomorrow?” | |
| 4 | A learner quietly tells you that another participant made a discriminatory comment about them during the break. | |
| 5 | A learner asks a question about a concept you haven’t seen before and you need to look up documentation. | |
| 6 | A learner repeatedly interrupts others and dominates the session. | |
| 7 | A learner mentions they are experiencing panic attacks and cannot continue working. | |
| 8 | A learner is frustrated and asks, “Can you just type the answer for me?” but seems open to guidance with encouragement. |