ARR-01 //// After Action Report

Status / archived

Quality Counts / 2021–2022

DataPoint

A self-serve traffic-data product for city planners, engineers, and residents.

Shipped outcome

Shipped DataPoint 2.0, its capacity-planning workflow, and the Cardinal design system.

Role
Product Designer
Organization
Quality Counts
Period
2021–2022
Scope
Product design / Interaction design / Design systems

Executive read

The short version

Challenge
Turn an experimental traffic-data tool into Quality Counts’ first production software product without leaving residents or expert planners behind.
My contribution
I was the only designer, so I handled the product structure, research synthesis, interface design, creative direction, and the Cardinal design system.
Result
We shipped DataPoint 2.0 and its capacity-planning tools. About 30 customers were waiting to onboard when I last spoke with Quality Counts.
DataPoint 2.0 map showing intersection and midblock markers, search and filter controls, and a contextual station-results inspector

Shipped product / DataPoint 2.0

The redesigned default view connected three stable surfaces: search and filters, a map for spatial context, and an inspector that changed with the user’s selection.

Open full size ↗

Operating context

Quality Counts had an experimental web app for exploring traffic-count data, but this was its first attempt at production software. The company asked me to lead the creative direction, redesign DataPoint, and help establish a software practice with its internal team and a contracted development team.

City planners and traffic engineers needed enough detail to analyze intersections and midblocks. Residents needed a faster way to check traffic conditions and test assumptions about their communities. The same product had to support both groups without turning every view into an expert-only interface.

The original product centered on a full-screen map. Customers selected an intersection or midblock, reviewed an overview panel, and opened a separate view for detailed count data. The information was there, but the path from search to comparison and deeper analysis was hard to follow.

Constraints

  • I did not have a background in traffic planning or city government.
  • Quality Counts was building its first production software product.
  • Historical traffic data varied in structure and quality.
  • Residents and technical customers brought very different domain knowledge.
  • Each customer had a separate DataPoint instance and city-specific URL.
Original DataPoint interface with a dense full-screen traffic-station map and search controls floating over the map

Baseline / Original product

The original interface put a large station inventory on the map, but it did not give people a clear path from search to overview and deeper analysis.

Open full size ↗

Responsibility

I was the sole designer. I owned the product experience, interface design, visual direction, and Cardinal design system. I spent my first month learning the traffic-planning domain, auditing the existing product, interviewing Quality Counts staff, and contacting cities that had already seen a DataPoint demonstration.

Quality Counts supplied domain and business context. I partnered with its internal team and the contracted development team as they implemented the product. Product scope was collaborative; I did not write the production application.

Decision 01: Make the product native to the web

The problem: Traffic engineers often used desktop software built around older Windows interaction patterns, while residents expected something closer to the map products they already knew.

What I chose: Treat DataPoint as a web product instead of recreating a desktop application in the browser.

Why: It would work from any connected computer and could use familiar web patterns for navigation, search, filtering, and progressive disclosure.

The tradeoff: We could not copy expert workflows directly from legacy tools. We had to decide which controls belonged in the default interface and which could wait until a deeper analysis view.

What informed it: Competitive analysis, an audit of the original product, and conversations with Quality Counts and prospective city customers. “Modern” and browser-based access came up repeatedly.

Decision 02: Separate overview from analysis

The problem: Some customers wanted a quick status check. Others needed count files, turning movements, peak periods, vehicle types, and capacity controls.

What I chose: Organize DataPoint 2.0 around a search and filter bar, the map, and a contextual inspector. Selecting a station opened deeper analysis in a modal, which could move to a separate browser tab for comparison.

Why: The map and inspector kept the most common information close at hand. The modal made room for detailed analysis without crowding the default view with every control.

The tradeoff: The modal only worked with one station at a time. People still needed separate tabs to compare several stations.

What shipped: People could browse visible stations, inspect one, and move into intersection or midblock analysis without losing the map as their starting point.

DataPoint 2.0 intersection inspector showing peak-hour filters, a turning-movement diagram, station metadata, and attached files

Progressive disclosure / Intersection

The station inspector provided a readable peak-hour summary before offering the full traffic-count workspace.

Open full size ↗
DataPoint 2.0 midblock analysis showing vehicle-classification charts and a detailed count table

Detailed analysis / Midblock

The midblock workflow separated the two-direction traffic model from the more complex intersection model while keeping shared filters and export paths.

Open full size ↗

Decision 03: Support basic and advanced capacity planning

The problem: Newer engineers needed a clear starting point, while experienced customers needed control over the inputs behind intersection-capacity analysis.

What I chose: Give the Capacity Planner and Simulator a basic mode for common decisions and an advanced mode for direct control. The calculation used a formula supplied by engineers at Kittelson and based on the Highway Capacity Manual.

Why: One module could work for different levels of expertise without forcing every customer through its most complex workflow.

The tradeoff: Hiding the advanced controls made the first view easier to read, but we still needed to test how people moved between a quick review and detailed analysis.

What shipped: The intersection workflow included both modes, with the underlying traffic-count inputs available in the advanced view.

Decision 04: Build a shared product foundation

The problem: Quality Counts needed to improve DataPoint while testing related software ideas.

What I chose: Create Cardinal as a shared design system for DataPoint and related concepts.

Why: Reusable patterns gave the team a consistent starting point instead of treating every experiment as a separate visual system.

The tradeoff: Shared patterns only help when a team maintains and uses them. We did not measure either part.

What we saw: The team used Cardinal while exploring related concepts, including computer-vision traffic counting as an alternative to physical road tubes.

System specification

DataPoint 2.0 used a small set of stable interface regions:

  • Search and filter bar: Located stations and narrowed the data shown on the map.
  • Map: Displayed intersections, midblocks, traffic signals, bus stops, and crash data with distinct iconography.
  • Contextual inspector: Summarized either all visible stations or the selected station.
  • Intersection analysis: Organized station details, traffic counts, and capacity planning into three tabs.
  • Midblock analysis: Separated station details from directional vehicle-count charts and filters.
  • Support: Integrated Intercom to connect onboarding and customer-support workflows.

Detailed views retained export paths for customers who needed to continue analysis in tools such as Excel.

DataPoint 2.0 detailed intersection traffic-count workspace with turning movements, truck percentages, pedestrian volumes, bike movements, a peak-hour chart, and a data table

System depth / Traffic counts

The detailed workspace brought related traffic measures into one filterable view. This preview is cropped for the page; the full artifact includes the chart and count table below.

Open full size ↗

Validation

I studied the existing product and traffic-planning domain, interviewed Quality Counts staff, contacted cities that had seen a product demonstration, and compared the tools used by engineers with map products familiar to residents.

That work shaped the scope, the three-part layout, and the way we revealed advanced controls. We did not collect reliable metrics for task success, support volume, or implementation time, so I cannot make claims about them.

Outcome

The team shipped DataPoint 2.0, its capacity-planning workflow, and the Cardinal design system. When I last spoke with Quality Counts, about 30 customers were waiting to be onboarded. That showed demand, but it did not tell us anything about adoption, retention, or task efficiency.

Cardinal also gave the team a shared starting point for testing other product ideas. We did not measure how much time it saved or how consistently the team used it.

What I would do next

The decision that held up best was separating quick checks from detailed analysis. Even expert users benefit from a clear default view when advanced controls are easy to find.

I would now prioritize three follow-up areas:

  1. Build internal tools to validate and clean historical data before import.
  2. Test a unified DataPoint instance so cities can share traffic data without separate product URLs. I proposed this direction, but the team postponed it beyond the 2.0 release.
  3. Test windowing or minimized stations for side-by-side comparison instead of relying on separate browser tabs.

I would measure onboarding completion, time to find a station, errors during data import, use of basic versus advanced capacity controls, and the number of stations compared during a planning task.

Additional artifact

Working file

DataPoint 2.0 product design

Explore the product flows, detailed traffic-count views, and interaction states shown in this report.

Open in Figma ↗