Iterative UX: Find It Cambridge Case Study
summary
Find It Cambridge starts from 1,250 parent survey responses and 220 provider interviews, builds a structured-data site via a Jekyll-powered living wireframe and then ports refined HTML/CSS into a Drupal backend with Contentful/GatherContent experiments, Google Forms for ingestion, and trash/killfile recovery for deleted nodes. Iterations fix automatic-translation failures, remove a curated collections feature when maintainability fails, adjust neighborhood mapping and search (IE11 in library lab tests surfaces bugs), and hack results (water parks) to improve relevance.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:29Find It Cambridge
- 4:27Research
- 8:02Iterate on what someone else has built.
- 11:35Iterate before you build.
- 27:45Meet expectations.
- 28:24Go where your users are.
- 28:40Internet Explorer 11
- 29:47Performance is part of UX.
- 30:09Keep user testing an integral part of the process.
- 30:43Results relevance
related talks
42mFast UX Feedback for Your Drupal Project
49mEmploying UX Research Methods To Create User-Informed Text
59mFrom Feedback to Finish: How to Leverage User Focus Groups for Website Design
36mRefreshing the John Carter Brown Library’s Web Presence for Non-Academic Audiences
17mThe Uxers
32mEmbracing usability and accessibility: a Pace case study
33mA Scrappy UXer's Tale of Effective Low-Tech, Low-Prep, Quick Turnaround UX Research
47mExperience Maps—Empowering Designers in Agile Teams to Navigate and Address UX Debt