Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Take a real user problem and run a mini end-to-end UX process. Do lightweight RESEARCH (3-5 user interviews or a survey with non-leading questions), synthesize it into a persona and a journey map that surfaces pain points, define the core problem, then design a user FLOW and an interactive PROTOTYPE (Figma) for the key task. Test the prototype with at least 3 people (task-based, think-aloud) and document what you'd iterate. Show your thinking at each step, not just the final screens.
Non-leading questions; findings grounded in what users said/did; synthesized into an evidence-based persona + journey map (not invented).
A coherent user flow and an interactive prototype for the key task; states (empty/error/loading) considered.
Task-based, think-aloud sessions with real users; findings prioritized by severity; concrete iteration plan.
Each stage (research->define->design->test) shown with rationale; decisions traceable to evidence.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# Research-driven flow: from interviews to prototype ## Goal Take a real user problem and run a mini end-to-end UX process. Do lightweight RESEARCH (3-5 user interviews or a survey with non-leading questions), synthesize it into a persona and a journey map that surfaces pain points, define the core problem, then design a user FLOW and an interactive PROTOTYPE (Figma) for the key task. Test the prototype with at least 3 people (task-based, think-aloud) and document what you'd iterate. Show your thinking at each step, not just the final screens. ## Acceptance criteria - [ ] Research quality: Non-leading questions; findings grounded in what users said/did; synthesized into an evidence-based persona + journey map (not invented). - [ ] Flow & prototype: A coherent user flow and an interactive prototype for the key task; states (empty/error/loading) considered. - [ ] Usability testing: Task-based, think-aloud sessions with real users; findings prioritized by severity; concrete iteration plan. - [ ] Process narrative: Each stage (research->define->design->test) shown with rationale; decisions traceable to evidence. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.