UX, Success Metrics & Risk Mitigation

Design principles, analytics, QA plans, and contingencies that guide delivery of the NC GOTV Web App.

UX Requirements

Global Experience

  • Persistent search bar with fast updates and filter chips.
  • Keyboard-first shortcuts: / to focus search, Enter to submit, Tab to traverse, ? for help.
  • High-contrast toggle, adjustable font sizes, semantic headings, ARIA-tagged tables, and focus-visible styles.
  • “Copy query as URL” affordance to share setups across organizers.

Phase-Specific UI

  • Phase 1: Unified page with search, filters, results grid, and export controls.
  • Phase 2: Precincts page featuring a map, polling-place card, and export buttons.
  • Phase 3: “Unregistered” tab that allows polygon selection and displays candidate addresses with confidence tiers.

Analytics & Success Metrics

  • Adoption: Weekly active users and queries per organizer.
  • Throughput: Median time from query to export under 60 seconds.
  • Coverage: Percentage of precincts with lists pulled before Election Day.
  • Impact Proxies: Early voters removed from GOTV lists, canvassed addresses, and registrations attributed to outreach.
  • Data Quality: Join failure rates under 0.5% and ≥70% high-confidence matches for AddressNC comparisons.

Validation & QA

  • Golden datasets: 10 hand-checked searches, 10 filter recipes, 5 precinct exports, 3 unregistered polygons.
  • Cross-check aggregated counts against raw voter files and precinct tallies.
  • Monitor SLO dashboards for latency, error rates, job durations, and data freshness.

Risks & Mitigations

  • Post-election history lag: Display “data as of” timestamps and allow filtering by last update.
  • Precinct boundary churn: Store versioned geometries and label exports with precinct vintage.
  • Address granularity: Provide confidence tiers and solicit canvass feedback to refine matching.
  • Name search false positives: Expose similarity scores and include an exact-match toggle.

Rollout Plan

  1. Weeks 1–2: Ingest Halifax voter file and history; deliver Phase 1 search/filters; validate against golden sets.
  2. Weeks 3–4: Layer in polling places and precinct exports for Phase 2.
  3. Weeks 5–6: Integrate AddressNC, build matching pipeline, and ship Phase 3.
  4. Week 7+: Expand statewide and prioritize Phase 4 action tooling.

Legal & Compliance Notes

  • Use the NC voter file solely for political purposes, without inferring excluded sensitive fields.
  • Clearly display data freshness timestamps and non-commercial usage terms.
  • Offer “remove from export” toggles for data elements organizers deem sensitive.