Strategy · published

A repeatable evidence workflow from the student projects — which metrics to calculate, with which tool or method, and the decision it led to.

SummaryService circles drawn over a population-density map show how many small hubs are needed to cover a city within a delivery time.
Tool or methodmanual / formula (service radius drawn as a map overlay)
Statuspublished

The question it answers

How many urban hubs, and where, can cover the city within a target delivery time?

How it works

  1. Set a service radius from the target delivery time.
  2. Map population density to find where demand is highest.
  3. Place hubs so that their service circles overlap and cover the dense areas.
  4. Count the hubs and design one repeatable hub type for the different neighbourhoods.

In the student projects

  • Roshni Basu — manual / formula (map overlay). Delivery catchment: radius 2.5 km (text: 2–3 km); 12 microhubs with overlapping coverage. Decision: “Population density and service-radius analysis led to a network of twelve neighbourhood microhubs instead of more parcel lockers.”

Values and decisions as reported by the student; see each case study for the page in the portfolio.

Where it falls short

  • Only one project uses this workflow; the radius is adapted from a delivery company’s dark-store practice, not computed from a street network.
  • In Roshni Basu’s portfolio the delivery time given is not consistent (10–15 min on the diagram, ~5 min in the caption).

Where are the ambitions, metrics and tools?

They appear automatically below under Connections, and in Obsidian under the auto_ properties.

Connections


Something wrong or missing? Suggest a correction