SOAR Course Review — 2026-01-30

Client: ^[1]
Date: 2026-01-30
Attendees: Isalia Ramirez (Asymmetric), Mark Hope (Asymmetric), Gus Donelson (Agility Recovery)
Next Meeting: Thursday, Feb 6, 2026 at 9:30 AM Central (contingent on Gus's dentist appointment)

Overview

Working session to review SME feedback on the SOAR course from Luke Terry (Hardware Testing, Proof of Concept sections) and to resolve two blocking technical issues: the unreadable Salesforce Storyline block and the similarly broken Co-pilot module. Both issues stem from embedding Storyline as a block within Rise 360, which renders too small on laptops.

Key Decisions

Action Items

• [ ] Isalia — Test standalone Storyline module to confirm whether readability issue is Rise-specific or persists
• [ ] Gus — Download Salesforce SCORM file; send to former designer + LMS admin contact for scaling/approach advice
• [ ] Isalia — Draft video-based Salesforce training outline: 2-minute chunks, cursor visibility considerations, share with Gus
• [ ] Isalia — Update Co-pilot module: move exercises into Rise course; add facilitator notes for live Prompt Cowboy demo
• [ ] Isalia — Hardware Testing updates: add hardware bullet list (Servers, PCs, Firewalls, LTE/LEO/Satellite); clarify virtual vs. physical delivery; add Mobile Unit full-DR sentence
• [ ] Isalia — Revise "When to Position It" flip card: reframe tabletop testing as Proof of Concept; update "How to Say It" language accordingly
• [ ] Isalia — Add facilitator note on tabletop-as-negotiation-tactic (Gus to deliver verbally during debrief)
• [ ] Gus — Confirm with Luke Terry whether Advanced Tabletop is still offered; update course accordingly
• [ ] Isalia — Schedule Thursday Feb 6 check-in at 9:30 AM Central

Topic Detail

Salesforce Training Strategy

Problem: The Salesforce training module was built as a Storyline block embedded inside Rise 360. On laptops (the only device Agility Recovery's team uses), it renders too small to read or interact with meaningfully. Gus noted he "just clicked until it told me I had to move on."

Options under consideration:

Option A — Standalone Storyline Module
- Hypothesis: the readability issue may be specific to the Rise embedding, not Storyline itself
- Isalia to test a standalone Storyline publish to confirm
- Gus to consult a former designer and his wife's LMS admin for technical guidance
- Gus will download the SCORM file and send it to both contacts

Option B — Video-Based Training
- Embed short videos directly in Rise instead of interactive Storyline
- Videos must be ~2 minutes max to avoid learner fatigue (Gus referenced sitting through a 30-minute vendor video as a cautionary tale)
- Cursor visibility is a key production consideration for screen-capture walkthroughs
- Isalia to draft a multimedia outline structured in 2-minute chunks
- This was Mark's original preferred approach; Gus has come around to it if Storyline can't be made to work

"If we can't figure out the Storyline type stuff, I'm not going to continue to get spun on it because I would rather it just get done and move on." — Gus

Co-pilot Module Redesign

Problem: Same embedding issue as Salesforce — the Co-pilot Storyline block is unreadable in Rise.

Decision: Scrap the standalone Co-pilot module entirely.

Restructure plan:
- Exercises (which were practice-focused, not content-heavy) integrated directly into the main Rise course, consistent with format used in other modules
- Hands-on Co-pilot practice moved to the live facilitator session
- Facilitator guide updated to include a live demo of Prompt Cowboy (a prompt-building website) — Gus to run this during the follow-up session
- Key Co-pilot content principles (be specific, iterate, ask "what else do you need before you execute?") remain in the Rise course

SOAR Course Feedback — Luke Terry Review

Feedback came from Luke Terry during a Hardware Testing / Proof of Concept review. ~18 comments total; most were straightforward.

Hardware Testing Section

• Tabs (Phone / Power / Technology): Luke suggested breaking into separate tabs like Tabletop and Pen Testing sections. Decision: keep consolidated for v1. Content density doesn't justify the split.
• Hardware bullet list: Add explicit list of hardware types — Servers, PCs, Switches, Firewalls, LTE, LEO/Satellite — to the relevant section.
• Virtual vs. physical clarification: Hardware tests can be done virtually (Agility ships equipment to customer) or physically (customer visits Agility's site). Add this distinction to the content.
• Mobile Unit: Luke flagged this needs more detail. Add a sentence clarifying: the mobile unit is a full-scale DR test — Agility deploys physical space, power, equipment, and connectivity to the customer's preferred location; employees work live from the unit while testing runs in parallel. (Reference example: Express Scripts deployment with 20 PCs, server, LEO, generator, bathrooms — full kit.)

Advanced Tabletop Section

• Luke flagged "preparing your tabletop" content as likely outdated — he doesn't believe Agility currently offers anything like it.
• Decision: Remove the section. Luke is the SME who runs this service; his call is final.
• Gus to confirm with Terry whether Advanced Tabletop is offered at all before next meeting.

"When to Position It" Flip Card

• Luke suggested reframing tabletop testing as a Proof of Concept (POC) — useful for prospects who are uncertain about committing to a full contract.
• Update the flip card: position tabletop as a POC opportunity ("we don't sign for LEO satellite until we see what it's capable of").
• Update "How to Say It" language to match the POC framing.

Cost-Effective Risk Mitigation Flip Card

• Luke flagged the content may be too complex for introductory reps (negotiation tactics around building tabletop into contract pricing).
• Decision: Keep the flip card content as-is (it's accurate).
• Add a facilitator note for Gus to verbally explain during debrief: successful AEs use tabletop testing as a closing/negotiation tactic — e.g., "sign today and I'll include one tabletop test per year."

Notes

• Luke Terry was on paternity leave when the SOAR course was originally reviewed; Gus wanted to loop him in before finalizing.
• Gus traveling to Arizona Sunday (Jan 31); will review downloaded participant/facilitator guides on the plane and send feedback early the following week.
• Isalia off Friday Feb 7; hence the Thursday Feb 6 check-in.