Fellowship Status Report

Code for America is partnering with Salt Lake County to build technology solutions to improve services and strengthen the
relationship between the county and its citizens, with an aim to lower the rate at which citizens fail to appear (FTA) in court, for
supervision and treatment appointments in addition to lowering the recidivism rate. In order to accomplish these objectives we
pursue three workstreams - build, measure, learn - to insure we iterate quickly and that our decisions are based on data and user
focused.

Phase III - Prototyping (03/06/2016 to 05/02/2016)

Workstream
Build
agile
development

Goals during this phase

Understand and connect data sources to support the functionality

of an SMS reminder tool

Build an SMS (text-messaging) tool that notifies of upcoming court

hearings

Measure
data-driven
decisionmaking

Learn
user centered
design

Determine feasibility of measuring FTA

Programmatically measure FTA count and rate over time

Understand the justice system, how people move through it, and
their attitudes and behaviors towards it

Identify opportunities to design and build ways to make the

process more efficient and easier to successfully navigate

Week ending 04/29/2016

This report is our 11th report so far since beginning the project and marks the conclusion of the Initial
Prototyping phase of the project. In next weeks report, we will outline our plans for the subsequent
phase and how iterative development sprints with ClientComm will play a role in researching and
better understanding the client population and behavioral archetypes in a longitudinal manner. This
week was a nice capping off of the first portion of our Fellowship, including the Tuesday presentation
to service providers, Mayoral leadership, Salt Lake City police leadership and officers, Criminal Justice
Services and CJAC representatives, and many others. All told, 35 individuals showed up for the event.
Results of the event included the identification of 3-4 potential client-facing paths we could go down
that involve opening up the ClientComm interface (potentially) to service providers, as well.
Looking to next week and our next phase, we will - in that report - outline what Iteration - Part I will
entail. Broadly, we aim to make the next period focused specifically on tackling the 34+ issues that are
outstanding and requested by some of our top ClientComm users (case managers) as well as
evaluating the potential additional aspects of the tool that were identified at the Tuesday morning
event. The time frame for this first part of the iteration will be from 5/02/2016 - 6/17/2016. The final
week will give us the opportunity to pause, return to our hypothesis, and evaluate the effort thus far.
Workstre
am
Build

Measure

This weeks accomplishments

UX modifications to
message view for ClientComm

Debug on outstanding
Report Sites

Next weeks objectives

UX feedback review from

Case Managers

Build out enhanced

performance tool for supervisors
(also explore performance
visualization for case managers)

Setting up internal
prioritization tools for feature
development

Document SLCo Court

Data dump

Identify FTA calculation

opportunities

Learn

Gather and catalogue

event responses

Set up relationships with

service providers who were
willing to speak further from
event

Thanks as always,
Kuan and Ben, Code for America, Team Salt Lake County

Exploring user needs in a

checklist component of ClientComm

Exploring survey results

from event and report