transit system redesign

redesigned the staff intranet and helped coordinate requirements for a major systems upgrade at a municipal transit agency.

the intranet redesign

the existing intranet was outdated and difficult to navigate—information scattered everywhere, unclickable elements, inconsistent updates. basically a website with nothing useful on it.

redesigned the information architecture to make it actually functional for staff. organized content by workflows instead of organizational structure. the biggest impact was making onboarding easier for new employees who needed to find information quickly.

requirements coordination

helped manage 500+ business requirements across multiple departments for the systems upgrade. our approach was systematic but not revolutionary: excel spreadsheets, categorized decks, lots of workshops with metrolinx and ttc to group and close out requirements.

my role was mostly helping my coworker push for alignment and get unstuck when the client kept going in circles. having a second person focused on coordination helped accelerate delivery by about 30%—not through any special framework, just by maintaining momentum and preventing endless loops.

we spent the most time on wheel trans (paratransit identification cards), though even that involved significant back-and-forth.

what i learned

requirements management is as much about facilitating difficult conversations as it is about documentation. success meant building trust across departments and keeping people aligned when everyone had competing priorities.

enterprise systems work often feels less glamorous than product design, but it matters. making daily workflows slightly less frustrating for frontline staff who serve thousands of transit riders—that's real impact, even if it's not revolutionary.