Index
Interface texts influence data quality and the ability to retrieve a task. A UX writing review should correct ambiguities where they generate error, unnecessary contact or abandonment.
How to evaluate this decision
Start with the words that change a decision: confirm, publish, cancel, delete and approve. Check that each action describes its real consequence. In forms, explain format and condition before failure; in error messages, show what needs to be fixed. The review needs to be done in the flow, as an isolated sentence may seem clear and remain confusing with the available options.
Criteria for comparing proposals
- Vocabulary: use the same term for the same object and record differences that the operation considers important.
- Guidance: distinguish mandatory field, optional information and dependency on another step.
- Recovery: Explain what occurred, what was preserved, and what action is available.
A scenario to discuss with the supplier
Hypothetical example: the cancel button could mean exiting editing or definitively canceling an order. The interface should separate these actions and explain the effect on registrations and approvals.
What to validate upon delivery
Validate texts on real screens, including long data, server errors and screen readers. Check if support can guide the user with the same terminology. An approved phrase sheet outside the system is only part of the deliverable.
Prepare the conversation about the project
Take the journeys with the most questions, anonymized support tickets and business rules to Quantum9. The review may begin with a critical form and establish standards for the remainder of the product.
Prototyping and validation · Map the company's priority