The Feedback Workflow
What happens the moment a learner finishes a session: from a personalized congratulations, through a three-question pulse, into scored response paths, and finally the log every admin can act on.
Learner completes a session
The workflow fires on the completion event: the learner commits or finishes their mission. A pop-up appears first; they can return to their progress view right after.
Personalized recognition
Never a generic “nice job.” We have the data, so we use it: the congratulations names what they actually accomplished and where it puts them.
Three-question pulse
Short enough to finish in a minute or two. The goal is a trend line: confidence and capability climbing session over session.
- Q1. Do you feel more confident? (1–5)
- Q2. Do you feel more capable? (1–5)
- Q3. Why? (open text)
Route on the average score
The average of Q1 + Q2 lands the learner in one of five lanes. Each lane has its own response and its own audience.
“We’re thrilled!” → Ask: can we use this as a testimonial? If yes, route the quote onward.
“Great feedback, we appreciate it.” Thank them, log it, watch the trend.
“What can we do to help you get more out of this?” Offer a callback.
Concern flagged. Offer support and a direct contact before they disengage.
“Oh no.” Escalate immediately so it gets fixed: this goes to whoever built the content.
The reward-hack layer
Every stakeholder has an incentive: the learner, the content creators, the managers, the org. Lean on them: “You’re the first to finish today,” streak call-outs, or a nudge to a learner’s manager that they’ve cleared all their courses. Applies across the congratulation and response steps.
Log everything
The workflow only closes when the record is written. Two things get stored:
- What was collected: scores, open-text answer, learner + session IDs, testimonial consent.
- What happened: which path fired, who got notified, any follow-up task or channel post created.
Feedback Workflow, draft v1 · captured from the AIOLabz coaching session on September 17, 2026 · Try the clickable wireframe →