Day 5 Task 03 Flow review

Task 03. Improve the User Journey

When the database physical schema or core business logic changes, analyze the affected API specs and UI screens and write a summary automatically.

Task 03 User Journey Improvement Lab Guide

📥 Lab input

  • • schema-change-request.md (change request)

💾 Lab output

  • • change-impact-report.md (change impact analysis)

1. Story and lab background

The share of users who open the app and make it to booking payment dropped sharply. Research showed they felt worn out going through 9 screen changes, clicks and terms checkboxes to book a session, and gave up midway.

Every extra screen, separate consent page and manual card entry step is another chance for users to leave. When the dev team quietly added an is_approved column to the Reservations table, the consent and payment screens weren't updated either, adding yet another confusing wait step. If the team doesn't map the full path and cut unnecessary steps, drop-off keeps rising.

In this lab, you'll learn a workflow: when the schema changes, use Codex to automatically analyze all the API endpoints and screen design changes affected in a chain, and write a report to share with teammates.

2. Learning goals

  • Trace the chain effects of a data structure change (Schema Change) on the system.
  • Identify and map the consent, payment and other screens that can be merged or shortened.
  • Independently produce a sharing report summarizing the changes and impact for teammates.

🛠️ Follow-along lab guide

  1. Create the lab file: press the download button below and save day5_signup_flow.md in the automation/ folder.
  2. Hand the analysis to Codex: send the **Codex request prompt** below in the Codex Client prompt box and build.
  3. Check the impact report: confirm the report properly covers the more detailed DB status (Wait Approve), API Response field changes and screen UI button and status panel requirements.

Download lab materials

Codex request prompt

Task 03 Prompt
Analyze the detailed booking scenario path in the provided day5_signup_flow.md and write a User Journey Report that minimizes the click steps and screen changes a user needs to complete a session booking.

4. Example output

Codex accurately traces the revision needs across all downstream modules based on the schema change.

Flow step AS-IS flow (9 steps) TO-BE improved flow (4 steps) Key improvements and why they matter
Booking schedule More detailed status codes in the Reservations table (add WAIT_APPROVE state) List ➔ merged detail/calendar tab ➔ choose time Show the expert detail and calendar on one screen to remove a screen change
Consent and payment Request booking ➔ go to privacy consent ➔ go to refund consent ➔ choose payment method ➔ enter card by hand High Update the related APIs in api-specification.md
Screen UI Add a disabled state to the 'Pay' button on the booking detail screen and add a 'waiting for expert approval' panel High Update the member booking screen plan & UI components