03 / ATX Untangled · Independent product
A city problem should end with a next step.
I build ATX Untangled for Austin residents. It brings city requests, savings programs, and public records into one place, with sources and a practical way forward.
Walk through ATX Untangled.
Start with a resident’s task
The homepage starts with the resident’s question rather than an agency dataset. The goal is a useful next step with as little input as the task requires.


The problem
Public information still leaves the resident doing the work.
Useful information lives across agency pages, PDFs, maps, and datasets. A resident has to work out what applies, find the official route, and figure out what happens next.
Product decisions
Design around the task, then show the source.
Start with a resident’s question.
Organize the product around saving money or solving a city problem, rather than asking people to start with a dataset or department.
The tradeoffFewer paths with useful next steps are worth more than broad coverage that ends in another search.
Keep the source beside the claim.
Program guidance and public records link back to official sources. Eligibility and filing availability need to be visible before someone acts.
The tradeoffA simpler interface still needs enough context for a resident to check a consequential claim.
Let people get help as a guest.
Keep resident inputs to what the task requires. An account should not be the price of understanding a city service.
The tradeoffCollecting less information limits personalization. It also keeps the first useful step easier to reach.
