Read the three-minute walkthrough
Imagine choosing a Tuesday appointment, making a typo in your email, and having to pick your appointment all over again. That is the problem in this fictional mobile booking flow from UX Design Coach. Watch the time field as we walk through it. By the end, you will have a finding an engineer can reproduce, a repair to try, and two ways to check that it works. Start at a mobile viewport of 390 pixels.
Use fictional details. Choose Tuesday at ten in the morning, Eastern time. Enter Alex followed by the at sign. The domain is missing. Capture the selected appointment and the incomplete email together.
Submit the form. The address shows an error. Look one field above it. The selected time is gone. The visitor must pick it again.
Save the before and after under the same evidence reference, E02. Include the starting state, the action, and what changed. Here is the finding. On this mobile walkthrough, submitting an incomplete email cleared the selected appointment. Continuing required a second selection.
Give that recovery problem high priority in this walkthrough. The repeated work interrupts the primary task. How often it happens for real visitors is still unknown. Give your AI editor a bounded job. Ask it to flag any claim in the finding that lacks an evidence reference.
Suppose the draft says, customers are abandoning booking. The walkthrough did not measure abandonment. Change the claim to the action you observed. If frequency would change the priority, record a research question. For example, after an email error, how often do visitors complete the booking?
Now describe the desired behavior. For an email format error, preserve the appointment and the other valid fields. Put the correction beside the email. In the example, Tuesday at ten stays selected. The visitor can see exactly what needs attention, correct only the address, and submit again.
There is an important exception. If another person takes that time during correction, explain that the slot is unavailable and offer an alternative. First, keep the slot available. Submit the incomplete address, fix only the email, and retry. Check that the confirmation contains the original date, time, and time zone.
Then repeat while making the slot unavailable before the retry. Check that the page explains what changed and allows a new selection. Choose an alternative and confirm it. The confirmation should match the new selection. Record each outcome separately so a passing first path cannot hide a broken second path.
Give the team the evidence, the impact you observed, the proposed change, and both acceptance checks. Name an owner and agree when someone will verify the fix. The developer can reproduce the issue, the designer can specify the exception, and the product lead can decide whether to measure how frequently it occurs. Try the free two-page sample on one booking or signup flow you have permission to review. The full UX kit adds the worked review, editable materials, and practice lab.
Record what you did, what the interface did, and the task you had to repeat. Attach the evidence and describe exactly how someone can check the repair.