01 / Customer task
Describe a task that can be observed
“Make the site easier” is a broad ambition. “Find a cage with the required dimensions and add the correct quantity to a quote” gives the review a defined beginning and ending. We identify what the person knows at the start and what information they need along the way.
The same approach applies inside a business. A staff member preparing a quote may need the selected products, customer message and relevant attachment in one record. Their task differs from the visitor’s product search.
02 / Catalogue example
Use the equipment catalogue as a concrete example
Material Handling Solutions’ catalogue includes nested categories, supplier controls and product pages with part numbers, dimensions, capacity and weight. Those elements provide different kinds of information: narrowing the range, confirming the item and checking its suitability.
A review can follow that sequence and note where information appears. For example, selecting a supplier should be checked against the products then shown, including the route back to the full range. Observing someone perform the task can reveal whether the labels and responses are understandable.
03 / Quote handover
Include the step after the visible action
Adding an item to a quote is only part of the task. The resulting request needs to preserve the relevant product identifiers and quantity. Refined IT’s implemented MHE CRM build includes a handover for those fields, connecting the selected equipment with the information used to prepare a response.
This distinction informs the review: inspect the customer-facing choice and the receiving record separately, then compare them. A success message alone does not demonstrate that the intended information arrived.
04 / Task testing
Turn observations into specific design changes
Each proposed change should identify the observed problem and the task it affects. A shorter category label, a visible specification section or a clearer quote confirmation are different responses to different issues. They should not be bundled under an unexplained claim that the experience is improved.
We can review a prototype or revised interface with representative tasks and record what happens. Where the project measures completion, time or errors, we establish a baseline and use equivalent conditions for the later comparison. That keeps the assessment tied to the task being improved.
05 / Your questions
UX Design questions
How do we choose the first task to review?
Start with a task that matters to the business and has evidence of difficulty, such as recurring support questions or incomplete requests. Its frequency, effect and available observations help decide whether it should take priority over a less consequential annoyance.
Do you need real customer details for the review?
A representative task can often use synthetic records with the same fields and choices. Keep the structure needed to test the journey while removing names, contact details and private messages that do not affect the question being examined.
07 / Request UX review
Choose one task that should be easier
Tell us who performs it, where they start and what a successful result looks like. We can define a focused review.