Skip to content
frhino edited this page Jan 12, 2019 · 17 revisions

Jump to Welcome page

Overview

Critical User and Customer Data

There is a genius in our ability to identify situations where people's lives can be improved by building new or combining existing technologies. Given the choice between making a small or large impact on the quality of life in our community, we will all choose the larger impact. Often the difference lies in how well we understand the problem. If we set out to engineer solutions based on untested assumptions or incomplete domain knowledge, we are gambling with our chances of making the biggest impact regardless of how much effort we make. The realm of UX Designers and Product Managers exists to assist software engineers with the user and customer data needed to validate problems and inform decisions among competing solution ideas. On many "Code for America" teams, volunteers with backgrounds in user research and customer development are missing, or the team might be so small that competing priorities makes sufficient due diligence impossible. This tool is designed to let all members of a project team-- from engineers to product managers to designers-- acquire exponentially more user research data than through conventional methods of surveys and interviews alone so they still stand a great chance to make a huge impact.

Why Re-invent the Pipeline?

Our assumption is that most brigade projects could benefit from the same tool with only minor if any modifications. Code for America brigade volunteers come with a variety of backgrounds and experience levels, but generally have a very limited exposure to the full spectrum of technologies that might be applied to any given problem. Most would love to know more about machine learning (ML), APIs, and pipeline workflows as these technologies are powerful, in-demand, and currently dominate tech headlines. The intersection of interest and usefulness creates a great opportunity to save a number of teams from having to replicate a tool that all can use, so a key objective of this project is to build a tool that generalizes well to the widest range of project research needs. Our goal is to create an easy to understand and usable library with clear documentation so that any team member can quickly pick it up and start doing user research.

Architecture

Envisioned as a pipeline of integrated components, we expect all research tasks will be able to use the exact same component for pulling data from Twitter (using their own API creds). Projects would choose additional components to add to the pipeline as needed to accomplish whatever task they're trying to accomplish.

Jump to Welcome page

Clone this wiki locally