Ask Harvey: Tahoe 200
Two hundred miles. One crew. A phone tool that kept the plan honest when the plan stopped being enough.
Context
Tahoe 200 is not a race you wing. Crew coordination, pacing math, and real-time decisions need a single source of truth. Spreadsheets and group texts break under sleep deprivation and elevation.
What I built
Two surfaces, one system:
Crew Chief — the ops site for logistics. Race board, aid timeline, optimistic/baseline/conservative pacing, crew and pacer plans. Built to answer “where should we be, and who is next” without a meeting.
Ask Harvey — a phone-first agent for crew and remote family. Check in with your name and role, then talk to Harvey in his voice with live race context in the header (mile, speed, last ping, status).
How it worked
Clarity under stress. Big type. Minimal navigation. Every screen answers one question at a time. Static delivery for spotty mountain service. The agent layer sat behind Cloudflare (named tunnel at agent.wheresharvey.com) while the crew site shipped on GitHub Pages at wheresharvey.com. The full-loop course file (50 waypoints with cutoffs, from Start through Heavenly, Loon Lake, Tahoe City, Brockway, Spooner, Finish) ships here as tahoe-200-full-loop.gpx.
Audience mattered: on-course crew got logistics chips and operational tone; remote family got a calmer check-in path. Both stayed oriented by the same live status strip.
Outcome
The crew ran calmer. The athlete had fewer “what mile am I on?” moments. The project became a personal proof point for building human-centered tools outside the day job, and it is the product that originally lived on this domain.
What I’d do next
The archived Ask Harvey check-in experience lives at /tahoe. A v2 would deepen crew handoff flows, keep the agent API stable without tunnel churn, and capture a cleaner post-race debrief.