Timeframe: June 2018 - Jan 2019
Role: Product Designer
Team: Developers (3), Manager, Product Owner
NYU uses tax free bond money to reimburse money spent on ongoing building maintenance and construction projects.
To avoid regulation violations, Treasury users currently work in a legacy system to manage bonds and generate reports and requests.
What does this legacy process look like?
Treasury’s legacy processes involve a ton of manual labor– querying, filtering, data transfer, math work (they maintain actual formula sheets!!!), and back and forth between applications– to successfully generate a single report or request.
1. To present complex data in a way that is (1) easy to understand and comprehend and (2) easier on the eyes so that users can focus on making decisions central to their workflow.
2. To minimize manual data entry for Treasury users.
3. To augment this solutions package with a front end design for an enhanced user experience.
Although most of my work is under NDA, I can walk through my thinking behind the external data import (EDI) feature.
Treasury users want to upload local data onto the portal so they can easily access and analyze them so they can use bond proceeds more effectively.
JTBD AND INITIAL EXPLORATIONS
Using the JTBD framework, I synthesized my findings into three use cases and sketched out the flows for each case.
Upon deployment, Treasury users will be able to move away from the legacy system and towards this enterprise system with increased capacity and navigability. As a result, they spend less time compiling data from different sources and more time analyzing those data to use bond proceeds as effectively as possible.
James Walsh for taking a chance on sophomore year me. Brian, Nedim, Lilith ++ for your dev chops and mini stroopwafels. Especially Nichole Latimer, my manager, and Grant Ng, co-designer-dev-hybrid, for having my back (and for the laughs).