Aerial view along the 110 freeway as it runs through dense Los Angeles neighborhoods toward downtown, with mountains behind

Los Angeles is home to many distinct communities, each with its own story in the data. Photo: Jon Tyson / Unsplash

ACT Data Hub

Designing a path from a community question to evidence a decision-maker will accept.

Context
UCLA, All Children Thrive – California: 14 community coalitions
Role
Research, information architecture, interaction design, build
Team
Sole designer; a student worker prepared map layers
Timeline
Spring 2025 – spring 2026
Methods
Moderated usability testing, information architecture, prototyping
Tools
ArcGIS Hub, Experience Builder, StoryMaps, HTML and CSS with Esri's Calcite components

Context

All Children Thrive – California supported community coalitions working on housing, homelessness, education, environmental conditions, youth spaces, and other conditions affecting children and families. Each coalition chose its own questions and policy goals, usually with a decision date ahead: a council vote, a funding meeting, a report.

I worked in UCLA's data technical-assistance program, helping coalitions turn those questions into evidence. Session after session went to finding individual variables and rebuilding basic maps. Little time was left for what mattered: what the data could support, what it couldn't, and how to make the case.

The resources already existed. They were scattered, named in technical terms, and organized the way data teams organize data. I proposed one hub where teams could explore on their own and bring better questions to our sessions.

First version

I started where most data portals start. In spring and summer 2025 I built the Hub around types of data product: a searchable catalogue of datasets, StoryMap guides organized by data category, and a separate section for mapping tools. Hub pages don't run JavaScript, so I built the pages in HTML and CSS with Esri's Calcite components.

By fall I had added entry points on the homepage for the deliverables teams were working on ("I'm working on a needs assessment"). Underneath, the three sections hadn't changed, and the catalogue was still the most prominent way in.

Testing

In October 2025 I tested the Hub with 5 staff members from 3 funded projects, in facilitated sessions of 45 to 60 minutes. Each brought a question from their own project, and I asked them to find relevant information, interpret it, and decide how they would use it.

0 of 5completed the core tasks without help
5 of 5started in the catalogue and got stuck
4 of 5couldn't work out how to combine indicators
“There's a lot of tabs… when you see something for the first time, it could be a little bit overwhelming.”
“How would you bring those into one combined map to demonstrate the interplay of those factors?”
Participants, October 2025 testing

But the parts worked once people reached them. Every participant understood the guide to combining indicators as soon as they saw it, the community context maps drew the strongest reactions, and people asked for more step-by-step guidance, not less. The problem wasn't capability. Each part of the Hub was an island.

ACT Data Hub structure, before and after testing Before: three separate sections organized by data product (a data catalogue, guides by data category, and standalone tools), with deliverable entry points layered on the homepage. Each section was a dead end. In October 2025 testing, none of five participants completed the core tasks without help. After: one connected flow from find and explore, to understand and apply, to communicate and share, with a next-step prompt at each transition and a prompt back to combining before storytelling. ACT DATA HUB · INFORMATION ARCHITECTURE From separate sections to one connected flow BEFORE · ORGANIZED BY DATA PRODUCT Deliverable entry points on the homepage, sections unchanged underneath Data catalogue Search by topic, geography, provider Category guides StoryMaps by data category Tools and apps A separate section Each section was a dead end: finding a variable led nowhere, and a guide didn't link to its map. Testing, October 2025: 0 of 5 participants completed the core tasks without help AFTER · ORGANIZED BY THE WORK A next step at every transition 01 Find and explore Combined exploration map 02 Understand and apply Guides, combining indicators 03 Communicate and share StoryMaps resources What's your next step? Ready to communicate? Have you combined your indicators yet? Entry for newcomers: "New to community data analysis? Start with Understanding Your Data."
ACT Data Hub structure, before and after testing Before: three separate sections organized by data product, each a dead end. In October 2025 testing, none of five participants completed the core tasks without help. After: one connected flow from find and explore, to understand and apply, to communicate and share, with a next-step prompt at each transition. ACT DATA HUB · STRUCTURE From separate sections to one connected flow BEFORE · BY DATA PRODUCT Data catalogue Category guides Tools and apps Each section was a dead end. Testing, Oct. 2025: 0 of 5 completed the core tasks without help AFTER · BY THE WORK 01 Find and exploreCombined exploration map What's your next step? 02 Understand and applyGuides, combining indicators Ready to communicate? 03 Communicate and shareStoryMaps resources Prompt back before storytelling: "Have you combined your indicators yet?"
The Hub's structure before and after testing. Each section was a dead end; the redesign connects them in the order people work.

Redesign

I reorganized the Hub around the work instead of the data: find and explore, understand and apply, communicate and share. Each decision traced back to something I'd watched happen.

Hub homepage: a pointer for newcomers above three paths, Explore Community Data, Learn to Combine Data, and Communicate Your Story
The homepage after the redesign. Three task paths replace six to eight equal options, with one pointer for newcomers.
After exploring the maps A What's Your Next Step panel offering Understand What Data Means or Combine Multiple Indicators
Combining indicators Four steps for combining indicators: identify, overlay, analyze, validate
Before storytelling Before you start: Have you combined your data indicators yet? with a link to learn how
Prompts at each transition in the live Hub. Each one points to the next step, or back a step if one was skipped.
An analysis guide in the Hub: behind, a combined map of Los Angeles with school results over neighborhood conditions under the heading Look for patterns and exceptions; in front, What should you ask before sharing a claim, with five numbered questions
An analysis guide in the live Hub: the combined map of school results and neighborhood conditions, then the questions to ask before sharing a claim.

Results

In spring 2026 the project's Equity Advisory Group reviewed the redesign and how the guides were framed for non-technical users; their feedback was minor. Then I ran a final round of 30-minute tests with four project staff who hadn't taken part in October. The tasks matched the first round, and I gave no help beyond validating testers' comments.

4 of 4completed the full path, from exploring to communicating
14coalitions had access to the Hub
5active teams kept using it after testing

I didn't instrument the Hub, so these are observations from sessions rather than measured changes.

The Hub homepage behind the combined exploration map: the share of children by census tract from South Los Angeles to Orange County, with a tract's popup reporting 892 children and 26.5 percent of them below the poverty line
The combined exploration map in the live Hub, at census-tract level with one tract open. It became the way into the Hub and its most-used component.

Reflection

The ACT program closed in 2026. I documented the Hub's information architecture, production routines, and guides so they don't depend on the public site staying up.