Where support may matter

I grew up in a small village where the limits around us felt normal because they were part of daily life. It was just home.

I noticed those limits for the first time on bus rides to basketball games in junior and senior high. We would ride 10, 20, maybe 30 minutes from home and arrive somewhere that felt entirely different. The buildings, gymnasiums, and cars in the parking lot all looked unlike what I was used to seeing. The uniforms looked almost professional. The roads on the way there had more trees, more space, and signs that money had been spent there. I did not have the language for it yet, but I was noticing public investment.

These were not distant places. They were close enough to play on a weeknight. The differences were easy to see, but harder for me to understand.

I kept wondering why places so close together could feel so differently resourced.

That question stayed with me.

Over time, it shaped what I studied and the kind of work I wanted to do. Geography gave me a way to think about place. Planning gave me a way to think about public systems, infrastructure, and institutions. GIS and data gave me tools for seeing patterns that were easy to feel but harder to prove.

The question kept changing form, but it never really went away: why do some places have more room to function than others, and what would it take to build practical support for the places that do not?

Space for Us comes from that question.

It is my way of working with small public-serving institutions that know their communities, but may not have the time, staff, money, or technical support to build the systems they need.

That work usually starts with ordinary things: records, forms, spreadsheets, websites, maps, public data, inboxes, meeting notes, and the informal knowledge people carry because no system has been built to hold it. In small governments, schools, classrooms, and nonprofits, these details matter. They shape whether people can find information, make decisions, respond to residents, communicate clearly, and keep work from depending on one overextended person.

I want to help the schools, local governments, nonprofits, and community organizations serving small places see what is happening, share what matters, and make decisions with information that is clearer, steadier, and easier to maintain. Not because data solves everything. Because without usable information, even people who care deeply are left trying to serve their communities through fog.

That same question led to this project.

I wanted to know whether I could use public data to find small places like the one I came from: places where local institutions may be serving real needs with limited resources, limited staff, and systems that were never designed for the amount of work people are carrying.

This is one example of what Space for Us is built to do.

The work did not require private data, expensive software, or a complicated platform. It started with public information that already exists. The useful part was bringing it together, cleaning it up, comparing places in a consistent way, and turning scattered data into something easier to see.

Public data is messy. It lives in different files, tables, formats, and geographies. One dataset may describe population. Another may describe housing. Another may describe internet access, income, or poverty. On their own, those pieces are useful but limited. Put together carefully, they can begin to show patterns that are harder to see one spreadsheet at a time.

For this project, I used public Census data to screen for small U.S. places where household conditions, housing pressure, and digital access suggest that local organizations may be working in communities with real constraints. The point was not to label places or reduce them to a score. It was to create a starting point for better questions.

Where might small governments, schools, nonprofits, or community groups benefit from systems built for the conditions they are actually working in? Where might a practical system help people see what is happening, understand what needs attention, and respond with less friction?

In that sense, this project is both an analysis and an example of the same kind of work Space for Us is built around.

The code and map are available here: Small Place Analysis on GitHub

This does not replace local knowledge. It does not tell me what any one place needs. But it gives me a clearer way to begin: with evidence, with humility, and with attention to institutions that are often asked to do more than their systems can support.

That is the kind of work Space for Us is meant to make possible: simple, useful systems for schools, local governments, nonprofits, and community organizations serving small places, built for the reality they are working in.