I'm a UX designer who codes and works with data — which means I can prototype at real fidelity and back design decisions with data, not just intuition.
Placeholder — describe the noise/complexity problem journalists and fact-checkers faced before this tool existed.
Placeholder — clarify what you personally designed vs. what existed already (e.g. the underlying AI parser).
Placeholder — walk through at least one real decision point: an alternative you considered and why you didn't choose it.
Placeholder — what changed? Adoption, feedback, time saved, anything directional if exact numbers aren't available.
Placeholder — state the central-vs-local tension plainly, with the real scale (70,000+ volunteers, 34 microsites).
Placeholder — what made this hard? Resourcing, who maintains the sites, need for a lightweight system.
Placeholder — describe the actual system: what's centrally controlled, what's locally flexible, and the reasoning behind the split.
Placeholder — state current rollout status honestly. In-progress work is fine to show; just don't overstate it.
Placeholder — describe what students needed: a single place to find their class, lectures, and assignments.
Placeholder — explain the retro aesthetic as a deliberate choice, then the real structure underneath: class selector, assignment states, nav.
Placeholder — in development; update once live for your students.
Placeholder — the real problem: building an equitable syllabus was unstructured and isolating for instructors, with no shared framework.
Placeholder — you led research and designed the system architecture (guide, database, request service).
Placeholder — walk through how the guide, database, and research service were structured to meet different instructor needs.
I led research and initial design for this project; it has continued to evolve under the current team since I left.