Use illustrations to support business explanations
Business illustrations should explain a relationship, sequence, or decision that customers need to understand. Choose their purpose first, provide the right text equivalent, and remove decoration that competes with the explanation.
Read MoreImprove perceived speed with honest progress feedback
Progress feedback should reduce uncertainty without inventing completion or hiding slow work. Distinguish accepted, queued, processing, and finished states, and choose indicators that reflect what the application can actually measure.
Read MoreDesign destructive actions with understandable consequences
Deletion and cancellation need more than a generic confirmation dialog. Explain the affected records, downstream consequences, recovery limits, and actual outcome so users can decide deliberately and recover when the product permits it.
Read MoreMake tables useful without relying on horizontal scrolling
A useful business table keeps identity, comparison, and action within reach. Choose a task-specific column set, preserve header relationships, and provide detail views instead of making every decision depend on horizontal scrolling.
Read MoreTest browser zoom before accepting a desktop layout
A desktop layout can fail when users enlarge the page. Test real browser zoom with complete tasks, then inspect reflow, fixed elements, dialogs, and controls before accepting the design.
Read MoreExplain configuration estimates without implying a final quote
Configuration tools can help customers explore options without pretending to issue a binding price. Make assumptions, exclusions, uncertainty, and the next scope discussion visible beside any indicative estimate.
Read MoreKeep mobile approvals usable on a small screen
Mobile approval needs enough evidence for a responsible decision without reproducing a desktop page. Prioritize the summary, reveal supporting detail, and make approval consequences clear before users commit on a small screen.
Read MoreBuild bilingual interfaces beyond translating labels
A bilingual product needs consistent business meaning, formatting, recovery messages, and language switching. Review complete English and Vietnamese workflows rather than approving translated labels in a spreadsheet alone.
Read MoreDesign empty loading and unavailable states deliberately
An empty result, an unfinished request, and an unavailable service need different explanations. Define these states before screen approval so users know whether to wait, change a filter, create a record, or seek help.
Read MoreMake error messages explain the next useful action
An error should tell users what happened, what remains safe, and what to do next. Separate correctable input, unavailable services, and uncertain outcomes before writing messages or adding a retry button.
Read More