Reflect after action
Reflection is not paperwork. It’s the part of the engagement where you turn what you just did into something you can carry into the next situation. Pondara is built around it because action without reflection doesn’t transfer.
Why reflection matters
You can repeat a scenario ten times and learn nothing if you don’t stop and notice what you did, why you did it, and what you’d do differently. Field experts who shaped these scenarios know that — the prompts you see were designed to surface the choices that mattered, not to tick a box.
What the AI does here
In reflection the AI sparring partner is reading the dialogue with you. It opens questions; it doesn’t assess. It might point at a moment you skipped past and ask what you noticed there. It does not tell you whether you were right.
Prompts you might see
- “When the customer raised their voice, what did you choose to do? Why?”
- “Was there a moment you nearly said something different? What stopped you?”
- “If you ran the same conversation tomorrow, what would change?”
- “Which part felt most automatic? Which felt the most effortful?”
The exact prompts vary by scenario and by the dimensions it exercised.
How to reflect well
- Be honest. “I froze” is more useful than “I followed the procedure.”
- Name what you noticed, not just what you did. The noticing is the evidence.
- Concrete beats general. “I missed that she said ‘usually’ before the complaint” is worth more than “I should listen better.”
- Short is fine. A few sentences per prompt is the right length.
When something goes wrong
- The prompts feel off. Answer however you want — the AI’s prompts aren’t binding, and answering “this question doesn’t fit what happened” is a legitimate reflection.
- The prompts won’t open. Refresh the engagement page. If they still don’t load, contact your trainer and they can render the verdict directly from the dialogue.