Find the signal
Audit high-volume page sets and user-facing flows for accessibility, usability, structural, content, and release-readiness issues. Separate one-off defects from recurring patterns that need a system-level response.
Selected work01 02 03 01 02 03 04
Case study · Education platforms
College Board — clarity at enterprise scale
Helping large education platforms turn complex requirements into consistent, accessible, and release-ready digital experiences.
Thousandsof pages included in large-scale audits
WCAGused as an experience and release lens
Reusablepatterns built for consistency at scale
01 · Context
The problem worth solving
College Board's digital ecosystem serves students, educators, and administrators across high-stakes moments. The experience has to remain clear and dependable even as many teams, content types, and release cycles intersect.
My role sits in that intersection: identifying where content, structure, interface behavior, accessibility, and publishing operations create friction—and helping cross-functional teams turn those findings into practical improvements.
The design questionHow might we reduce inconsistency and improve usability across an enterprise ecosystem without slowing the teams responsible for shipping it?
02 · The work
My contribution
Shape the experience
Translate business requirements and usability findings into clearer page structures, interface content, modular publishing patterns, and recommendations teams can act on.
Validate the release
Test responsive interfaces, components, content states, and accessibility behavior across environments. Document defects clearly and partner with teams through validation.
What I owned or directly supported
- Large-scale content and experience audits
- Interface copy and page-structure recommendations
- Reusable content models and publishing patterns
- WCAG-informed accessibility review
- Responsive QA, defect documentation, and release validation
- Cross-functional alignment across UX, product, engineering, and content
03 · Outcome
Outcomes
Surfaced experience and content-quality issues at a scale that made prioritization easier for partner teams.
Helped strengthen consistency through reusable patterns and clearer implementation guidance.
Caught interface, content, and accessibility problems before production through structured QA and validation.
Created a more useful bridge between user needs, content decisions, technical constraints, and release operations.
Representative public examples
Representative public work · CLEP examsRepresentative public work · Question of the DaySome details are intentionally generalized to respect client, partner, and project confidentiality. Public links represent the broader digital ecosystem and are not intended to claim sole authorship of every element shown. Live websites may have changed since my work.