Write links as simple sentences: “Long wait at bus stop increases jaywalking.” Ask, “If this rises, does that rise or fall, all else equal?” Mark uncertainty with dotted lines. Encourage people to explain links with short, lived examples. Avoid acronyms and technical shorthand that exclude neighbors. Keep arrows honest by challenging assumptions and checking whether data or stories support them. When in doubt, park questionable links in a corner and return after gathering more observations from multiple perspectives.
Name a loop only when you see its circular logic: “Slow buses reduce ridership, which reduces funding, which slows buses.” Then propose a practical nudge that could break or strengthen it, like signal priority or shelter improvements. Identify indicators for each link, even if informal at first, such as observed wait times, rider counts, or photo diaries. If the loop exists, small changes should ripple predictably. If not, your test teaches you which portion of the story needs revision.
Lean on everyday data sources: school newsletters hinting schedule waves, 311 logs showing clustered complaints, utility notices predicting street work, and receipts reflecting shopping distances. Use simple tallies of near-misses, before-and-after photos, and heatmaps from phone surveys. Respect privacy, avoid doxxing, and focus on neighborhood-scale signals. Data does not need to be perfect to be useful; it needs to be transparent and repeatable. Let neighbors co-collect, co-interpret, and co-own it so insights travel faster than rumors.
All Rights Reserved.