ZETA- Zero Emission Transit Analysis

Three questions to the project team

What was the particular challenge of the project from a UX point of view?
The biggest UX challenge was designing a tool for multiple internal stakeholders—data analysts, service planners, and capital teams—who each had different needs, workflows, and technical fluency. We needed to create a shared platform that was intuitive enough for daily operations yet robust enough to support complex simulation logic. Balancing clarity, collaboration, and data density was central to the UX process.

What was your personal highlight in the development process? Was there an aha!-moment, was there a low point?
A major highlight for our team came after testing the mid-fidelity prototype. When we observed different roles using the tool collaboratively and providing feedback that it reduced confusion and improved alignment, we realized the collaboration space truly added value.
The low point was early on when our linear user flow excluded key roles. This prompted a pivot to a shared workspace model—an “aha!” moment that significantly enhanced the product’s effectiveness.

Where do you see yourself and the project in the next five years?
We envision ZETA evolving into a flexible, cloud-based platform that can be adapted by transit agencies across the U.S. and beyond. It could standardize how agencies plan zero-emission transitions, replacing manual processes and costly consulting. As a team, we hope to continue scaling impact-driven tools for public services, combining research, design, and systems thinking to address complex infrastructure challenges.