Interaction Lab Twelve experiments
Press. Filter. Move. See what happens.
- Data
- Local, fictional examples
- Input
- Pointer, touch or keyboard
Make system status legible
Step through the transition
Access review · Q2
Local sample · 3 groups ready
Review is ready to run.
Inspect every system state
Select a system state
Change the state directly. The demo uses local, fictional content—no network request is made.
Quarterly access review
3 records · last updated just now in this simulation.
- Finance · 14 membersReady
- Operations · 8 membersReady
- Research · 6 membersIn review
Problem / behavior / why
A real sequence should resolve clearly; an error should offer a way back.
- PROBLEM
- A wait with no explanation feels broken; a result with no next step feels final.
- INTERACTION DECISION
- Let the visitor inspect processing, choose an outcome, and use reset/retry paths without an artificial delay.
- WHY IT WORKS
- Status remains visible in context, and the visitor can inspect loading, empty, populated, error, and success deliberately.
Refine a dense list
4 of 4 fictional tasks · filter and sort stay in sync
Problem / behavior / why
Filters and sorting respond together, with a designed zero-result recovery.
- PROBLEM
- Dense work queues need fast narrowing, but combined filters can produce an opaque or dead-end result.
- INTERACTION DECISION
- Apply category and text filters together, make ordering reversible, and provide clear-filter recovery.
- WHY IT WORKS
- Immediate feedback lets a person understand the result set and recover from an empty one without losing their place.
Adjust without leaving
Review access scope
Open the side panel to change a local preview setting.
Problem / behavior / why
Keep the task in context, make the overlay dismissible, and return focus.
- PROBLEM
- A settings detour can interrupt the task, and a modal that traps attention without clear exits erodes control.
- INTERACTION DECISION
- Use a side panel with explicit close, cancel, apply, outside-click, Escape, and focus return.
- WHY IT WORKS
- The user can change a sample scope while preserving the underlying context; all exits are reversible.
Show the whole workflow
Stage 02
Review access request
Owner confirms the request context.
Forward and back are both available.
Problem / behavior / why
Make progress and next steps explicit; allow a person to move both ways.
- PROBLEM
- Multi-stage enterprise work is hard to reason about when progress and prerequisites are hidden.
- INTERACTION DECISION
- Show completed, current, and upcoming stages; let the visitor step in either direction.
- WHY IT WORKS
- The animated connector reinforces sequence while explicit labels, step counts, and controls keep orientation intact.
Recommendation is not a decision
Policy summary
A fictional analysis state. No model or external service is called.
Start the demonstration to reveal a sample recommendation for access review.
Human decision
Keep the decision with a person
Processing produces a recommendation, not an automatic approval.
Problem / behavior / why
Expose simulated processing, then put the consequential choice in human hands.
- PROBLEM
- Automated-looking recommendations can imply certainty or silently trigger a consequential action.
- INTERACTION DECISION
- Mark processing as simulated, separate recommendation from approval, and make approval explicitly human-controlled.
- WHY IT WORKS
- Cause and effect stay visible. The visitor can approve, undo, retry, or reset without any external call.
Responsibility changes access
Problem / behavior / why
Switch roles to inspect the action boundary.
- PROBLEM
- A visible record can still contain actions outside a person's responsibility.
- INTERACTION DECISION
- Keep context visible, expose dependencies, and gate approval by role.
- WHY IT WORKS
- The boundary explains itself before anyone tries an unavailable action.
Put the urgent work first
- 01Resolve access exception
- 02Review supporting evidence
- 03Confirm the next owner
Drag a handle, or use the move buttons.
Problem / behavior / why
Drag a handle, or move a record with the keyboard.
- PROBLEM
- A queue changes priority as work changes.
- INTERACTION DECISION
- Make order tangible with drag handles and equivalent move controls.
- WHY IT WORKS
- Pointer, touch and keyboard users can perform the same task.
Same work, different space
Readiness at a glance.
Workspace layout · the same records and actions stay available.
Problem / behavior / why
Change the canvas. Keep the context.
- PROBLEM
- A smaller screen changes hierarchy, not the underlying task.
- INTERACTION DECISION
- Recompose navigation and metrics while preserving record content.
- WHY IT WORKS
- Spatial continuity makes the new layout understandable.
An exception still has a path
Step 1 of 4 · Submitted
Problem / behavior / why
Step through the standard and exception routes.
- PROBLEM
- A happy path alone leaves exceptions unexplained.
- INTERACTION DECISION
- Branch the connector and label every current and completed stage.
- WHY IT WORKS
- A visible recovery route keeps an exception from becoming a dead end.