Ultra PatternsAI interface patterns with receiptsULTRA project

Pattern 16 · Chat or assistant · Interaction pattern

View

Your words first, then feedback

Seen in a case Built for a real case and observed with its users, or built for a case whose user test is still to come. No controlled comparison yet.

Practice view. What to build, the words on screen and how to measure it. Switch to Research for why it should work, the framework properties and the references.Research view. The research side is shown below the card: why it should work, the properties it targets and the references. Switch to Practice to hide it.

A practice mode shows a situation, the person writes a response, and the assistant reviews it against a few named criteria (warm, concrete, checks safety) with one strength and one improvement. The assistant never replaces the person's text.

WhyA tool that writes the reply leaves nothing to practise. Feedback on the person's own words keeps them the author and gives them something to work on. Whether it builds skill is untested here; the Goose sessions show only that participants valued the feedback panel. Goose's steering group asked for that feedback to use the building blocks of connecting communication.
WhenTraining and coaching, onboarding of new staff, communication skills, customer-facing writing.
Not whenTime-critical tasks where the person just needs a good draft. Then use a suggestion pattern instead.

The user stays in chargeThe system adapts to the personCase: Goose conversation guide

Done right, done wrong

Schematic screens, not real products. Click a screen to enlarge it.
Right. The person writes the reply; the assistant reviews it against named criteria and suggests one improvement.
Wrong. The assistant writes the reply for the person; nothing is practised.

In practice

Goose’s simulation mode presents a message from a friend, asks the person to write their reply, and then shows feedback in a separate panel: what works in the reply, and one thing to add, such as asking whether the friend feels safe. The steering group’s wish was that this feedback speaks the language of connecting communication too, so the practice teaches the method and not only manners.

One finding to design around: the role play let people swap roles, and that confused them. Keep the roles fixed in a practice turn. The person always writes as themselves, the assistant always plays the other side and the reviewer, and the screen says which is which.

Words on screen

"Your reply is warm and supportive. You could ask explicitly whether she feels safe right now.""Try again""Continue the conversation"

Obligations to keep in mind (AI Act, GDPR)

  • The person's text stays the person's. Feedback edits nothing without consent. (O4, IUI 2026, Table 1)
  • Say what the feedback is based on, so it is a review against criteria and not a verdict from nowhere. (O1, IUI 2026, Table 1)

Design considerations, not legal advice or a conformity assessment. What O1 to O5 mean.

Build it

Illustrative signatures, not a published library: the names below are suggestions to adapt to your stack. Thresholds are examples to tune on your own data.

States: scenario, writing, feedback, retry

Component: <PracticeTurn scenario={s} criteria={[warm, concrete, safety]} onSubmit={fn} />

Prompt snippet: Review the person's reply against: warm, concrete, checks safety. Give one strength and one improvement. Do not rewrite the reply.

Output schema: { "strength": "string", "improvement": "string", "criteria_met": ["string"] }

Measure it

Users are sure of their decision · 2 minUsers feel in control · 8 minThey want to keep using it · 3 minPlan your testTen minutes per participant is the usual budget: pick the two or three cards that fit.

Same idea, other names

Google PAIR: Feedback + ControlMicrosoft HAX: G9 Support efficient correction

All the libraries we build on

Applied by: nobody yet · Replicated by: nobody yet · Used this pattern? Tell us and get listed

Research side · why it should work

Why it should work

The mechanism, notes and references for this card are written together with the science editor at KU Leuven Augment. Until then this side lists the properties the pattern targets and the contexts in which it was seen.

Properties targeted

Controllability · Confidence · Axes: type: feedback, format: text, interaction: after user input · Vocabulary bridge

Across contexts

ContextUsersStateResult
Goose conversation guide, v4adults, mobileSeen in a casefeedback panel valued; the role-switch in the role play confused participants
Your contextBring your case

Editors

Practice: Rutger De Wilde (Odisee UX Lab) · Science: to be assigned by KU Leuven Augment · card v1.0 · 2026-09-03