Reporting & Analytics at athenahealth
A mature reporting ecosystem, designed to help people find, build, and carry reporting forward.
Business problem
A mature reporting ecosystem had grown across years of releases and changing data foundations.
User problem
Customers needed to find a trusted report, build one when their question differed, and carry useful work forward.
Product problem
Library, self-service creation, and publishing needed to work as one reporting journey.
The reporting journey
Find or create a report, check its context, refine the result, then share, schedule, or publish it.
From a business question to a trusted outcome
People do not experience Report Library, Report Builder, and Publishing as isolated products. They experience one job: getting an answer they can understand, refine, and use.
- 01
“I need to understand what is happening.”
Start with a question
Something in the practice needs attention, explanation, or follow-through.
- 02
“Has someone already answered this?”
Find or create
Reuse a trusted report, adapt one, or begin a new query when the need is different.
ReuseAdaptCreate - 03
“Can I trust what I’m seeing?”
Check the conditions
Understand the owner, freshness, fields, and filters that shape the result.
- 04
“Does this answer my question?”
Inspect and refine
Compare results, change columns or filters, and run again without losing context.
↺ Refine when the answer is incomplete - 05
“How does this become useful to others?”
Act and carry forward
Use the answer, share it, schedule it, publish it, and maintain it as needs change.
Key Decisions
- Support confident reuse. Treat discovery, understanding, and lifecycle management as connected problems.
- Keep reasoning in context. Let users configure a query and inspect its results together; refine the denser workspace through testing.
- Organize publishing around the report. Bring technical actions into one report lifecycle, with detailed choices developed alongside engineering.
Focused case studies
Each story stands on its own. Read them together for the ecosystem view; pick one to see a specific dimension of the work.
Report Library
From better search to confident discovery, reuse, and lifecycle management. RITE-validated; in deployment when I left.
Report Builder
Configure, preview, and refine in one workspace. A validated interaction pattern adapted through the Sigma platform shift.
AI explorations
I explored three AI concepts: interpreting a report, describing the report you need, and keeping the library healthy. All three were in the Report Library RITE prototype, where participants said they addressed major pain points. They were later deprioritized; nothing here is presented as shipped.
Outcomes
- Report Library: Core workflow supported in RITE; the experience was being deployed for launch when I left.
- Report Builder: Drill-down and saved-query entry points shipped; the standalone builder followed.
- Publishing: Proposal and prototype informed engineering review and next-step planning; not shipped or user-tested.
Outcomes differ by workstream. No measured adoption, engagement, or resource savings are claimed.
Lessons
- Investigate the workaround behind a feature request.
- Design for the reporting lifecycle, beyond creation.
- Share mental models while allowing domain differences.
- Carry validated design intent through platform changes.
Additional stories in the cluster
One additional story is scoped but not yet published:
- Designing Through a Platform Shift — a shorter Thinking piece on adapting the reporting experience when the underlying analytics platform strategy changed. Touched on briefly in the Report Builder and Publishing case studies; deserves its own treatment.