Task 01 User-View Screen Review Lab Guide
📥 Lab input
- •
day5_meeting_notes.md(meeting notes)
💾 Lab output
- •
erd-schema.md(data spec and ERD)
1. Story and lab background
The service screens were finished and the booking process designed and released, but users kept dropping off on the way from the dashboard to booking. The cause: the information hierarchy was laid out from the developer's or designer's view, so first-time customers had a very hard time finding the button they wanted.
In this lab, you give Codex the plan and experience a consistency check where it points out readability and button flow problems strictly from a 'beginner user's view'.
2. Learning goals
- See the information layout of a screen plan from every angle as a first-time user.
- Point out pain points that hurt usability, like poor calendar contrast or hidden prices.
- Use AI to work out layout recommendations that improve user experience (UX).
- Move beyond feature-centered thinking and build a user-centered design mindset.
🛠️ Follow-along lab guide
- Create the lab file: press the download button below and save
day5_meeting_notes.mdin theautomation/folder. - Hand the review to Codex: attach the file, send the **Codex request prompt** below in Codex Client and build.
- Check recommendations: check whether the report's fixes for time slot contrast errors and price display make sense.
Download lab materials
Codex request prompt
Task 01 Prompt
Based on the screen spec of the provided booking request form, review whether the information structure is clear from the view of a beginner who's new to the service, point out what hurts usability, and write an improvement report (UX Review Report).
4. Example output
Codex diagnoses the screen spec from many angles and builds a logical improvement report like below.
| Entity | Explanation | Main attributes | Relationships |
|---|---|---|---|
| Counselor profile area | Regular member who uses the consultation service | Rating and introduction are placed in the scroll area at the bottom of the screen | 1:N with Reservation |
| Time slot area | Partner expert who gives consultations | expert_id (PK), name, category | 1:N with Reservation |
| Payment area | Booking mapping between user and expert | The final price can't be seen until the payment pop-up opens | N:1 with User/Expert, 1:1 with Payment |
| Going back | Payment transaction info to confirm the booking | On error, the whole form resets, wearing users out | 1:1 with Reservation |
5. AI use points
- Usability detection: spots sections in the description where users will actually hit pain or confusion.
- Layout improvements: recommends wireframe structures you can apply right away, like fixing unclear contrast and merging fields.