UDT Insights
Practical perspectives on technology, engineering, and delivery.
User Experience
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 article
User Experience
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 article
User Experience
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 article
User Experience
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 article
User Experience
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 article
User Experience
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 article
User Experience
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 article
User Experience
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 article
User Experience
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 article