Choose a task someone can finish

For a customer portal, that might be finding an unpaid invoice and checking when it’s due. Include the screens and information needed to finish that job. Other features can wait.

Watch where the work slows down

Give someone a realistic starting point and ask them to talk through what they would do. Watch what they look for, what they misread and where they leave the intended path. A hesitation can reveal as much as a failed task.

Take the findings into the build

Revise the labels, order or interaction and try the same task again. Keep a short record of what changed so the developer understands the reasoning when implementing the flow.