Foundation Sprints
Sign in

Build · 9 of 12

Flow

How someone moves through the experience, start to finish, and where it currently breaks.

Sounds like what you need?

  • Find where people drop off, and fix it
  • Get new people started in fewer steps
  • See the whole experience end to end
  • Design the edge cases, not just the main path
  • Screens that look and feel polished

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 flow produced in a real engagement, exactly as the client has it. See the whole Hub

First Trip journey

User journey

The core product loop: setting up the dongle, driving hands-free, and seeing a trip summary that builds trust.

  1. 1

    Setup

    Get the dongle installed and connected once, confidently, with minimal effort

    Feels · Cautious optimism → mild anxiety

    Breaks when · "Am I doing this right?" — OBD port location, compatibility uncertainty

  2. 2

    Trigger

    Start driving normally without needing to remember to do anything

    Feels · Relief (if truly hands-off)

    Breaks when · Uncertainty that it actually started logging; the temptation to check the phone

  3. 3

    Interpretation

    Understand how Miles works, and trust it's accurate and working quietly in the background

    Feels · Invisible trust-building (or skepticism if flaky)

    Breaks when · Missed trips, split trips, or weird trip boundaries

  4. 4

    Action

    Turn the drive into a usable artifact (not raw data)

    Feels · Curious and interested — surprised by the simplicity

  5. 5

    Resolution

    See proof it worked, and a helpful summary that feels encouraging

    Feels · Satisfaction and confidence

    Breaks when · The first result is empty, overly technical, or judgmental — and they churn

  6. 6

    Follow Up

    Build the habit and deepen setup without regret or overwhelm

All twelve building blocksNext: Prototype →