My interpretation of bridget's fixes
This commit is contained in:
parent
0c412dfea7
commit
56d05a34b5
1 changed files with 8 additions and 3 deletions
|
@ -1,10 +1,15 @@
|
|||
# Iterative UX: Find It Cambridge Case Study
|
||||
|
||||
Find It Cambridge is an online resource to help families easily find activities, services, and resources in the city of Cambridge, Massachusetts.
|
||||
A handful of visionary people in the city of Cambridge, Massachusetts wanted an online resource to help families easily find activities, services, and resources.
|
||||
|
||||
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.
|
||||
Find It Cambridge was informed and further inspired by extensive initial research done by Code for Boston and the City of Cambridge. As this was wrapping up, the city brought Agaric in, so we found ourselves in the incredibly fortunate situation of starting with this in-depth knowledge.
|
||||
|
||||
This session will start with highlights from this research conducted before anything was built. Next, we will take you through the iterations of design and mockup testing led by Todd Linkner, our design partner. We'll also cover the learning from the initial user testing with people in a library computer lab, which was particularly real-world conditions for this site! Finally, we will go into the iterative improvements continuing through today, regularly informed by feedback from people using the site in real conditions.
|
||||
|
||||
We will also discuss the challenge of balancing client feedback with 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.
|
||||
|
||||
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. This session will also present frankly what could have been done better, and what could still be done better.
|
||||
|
||||
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
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue