UX Goal
The user experience should make a deep reflective process feel manageable. The student should always know where they are, why a question is being asked, and what will happen next.
Primary Flow
- Landing page
- Sample output preview
- Checkout or free snapshot entry
- Accountless or lightweight access
- Consent and boundary screen
- Intake form
- Guided interview
- Progress review
- Profile generation
- Student review and edit
- Export and delivery
- Feedback survey
- Optional upgrade or revision
Screen Map
| Screen | Purpose | Key Elements |
|---|
| Landing Page | Convert interest into start. | Headline, sample output, CTA, pricing, privacy note. |
| Consent Screen | Set boundaries. | Not therapy, private by default, editable output, deletion option. |
| Baseline Intake | Collect facts. | Education, work, activities, goals, constraints. |
| Interview Module | Collect qualitative evidence. | Question groups, progress indicator, save/resume. |
| Reflection Checkpoint | Reduce fatigue. | Summary of answered sections and option to continue. |
| Generation Screen | Set expectation. | Explains that profile is being built from evidence. |
| Review Screen | Let user inspect output. | Profile sections, edit controls, evidence labels. |
| Export Screen | Deliver artifact. | HTML, PDF-ready, Markdown/aboutme.md. |
| Feedback Screen | Measure value. | Recognition, usefulness, referral intent. |
UX Principles
- Do not make the student answer too many questions at once.
- Use progress indicators.
- Explain why each section matters.
- Allow skipping sensitive or unclear questions.
- Use plain language instead of assessment jargon.
- Show sample answers where helpful.
- Make the final artifact feel earned, not magically generated.
Fatigue Management
| Risk | Mitigation |
|---|
| Long interview abandonment | Break into modules and show progress. |
| Thin answers | Provide optional prompts and examples. |
| Overthinking | Tell students rough answers are acceptable. |
| Privacy hesitation | Make sensitive questions optional and explain data use. |
| Output distrust | Show evidence labels and editable sections. |
Wireframe Notes
The MVP does not need complex visual design. It needs trust, clarity, progress, and strong final output. The visual system should feel closer to a professional report builder than a quiz app.