Evidence audits, personal observations, local civic projects, and design experiments that can strengthen, weaken, or change the doctrine.
Find confusing questions, missing domains, false precision, cultural bias, double-counting, and cases where the total score hides the useful story.
Failure condition: if the 0–100 score feels falsely authoritative, turn the Audit into a profile instead.
Try the Audit →Track where waking time actually goes before optimizing it: paid work, commuting, care, household labor, bureaucracy, relationships, making, recovery, entertainment, and unstructured time.
Question: which burdens are imposed rather than chosen?
Keep a useful service but remove nonessential notifications, badges, feed shortcuts, and interruptions for one week.
Measure: useful tasks, missed information, checking, time, frustration, and benefit preserved.
Map where people can linger without spending much: libraries, parks, plazas, gardens, community rooms, beaches, recreation, and inexpensive gathering places.
Look for: shade, seating, bathrooms, accessibility, children, transit, cost, and repeated encounter.
Measure usable shade, outdoor space, gardens, habitat, renter access, soil safety, heat, walking routes, maintenance, and children’s access.
Distinction: usable access versus symbolic acreage.
Record forms, duplicate fields, calls, hold time, logins, documents, transfers, trips, delays, errors, appeals, and active human time for one real process.
Goal: distinguish safety/accountability from friction created by poor coordination.
Document one physical project—crossing, shade, garden, repair event, bench, tool library, meal, restoration, walking group—from problem through approvals, labor, maintenance, outcome, opposition, and failure.
Rule: one successful project is implementation evidence, not proof of a worldview.
Completed: Human Nature and Land & Life.
Local versus digital connection, third places, loneliness, social infrastructure, exclusion, mobility, and the difference between belonging and coercion.
Schedule control, commuting, shorter workweeks, remote work, caregiving, productivity, income, and time returned to life.
Attention, persuasive design, interoperability, repair, privacy, skill retention, AI, dependence, and exit.
A case where a Human Scale principle predicts the wrong thing.
A primary source, dataset, replication, failed replication, or methodological criticism.
A garden, schedule, technology, localism, policy, or community intervention that created more burden than benefit.
Costs, time, approvals, participation, maintenance, before/after measures, and what actually happened.
A place where “healthy,” “local,” “walkable,” “independent,” or “simple” assumes an able-bodied or culturally narrow user.
A calmer interface, local map, policy draft, civic tool, data visualization, open-source implementation, or physical design.
Human Scale should become a network of claims, experiments, local projects, evidence audits, and design patterns—not only a book.
The project does not need applause as much as it needs information that changes what we build.