RISE360 Course Review — 2026-04-05

Weekly sync with Gus Donelson (Agility Recovery) to resolve module access and version issues, align on RISE360 as the single collaboration platform, and plan next steps for content development.

Attendees: Mark Hope (Asymmetric), Isalia Ramirez (Asymmetric), Gus Donelson (Agility Recovery)

Overview

The call surfaced a significant version mismatch: Gus had only been able to see outdated versions of Module 1 (and limited access to other modules) because of how sharing was configured in Articulate. The team worked through the access issue live, established RISE360 as the single source of truth for all feedback going forward, and aligned on immediate next steps across content, visual assets, and a new sales process initiative called "The Agility Way."

Key Decisions

• RISE360 is now the single source of truth. All feedback, comments, and revisions will happen inside RISE360 going forward. Prior channels (email, Word documents, Google Docs) are deprecated for this purpose.
• Module access via collaborator role, not Review 360. Sharing via "Request Review" puts Gus in a non-licensed viewer state that doesn't surface content correctly in his dashboard. The fix is to add him as a collaborator/editor directly in RISE360, which gives him equivalent review functionality.
• Module 1 will be fully rebuilt. The current Module 1 is a scrambled version from an earlier iteration. It will be blown up and reconstructed; Gus's existing comments will be preserved as reference.
• No pricing in any module. If pricing was referenced anywhere in earlier drafts, it should be removed — pricing changes would require re-publishing the e-learning.
• Weekly Friday touchpoints established as a standing call with the same attendees. Raphael (module builder) should be included on future calls.

Action Items

• [ ] Gus — Review all 10 modules in RISE360 and add comments/feedback
• [ ] Gus — Resolve comments in Module 3 that he had previously addressed (only module he had access to prior to this call)
• [ ] Isalia — Resolve comments in RISE360 that were previously addressed in the Word document
• [ ] Gus — Compile document with case studies, testimonials, and video references; share as a live document with the team
• [ ] Gus — Share MRC walkthrough video (3-minute bank member setup walkthrough) for potential module inclusion
• [ ] Gus — Sketch or describe the "The Agility Way" sales process flow (even rough/on paper) and send to Mark
• [ ] Mark / Designers — Once Gus provides the concept, have designers produce a visual representation of "The Agility Way"
• [ ] Raphael — Rebuild Module 1 from scratch using the corrected structure; preserve Gus's prior comments as reference

Topics Discussed

Module Access & Version Control

Gus arrived at the call unable to see most modules. Investigation revealed two issues:

1. Modules had been shared via "Request Review," which treats Gus as an external, non-licensed viewer — content doesn't appear in his RISE dashboard, only via email link.
2. Module 1 had two versions in circulation. Gus was seeing the August version (8-27-25); the team had been working on an October rebuild. Re-publishing the updated version resolved the discrepancy.

Resolution: Mark added Gus as a collaborator/editor on all 10 modules directly in RISE360. Gus confirmed he could see and comment on them in this mode.

Content Review Status

• Module 1: Scrambled/corrupted. Will be fully rebuilt. Gus had provided feedback via email and in-module comments on the old version — those should be referenced during the rebuild but not treated as current.
• Module 3: Gus had access and left comments. Isalia incorporated feedback from the Word document but did not resolve the in-RISE comments. Both Gus and Isalia will go in and resolve their respective items.
• Modules 2, 4–10: Gus is seeing these for the first time. He will review and comment.

Visual Assets

Gus shared access to an Agility Recovery SharePoint folder containing:
- Logos and brand assets (Marketing Collateral folder)
- Product images including MRC photos (in the 2025 Bootcamp product PowerPoint)

The team noted that stock/generic images (e.g., flooded street from Superstorm Sandy) are acceptable where specific assets aren't available. Gus offered to track down specific images on request rather than having the team search the SharePoint, which he acknowledged is disorganized. Note: IT has restricted access to the training folder only; private marketing and product folders require Gus to retrieve assets directly.

Testimonials & Case Studies

Current modules reuse the same three testimonials across multiple modules. Gus is actively compiling a broader reference document pulling from the Agility Recovery website (success stories, testimonial videos, case study downloads). Goal is a filterable bank sellers can use without needing to call a live reference.

The MRC walkthrough video (a 3-minute tour of a mobile recovery center set up for a bank member test) was flagged as a strong candidate for embedded video content in the modules.

Course Structure & Interactivity

Mark shared the current content distribution across all modules:
- 42 text blocks
- 22 knowledge checks
- 15 interactive tabs
- 12 interactive accordions
- 12 statement blocks

Target is ~60% standard content blocks to create a varied but not overwhelming learning experience. Gus affirmed the balance — too much interactivity feels gamified; too little is flat.

"The Agility Way" — New Sales Process

Gus is developing a new sales methodology called "The Agility Way" consisting of:
- 6 behaviors to display throughout all customer interactions
- 6–7 process steps (pre-call, during call, meeting setup, objection handling, etc.)

The process is non-linear — sellers may need to jump to later steps (e.g., objection handling) earlier depending on the conversation. Gus wants a visual representation (call flow / process diagram) to anchor the e-learning module.

Next step: Gus will sketch the flow (even on paper) and send to Mark. Designers will produce a polished visual for review at a future call.

Context & Notes

• Gus's Agility Recovery account is tied to his work email (@agilityrecovery.com), but his Google account (used for some collaboration tools) routes to a personal Gmail. This caused some notification confusion earlier in the project.
• The Preparis brand (a former Agility product/acquisition) should not appear in any module as an active product — it was divested. It may appear in historical context only.
• AFAM (sister organization) content found in the client-provided files folder is not relevant to this project and can be excluded from the AI training corpus.
• Mark uses a custom AI project scoped to Agility Recovery's provided files to generate module content. If generated content is incorrect, it likely traces to a specific source file — Gus should flag these and Mark will investigate the source.

Related

• ^[1]
• ^[2]