ATX Untangled

Leadership layer

Stakeholder Map

Austin residents trying to finish a city-related task
Community organizations helping residents navigate local services
Public agencies and official sources that own the final handoff

Decision Tradeoffs

Prioritize task completion over adding another passive data dashboard
Keep resident inputs minimal and private, even when more collection could simplify the build
Prefer source-backed guidance over broader but harder-to-verify coverage

Governance Model

Attach provenance and freshness context to consequential guidance
Keep guest-first use available without requiring an account
Send residents to official systems for authoritative submissions and decisions

Rollout Plan

Start with high-friction Austin workflows where a clear next step can save time or money
Test the complete resident journey at desktop and mobile sizes
Expand coverage only when the source and action path can be maintained

Adoption Strategy

Write for the resident's immediate question rather than the underlying dataset
Make official handoffs and eligibility boundaries explicit
Use feedback to improve completion steps instead of collecting unnecessary personal data

Architecture evolution

Before

Useful local information was scattered across agency pages, PDFs, maps, and datasets.
Residents had to translate public data into a practical next step on their own.
Many research paths ended with more tabs instead of a completed task.

After

Resident questions are organized around outcomes such as saving money or resolving a city problem.
Guidance carries source context and an explicit official handoff.
The product minimizes data collection while still helping a resident move forward.

ATX Untangled is a resident-action product for Austin. It turns fragmented public information into practical, privacy-conscious workflows that help someone understand a problem and take the next useful step.

The operating problem

Austin publishes a large amount of useful information, but completing a real task can still require searching across agency pages, decoding policy language, checking eligibility, and finding the correct official handoff.

The product starts with the resident outcome—not the dataset—and works backward to the smallest complete path that can help.

Product principles

Outcome first: every data surface needs an action, explanation, or resident-ready output.
Evidence visible: source provenance and freshness context stay close to consequential guidance.
Privacy by default: guest use comes first, and resident inputs are kept to the minimum a workflow requires.
Official handoff: ATX Untangled helps residents prepare and navigate; the responsible agency remains the authority for submissions and decisions.

Public boundary

The live product is public. Its source code, operating systems, and resident feedback remain private so the portfolio can show the product judgment without exposing implementation or user information.

ATX Untangled

Intended operating outcomes

A useful next step

Source-backed guidance

Guest-first by design

Leadership layer

Architecture evolution

The operating problem

Product principles

Public boundary

Let's talk about the operating constraint.