Workplace Practice: Four Guided Sessions · Session 2 of 4 · Facilitator sheet
Handling a mistake and repairing it
Owning an error without taking blame for the whole system, and choosing a repair move. About 30–45 minutes.
Learners can carry this session into their Spark learning guide without enrolling.
Learning outcomes (observable)
By the end, a learner can be seen or heard doing the following. These guide discussion; they are not assessed.
- Distinguishes the part of an error that belongs to a person from the part that belongs to a process.
- Describes a specific repair action: who to tell, what to say and what to fix first.
- States what a repair protects and what it may still risk.
Choose one activity
The Wrong Load · Croft & Sons
A wrong delivery: owning it, flagging the process and calling the customer.
Reply All · BrightSpark Digital
An email goes further than intended; repairing without spreading it.
After the Trucks Left · Fenmore Line 4
A missed quality check found after the fact.
Session plan
| 0–5 min | Follow-up from session 1, then the opening prompt. |
|---|---|
| 5–20 min | Play one workday. Pause when the mistake becomes visible. |
| 20–35 min | Discussion: sort the error into 'person' and 'process' on a board or sheet. |
| 35–45 min | Optionally draft or talk through a two-sentence repair message. Introduce the optional real-world step. |
Delivery options
- Individual
- Learner plays the workday, then may write the repair message they would send on the learner sheet, or plan it privately.
- Paired
- Partners each draft or talk through a repair message separately, compare them if they wish, and name one thing each version protects.
- Group
- Small groups take different workplaces, then compare: what was the first repair move in each room?
Opening prompt
“Mistakes happen in every job. What makes it easier or harder to tell someone about one? Think about it generally; no personal story needed.”
Discussion questions
- Which part of the mistake belonged to the person, and which part to the process or the system?
- Who was affected by the error, and who would be affected by hiding it?
- What does a good repair sound like when you are nervous about the reaction?
Optional real-world practice step
Notice one small slip this week (yours or a process's) and practice naming it plainly, plus one fix.
Next-session follow-up
Next time, start with: what made a repair easier or harder to say out loud?
Optional “Try it your way” companions
Use these only if there is time. They print with the facilitator sheet.
Practice a repair message
Companion · optional “Try it your way” practice
Practice a repair message
Purpose. Discuss communication, accountability and how to repair a mistake without escalating it.
Durable skills explored: Professional communication, Accountability, Written tone.
This is a separate practice email on the Dunmore project, not Monday's thread. The facts are deliberately simpler so you can practice the repair from the start. Everything here is simulated — nothing is sent.
Source material (as learners see it)
Dunmore project email · 09:10
- “Please send the revised launch copy to Denise only for review. Do not send to the client.”
- Your reply-all went to the client. It said: “We are still waiting on Marcus.”
- Delivery timing is not confirmed.
- Denise can authorize client updates.
Discussion prompts
- What is the difference between a draft and a sent message here?
- How do you describe what happened without guessing anyone's motive?
- When Denise takes over, what is still yours to do?
One possible response
To Denise: “I sent an internal update to the client by reply-all. Here is the exact message; can you approve a correction and confirm who will send it?”
Proposed correction (draft — not sent): “Our earlier message included an internal coordination note. Denise will confirm the delivery update once checked.”
The example is one possible response, not the required wording. Look for exact reporting, no invented motive, and a clear question about who sends the next message.
What changes if…?
Denise says she has already spoken to the client and wants no further email.
- The client draft stays unsent. Denise is now the owner of anything said to the client.
- You can still ask whether any internal follow-up is needed — for example, letting Marcus know what was shared.
- Nothing here tells you the client accepted an apology, so it's worth not assuming that.
Participation options
- Individual:
- Learners read the email and draft privately, or just think it through. Writing is optional.
- Paired:
- One partner drafts the note to Denise; the other reads it as Denise and says what they would still need to know.
- Group:
- Show the source email. Collect possible first sentences aloud, then introduce the changed condition and discuss what changes.
Writing is optional; learners may think privately, discuss, or skip. Nothing is graded or collected. Source: Blueprint v3.0 · Section 30 · B1 Reply All · p. 75.
Companion · optional “Try it your way” practice
Practice a repair message
Purpose. Discuss communication, accountability and how to repair a mistake without escalating it.
Durable skills explored: Professional communication, Accountability, Written tone.
This is a separate practice email on the Dunmore project, not Monday's thread. The facts are deliberately simpler so you can practice the repair from the start. Everything here is simulated — nothing is sent.
Source material (as learners see it)
Dunmore project email · 09:10
- “Please send the revised launch copy to Denise only for review. Do not send to the client.”
- Your reply-all went to the client. It said: “We are still waiting on Marcus.”
- Delivery timing is not confirmed.
- Denise can authorize client updates.
Discussion prompts
- What is the difference between a draft and a sent message here?
- How do you describe what happened without guessing anyone's motive?
- When Denise takes over, what is still yours to do?
One possible response
To Denise: “I sent an internal update to the client by reply-all. Here is the exact message; can you approve a correction and confirm who will send it?”
Proposed correction (draft — not sent): “Our earlier message included an internal coordination note. Denise will confirm the delivery update once checked.”
The example is one possible response, not the required wording. Look for exact reporting, no invented motive, and a clear question about who sends the next message.
What changes if…?
Denise says she has already spoken to the client and wants no further email.
- The client draft stays unsent. Denise is now the owner of anything said to the client.
- You can still ask whether any internal follow-up is needed — for example, letting Marcus know what was shared.
- Nothing here tells you the client accepted an apology, so it's worth not assuming that.
Participation options
- Individual:
- Learners read the email and draft privately, or just think it through. Writing is optional.
- Paired:
- One partner drafts the note to Denise; the other reads it as Denise and says what they would still need to know.
- Group:
- Show the source email. Collect possible first sentences aloud, then introduce the changed condition and discuss what changes.
Writing is optional; learners may think privately, discuss, or skip. Nothing is graded or collected. Source: Blueprint v3.0 · Section 30 · B1 Reply All · p. 75.
Facilitator reminders
- Invite reasoning, not disclosure. Ask what the character could do and why. Never require learners to share personal experiences; offer 'think about it privately' as a normal option.
- Allow disagreement and silence. Different choices are expected. Silent participation, written answers and passing are all legitimate ways to take part.
- Separate judgment from personality. Talk about actions and reasons, not character traits. 'You checked before promising' rather than 'you're cautious'.
- Ask who bears the consequences. For each option, ask who gains, who waits and who carries the risk — customers, coworkers, the business or the worker.
- State safety boundaries clearly. Some lines are not matters of style: allergens, machine guards, privacy and unsafe lifting. Name the boundary plainly before or after play. Never demonstrate an unsafe workaround.
- Not an employment screening tool. Do not use choices, reflections or evidence cards to select, rank or assess people for jobs or placements. The scenarios are fictional practice.
- Describe evidence cards accurately. An evidence card records the choices a learner made and anything they wrote in a fictional scenario. It is not a grade, credential or proof of workplace competence, and it is saved only in that learner's browser.
Full orientation and adaptation notes: program overview.
Workplace Practice: Four Guided Sessions · Session 2 · Learner sheet
Handling a mistake and repairing it
Writing is optional. There are no grades and nobody will check this sheet. Use words, notes or drawings.
To think about: Mistakes happen in every job. What makes it easier or harder to tell someone about one? Think about it generally; no personal story needed.
The mistake, described in plain facts:
What belonged to the person / what belonged to the process:
My two-sentence repair message:
Optional, this week: Notice one small slip this week (yours or a process's) and practice naming it plainly, plus one fix.
Scenarios are fictional practice. What you do here is not a record of employment or a credential.