The problem
A college-application platform needs to help students and families navigate recommendations, admissions predictions, essays, a case library and community. Product requirements must make user needs and quality expectations explicit across that journey.
My role
My contribution
Led user-problem definition, research, requirements and product-quality criteria for the Web/iOS platform.
Team contribution
A teammate managed delivery. Research and requirements ownership are kept distinct from delivery ownership.
Research to decisions
Research the problem
Led research and user-problem definition across the college-application experience.
Define requirements
Translated findings into requirements for recommendations, predictions, essays, the case library and community.
Make quality testable
Turned quality goals into five measurable trust dimensions and pass/fail acceptance criteria. The complete private dimension definitions are not reproduced here.
Cover the journey
Built release QA coverage across 11 core journeys and sub-journeys.
Close the feedback loop
Triaged 17 feedback items through root-cause analysis, acceptance criteria and release batching. Benchmarked school predictions while separating consensus, hypotheses and claims pending validation.
Consensus
Keep supported agreement explicit.
Hypotheses
Label interpretations that still need evidence.
Pending validation
Keep unvalidated claims separate from established results.
What the results show
The supplied record supports responsibilities and scope. It does not include the complete private requirements document, product screenshots or an independently verified admissions outcome. No illustrative interface is presented as a real product screen.