This article is written as a working review tool rather than a universal formula. Apply the parts that match the product, evidence and constraints in front of you.
Navigation and location
Can users tell which workspace, account, module or record they are in? Is the path back predictable? Complex SaaS needs location cues because the same entity can appear in several workflows.
Avoid using the sidebar as a storage drawer for every feature the product has accumulated.
Priority and density
Put high-frequency decisions and exceptions before secondary metrics. Dense interfaces can be efficient when hierarchy is strong; sparse interfaces can still be confusing when every card competes equally.
Review what the user needs to notice in the first few seconds.
Tables, filters and bulk work
Check column priority, sorting, active filters, zero results, row actions and bulk selection. Make sure the identifier remains understandable when horizontal space gets tight.
Operational tools need efficiency without turning every action into an unlabeled icon.
States and recovery
Review loading, empty, error, permission, stale data and destructive-action feedback. The dashboard should explain whether the user can recover and whether their previous work is safe.
These states usually matter more to trust than another chart animation.
Responsive behavior
At narrow widths, protect task priority rather than mechanically stacking every desktop block. Decide what becomes a drawer, what can hide and which actions must remain visible.
Test real content at 375, 768 and common desktop widths rather than relying on one ideal mobile frame.