The project was delivered through a structured UX process that combined stakeholder collaboration, evidence-based design decisions, and iterative testing. The final direction improved wayfinding, content comprehension, and task completion confidence across the auction workflow.
How might we design a spectrum auction experience that helps users find critical information faster, complete tasks with fewer errors, and feel confident at every step of the process?
Explore the HTML prototype used for usability testing and stakeholder reviews.
View interactive prototypeWe started by interviewing internal stakeholders and reviewing 30+ legacy documents to map current user journeys and identify friction points in the spectrum auction experience. This phase clarified key pain points for both public users and internal teams, and defined the project goals, constraints, and success metrics.
Based on research insights, I reorganized navigation and page flow to make high-priority tasks easier to find and complete. I simplified labels, reduced content density, and introduced a clearer step-by-step structure so users could understand eligibility, timelines, and submission requirements with less effort.
I designed 50+ Figma screens and built 4 HTML prototype versions to test layout, interaction patterns, and content hierarchy. Each iteration was refined using stakeholder feedback and observed user behavior, allowing the team to quickly validate decisions before implementation.
I co-led usability testing with 20 participants and translated findings into targeted improvements for navigation, readability, and task completion. Accessibility checks were built into every round, including keyboard flow, screen reader behavior, and contrast verification, to ensure final outputs aligned with WCAG 2.2 AA standards.
Proposed direction from testing showed promising early indicators: users completed primary navigation tasks faster, reported lower confusion around eligibility steps, and gave stronger confidence ratings for understanding next actions. Internal stakeholders also reported that the revised structure better supported policy communication and reduced repetitive clarification requests.
The discovery phase surfaced five consistent pain points:
Stakeholder interviews, legacy document review, and user journey mapping were used to identify friction points, align priorities, and define measurable UX goals before design work started.
I used Figma for wireframes and high-fidelity screens, built HTML/CSS prototypes for realistic interaction checks, and ran usability/accessibility validation (including NVDA) to ensure decisions were evidence-based.
Figma, GitHub, Userlytics, Miro, HTML/CSS prototypes, NVDA, WCAG 2.2 AA checklists, and collaborative feedback sessions with stakeholders.
This project strengthened my ability to design in policy-heavy environments where clarity and trust are as important as visual design quality. If I were continuing this work, I would expand mobile-first testing earlier, run another accessibility audit with assistive technology users, and add a metrics dashboard to monitor task completion and drop-off trends after launch.