Output: Adjusting Andamio/Edify Platform Based on Feedback
Criterion: refining the platform based on user input. Evidence required: platform feedback tracking report.
Sessions ran 7, 14 and 17 October 2026 with the first cohort. Six changes were made to our own side of the programme, items 1 to 3 from session 1 and 4 to 6 from session 2. Session 3's feedback was about the Andamio platform rather than our delivery and is tracked in Andamio platform enhancement requests.
| Observed | Changed | Verify | |
|---|---|---|---|
| 1 | The public course reference was linked only from under the module list, so learners arriving anywhere else could not reach it | Course docs link in the footer of every page, with acceptance criterion ISC-17 and an automated probe asserting it on three pages | Commit 2e99c29, deployed 8 October 2026, live on edifysystemsgroup.com. ISC-17 |
| 2 | Session 1 was not recorded, though the deck promised recordings, because the call ran on a personal account with recording started by hand | Sessions moved to a recurring Edify-side meeting with cloud recording and transcription set on the meeting itself. A written recap published for session 1 | Session 1 recap, 8 October 2026. Sessions 2 and 3 recorded without host setup; session 3 recording |
| 3 | Cohort members joined the Discord and did nothing: no welcome, no introduction prompt, and the channel sat in a public category | Cohort category restricted to the cohort role, pinned welcome, structured introduction prompt, announcements channel read-only | Discord server Edify Impact V2, #dev-accelerator. Restricted to cohort members, so attested |
| 4 | Two of fourteen learners joined session 2. The delivery partner, who recruited eleven of them, had sent no reminders and reported WhatsApp as his community's actual channel | Cohort coordination moved to WhatsApp under the delivery partner, who runs promotion and reminders. Discord kept as support and record channel. Newsletter before each call. Session 2 deferred and re-run at session 3 | Session 2 recap, session 3 recap. Mailing list tag deva_cohort_f11, fourteen members |
| 5 | Neither learner on session 2 had minted an access token a week after being told to. The blocker was holding ADA, not the instruction | ADA sent to any learner who supplies a receive address, so the platform fee is not funded up front | Access token cost and refund |
| 6 | The recorded minting walkthrough did not capture the wallet signing dialog, the step a first-timer stalls on | Walkthrough re-recorded with the signing screen and posted to the cohort channel | #dev-accelerator in the cohort Discord. Restricted to cohort members, so attested |
How feedback is collected and tracked
| In session | questions and objections raised live, captured in the session summary |
| Between sessions | WhatsApp, run by the delivery partner, with #dev-accelerator in the cohort Discord as the support and record channel |
| Before each session | cohort newsletter to the deva_cohort_f11 mailing list |
| From the material | each group reports on the modules it is assigned, so all nine are covered between the three groups |
| Written, once | cohort feedback form, issued 24 October 2026. Seven open questions, with a consent item setting whether an answer may be quoted. Nine of fourteen responded; findings in the cohort feedback report. Individual responses are not published |
Outstanding
- The groups' own reports on the modules they were assigned.
The cohort feedback report and the improvements and action plan are complete.