Ultra PatternsAI interface patterns with receiptsULTRA project

Pattern 17 · Dashboard with AI insights · Interaction pattern

View

Board first, guided brief on request

Tested (pilot) · 7 participants The same comparison with sixteen or fewer participants. Indicative, too small to test a hypothesis.

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.

The landing view is a board with a few columns the person understands (needs action, needs review, needs follow-up), every item with its urgency and its due date in words. The AI's guided brief, which opens one task at a time in the AI's order with a summary and proposed actions, is a mode the person starts from a task, not the default screen.

WhyA board lets people scan first and decide for themselves; a brief makes them read. In the CNEXT test all seven counted their four tasks on the board and one of six managed it on the brief (six answers recorded), where the gaze jumped across the page without settling. Five of seven preferred the board. The two who preferred the brief liked that the urgent task was already open, which the on-request mode keeps.
WhenWork queues where people know their own priorities: e-mail triage, tickets, review queues, any inbox with more than a handful of items.
Not whenSingle-task flows, or first-time users who need to be led. And do not bury the brief: the two juniors who liked it should find it in one click.

The user stays in chargeThe system shows how it worksCase: CNEXT Mail2Flow (company approval pending)

Done right, done wrong

Schematic screens, not real products. Click a screen to enlarge it.
Right. A board the person scans and orders; the AI's guided brief opens per task, on request.
Wrong. The AI's brief is the landing page: one task already open, two proposed actions side by side, the rest hidden below.

The receipt

CaseE-mail triage for accountants, CNEXT Mail2Flow (Kairos prototype)
ComparedTask board vs. Guided brief · the same seven people used both views, in counterbalanced order (four saw the brief first, three the board)
Participants7 accountants at one Belgian accountancy firm, three juniors and four seniors, none had seen the tool
Main resultPreferred view 5 of 7 the board (stated preference)
Read asAn overview at a glance, their own choice of what to do first, less effort to read the layout. The two who chose the brief were juniors who valued that the urgent task was already open.
SecondaryCounted their four tasks correctly while exploring: 7 of 7 on the board, 1 of 6 on the brief (six answers recorded; four thought they had two)
SecondaryIn the six-second look, the board's columns and count were recalled; on the brief the gaze jumped across the page without settling
Methodsmoderated think-aloud · eye tracking with a six-second first look · six task scenarios · post-interview
Per groupjuniors (3): 1 preferred the board, 2 the brief · seniors (4): all 4 preferred the board
HonestlySeven people from one firm, a prototype with sample data, and the two views differed in more than who orders the work: the brief also opened the top task with two proposed actions side by side. Preference is self-report. Indicative. Three measures point the same way, which is why we print it; the size means nothing yet.
SourceAbdul Khalil (2026), Mail2Flow usability report, Odisee UX Lab, internal · case page opens after company approval · study run 2026-07 · ULTRA case

A receipt is the result of one test, printed on the card: the case, what was compared, how many people took part, the main result, the methods, and what we do not know. The plan written before the analysis is the study card. How a pattern earns its label.

In practice

Mail2Flow’s prototype offered two views of the same morning. The task board is a kanban with three columns, needs action, needs review and needs follow-up, plus filters; the accountant picks what to open. The guided brief is the AI’s answer to the same inbox: the most urgent task already open with a summary, two proposed actions and a chat assistant, and the other tasks listed below it. Everyone saw both, in counterbalanced order.

The board won on every measure the test could take. In the six-second look people recalled its columns and its count; the brief was too much text to parse. While exploring, all seven counted their four tasks on the board; on the brief only one of the six recorded answers was right, and four people thought they had two, because the open task read as an e-mail and the rows below read as subtasks. Five of seven preferred the board, and their reasons came in the same words: overview, my own choice, less effort.

Two people preferred the brief, both juniors, because the urgent task was already open and ready to act on. That is the part worth keeping. The report’s path, and this pattern, is a combination: the board as the landing view, the brief as a focus mode that opens from a task. What a bigger test should separate is the ordering from the rest, because the brief in this test also carried the two side-by-side proposals that confused people on their own (see One proposed action, one named button).

Words on screen

"Good morning. 4 items on your desk: 2 need action, 1 needs review, 1 needs follow-up.""Guide me through this""Due Friday"

Obligations to keep in mind (AI Act, GDPR)

  • The order of work is the person's decision; the AI's order is an offer, not the screen. (O4, IUI 2026, Table 1)
  • Say what the AI did to the list: which items it flagged as urgent, and why. (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: board, filtered, brief-open, brief-done

Component: <TaskBoard columns={[action, review, followUp]} onGuide={(task) => openBrief(task)} />

Prompt snippet: For each item return one column (action, review, follow_up), an urgency with the sentence that justifies it, and a due date. Do not reorder the list.

Output schema: { "column": "action | review | follow_up", "urgency": "high | medium | low", "reason": "string", "due": "date" }

Measure it

Users feel in control · 8 minMental effort · 5 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

Microsoft HAX: G17 Provide global controlsGoogle PAIR: Feedback + Control

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 · framework v0.2

Why it should work

Two mechanisms point the same way. Cognitive load: a board exposes structure (columns, counts, tags) that a limited working memory can take in at a glance, while a brief presents prose that has to be read; the six-second recall and the task counts in the CNEXT test are what that difference looks like. Control: when the system orders the work, the person loses the decision of what to do first; when the system only labels and the person orders, the automation sits at the information-analysis level rather than the decision level, which keeps reliance easier to calibrate.

Properties targeted

Controllability · Cognitive load · Satisfaction · Axes: scope: global, type: ordering, format: board, interaction: user-initiated · Vocabulary bridge

Notes

How to measure: controllability with the feeling-in-control items; cognitive load with the mental-effort scale after a fixed set of tasks in each view, plus the number of tasks correctly identified within a time limit; satisfaction and intention to use after both views. Counterbalance the order and, in the next round, keep everything but the ordering constant, so the effect of who orders the work is separated from the layout of the open task.

Relations

  • Interactive systems call for controllability as a property (Donoso-Guzmán et al. 2025, Figure 14); the possibility of interaction increases trust, and an explanation with low cognitive load is easier to understand (Donoso-Guzmán et al. 2023, Table 2).
  • Levels of automation: sorting and labelling incoming items automate information acquisition and analysis; proposing what to do with a task is decision selection (Parasuraman, Sheridan and Wickens 2000). The brief did both, the board only the first.
  • Learned trust grows with experience of a reliable system (Hoff and Bashir 2015), which is the argument for offering the AI's order as a mode people can adopt later.

Across contexts

ContextUsersStateResult
CNEXT Mail2Flow, Kairos prototypeaccountants, desktopTested (pilot)5 of 7 preferred the board; 7 of 7 counted their tasks on the board, 1 of 6 on the brief
Your contextBring your case

References

  1. Sweller 1988, Cognitive load during problem solving: effects on learning, Cognitive Science 12(2). https://doi.org/10.1207/s15516709cog1202_4
  2. Parasuraman, Sheridan and Wickens 2000, A model for types and levels of human interaction with automation, IEEE Transactions on Systems, Man, and Cybernetics, Part A 30(3). https://doi.org/10.1109/3468.844354
  3. Hoff and Bashir 2015, Trust in automation: integrating empirical evidence on factors that influence trust, Human Factors 57(3). https://doi.org/10.1177/0018720814547570
  4. Amershi et al. 2019, Guidelines for Human-AI Interaction, CHI, guideline 17. https://doi.org/10.1145/3290605.3300233
  5. Donoso-Guzmán et al. 2025, A systematic review of user-centred evaluation of explainable AI in healthcare. arXiv 2506.13904
  6. Donoso-Guzmán, Ooge, Parra and Verbert 2023, Towards a comprehensive human-centred evaluation framework for explainable AI. arXiv 2308.06274

Editors

Practice: Abasin Abdul Khalil (Odisee UX Lab) · Science: to be assigned by KU Leuven Augment · card v1.0 · 2026-09-08