Foundation Sprints
Sign in

Build · 11 of 12

Interface

The screens themselves — layout, hierarchy, and interaction, refined until they feel right.

Sounds like what you need?

  • Calmer, simpler screens
  • A mobile experience designed for mobile
  • Screens ready to hand to developers
  • Make similar things work the same everywhere
  • Make things easy to find

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

Trips screens

Screens

  • Trips List

    The list of trips, and the entry to filtering. Already effective.

    Open in Figma
  • Trips Filter

    Filter by driver, vehicle and date range. The open question this cycle: the controls may be too crude.

    Open in Figma
  • Trip Detail

    The map and the way the route is shown and navigated are the favourite part; the content is good to go.

    Open in Figma

Agent screens

Screens

  • Dashboard

    The map, a coaching card from Miles, and each vehicle at a glance.

    Open in Figma
  • Ask Miles

    Opened from the Ask Miles badge: a greeting and suggested prompts.

    Open in Figma
  • Action card

    Miles answers with an action card the parent can act on in place.

    Open in Figma