What the May 21 discussion tells us
Source: May 21, 2026 Demo Sync transcript, 33 PDF pages, through 43:15. All exchanges were read. Names/timestamps below follow the transcript. This is a discussion of slides and wireframes, not a usability session or the October working prototype. Automatic transcription contains apparent errors such as “Summit Inquiry”; do not treat those spellings as verified screen copy.
Main evidence
- E-009, stakeholder feedback: relevant non-credit examples, visible course formats, a clearer registration sequence, a reference number and a simpler dashboard received positive comments. [Denise 3:02, page 3; Anuraag 19:02–19:23, pages 15–16; Denise 28:48, page 22; closing comments pages 30–31.] Strong evidence of these reviewers' reactions, not proof of learner task success.
- E-010, unresolved registration model: reviewers did not share one understanding of whether several courses could be selected and paid for together. The discussion was parked for further exploration. [Denise, Alan, Francisco, Rachel and Anuraag, 20:15–25:08, pages 16–20.] Strong evidence of that disagreement at this date; it does not settle current checkout behavior.
- E-011, one reported personal experience: Denise described registering for two community-education classes at one college when places filled within five minutes. She worried that repeated checkout could prevent obtaining both. [24:06, pages 19–20.] This is a useful self-report from one stakeholder, with campus, dates and prevalence unknown. It suggests a scenario to investigate; it is not systemwide demand data.
- E-012, field policy needs context: reviewers distinguished current collection practice, workforce examples, other activity types and the future system. They discussed showing SSN/DOB as required for the CNA demo, while preserving conditional fields for other activities and acknowledging alternatives. [6:47–18:48, pages 5–15.] Strong evidence of a nuanced discussion, not a universal approved SSN policy.
Full discussion notes
| Time and pages | Speaker(s) | What happened and its status |
|---|---|---|
| 0:08–0:45, 1–2 | Group | Opening and availability. No product decision. Personal circumstances are not reproduced here. |
| 0:53–3:16, 2–3 | Alan; Denise; Rachel | Revised portal introduces a personalized greeting/recommendations, catalog search by campus and filters, format on results and instructor detail at section level. Denise appreciates more relevant examples and visible CNA formats; Rachel agrees. This is feedback on the demonstration. |
| 3:19–5:28, 3–4 | Alan; Denise; group | Course details include eligibility, sections and schedules. A course-specific inquiry pre-fills course context. To keep the demo narrative clear, registration/payment is shown first, then the detail screen returns to introduce questions before registration. Agreement concerns presentation order, not forcing learners to register before asking. |
| 5:30–7:34, 4–6 | Alan; Denise; Rachel | New registration screen pre-fills profile data and adds course-specific fields. Alan initially says DOB/SSN are optional. Denise questions DOB; Rachel checks the source sheet and values clear treatment of sensitive information, including possible reluctance to continue. This is stakeholder concern, not a measured abandonment rate. |
| 7:51–10:41, 6–9 | Francisco; Denise; Rachel | Francisco prefers clear required-field markers and suggests optional fields might be omitted or marked. Denise asks for explanation of why SSN is collected, reporting campus requests for that explanation. Rachel confirms DOB is required in the checked material. The team discusses an information aid, but does not approve final copy or policy. |
| 10:48–12:48, 9–11 | Francisco; Denise | Francisco says current optional SSN handling reflects storage/collection concerns and proposes required SSN in the future-system demo. He cautions against committing to detailed explanatory wording without executive alignment and says alternatives are being explored. Denise anticipates mixed campus reactions. These are attributed statements, not a security assessment or settled policy. |
| 12:53–14:17, 11–13 | Rachel; Denise; Alan | Rachel proposes using a side callout to explain that fields vary by activity type. She distinguishes demo explanation from final-screen design. Alan recaps required DOB/SSN for the example. |
| 14:17–17:39, 13–14 | Francisco; Rachel; Denise; Alan | Rachel qualifies the workforce claim: youth/pre-college activity can make SSN conditional as one of several identity elements. They confirm the demo is CNA workforce training. Agreement is to make its fields required and keep the explanatory callout general because rules vary. |
| 17:45–18:48, 14–15 | Deepak; Denise; Francisco | Deepak recalls the initial CSV's optional SSN and “not provided reason” field. Denise confirms it existed. Francisco is unsure the future system should continue that practice. No final resolution. |
| 19:02–19:29, 15–16 | Anuraag; Alan; Denise | Registration sequence and progress indicator receive praise. Alan describes helping a learner understand remaining steps. This supports preserving clarity when reviewing later designs. |
| 19:33–20:15, 16 | Alan; Denise | Read-only review precedes payment; a timed seat reservation message is shown. Denise raises multi-course/campus expectations. No exact approved hold duration is established here. |
| 20:15–23:46, 16–19 | Denise; Alan; Francisco; Rachel; Anuraag | Alan describes one class/campus per registration. Denise had expected a shopping cart spanning campuses. Others discuss separate campus payment routes. Francisco recommends leaving broader implementation open, without a public commitment either way. Rachel raises campus-specific carts. |
| 23:46–25:08, 19–20 | Denise; Alan | Denise asks about two courses at one campus and gives her limited-seat example. Alan says this was not understood as the ask, but agrees it can be explored. Treat as an open question, not a rejected user need. |
| 25:32–27:30, 20–21 | Alan; Denise | Payment mockup shows card/bank options and an undefined “other” category. Alan describes passing payment details to campus gateways without storing them in NCSIM. This is proposed behavior, not verified security. Denise asks to review copy and remove unexplained NCSIM wording. The group stresses the early mockup status. |
| 27:30–28:55, 21–22 | Alan; Denise | Confirmation replaces SIS jargon with enrollment/reference IDs, receipt download and email. Denise likes the clear reference ID. |
| 28:55–31:59, 22–24 | Alan; Denise; Anuraag; Francisco | General inquiry supports people not signed in; course-specific inquiry uses existing context. Denise worries an invitation to create accounts just to track inquiries conflicts with license expectations. Anuraag proposes shortening demo copy to connecting people with the right person. Broader account-policy discussion is parked. |
| 32:18–33:38, 24–26 | Alan; group | Course inquiry pre-fills course/profile, captures question, preferred time/method and outreach preference. Discussion supports general wording rather than naming Marketing Cloud; a related data element is mentioned. Alan describes CAPTCHA. Next day's changes must be read before treating this as final. |
| 33:38–36:55, 26–28 | Alan; Denise; Francisco | Inquiry confirmation has reference, routing and status, with dashboard tracking. Denise says PRI was unfamiliar and questions it on public screens. Francisco suggests “My inquiries.” Alan acknowledges he had assumed PRI was standard. Agreement: use clearer wording in the demo. |
| 36:57–39:41, 28–29 | Alan; Denise | Dashboard reduced to courses, credentials, progress and support. Alan describes external-credential upload and validation. Denise spots remaining academic/meal-plan copy inconsistent with non-credit and asks for careful review. Upload is described, not demonstrated in this transcript or established as accepted scope. |
| 39:44–40:08, 29–30 | Denise; Alan | Denise questions “link farm”; Alan explains his intended meaning and is open to alternatives. Another example of internal language entering a public-facing discussion. |
| 40:08–41:39, 30–31 | Alan; group | Support cases and inquiries route to campuses; knowledge, phone and new-case options are described. Reviewers praise revisions and responsiveness. Alan will share slides for offline comments and incorporate known feedback. |
| 41:40–43:15, 31–33 | Kathryn; Denise; Alan; Francisco; group | Footer visibility competes with readability in the presentation. Denise reports tiny text. Alan says the footer can be omitted to gain room; Francisco is comfortable leaving this minor issue for now. Closing thanks. This does not establish an actual website font defect. |
What remains unresolved
Current field rules, consent/explanation text, guest/account policy, cart grouping, payment route and seat-hold rules require later sources. The source sheet reviewed during the call, the exact deck and its comments are not embedded in this transcript. The May 22 follow-up records accepted demo edits. Supplied screen notes distinguish what is actually visible in the separate images.
Coverage: all 33 pages and timestamps to 43:15; no written PDF annotations. Embedded images are small transcript/speaker icons, not the presented slides. Layout and icon role checked visually. No recording is included in this source.
Related topics: cross-source findings.