The Project
Overview
The Central Arizona Project (CAP) is a 336-mile canal system that contributes to the quality of life and sustainability of the state's water supply and economy.
Algae commonly grow in the canal, causing myriad issues for treatment plants and consumers alike. AZ-CATI, a biophysics research lab at ASU developed an algae tracking system using advanced probes along the canal. Unfortunately, the data is extremely complex and hard to decipher for anyone who is not a biophysicist.
I was hired to develop an interface that clearly communicated actionable insights to canal decision-makers about the bioactivity data being tracked in the canals.
https://www.cap-az.com/about/
Design Process
As the sole UX researcher and designer, I defined my own design process and scope. Other than being told I needed to “make an interface,” I received very little direction from the AZ-CATI team and was granted a significant amount of autonomy. This left me with the responsibility of defining the needs of the project clearly and planning out my execution.
Project Planning
Project Scope
The massive gap between the scientists’ understanding and that of the average user was apparent from day one. I felt that I was drinking from the firehose as the AZ-CATI team tried to explain all of the details about their algae tracking system. I determined it was critical to define the scope of the project before beginning any user research.
Project Proposal
I organized my scope into a formalized proposal. I presented this to the team and we determined the scope was too big. We narrowed down the deliverables into something that was achievable within the 4-month timeframe. This included removing the instructional material and focusing more attention on user research and prototype design.
User Research
User Interviews
Using my own personal connections as well as contacts from AZ-CATI, I conducted and recorded interviews with users in our target audience to gain a clearer understanding of their base knowledge of algae activity in water canals. I also wanted to understand how they were currently managing issues related to bioactivity in the canal system. These interviewees included residential farmers, water district executives, and water quality managers.
User Interview Report
I summarized my findings from the user interviews into a report. These findings were critical for my future design decisions.
Comparative Assessment
I reviewed the existing solution used by CAP to understand water quality and developed a report outlining opportunities to replicate and opportunities to improve upon the experience.
Hierarchical Task Analysis
I developed a hierarchical task analysis to better understand the actions and sub-actions that would be taken by those using the app.
Solution Design
Sample Dataset
Based on the data being tracked by the probes in the canal, I distilled relevant information into a proposed sample dataset. This dataset would serve as the underlying structure needed for the app. I designed it to be easily created by transforming existing data in Python Jupyter Notebook - the computing platform of choice for the AZ-CATI team.
The key metric of this dataset is my proposed “Algae Index”—a 0 to 5 scale indicating the severity of algae activity at any given tracking location in the canal system.
Wireframe & User Flow
After a few iterations with the team, I landed on a user flow that accommodated my usability recommendations as well as AZ-CATI’s information requirements.
UI Design
I designed a mockup to review with the team before moving forward with the interactive prototype.
Algae Tracker Logo
While working on the solution design, I took the liberty of designing a logo for the app. The “A” is designed to look like the cross-section of a canal tunnel.
Stakeholder Integration
Stakeholder Overview
Throughout the design process I worked with three groups of stakeholders:
End Users (Farmers, Canal Workers, Water District Employees, Residents)
Scientists
Policy Makers
End Users
I continually worked with farmers, canal workers, water district employees, and residents throughout the research and design process. From interviews, to solution ideation, to usability testing, I ensured their voice was always understood and included in my decision-making.
Scientists
I met weekly with the team over data gathering and analysis. As the ultimate owners of the project, they specific priorities for the app as well as final say in what information was shown in the app. I commonly found myself striking a balance between complexity and simplicity as I accommodated their requests with designs that communicated their data in actionable and simple terms.
Policy Makers
As a public resource, much of the way the canal operates is determined by public policy. Our team had a handful of occasions in which we met with policy makers who had a stake in canal health, using data to inform their decisions related to its operation. These meetings gave us opportunities to evangelize the work the team was doing. The designs played a critical role in converting complex information into clear insights.
Final Deliverables
Interactive Prototype
As one of my final deliverables, I created a component-based high-fidelity interactive prototype in Adobe XD. I chose to design it mobile-first to accommodate farmers and workers who are likely outside and away from a laptop and/or monitor.
Monitor Mockup
Toward the end of the project, we learned from CAP that another use case would include monitors mounted in office spaces to continually show the conditions of the canal. I reimagined the mobile view into a non-interactive view to meet the needs of this new requirement.
Developer Notes
As part of my deliverable, I included technical notes for the developers.
Final Design
The final result of this project is an app that is designed to be clear and valuable to any individual concerned with algae levels in the canal.