Worked example
Software Engineer: Repair an Incident Explanation
A B2 software engineer knows the technical content but uses an unclear timeline and ambiguous pronouns.
This is a constructed teaching example, not a report of a real student or a claimed learning outcome.
Student context
A B2 software engineer needs to explain a production incident to a non-technical product manager. The learner understands the incident but must make the sequence and ownership clear.
Evidence
- The learner names the technical cause accurately.
- The explanation jumps between detection, diagnosis, and recovery.
- Repeated use of it and they makes the responsible system or team unclear.
Decision
Repair
The recurring timeline and reference errors block the listener from understanding the incident, so advancing to broader incident vocabulary would add complexity without fixing the communication failure.
Lesson objective
By the end of the lesson, the learner will explain a four-stage incident timeline using explicit subjects and time markers that a non-technical listener can follow.
Activity sequence
- 1Order four incident events from detection to recovery.
- 2Replace ambiguous pronouns with the system, service, or team responsible.
- 3Explain the timeline once with a visual sequence and once without it.
- 4Answer two non-technical clarification questions.
Evidence to collect next
- Whether every event has an explicit actor or system.
- Whether timeline markers remain accurate in the second explanation.
- Whether clarification answers simplify rather than add technical detail.
What Should I Teach Next?
Get Edooqoo updates about adult 1:1 teaching decisions. Each email links to the full article or worked example as the canonical source.