Skip to main content

Overview

Every UI lesson needs the normal path and the states a user can actually encounter: empty, loading, disabled, missing access, disconnected, failed, interrupted and completed. Explain why a control is unavailable and the next useful action. Include how to recover without repeating completed model changes or losing an unsaved copy.

In Ideatura

  1. Identify the affected screen and operation.
  2. Read its state or error.
  3. Check the corresponding prerequisites.
  4. Recover and inspect the actual result before retrying broadly.

Check the result

The user has a concrete next step for each documented state.