Mission 1 First-Time User Lab Guide
📥 Lab input
- •
day5_signup_flow.md(screen flow spec)
💾 Lab output
- •
design-decision-log.md(first-time user feedback doc)
1. Story and lab background
Picture a small business owner in their 50s who can send messages and read news on a smartphone, but has hardly ever filled in a new mobile sign-up form or booked a time slot through a complicated process.
The dev team designed password rules and the like without much thought, but beginner customers get frustrated: they miss the username check button, struggle with small text, and lose everything they typed when an error happens.
In this mission, you'll learn to use Codex to write the reasons behind data normalization and architecture decisions from the technical design stage as a structured Design Decision Log, and safely manage the system's history and design reasons (Why).
2. Learning goals
- Accurately extract normalization and database structure decisions from meeting notes.
- Write down the decision item, background reason, alternatives reviewed, approver and chance of future change.
- Record the history of design decisions (Why) to prevent repeat meetings and mistakes by new team members.
🛠️ Follow-along lab guide
- Create the lab file: press the download button below and save
day5_signup_flow.mdin theautomation/folder. - Hand logging to Codex: send the **Codex request prompt** below in the Codex Client prompt box and build.
- Check the log: review whether the decision ID (DEC-003), background, alternatives reviewed (rejection reasons) and approver are structured correctly.
Download lab materials
Codex request prompt
Mission 01 Prompt
You are a self-employed person in your 50s who is a bit clumsy with smartphone apps. Looking at the sign-up and first screen UI spec in the provided day5_signup_flow.md, write from your own point of view what is most confusing and hard when signing up, with your emotional reactions and requests for improvement.
4. Example output
Codex documents the architectural conclusions and the trade-off reasons from the conversation like this.
• Task: sign up and book a first session on a phone.
• First reaction and feedback (Pain Point): "The text is too small, and I didn't notice I had to press 'Check username' first. When I got an error, everything I typed disappeared and I had to start again."
• Where they got stuck: password rules shown only after an error; a small 'Done' button at the top right that's hard to find
• Requested fixes: bigger text and buttons, rules shown before typing, keep entered data after an error
• Impact: high chance of quitting at sign-up without these fixes.