Jessica Danielson

         UX and Behavior Design.

Police Scheduler

dakota criminal justice network.

The Saint Paul Police Department (SPPD) is responsible for the covering traffic at Xcel Energy Center, CHS Field, as well as supporting over cities as part of overtime work. The current system for scheduling is paper-based, labor intensive with several redundancies and points for human error. 


My team in conjunction with developers from the Dakota Criminal Justice Network designed a web application to help automate parts of the overtime scheduling process.

clients.

 ​Dakota County Criminal Justice Network (CJN) is a group of public-sector developing an information integration network that always data to be shared quickly among law enforcement officers, attorneys, and judges to save time, money, and make communities safer.

 
Dakota CJN approach my team of UXers for help designing web app for overtime scheduling system for the SPPD
.

Typically 12-17 SPPD officer man different corners before, during and after major events in the city. For the Super Bowl, they will be sending 100 officers a day to Minneapolis
. They are worried about how they will deal with this 5 times increase, and that brought them to Dakota CJN. Seeing the complexity in creating a system that appropriately flows through this system send Dakota CJN to me.

approach.

My team in conjunction with developers from the Dakota Criminal Justice Network designed a web application to help automate parts of the overtime scheduling process.
We used contextual interviews, Affinity Mapping, Task Flow Analysis, Wireframing, Rapid Iterative Prototyping, Interactive Prototyping, User testing to create our final design.

problem.
CJN was looking to add an application to that would function not only for the SPPD but could be used by other law enforcement agency. It needed to meet the strict regulations of law enforcement like seniority. 

Police Overtime Scheduling AppThe Saint Paul Police Department (SPPD) is responsible for the covering traffic at Xcel Energy Center, CHS Field, as well as supporting over cities as part of overtime work. The current system for scheduling is paper-based, labor intensive with several redundancies and points for human error. 

discovery research.

 

CJN

 Our first meeting with Dakota CJN, my team became familiar with some of the technological challenges facing law enforcement todayWe got to take a look at their existing suite of applications.
 
We learned about the technological constraints in the secure police network, optimizing for using on Microsoft-based browsers and their current style guide. Dakota CJN gave us an overview of the paper process currently being used
.
 
Dakota CNJ wanted the new application to be used by multiple agencies, not just SPPD
. 

 

SPPD

We conducted a contextual interview at the SPPD with the two Inspectors in charge of scheduling. During this time we walked through the existing process focusing on the regulations, requirements, and considerations the Inspectors were keeping track of while completing the paper process. 

data analysis and synthesis.

After our meeting, we created an affinity diagram where we compared our observations from our interviews. We did several rounds of diagraming breaking out the data in a variety of ways. This gave us an in-depth understanding of the complexity of the requirements, considerations, and pain points of SPPD and Dakota CJN. 

 

 The affinity diagram naturally lead into a journey map of the current paper system. From there, it was easy to see where we could start adding automation, resulting from pain points, and begin shaping the digital system. This moved into a Task Flow Analysis where we mapped out tasks, workflows, interaction point between users and the system

 

rapid iterative prototype.

About mid-way through our synthesis, we began doing some low-fidelity wireframe. We saw the complexity of the information and interaction and realized it would take several iterations to get to the solution that was best for the user's needs and match with CJN goals. 

 

wireframing

As we wireframes, we would have critique sessions we worked as a team to identify design holes, fringe cases and consult with designers outside our team to ensure the design was intuitive. We would find points where more information was needed, or we began to deviate from the mental models of SPPD, and I would go back to the SPPD or CJN with more questions then go to synthesis and adjust our Task Flow Analysis to fit out new information better. 

 

interactive prototype

After several rounds of sketch wireframes, I created an atomic pattern library utilizing components of CJN existing style guide and sharing amount our team for the quicker creation of an interactive prototype. 

 

user testing.

We were able to complete a scenario-based moderated user test with one of the Inspectors in charge of scheduling. He was able to complete all 5 task with two small wrong turns that he was able to recover from and complete the tasks quickly. The wrong turns were related to signals. 

 

next step.

Development was scheduled to state in August or September.

 

Going forward, we would like to do additional testing with officers at SPPD and with other agencies to make the application more universal. 
 
 
Some challenges we faced during this project were:

  • The 3-week timeline.

  • Limited access to users CJN wanted to be the point of contact between our team and SPPD, so it often took a day or two to get answers to our questions. 

  • Lack of access to CJN application suite as several applications only ran on PC and our team only had access to Macs.