Skip to content
flowss
Start freeChecking your session
User story map templates

Story Map — Food Delivery Evening

The backbone is the customer's evening rather than the org chart: decide, order, wait, deliver, put it right. Written with bullet-led cards, it ships one restaurant in one city first and leaves every complaint path to band two.

User story mapLean & FlowUser story map syntax docs
Template previewUser story map
Food delivery — the customer's eveningPersona: Weeknight customer ordering dinner for two · Goal: Order, watch it come and eat within forty minutesR1 — One restaurant, one city46 pts · 7 cardscovers 4/5 · cum 46R2 — Marketplace63 pts · 8 cardscovers 5/5 · cum 109R3 — Scale68 pts · 5 cardscovers 4/5 · cum 177Later13 pts · 1 cardcovers 1/5 · cum 190BACKBONEactivities, left to rightTASKSthe walking stepsDecide what to eat36 pts · 5 cards · 2 tasksOrder47 pts · 5 cards · 2 tasksWait47 pts · 5 cards · 2 tasksDeliver39 pts · 4 cards · 2 tasksPut it right21 pts · 2 cards · 1 taskgapBrowse restaurantsRead a menuBuild the basketPayTrack the orderChange your mindAssign a courierHand overReport a problemOpen restaurants with adelivery estimate5Menu with prices andallergen notes5Add, remove and changequantity5Card payment with addressand delivery note13Accepted, cooking, on theway, delivered8Manual dispatch from theoperations desk5Photo and contactless dropconfirmation5Cuisine, rating and pricefilters8Item photos and popularitybadges5Item options, extras andspecial instructions8Saved cards and one-tapreorder8Live courier position on amap13Cancel before the kitchenaccepts5In-app chat betweencourier and customer8Missing item or cold foodreport with photo8Personalised ranking frompast orders13Arrival estimate thatupdates with traffic13Add a forgotten itemwithin two minutes8Batching two orders ontoone route21Automatic partial refundinside a policy band13Split the bill across thetable13backbone gapNot a walking skeleton — 1 of 5 activities have no card in R1 — One restaurant, one city: Put it rightStory cards21Estimate190 ptsBackbone5 activitiesReleases4First release spans4/5 · 80%Walking skeleton1 gapFirst release load46 ptsSmallest full slice · 63 ptsR2 — MarketplaceHeaviest releaseR3 — Scale

Make it your own.

title "Food delivery — the customer's evening"
persona "Weeknight customer ordering dinner for two"
goal "Order, watch it come and eat within forty minutes"

release "R1 — One restaurant, one city"
release "R2 — Marketplace"
release "R3 — Scale"

# The backbone is the customer's evening, not the org chart.
activity "Decide what to eat"
  - task "Browse restaurants"
    - R1: "Open restaurants with a delivery estimate" (5)
    - R2: "Cuisine, rating and price filters" (8)
    - R3: "Personalised ranking from past orders" (13)
  - task "Read a menu"
    - R1: "Menu with prices and allergen notes" (5)
    - R2: "Item photos and popularity badges" (5)
activity "Order"
  task "Build the basket"
    R1: "Add, remove and change quantity" (5)
    R2: "Item options, extras and special instructions" (8)
  task "Pay"
    R1: "Card payment with address and delivery note" (13)
    R2: "Saved cards and one-tap reorder" (8)
    later: "Split the bill across the table" (13)
activity "Wait"
  task "Track the order"
    R1: "Accepted, cooking, on the way, delivered" (8)
    R2: "Live courier position on a map" (13)
    R3: "Arrival estimate that updates with traffic" (13)
  task "Change your mind"
    R2: "Cancel before the kitchen accepts" (5)
    R3: "Add a forgotten item within two minutes" (8)
activity "Deliver"
  task "Assign a courier"
    R1: "Manual dispatch from the operations desk" (5)
    R3: "Batching two orders onto one route" (21)
  task "Hand over"
    R1: "Photo and contactless drop confirmation" (5)
    R2: "In-app chat between courier and customer" (8)
activity "Put it right"
  task "Report a problem"
    R2: "Missing item or cold food report with photo" (8)
    R3: "Automatic partial refund inside a policy band" (13)