Foundation Sprints
Sign in

Build · 10 of 12

Prototype

Something real enough for people to try, so we learn from behavior instead of opinions.

Sounds like what you need?

  • Turn what's in our heads and slides into something people can click
  • Put our biggest hunches in front of real people
  • Find the right people to try it, and hear what they say
  • Map the one path from first tap to "got it"
  • Cut it down to the first version worth building

What the Build Sprint looks like

The questions this sprint answers

  • What's the path from first touch to done?
  • What's the riskiest assumption we need to test?
  • What's the most important thing on each screen, and does it read that way?
  • What are our tokens — color, type, spacing, radius?

Decisions we'll make together

  • The path from first touch to done
  • Where people drop off, and the fix
  • The riskiest assumption to test
  • What counts as a pass

Week 1 · Get unstuck

  1. MonWorkshop — We confirm the scope, check the foundation, and agree what we're testing and how.
  2. TueExplore — Research, and two or three directions for flow, prototype, interface and system.
  3. WedExplore — The directions, taken far enough to compare honestly.
  4. ThuShape — The strongest direction, sharpened for the lock.
  5. FriDirection lock — We review the directions together and commit to one.

Week 2 · Get something real

  1. MonMake — The chosen direction, built out.
  2. TueMake — The core of it, made real.
  3. WedRefine — A review together, then the fixes it turns up.
  4. ThuTest — Checked against what we set out to learn, and finished.
  5. FriDelivery — A walkthrough, and everything lands in your Hub.

You leave with: A user journey · A screen map · A clickable prototype · A test plan you can run · Key screens, designed · Specs a developer can build from · Design tokens · A component library

Every sprint follows this shape; yours is written around your project when you start.

In a real project

Miles

What prototype produced in a real engagement, exactly as the client has it. See the whole Hub

  • Kid Starts Driving / Trip in Progress

    Mobile app

    Prove that both parents receive, view, and trust a live trip as it happens and after it ends.

    Scenario 1 of Miles Proto 4.

    Opens from a push notification.

  • Kid Speeding

    Mobile app

    Show the agent interrupting an active trip thread with a driving behavior alert and parent response options.

    Scenario 2 of Miles Proto 4.

    Opens from a push notification.

  • Hard Braking (Real-Time Alert)

    Mobile app

    Same as speeding but for a deceleration event, proving the mid-trip alert pattern repeats cleanly.

    Scenario 3 of Miles Proto 4.

    Opens from a push notification.

  • Fuel Low After a Trip

    Mobile app

    Establish the baseline reminder pattern: agent surfaces a low-stakes issue, user picks how to handle it, done.

    Scenario 4 of Miles Proto 4.

    Opens from a push notification.

  • Low Tire Pressure

    Mobile app

    Prove the full card anatomy works end-to-end: data visualization, coaching layer, action set, and resolution.

    Scenario 5 of Miles Proto 4.

    Opens from a push notification.

  • Oil Change Due

    Mobile app

    Show the reminder pattern with more action variety (time-based, mileage-based, already done) and the "don't badger" behavior.

    Scenario 6 of Miles Proto 4.

    Opens from a push notification.

  • Check Engine Light

    Mobile app

    Test the alert → chat flow with a higher-anxiety vehicle issue that needs calm explanation. Surface context on the issue, severity, and cost range. CTAs: get reminder in 2–3 days; send email/documentation to mechanic.

    Scenario 10 of Miles Proto 4.

    Opens from a push notification.

  • Trip Summary — Contextual Q&A

    Mobile app

    Prove the agent can be user-initiated from a screen, not just alert-driven, with suggested prompts scoped to a completed trip.

    Scenario 11 of Miles Proto 4.

    Opens from the Ask Miles screen.

  • Hard Braking (Post-Trip Review)

    Mobile app

    Show braking events as markers on a completed trip route inside the trip summary view.

    Scenario 12 of Miles Proto 4.

    Opens from the Ask Miles screen.

  • Registration Expiring

    Mobile app

    Show the passive badge entry point for a time-based reminder that's handled in seconds and backgrounded.

    Scenario 14 of Miles Proto 4.

    Opens from a push notification.

Prototype planning board

Where the prototype scenarios were planned: reference apps, a row of steps and open questions per scenario, and the flows sketched out.

  • Prototype planning board