Kentucky’s mix of rural and urban food deserts (documented in Next City’s Aug 22, 2025 feature) shows the same problem expressed differently across places. This post explains how to run a focused qualitative analysis of food access (interviews, field notes, program logs) to extract actionable themes fast, then operationalize them with Evidano. Read the original reporting at www.nextcity.org/features/linking-city-and-countryside-to-solve-food-insecurity. If you want to test this workflow on your own corpus, start a free trial at www.evidano.com and follow the checklist below.
Fast take: what the Next City piece found
The story (Aug 22, 2025) profiles Kentucky programs; Black Soil (founded 2017), FoodChain (started 2011), God’s Pantry Mobile Market (Mayor-backed in 2020) and the Hazel Green Food Project (launched 2021), showing shared solutions: mobile distribution, farmer–market linkages, education, and cross-county redistribution.
- Key stat: >6% of low-income households in southwest Lexington lack both a personal vehicle and a supermarket within half a mile (USDA Food Access Research).
- Hazel Green population ≈200; its Munchkin Market sees multi-mile lines and multi-county reach.
- Policy context: USDA changes reported July 10, 2025 affected grant eligibility for ‘socially disadvantaged’ farmers, shifting local strategies.
Findings snapshot (quick table)
| Date/Metric | Value / Fact | Source | Research implication |
|---|---|---|---|
| Published | Aug 22, 2025 | www.nextcity.org/features/linking-city-and-countryside-to-solve-food-insecurity | Contemporary field examples, policy context |
| Black Soil | Founded 2017; neighborhood Farmacy markets + market-on-wheels | www.blacksoilky.com (cited) | Program model: supply-chain linking farmers → urban markets |
| FoodChain | Program start 2011; public aquaponics + education | www.foodchainlex.org (cited) | Model mixes production + skills training, track program outcomes separately |
| Hazel Green Food Project | Began 2021; large surplus pickups; serves multi-county patrons | www.nextcity.org (report) | Redistribution patterns and travel-time burdens are measurable |
| USDA Food Access stat | >6% low-income households (SW Lexington) lack vehicle + supermarket <0.5 mi | USDA Food Access Research (cited in story) | Use as baseline for access segmentation |
| Policy change | USDA removed race/gender consideration for some grants (reported Jul 10, 2025) | www.civileats.com (cited in story) | Shifts funding flows; code for policy references |
How the programs work (what to code for)
Plain-language mechanics to capture in your qualitative coding: who supplies food, distribution modality (mobile vs stationary), eligibility rules (open vs means-tested), education components, partnership structure (nonprofit × retailer × city), and reported barriers (distance, transit, stigma).
- Supply chains: farm → nonprofit → market/meal, tag mentions of origin, perishability, scale.
- Access modalities: mobile market schedules, delivery, and pop-ups, code for frequency and coverage.
- Community dynamics: trust-building, social benefits of distributions, stigma around aid, treat as separate thematic nodes.
- Policy & funding: note explicit dates (e.g., 2020 mayoral commission; USDA July 10, 2025) in timeline coding.
Implications for researchers: what to ask next
For UX / service designers
Map user journeys for low-access households (transit time, wait time, childcare constraints). Quantify recurring friction points from interview text and field logs to prioritize service tweaks.
For program evaluators
Disaggregate impact by delivery mode (mobile vs stationary) and origin (local vs out-of-region surplus). Use cross-segment frequency analysis to compare rural/urban outcomes.
For policy & funding teams
Track references to grant policy changes and service scaling (2017–2025). Use coded evidence to argue for flexible funding that covers transportation and distribution costs.
Do more, faster with Evidano: AI-enabled qualitative analysis of food access
Problem: scattered field notes, interviews, program logs
Solution: ingest reports, interview transcripts, and spreadsheets into Evidano for a single searchable corpus. The platform handles uploads and secure storage (data encrypted; not used to train external models).
Problem: inconsistent coding across teams
Solution: import a codebook or let Evidano suggest themes from the corpus, then apply AI-assisted coding and hierarchical codes→subcodes to standardize labels (e.g., ‘transport burden’ → subcodes: distance, transit frequency, wait time).
Problem: comparing urban vs rural narratives
Solution: run cross-segment frequency and co-occurrence network analyses to surface difference-in-dictionary, see which themes cluster with ‘mobile market’ vs ‘farm surplus’.
Problem: long syntheses for stakeholders
Solution: generate executive-friendly visualizations (word clouds, co-occurrence graphs) and exportable reports. Use the AI chat over your documents to produce annotated excerpts and recommended action items.
Follow-up research
Evidano supports AI avatar interviewers to run short autonomous follow-ups (surveys or conversational prompts) to fill gaps identified in your analysis, e.g., precise travel times or post-distribution food-use outcomes.
Checklist: run this analysis in 7 steps
Quick reproducible workflow to go from reporting to recommendations:
- 1) Collect: save articles, transcript interviews, distribution logs, and survey CSVs.
- 2) Import: upload documents and spreadsheets into Evidano (retain source metadata and dates).
- 3) Preprocess: auto-transcribe any audio, apply PII redaction if needed.
- 4) Auto-code: generate initial themes; merge with your codebook and refine iteratively.
- 5) Segment: tag records rural vs urban, by partner (Black Soil, FoodChain, God’s Pantry, Hazel Green).
- 6) Analyze: run thematic frequency, cross-segment comparisons, and co-occurrence networks to identify leverage points.
- 7) Report & act: export visuals and annotated quotes for funders, city staff, or partners; schedule follow-up interviews via AI avatars if questions remain.
Conclusion: next moves
If your team is synthesizing mixed field sources (reports, interviews, program logs) to improve food access programs, a focused qualitative analysis will surface operational fixes, from routing mobile markets to timing education programs. The Next City piece (Aug 22, 2025) provides concrete artifacts and dates you can code against.
- Start a pilot: import 5–10 interviews + 2 program reports into Evidano and run a 2-week thematic sprint.
- Secure the work: Evidano encrypts your data and does not use it for third-party model training.
- Ready to test? Run your first upload at www.evidano.com and turn local reporting into prioritized, fundable recommendations.
Keep reading
- Commentary on NewsTwo Definitions: Climate Change Acceptance for UndergradsHow a PLoS One Delphi study (Aug 25, 2026) defined climate change acceptance for undergraduate science students, and how AI-enabled qualitative analysis applies it.
- Commentary on NewsResearcher-in-the-loop: AI-enabled UX researchHow the researcher-in-the-loop model governs AI-enabled UX research. Learn practical governance, stats from the August 2026 piece, and how Evidano supports this workflow.
- Commentary on NewsResearcher-in-the-Loop: Governance for AI UX ResearchGovern AI in qualitative UX research with the researcher-in-the-loop model from Jennifer L. Bowie (Aug 25, 2026): practical rules, risks, and tool mappings.
