MYCA Learning Demo Notes

The Relay Service Call
Effective Communication with Tenants

City of Los Angeles, Housing Department
Instructional design overview for the branching scenario prototype.

Learning by doing, not by being told.

Most eLearning courses start by defining things. They explain what a relay call is, describe how it works, list the steps, and then quiz the learner on what they just read. Your audience passes the quiz. Whether they retain the material is another question entirely.

This prototype takes a different approach, one grounded in how adults actually learn.

Your audience already knows how to answer a phone. They already know how to communicate with a tenant. They have years of professional experience they bring to every interaction. A course that starts by defining terms they already know wastes that experience, and signals to the learner that the course was not designed for them.

A better method: put them in the situation and let them work through it. Their existing knowledge becomes the foundation. The course adds the layer that is actually new, in this case, what it means to communicate effectively when a tenant reaches them through a relay service.

In this demo, the learner receives a relay call. We do not define what a relay call is. We do not explain the 711 system before they pick up. We put them on the phone and let them experience it, because that is the closest thing to what actually happens when a relay call comes in on an average Tuesday morning.

Some will find it disorienting at first. That is the point. That disorientation is the learning. By the time they reach the debrief, they understand relay calls not because someone explained it, but because they lived it. That understanding sticks.

One scenario. Significant depth.

This prototype covers a single scenario: a relay call from Maria Gonzalez, Unit 304, reporting that her air conditioning has not worked for two days during a heat wave. She is elderly and concerned about her health.

What happens from there depends entirely on the choices the learner makes.

24
Decision points
15
Unique endings
2,451
Possible paths

To put that in perspective: most branching scenarios in corporate eLearning offer three or four paths. They are designed to be completed quickly, with little consequence for the choices made. A learner can work through all paths in a single sitting and arrive at the right answer by process of elimination rather than genuine decision-making.

At 2,451 possible paths through 24 decision points, this scenario does not lend itself to that approach. The choices compound. A misstep at the opening changes what Maria says next. A poor close on an otherwise well-handled call changes the ending. The learner's experience is genuinely their own.

A note on this prototype: This demo was built to demonstrate the methodology and scale of what is possible, not as a finished product. The relay call simulation is based on our best understanding of how the 711 system works. Some details may not reflect exactly how a live relay call sounds or behaves. What you are evaluating here is the instructional architecture, the depth of branching, and the coaching quality. Those are what this demo is built to show.

A realistic call environment, with real stakes.

The scenario opens with a phone ringing. The learner answers, or does not. From there, every choice they make shapes the call in real time.

Where the real learning lands.

When the call ends, the learner receives a detailed debrief across five panels. This is where the coaching happens, specific to the choices they made, in the order they made them.

The debrief is specific to the learner's path. Two learners who reach the same ending via different choices will see different coaching in their decision breakdown. The feedback is earned, not generic.

Five outcomes. One is the standard.

Every path through the scenario leads to one of five outcome categories. These are not arbitrary. They reflect the quality of the overall call and its impact on Maria.

Ideal
Score 80–100 · Passing
Every decision reflected a full understanding of relay protocol and of Maria as a person. The call was handled with accuracy and care throughout.
Strong
Score 70–100 · Passing
The call was handled well overall. One or two moments created friction or missed the mark, but the outcome was appropriate and Maria was served.
Developing
Score 40–69 · Not passing
The right instincts were present, but key moments broke down. The call may have reached a resolution, but not in a way that fully served Maria.
Needs Significant Attention
Score 20–55 · Not passing
Significant gaps in relay protocol, communication, or follow-up. Maria was not well served. Substantial coaching is provided.
Critical Failure
Score 0–39 · Not passing
The call did not reach a resolution. Maria was left without access or assistance. The debrief explains what happened and why it matters.

Failing safely in a simulation is not a bad outcome. A learner who reaches Critical Failure and reads the debrief understands the consequences of their choices in a way no lecture could produce. That's the method working.

This is one scenario. Any scenario is possible.

The relay call was chosen because it is a specific, high-stakes situation that your staff actually encounters. But the methodology is not specific to relay calls.

Any interaction a housing department staff member might face can be built this way: a difficult in-person conversation with a tenant, a fair housing complaint call, a reasonable accommodation request, a language access situation. The scenario changes. The learning architecture, put them in it, let them work through it, debrief them on what they did, stays the same.

For learners who handle the call well, this is a confidence builder. They confirm to themselves that they communicate effectively. They walk away knowing they would do the right thing. For learners who struggle, the coaching is specific and immediate. They understand not just what they got wrong, but why it mattered to Maria, the actual person on the other end of the call.

A narrated lecture with a quiz at the end will not produce either of those outcomes at the same depth. This does.

Designed to reach every learner.

⏱
Adjustable timer The response timer can be turned off by any learner who needs more time. Toggle is visible in the upper right corner at all times.
🔊
Audio + on-screen text Every audio segment is mirrored as on-screen text. Learners can follow visually without audio, or audio without reading.
⌨
Full keyboard navigation All interactions, choices, debrief navigation, and the timer toggle, are accessible without a mouse.
♿
Screen reader compatible Content is structured semantically. Screen reader users receive full access to all text and controls.
↩
Segment replay A replay control will allow learners to re-hear and re-read any segment before responding. Planned for the production build.
✓
WCAG compliance Color contrast, font sizing, and interactive element sizing are designed to meet WCAG 2.1 AA standards in the production build.

Begin the Scenario →
Timer is off by default. Enable it using the toggle in the lower right corner.