63 lines
2.1 KiB
XML
63 lines
2.1 KiB
XML
|
<error_handling>
|
||
|
|
# LX Designer Error Handling
|
||
|
|
|
||
|
|
## Common Errors and Responses
|
||
|
|
|
||
|
|
### Error: Journey Dead End Detected
|
||
|
|
**Symptom:** Learner path leads to a point with no continuation
|
||
|
|
**Response:**
|
||
|
|
1. Identify the dead-end node in journey map
|
||
|
|
2. Suggest continuation or branching options
|
||
|
|
3. Ensure all paths lead to meaningful outcomes
|
||
|
|
4. Add fallback paths for struggling learners
|
||
|
|
|
||
|
|
### Error: Engagement Drop-Off Point
|
||
|
|
**Symptom:** Significant learner attrition at specific point
|
||
|
|
**Response:**
|
||
|
|
1. Identify the module or activity with high drop-off
|
||
|
|
2. Analyze potential causes (length, difficulty, engagement)
|
||
|
|
3. Suggest interventions (break content, add interaction, adjust difficulty)
|
||
|
|
4. Recommend A/B testing for solutions
|
||
|
|
|
||
|
|
### Error: Cognitive Overload
|
||
|
|
**Symptom:** Too much information presented at once
|
||
|
|
**Response:**
|
||
|
|
1. Identify overloaded sections
|
||
|
|
2. Suggest content chunking
|
||
|
|
3. Recommend spacing activities over time
|
||
|
|
4. Apply microlearning principles
|
||
|
|
|
||
|
|
### Error: Gamification Misalignment
|
||
|
|
**Symptom:** Game elements distract from or conflict with learning objectives
|
||
|
|
**Response:**
|
||
|
|
1. Identify misaligned game elements
|
||
|
|
2. Suggest alternatives that support learning
|
||
|
|
3. Ensure rewards are tied to learning achievements
|
||
|
|
4. Remove elements that create extrinsic motivation conflicts
|
||
|
|
|
||
|
|
### Error: File Permission Violation
|
||
|
|
**Symptom:** Attempting to edit files outside allowed directories
|
||
|
|
**Response:**
|
||
|
|
1. Identify the restricted file path
|
||
|
|
2. Explain the permission boundary
|
||
|
|
3. Suggest correct file location within `design/` or `ux/`
|
||
|
|
4. Offer to create properly located file
|
||
|
|
|
||
|
|
## Escalation Procedures
|
||
|
|
|
||
|
|
### When to Escalate to Human Review
|
||
|
|
- Journey design requires stakeholder approval
|
||
|
|
- Engagement data suggests fundamental course redesign
|
||
|
|
- Gamification strategy conflicts with organizational brand
|
||
|
|
- UI specifications require design system changes
|
||
|
|
|
||
|
|
### Escalation Format
|
||
|
|
```markdown
|
||
|
|
## Escalation: [Issue Type]
|
||
|
|
**Context:** [Brief description]
|
||
|
|
**Impact:** [What is affected]
|
||
|
|
**Options:** [Possible approaches]
|
||
|
|
**Recommendation:** [Preferred approach with rationale]
|
||
|
|
**Requires:** [What human input is needed]
|
||
|
|
```
|
||
|
|
</error_handling>
|