UX workshop
Challenges from our projects
Some UX questions come up in almost every project: long forms, lists full of decisions, processes that take a while. Here they sit side by side, each with how it looks today and a better version. They turn into rules that our agent builds by, too.
- Dialog
- Field
- NumericInput
- DateInput
- SearchableSelect
- DropdownMenu
- Progress
- Collapsible
- Alert
- Sonner
- SidebarList
- ScrollRow
- Table
- Drawer
- 1
Context
Where the pattern appears and what the original brief was.
- 2
Current
How the agent builds it today, recreated with made-up data.
- 3
Rule
The system rule that makes the difference.
- 4
Target
The same task following the rules, built from the library.
Cycle 1
First cases and design round 1
Three cases from the customer portal and the controlling tool. The designer took them further in a first round; each page shows what we adopted and what we did not.
Long forms in dialogs
Creating and editing records with lots of fields ends up in a dialog. Buttons scroll out of view, sections are missing, and closing loses what you’ve entered.
Working through decisions
Suggestions, queries and findings the team has to decide on. Lots of cards with equally loud buttons, no order, no way back.
Long-running background tasks
AI checks, transcripts and reports take seconds to minutes. Today a spinner turns, and sometimes all you get at the end is “Server Error”.
Cycle 2
Page types that come back in every project
Object pages with tabs, data lists with filters, pages full of cards, and the mobile view. The current state is assembled from real pages; the target is our draft as the basis for the next design round.
Object pages with tabs
A project, a billing area, an asset: a heavy header of title, badges, buttons and figures at the top, then many tabs, and only then the content.
Data lists with filters
Invoices, tasks, times: figure tiles above loose filter fields, a table that silently ends at 100 entries, and checkboxes without a bulk action.
Pages full of cards
Times, leave, approvals, overtime: cards stacked on top of each other, each with its own header, filters and buttons. After the third block nobody knows which filter applies to what.
On the phone
The desktop page, only narrower: hero, figure cards and four rows of tabs before the content; tables scroll sideways, dialogs fill the screen.
Rulebook
13 draft rules
The rules live in docs/ux-regeln.md in the library’s repo. The agent reads them from there; this page is for looking them up. The rules are maintained in German.
- R1Meldungen verschieben keine Nachbarn
- R2Seitenspalten bleiben stehen
- R3Aktionen bleiben sichtbar
- R4Dialoge bleiben kurz und gegliedert
- R5Eine Hauptaktion pro Eintrag
- R6Entscheidungen zeigen Fortschritt und lassen sich zurücknehmen
- R7Lange Läufe zeigen Schritte statt Spinner
- R8Fehler sagen, was passiert ist und was man tun kann
- R9Nichts sendet sich selbst
- R10Objektseiten haben einen leichten Kopf
- R11Datenlisten tragen ihre Werkzeuge an der Tabelle
- R12Eine Seite beantwortet eine Frage
- R13Auf dem Handy eine App, keine geschrumpfte Website