When I came on the team, it was consistently underwater, with work planning largely being an exercise in largest fire, and a number of efforts underway to try and stem the bleeding.

As TLM, I largely rebuilt the practices and rituals of the cross-functional Design System teams into something that provided stability, value, and reasonable expectations, rather than constant fire drills.

• Made Cloud Design System a part of the larger Material Design org, and served as the primary voice for Cloud.
• Made targeted technical changes to operating model, renegotiating expectations with feature teams and horizontals.
• Advised, proposed, advocated for, and planned larger technical frontend strategy with Director-level leadership.
• Reprocessed our backlog, splitting it from an accumulating pile into a number of tracked queues and burndowns.
• Directly triaged issues, and provided Accessibility support to feature teams alongside a11y horizontals.

As part of the overall strategy of updating the Design System across the Console to the latest Google Material specifications, I proposed, advocated for, and then drove execution on an overhaul-level Design System migration.

Whereas previous attempts to update the Console depended on brute force solutions and/or manual migrations, this strategy enabled the console to be updated with minimal changes to feature team code, something previously thought impractical.

• Leading voice in Director-level conversations on need, capability, and options for next-steps.
• Created and presented decks, demos, and Technical Design Documents to various org audiences.
• Drove the larger effort, helping to plan technical needs from GraphQL infrastructure, app shell.
• Supported migrating feature teams as primary engineering point of contact.

Bandwidth had historically been utilizing their Java feature developers to code the UI for the dashboard utilizing GWT, but had decided they wanted a more modern frontend stack.

The project to accomplish this had been stalled for some time, as there was an insistence that the new application be incrementally delivered, while the GWT pages continued to run the page chrome and crucial services. I successfully advocated for a more practical approach that enabled a React-only experience, and unblocked the project as a result.

• Pulled back from-scratch design system strategy that wasn't aligned with team size, pivoted to a theme on an existing component library
• Drove product/director-level conversations and presentations on need, strategy
• Delivered a fully react dashboard overhaul in 8 months, after > 1 year of stalled progress.

As Technical Product Owner for the console frontend, and a manager of three important cross-functional teams (Frontend, identity/auth, and developer experience), I was able to plan, enable, and execute far-reaching strategic change to the product, including:

• Enabling bring-your-own single sign-on by overhauling our login experience and adding additional identity infrastructure.
• Audited identity/frontend intersection points, removing security risk through the new React interface.
• Pushed GraphQL microservices as an alternative to the dominant monolithic service design paradigm
• Began moving poorly documented XML apis to OpenAPI documented json endpoints, decreasing frontend bloat in the process.

ScoreShots Next was a revamp to our existing product that I largely designed and architected. It rebuilt the shaky backend of the product to use GraphQL microservices, as well as redesigning the brand into a consistent look and feel via a Design System.

• Canvas / React App, also delivered as PWA for mobile
• Hundreds of clients, including the USGA and Dallas Mavericks
• Appeared and gave talks at national collegiate trade shows
• Serverless GraphQL microservices, Prisma 1 ORM
• Material UI-driven design system, enabling consistent look
• Photoshop-style UI enabled advanced editing for power users

ScoreShots Video was a cloud rendering pipeleine that enabled web-based video editing from any device. By compiling and utilizing custom ffmpeg binaries in serverless environments, I was able to cheaply and effectively offer on-demand rendering and editing of video graphics, including ones driven by statistics and After Effects motion.

• ffmpeg Lambda rendering streamed files in and out of s3
• Enabled direct AE file hand-offs from Designers to Eng
• Added video overlay effects to image posts, expanding impact
• Fully mobile-compatible video editing flow
• Architected pipelines for PSD/After Effects ingestion