Galaxy / Hubble

One report library, two audiences

Pierre Byrne Designs

Before and after — reports scattered across Tableau, Looker, Workbench and email, then one governed catalog

At Surescripts, reports were spread across Tableau, Looker, an internal Workbench and email. Every tool had its own login and its own search, so the same report could live in more than one place, and nobody could tell which version was the right one.

Staff kept asking, “Which of these is the right one?” Clients kept asking, “Where is last month’s report?” Both questions had the same cause: a report had no single home.

Galaxy and Hubble were the answer to that. Galaxy is for staff. Hubble is for clients. Both sit on the same source.


Before and after: reports scattered across tools, then one governed catalog in front of them

One catalog in front of every tool, instead of hunting through scattered links.

Galaxy: one catalog for staff

Galaxy opens on what moved, not on a wall of links: a watchlist of the numbers each person follows, beside the signals that changed. Search returns reports from every tool in one list. Open a report and the things that make it trustworthy sit right next to the number: who owns it and how it’s defined, with help attached.


Galaxy report catalog: a search for prior auth returns reports from Tableau, Looker and Workbench in one list

One search across every tool. Sample data.

Ask Stellar answers questions in plain language. It only draws on certified reports the person can already see, and every claim carries a numbered citation back to the report it came from.


Ask Stellar answering a question about prior auth turnaround, with numbered citations to four certified reports

Answers that show their sources. Sample data.

The rules behind the catalog

  • One search returns reports from Tableau, Looker and Workbench in one list.

  • Every report names who owns it and what its numbers mean.

  • Search shows only approved reports, so the version people find is the certified one.

  • Staff see everything they’re allowed to see. Clients only see their own reports.

Hubble: the same front door for clients

Clients need their own organization’s data, written for readers who may not be analysts. The reconstructed Hubble view gives them the same front door, scoped to their organization, with a plain-language summary at the top of each report.


The same prior auth report shown in Galaxy for employees and in Hubble for clients

Same source, rewritten for each reader.

One report, different reading depths

The reconstruction makes a specific design decision visible: keep the report as the shared reference and change the surrounding context for each audience. Galaxy puts sources and definitions close to the number; Hubble scopes the view to one organization and leads with a plain-language summary.

Using the same report in both views makes the audience difference visible. A reader can compare the surrounding explanation without having to compare unrelated examples.

My part

I was the product designer, and I also acted as the product manager. I led and facilitated the design and development of Galaxy, directed the design team through the whole build, built reports where they were needed, checked code, and ran UAT every day. For Hubble, I designed the architecture and the system, and set its direction.

Testing became a checklist everyone could see. Every requirement was checked at every stage, from development through QA and UAT to release, and every problem was logged against the requirement it affected. The prototype ended up as the standard the real build was checked against.

About these screens

The screens recreate historical project work with synthetic names and numbers. Source badges and trust cues were expanded for this portfolio reconstruction; the recreated Stellar answers also include citations. These additions illustrate design reasoning and do not establish which features shipped or any measured outcome.

From the case study

0