The Agility Recovery SOAR (Sales) Training Program is a multi-module eLearning course built in RISE, developed by Asymmetric for Agility Recovery. The program covers product knowledge, competitive positioning, and sales skills for Agility's sales team. Content is generated and refined using a Claude AI project maintained by the Asymmetric team, with Gus (the Agility client stakeholder) providing ongoing review feedback.
See also: [1] | [2]
The course is organized into at least 10 numbered modules ("courses"), each following a standard format:
Course 10 (Test Types and Recovery) was identified as potentially missing its standard closing elements (knowledge check and key takeaways), likely due to a copy-over error. Content for all courses should be verifiable in the Claude AI project; missing sections can be regenerated from there.
One recurring design challenge is how to present the competitive landscape — specifically, the three ways Agility may lose a deal:
Each competitor type is paired with:
- The customer pain points that signal they're considering that path
- A customer quote illustrating the scenario
This content is currently presented as a RISE accordion component. The format has been flagged as potentially unclear. Design principle: if a section's format doesn't serve the content, rework it — chart types, interaction types, and layouts are all flexible unless Gus has explicitly locked them down.
Testimonials are sourced from real Agility client documents. The available pool may be limited, causing repetition across modules. Recommended practice: flag repeated testimonials to the client stakeholder and request additional examples rather than generating synthetic ones.
The Claude AI project was prompted to vary lesson interaction types (accordions, scenarios, charts, etc.) to reduce learner fatigue. However, variety should not come at the expense of clarity or efficiency. Instructional designers should feel empowered to override AI-suggested formats when a simpler approach better serves the content.
When processing client (Gus) feedback on module drafts, apply the following triage logic:
| Feedback Type | Action |
|---|---|
| Clear, actionable correction | Implement directly |
| Ambiguous or unclear | Reply to Gus requesting clarification |
| Requires new or rewritten content | Use Claude AI project to generate; flag to Mark if output is unsatisfactory |
| Formatting/chart type preference | Designer's discretion; no approval needed |
Note: Some of Gus's earlier comments may have been made against a previous draft version. If a comment no longer applies to the current content, it can be dismissed — but confirm before discarding.