Branching Path Builder

Turn a learning objective into a fully mapped branching scenario (every decision point, the choices at each, where they lead, and the feedback learners see) so building it in your authoring tool is just data entry.

Für Instructional Designers L&D Content Teams Compliance Trainers Subject Matter Experts
Beispiel-Prompt für den Joy-Assistenten

Using our [course source material] in the Knowledge Center, draft the branching logic for a scenario on [topic]: map every decision point, the choices at each one, where each choice leads, and the feedback the learner sees.

So kann es aussehen

Ein anschauliches Beispiel. Ihr Ergebnis hängt von Ihren Quellen, Daten und Anfragen ab.

Using our customer service playbook in the Knowledge Center, draft the branching logic for a scenario on de-escalating an upset customer: map every decision point, the choices at each one, where each choice leads, and the feedback the learner sees.

I built this from the escalation steps in the Customer Service Playbook, Section 4 ("Handling Upset Customers"). It has one opening setup, three decision points, and four endings, with feedback written for every choice.

Branching scenario: De-escalating an upset customer

Branching scenario · De-escalating an upset customer · 3 decision points · 4 endings

Opening. A customer of six years calls, angry that a shipment arrived damaged for the second time this month. The learner picks up the call and hears the customer vent for fifteen seconds before the first choice appears.

Decision 1: How do you open?

  • A. Acknowledge the frustration and apologize → go to Node 2. Feedback: "Good. Naming the problem and owning it lowers the temperature before you try to solve anything."
  • B. Jump straight to a solution → go to Node 3. Feedback: "The fix matters, but skipping the acknowledgement often makes an upset customer feel unheard."
  • C. Explain the return policy first → go to Node 4. Feedback: "Leading with policy reads as defensive here. The playbook puts empathy before process."

Node 2, Decision 2: The customer is calmer and asks for a full refund plus expedited replacement. Under the playbook you can offer one, not both without a manager.

  • A. Offer the replacement now and explain the refund path → Ending 1 (Resolved). Feedback: "You gave a concrete next step within your authority and set an honest expectation. This is the target outcome."
  • B. Promise both to end the call quickly → Ending 2 (Escalation later). Feedback: "Overpromising feels good in the moment but creates a broken promise the customer will call back about."

Node 3, Decision 3: You offered a fix, but the customer is still angry that you didn't hear them out.

  • A. Pause and acknowledge now → routes back into Ending 1 (Resolved). Feedback: "Recovering with a genuine acknowledgement still works. It's just harder once trust has dipped."
  • B. Repeat the offer more firmly → Ending 3 (Standoff). Feedback: "Pushing the solution twice without acknowledgement usually hardens the customer's position."

Node 4, Policy-first path. The customer escalates and asks for a supervisor. This node has no further choice; it leads to Ending 4 (Transfer). Feedback: "When a call reaches this point, a warm handoff to a supervisor is the right move, but notice how the opening choice set the whole call on this track."

Endings. 1 Resolved (target) · 2 Escalation later · 3 Standoff · 4 Transfer to supervisor. Endings 2–4 each loop the learner back to a short debrief that replays the decision point where the call turned.

Want me to expand the feedback into full coaching notes for each choice, or lay this out as a decision table you can paste into your authoring tool?

From objective to a build-ready map

Branching Path Builder turns a learning objective and your source material into a complete branching map: the opening setup, each decision point, the choices at each one, where every choice leads, and the on-screen feedback for each. You review and refine it in chat, then paste it into Storyline, Rise, or whatever tool you build in.

  1. Add your source material

    Upload the playbook, policy, or course content the scenario is based on to the Knowledge Center so the choices and feedback match how your team really works.

  2. Describe the scenario you want

    Tell Joy the learning objective, the situation, and roughly how many decision points you need. Joy drafts the opening node and the full branching tree.

  3. Review and refine the logic

    Walk the tree with Joy. Ask it to add a recovery path, rewrite feedback for a choice, or collapse two endings. It keeps every path pointing somewhere real.

  4. Build it in your authoring tool

    Copy the finished map into Storyline, Rise, or your LMS and wire up the screens. The logic is done. You're just placing it.

  5. Make it one click for your team

    Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.

Machen Sie es sich zu eigen

Complete Branching Tree

Every decision point, choice, destination, and ending mapped out, with no orphaned paths or dead ends.

Feedback At Every Choice

Joy drafts the on-screen feedback learners see after each decision, in your organization's voice.

Grounded In Your Content

Choices and consequences reflect your actual playbooks and policies, not generic best practice.

Consistent On Every Edit

Change one node and Joy re-checks the tree so paths still connect and endings still resolve.

Customer Service Scenarios

Map de-escalation and complaint-handling paths where tone and sequence change the outcome.

Compliance Decisions

Build ethics and policy scenarios where each choice leads to a realistic consequence and coaching.

Clinical Or Safety Situations

Design step-by-step decision trees where the wrong path has a clear, teachable outcome.

Manager Conversations

Draft difficult-conversation branches so new leads can practice choosing what to say next.

Frequently Asked Questions

How do I design a branching scenario without losing track of the logic?

Describe the objective and situation to Joy, and it drafts the full tree: opening setup, each decision point, the choices, where each leads, and the feedback. Because it's written out as one connected map, you can see every path in one place instead of piecing it together in a spreadsheet.

Does Joy build the finished course in my authoring tool?

No. Joy drafts the branching logic as text you review in chat. You copy that map into Storyline, Rise, your LMS, or whatever tool you build in, then place the screens. Joy handles the design work; you handle the build.

Can the choices and feedback reflect how our company actually handles things?

Yes. Joy works from the playbooks, policies, and course content you connect in the Knowledge Center, so the choices, consequences, and feedback match your organization's approach rather than generic advice.

What happens when I change one decision point?

Ask Joy to add, remove, or rewrite a node and it re-checks the tree so every path still connects to a real destination and every ending still resolves. You won't end up with choices that point to screens that no longer exist.

How complex a scenario can it map?

You set the depth. Tell Joy how many decision points and endings you want. It can draft a quick three-choice branch or a multi-level tree with recovery paths and loop-backs, and you refine it in chat until it's build-ready.

Verwandte Vorlagen

Lernen & Entwicklung

Policy-to-Training Converter

Transform policies into engaging training content learners can ask about.
Lernen & Entwicklung

New Hire Learning Plan

Auto-generate role-specific learning plans for new team members.
Lernen & Entwicklung

Learner FAQ

Help employees apply training concepts on the job.

Ready to map your next branching scenario in minutes?

Melden Sie sich für die Warteliste an und probieren Sie diesen Workflow bei der Einführung von JoySuite als Erste aus.

Zur Warteliste Alle Vorlagen durchsuchen