consequential-actions
Separate Approve, Reject, and Request Changes
Specify approval outcomes by consequence, reason rule, resulting state, and next owner instead of relying on button order.
Updated 2026-08-01
Publication archive
Articles
Technology-neutral interface patterns, state maps, and acceptance checks for small operational tools.
consequential-actions
Show Bulk-Action Scope Before Changing Many Records
Make selected, visible, filtered, eligible, skipped, and failed records explicit before and after a bulk action.
Updated 2026-08-01
consequential-actions
Should a Destructive Action Use Confirmation or Undo?
Choose confirmation, review, delay, or undo from the actual consequence and recovery contract—not from a universal delete-dialog rule.
Updated 2026-08-01
interface-acceptance
Show an Expired Approval Request Clearly
Specify pending, expiring, expired, rejected, withdrawn, and re-requested approval states for a time-bounded operational decision.
Updated 2026-08-12
consequential-actions
Show Filtered-Data Export Scope Before Creating a File
Review row scope, active filters, field scope, freshness, exclusions, delivery, and server authorization before creating an export.
Updated 2026-08-01
interface-acceptance
How Should an Inline Edit Show a Version Conflict?
Preserve the operator's draft, expose the newer record version, and offer compare, copy, reload, or reviewed retry without silent overwrite.
Updated 2026-08-02
state-visibility
How Should an Interface Show a Long-Running Operation?
Specify queued, running, cancel-requested, completed, failed, and unknown job states without letting a spinner or closed request imply completion.
Updated 2026-08-02
interface-acceptance
Specify Operational Form Error States
Separate field, cross-field, service, permission, conflict, and success states so an operational form preserves valid input and exposes a safe correction path.
Updated 2026-08-11
state-visibility
How Should a List Show Empty, No Results, and Unavailable?
Specify not-loaded, ready, truly empty, no-match, and unavailable list states with distinct evidence, messages, and recovery actions.
Updated 2026-08-02
consequential-actions
How Should a Bulk Action Report Partial Success?
Report applied, skipped, failed, and unknown records separately with a durable result ledger and narrow retry eligibility.
Updated 2026-08-02
consequential-actions
Protect Unsaved Edits Without Pretending They Are Saved
Distinguish browser-memory edits, recoverable drafts, saving, durable success, and save failure before adding a leave warning.
Updated 2026-08-01
consequential-actions
Show a Changed Precondition Before a Consequential Action
Explain a changed required condition in text, preserve context, and show a policy-owned recovery path before a consequential action proceeds.
Updated 2026-08-17
state-visibility
What Should a Queue Show After Refresh Fails?
Keep stale operational rows useful without presenting them as current by showing timestamps, refresh failure, and action policy together.
Updated 2026-08-02