Skip to content

Case study · Leadership

From Legacy Dashboards to an AI-Powered Control Tower: Leading Design & Continuous Discovery for Arrive Pulse

Role
Interim Product Design Lead, City’s Experience
Timeline
August 2025 – Present
Team
Managed 3 Product Designers (hired and onboarded 1; coached 1 Senior Designer and 1 Designer). Partnered with VP/CPO product leadership, UX Research, Security and Engineering Architects.
Scope
Global municipal B2B platform, North America & Europe

The mandate

Moving from fragmented operator portals to one platform operators can trust

Operators worked across separate portals for policies, pay stations and regional dashboards. The goal was one global platform, Arrive Pulse.

It had to prove its commercial value (Now vs. Premium tiers) and support major municipal tenders, while I stepped up as player-coach.

  • North Star vision

    Hands-on

    Coded Pulse prototype, Moby AI reporting, peer benchmarking

  • Authentication & localization

    Hands-on

    Login UX with Security, US/EU formatting standards

  • Parking Policies

    Directed

    Self-service rate management, usability testing

  • Pay Stations (Project Phoenix)

    Directed

    US pay stations and monetization tiers; predictive maintenance

  • Occupancy

    Directed

    Heatmap and hexagon explorations; KPI period-over-period comparisons and exports

Outcome metrics

Defining what success means before shipping more features

Co-defined with Product and UX Research, the Pulse success framework gives every workflow a measurable outcome.

Pillar 1

Functional

% of core jobs-to-be-done completed each month, plus task start and abandonment rates.

Pillar 2

Performance

Login success, retention and session depth.

Pillar 3

Experience

Leading CSAT indicators for each workflow.

Pillar 4

Commercial

Tier adoption and enterprise tender readiness.

Track A · Core friction

Tracing 90% of login failures to three fixable root causes

Three causes accounted for 90% of operator login failures: entering an email instead of a username, forgetting the password, and MFA codes that never arrived.

Working with Security, I led the UX for “Remember username”, “Trust this device for 90 days” and explicit validation states.

90% of failures: 3 root causes

Sign in to Pulse

  1. 1

    Email vs. username

    A single generic field; entering an email fails with “Invalid credentials”.

  2. 2

    Password recall

    Operators retype both fields every visit.

  3. 3

    Undelivered MFA codes

    No feedback when a code never arrives.

One Pulse layout that adapts to US and European operators

I set the localization standards: CMS settings, currency and number formatting, and signage and zone codes for the US versus area numbers in Europe.

Downtown parking overview

USD · English · Last 30 days
Revenue
$182,400
Sessions
41,250
Occupancy
68%
Zone / signage codeRevenueOccupancy
Z-104 / S-12$18,42074%
Z-107 / S-15$12,98061%
Z-112 / S-03$9,34052%

Illustrative data. US uses zone and signage codes; EU operators use area numbers.

Track B · AI North Star

Making AI-generated numbers something an analyst can defend to a city executive

Analysts couldn’t customize fixed reports. Account Managers built one-off Streamlit dashboards, or cities wrangled CSV exports by hand, while tenders asked for ad-hoc reporting.

Operators also questioned whether AI numbers could be trusted when reporting upward. So I built a coded prototype with Pulse Home, Peer Benchmarking (a 100-index vs. rank governance model) and Moby custom reporting.

Try a municipal prompt

Mobile app revenue passed pay station revenue in 2 of 3 downtown zones in Q3.

Pay station Mobile app
  • Zone A (core)

    $212k
    $268k
  • Zone B (retail)

    $154k
    $171k
  • Zone C (garage edge)

    $98k
    $81k

Illustrative mock reports built for this portfolio, not customer data.

Validated with real municipal authorities before it became a PRD

Moderated 60-minute concept tests with US and EU municipal authorities covered unprompted queries, trust verification and willingness to pay. They shaped the Q1 Custom Reporting PRD and sales demo enablement.

Team spotlight

The team’s work I directed rather than designed

Leaders earn trust by spotlighting their team. These workstreams were designed by the team and directed and coached by me.

Deep dive

Tender context, PRD learnings and the full prototype