Program · Veteran Livability Index
The Veteran Livability Index, run as a program.
An interactive county-level decision tool — six metric overlays, click-to-drill navigation, a built-in VA disability calculator, eighteen attributed fields per county. Scoped deliberately around what it is and is not, and shipped on an architecture chosen for stability over polish. This page is the program lens; the tool and its attribution live in the case study.
What It Is
A county-level veteran livability decision tool — six metric overlays, one composite score
Coverage
Every U.S. county · eighteen attributed fields each · click-to-drill state-to-county
Sources
Census ACS, BEA, BLS, and VA — all federal public domain
Status
Live since 2026-05-09 · served through a stability-first embed architecture
The Program in Brief
A tool built to be used, not admired.
The Veteran Livability Index answers a question a veteran actually asks: of the counties I could live in, which ones treat veterans well on the things I care about — income, employment, cost of living, the purchasing power of VA benefits? It maps every U.S. county, lets a user drill from state to county, overlays six metrics plus a composite livability score, and carries eighteen attributed fields per county, with a built-in VA disability rate calculator so the benefits figures reflect the user's own rating.
What makes it a program is restraint as much as scope. The tool opens by stating plainly what it is and what it is not — a decision aid, not a ranking to win or lose. It is organized around four concrete moves a user makes to get an answer, rather than around everything the data could theoretically show. And every number is attributed to its federal source on the page. The discipline here is in what was deliberately left out.
Run as a Program
Three decisions that made it a program.
Scope stated, not assumed
The tool leads with a section titled “what this is, and what it is not.” A livability score is easy to misread as a verdict; saying plainly what the tool does not claim is a scope decision made for the reader, on the page, before they touch the map.
Built around the user's task
The tool is organized around four concrete moves to get an answer, not around a feature inventory. Designing to the task rather than to the dataset is the difference between a decision tool and a dashboard.
Every number attributed
All eighteen fields per county trace to a named federal source on the page itself. Attribution is not an appendix; it is a standard the build had to meet to ship.
Risk Managed in Flight
An architecture chosen for stability over polish.
An interactive county map of the whole United States is a heavy page. On this host, a static file above roughly one megabyte can fail a compressed request and return a server error rather than serving — the same compression-cap behavior the household-cost program hit during its launch. The full-weight build of the index ran into exactly that boundary.
The program response was to choose stability over the heavier ideal. The public page serves the interactive map through a lightweight embed — a stable, deliberately bounded build — rather than the full-weight version that trips the host's cap. It is a smaller surface than the maximal build, and that trade was made on purpose: a tool that loads reliably for every veteran who opens it beats a richer tool that returns an error. The fragility boundary is known, named, and engineered around rather than discovered by a user.
How this program sits in the section
The Veteran Livability Index is presented here through the program lens — scope stated on the page, a build organized around the user's task, and a fragility boundary engineered around rather than hidden. It does not carry the full chartered artifact set that the Workforce Stability program does: a standalone charter, a formal risk register, an executive deck.
What it carries is the same operating discipline, evidenced in its own way — an explicit scope statement, a documented attribution standard, and an architecture decision made openly for stability. The full tool, the six overlays, and the attribution for every field live in the case study.
Go Deeper
The full Veteran Livability Index
The case study carries the live tool and the depth this page summarizes — what it is and is not, who it is built for, the four moves to get the answer you came for, the interactive county map, and the attribution behind every number.
Veteran Decision Tool
Every U.S. county, six metric overlays, click-to-drill navigation, a built-in VA disability rate calculator, and eighteen attributed fields per county — built to be used, not to be admired.
6
Metric Overlays
18
Fields / County
4
Federal Sources
Work Together
A tool that loads beats a tool that impresses.
Scope stated on the page, a build shaped to the user's task, and an architecture decision made openly for stability. If your team needs that kind of judgment in a deliverable, let's talk.