From 0c412dfea71c5453ff89f89034b494de834d20c1 Mon Sep 17 00:00:00 2001 From: Bridget Harrison Date: Tue, 5 Feb 2019 19:16:51 -0500 Subject: [PATCH] Bridget's updates to make it not sound like i'm bashing our client --- find-it/abstract.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/find-it/abstract.md b/find-it/abstract.md index a4dfe6c..b317361 100644 --- a/find-it/abstract.md +++ b/find-it/abstract.md @@ -1,11 +1,10 @@ # Iterative UX: Find It Cambridge Case Study -Find It Cambridge needed to be an online resource to help families easily find activities, services, and resources in Cambridge. +Find It Cambridge is an online resource to help families easily find activities, services, and resources in the city of Cambridge, Massachusetts. -We came in with the incredibly fortunate situation of tons of research being done by Code for Boston and the City of Cambridge. We will describes some of the highlights from the research before anything was built, through initial user testing with people in a library computer lab (particularly real-world conditions for this site), and to the iterative improvements continuing today. The philosophy throughout has been listen/watch, learn, and loop that back into development. The interesting parts, as so often, lie in the details. - -This session will also present frankly what could have been done better, and what could still be done better. A major challenge has been listening to the client too much and the people using the site not enough— a tension accentuated by the fact that the people relying on the site in this case are the citizenry! +Find It Cambridge was inspired by extensive initial research done by Code for Boston and the City of Cambridge. We will describe some of the highlights from the research conducted before anything was built, and then take you through iterations of product testing and refinement from initial user testing with people in a library computer lab (particularly real-world conditions for this site) to the iterative improvements continuing today [that are informed by feedback from real users]. The philosophy throughout has been listen, watch, learn, and then use the knowledge gained to develop and prioritize enhancements and new features. The most interesting parts, as so often, lie in the details. +In this session we will also discuss the challenges of balancing client versus user feedback and offer strategies for making sure user needs are prioritized, including how to be a user advocate no matter what your role in a project is. We will take you through some of the client-developer decision processes and present what we've learned and how we plan to continue building on what we've learned as we continue to build on this amazing citizen resource. ## Speaker credentials