Report Library
Helping people find, trust, and reuse reporting content.
Report Library at a glance
Where practices find, understand and reuse reporting content: legacy reports, new reports, templates and their own saved reports, in one place inside the product.
Outcome. RITE testing supported the core workflow; the design was being deployed for launch when I left.
- 12
- customer-facing participants in discovery
- 15
- end users in RITE testing
- 4.0/5
- self-rated task completion
- 3
- lifecycle scenarios tested

My roleDesign lead and sole designer · Led research and experience direction · Ran RITE testing with 15 users · Created the MVP-to-full roadmap, prioritised with Product in a workshop I ran
A search problem reframed
Research showed people found reports but couldn’t trust them, so they made new ones, which made the library harder to search.
Enough context to choose
Descriptions, metadata and query context help people judge a report before running it, so reuse beats re-creating.
Priorities tied to principles
I ran the MVP workshop: features grouped by four experience principles and weighed on research signal, frequency and complexity.
Full case study
Problem
People could find a report and still be unsure it was the right one. Creating another report sometimes became the workaround, making the library harder to navigate.
Context
Legacy and newer reports coexisted in a mature catalog. The redesign needed to make that inventory understandable without asking customers to learn the underlying platform.
Explore the context
Reporting at athenahealth was embedded inside the main product customers used every day. Users didn't navigate to a separate destination — they accessed reporting from within the product they were already working in.
The ecosystem was mature. Legacy reports on an older data foundation coexisted with newer reports on a modernizing data platform. Customers depended on both. Reporting had accumulated across years of releases, and the surface for finding, understanding, and using that content — the Report Library — had accumulated with it.
The design brief for Report Library 2.0 was not to replace the ecosystem. It was to build a coherent access layer across the transition — one that let customers find, understand, and manage reporting content at the scale it had reached.
Role
I was the design lead and sole designer. I led research, experience direction, interaction design and RITE testing, and I created the product roadmap: iterative development from an MVP to the full product, prioritized with Product in a workshop I ran, with the PM holding final approval.
Read ownership details
My role and ownership
Lead UX/UI Designer, sole designer on Report Library. Product ownership sat with Product Management. My role went beyond receiving requirements — research, problem framing, experience direction, RITE-based validation, and MVP prioritization all flowed through my design work. My manager was a thinking partner and alignment support. One PM owned the broader analytics space, of which reporting was one part.
Report Library 2.0 was a full UX rebuild. Enhancements continued in parallel on the legacy 1.0 experience.
Process
I explored three concepts with 12 customer-facing participants, reframed the brief around the reporting lifecycle, and tested the direction with 15 end users. A cross-functional workshop translated the principles into MVP priorities.
15 RITE participants · Three lifecycle scenarios · Core workflow supported
Explore research and validation
The problem, as first framed
The initial framing was straightforward: a large, aging reporting library with weak search, accumulated categories, and users complaining about the friction of finding things.
The natural design problem was better search, better filters, better metadata. Ship a redesign that made finding a report easier. It sounded like a well-scoped project.
It wasn't.
Research changed the problem
Method. I used three early concepts with 12 customer-facing participants to test the framing, rather than validate a predetermined solution.
Finding. Search was only the visible friction. The deeper problems were confidence in choosing the right report, returning to frequently used content, and completing recurring work across reports, schedules, and outputs.
Decision. I reframed the brief from improving search to supporting confident discovery, reuse, and management across the reporting lifecycle. That decision shaped the four experience principles, the design direction, and the RITE scenarios that followed.
A counter-intuitive systems insight
Research surfaced a loop: when people couldn't find or trust a report, they made a new one. That made the library bigger and harder to search, which led to even more new reports. So the fix was not easier creation; it was easier finding and reuse.
The most useful thing the research produced was an observation I would not have arrived at from behavior data alone.
When users couldn't confidently find or trust an existing report, they sometimes solved the immediate problem by creating another one. A one-off ad-hoc report. A saved query. A quick copy-and-modify. Sensible for the individual user. At scale, a problem.
Each new report made the library larger. A larger library was harder to navigate. Because it was harder to navigate, users had more reason to create new reports rather than search through the existing ones. Because there were more new reports, the library grew larger still.
The loop reinforced itself.
The design implication changed the shape of the work. Making report creation easier would worsen the underlying problem, not solve it. The work had to reduce the friction of finding and confidently reusing existing reports so that the incentive to create new ones dropped. Not by blocking creation — users had legitimate custom needs — but by removing the pressure that made creation the easier path to what were, in many cases, reuse problems.
Discovery, comprehension, and lifecycle became joint problems, not separate ones.
Four experience principles
The design surface was broad — search, categorization, metadata, faceted filtering, sorting, descriptions, favorites, pinning, scheduling, admin governance. A feature-by-feature prioritization conversation wouldn't have held together.
I organized capabilities around four experience principles so stakeholders could reason about why different capabilities mattered before deciding which belonged in the MVP.
Familiarity
Users had built years of muscle memory with the reporting product. Modernization did not require unlearning what already worked. Preserve what users understand where it works; redesign what creates friction.
Transparency
Finding a report by name did not mean users knew it was the right report. The design needed to expose enough — description, metadata, ownership, underlying query configuration — for users to judge relevance before running.
Personalized Organization
Different users cared about different subsets of a very large inventory. Help users organize and return to the content that mattered to them — not organize the library as if there were one canonical taxonomy that fit everyone.
Predictable Lifecycle
Reports do not end at creation. Consider what should happen to a report over time — creation, use, reuse, scheduling, retrieval, management, housekeeping, archiving, governance.
These were not a formal, company-endorsed framework. They were how I organized the design conversation, and they later held up as a way to structure the cross-functional MVP prioritization workshop.
RITE validation
RITE testing with 15 end users confirmed the core Report Library workflow and mental model. Participants who rated their completion of the whole task on a 1–5 scale averaged 4.0: four rated it 4, two rated it 4.5 and one rated it 3. It surfaced refinements around terminology, metadata, permissions and report identification, plus some more exploratory concepts, rather than invalidating the core workflow.
RITE covered three scenarios that together tested more than any single-screen redesign would have.
Scenario 1 — Find, understand, and run a report
Users could locate the target report. The more interesting behavior wasn't where they clicked — it was what they relied on to confirm they had the right report. Description, metadata, and query configuration mattered as much as location. Search behavior showed users expected forgiving retrieval: they used terms like "denial" and expected relevant reporting content to surface, rather than remembering exact report titles.
Scenario 2 — Scheduled reporting lifecycle
Not just creating a schedule. Configuring a recurring report with recipients. Locating the resulting scheduled report. Accessing the most recent result through the Inbox / result experience. Downloading it. Returning to manage the schedule, including pausing it. The moderator probed users' expectations for where edit and delete controls should live. The design treated scheduling as an ongoing relationship among three objects — report, schedule, and generated output — not as a one-time action.
Scenario 3 — Housekeeping and governance
Users identified stale or potentially unused reports using signals such as ownership, last accessed/run, and modified/updated timestamps. Follow-up questions moved into generative territory: how should administrators handle stale, orphaned reporting content? What signals do they need before taking action? RITE wasn't used only for UI validation here — the session became an opportunity to deepen understanding of the reporting lifecycle.
Retrospectively, the three scenarios fit a lifecycle framing:
Discover → Understand → Run → Schedule → Retrieve → Manage → Govern
This framing was not something the team formally named at the time. It's a retrospective synthesis. That the framing holds up in hindsight is itself evidence that the redesign was doing lifecycle work, not screen work.
Validation happened through RITE usability testing with 15 end users — a largely fresh cohort, with only one participant overlap from the earlier customer-facing participants who had joined the generative research. Different research phases benefit from different participants: discovery benefits from breadth of perspective; evaluation needs the actual users.
Validation summary. Across the three task scenarios, participants completed the core workflows and interpreted the experience consistently. RITE exposed issues in terminology, action discoverability, hierarchy, metadata, and control placement; these were refined during the study without requiring a conceptual redesign.
The evidence supports usability of the overall direction. It does not establish that every proposed capability was fully validated or ready for implementation.
Key Decisions
- Support reuse, not only search. Descriptions, metadata, and query context helped people judge whether a report answered their question.
- Preserve familiar browsing. Keep the table/list foundation while improving discovery and organization.
- Separate quick access from saved collections. A small pinned set addressed frequent use; Favorites remained the broader collection.
- Prioritize user value. Use experience principles, research signal, frequency, and complexity to make MVP trade-offs explicit. Priorities were agreed collaboratively.
Explore designs, alternatives, and trade-offs
Design direction
Report Library 2.0 became a full UX rebuild of the discovery and access layer. The interaction foundation was preserved where users had strong prior mental models (the table/list foundation for browsing a large inventory). Behavior around discovery, comprehension, personalized organization, and lifecycle was substantially redesigned.
Findability. Stronger information architecture and category-based browsing. Faceted filtering across Type, Owner, and Tags — within-facet OR (multiple selections in the same facet broaden results) and cross-facet AND (selections across facets narrow results). Improved sorting and grouping across the report list.
Comprehension. Report descriptions and richer metadata surfaces (owner, last-run, tags). Query configuration exposed so users could evaluate what a report contained before running it.
Frequent-use access. Constrained pinning — up to approximately six reports pinned to the left navigation for immediate access. Distinct from the broader Favorites collection, which was preserved.
Lifecycle. Scheduling improvements including recipients configuration. Retrieval of scheduled outputs through an Inbox / result experience. Admin capabilities for identifying stale content, archive/housekeeping policies, and lifecycle governance.
Acceptance criteria
I translated each experience principle into observable acceptance criteria so the team could evaluate whether the experience worked—not merely whether the feature existed. The criteria guided RITE iteration, MVP prioritization, and engineering handoff.
Reconstructed at the level of intent, not the exact wording of the working document.
| Principle | The design is "done" when… |
|---|---|
| Familiarity | Users familiar with the previous library can locate and run a report without new training on interaction patterns. |
| The table/list foundation for browsing is preserved where the existing mental model already works. | |
| Transparency | A report's description, owner, and last-run are visible before a user opens it. |
| Query configuration is exposed on the detail surface so a user can judge relevance before running. | |
| Personalized Organization | A user can pin up to ~6 frequent-use reports to the left navigation, distinct from the broader Favorites collection. |
| Faceted filtering (Type / Owner / Tags) narrows the library across dimensions users actually care about, with within-facet OR and cross-facet AND behavior. | |
| Predictable Lifecycle | A scheduled report can be created with recipients, its most recent output retrieved through Inbox, and its schedule edited or paused from a predictable location. |
| Admins can identify stale reporting content using ownership and last-run signals, and take action within existing governance flows. |
Reconstructed acceptance-criteria structure — not an original artifact. Reproduced at the level of intent; the exact wording and edge cases from the working document are not preserved.
MVP prioritization
I structured and facilitated a cross-functional workshop around the four experience principles. I presented the feature list grouped by principle (Familiarity, Transparency, Predictable Lifecycle and Personalized Organization) and asked Product to mark the three most important features in each group. Those choices shaped the MVP, and I built the roadmap from the MVP to the full product around them.
My contribution. I created the roadmap from MVP to the full product, and brought the research-backed framework, user-story detail and design judgment behind it. The PM held final approval.
The framing shift was deliberate:
From: "Which features do we want?"
To: "Which value areas must the MVP adequately support?"
The framework I brought to the room
I opened the workshop with a working matrix. Capabilities were grouped by which of the four principles they served; each was weighed on the research signal supporting it, expected user frequency, and implementation complexity. The point wasn't the numeric roll-up. It was a structured surface where trade-offs became visible instead of implicit, and where a decision to defer wasn't a rejection — it was a claim about which value areas the MVP had to adequately cover before it earned the right to ship.
| Capability | Serves | Research signal | Expected frequency | Complexity | MVP status |
|---|---|---|---|---|---|
| Category browsing | Familiarity | Strong | Daily | Low | Included |
| Faceted filtering (Type / Owner / Tags) | Familiarity, Personalized Org | Strong | Daily | Medium | Included |
| Report descriptions | Transparency | Strong | Every use | Low | Included |
| Query configuration preview | Transparency | Strong | Every use | Medium | Included |
| Pinning to left nav | Personalized Org | Strong | Daily | Low | Included |
| Favorites | Personalized Org | Moderate | Weekly | Low | Preserved |
| Schedule with recipients | Predictable Lifecycle | Strong | Weekly | Medium | Included |
| Inbox / result retrieval | Predictable Lifecycle | Strong | Weekly | High | Included |
| Schedule management (edit / pause) | Predictable Lifecycle | Moderate | Weekly | Medium | Iteration 2 |
| Stale content detection (admin) | Predictable Lifecycle | Inferred | Monthly | High | Iteration 2 |
| Archive & housekeeping policies | Predictable Lifecycle | Inferred | Monthly | High | Deferred |
| Lifecycle governance workflows | Predictable Lifecycle | Inferred | Rare | High | Deferred |
Reconstructed prioritization matrix — not an original artifact. Values are directional (Strong / Moderate / Inferred; Low / Medium / High), not precise scores. This is the shape of the framework I brought to the workshop; the exact numbers, weightings, and disagreements from the room are not preserved.
I created the product roadmap: iterative development from an MVP to the full product. The PM held final approval, and prioritization was worked through together with Product. Alongside the roadmap I contributed the framework that structured the conversation, the user-story-level detail that translated the direction into scoped work, and the design judgment on what needed to hold together for the experience to remain coherent.
Outcome
RITE supported the core workflow and mental model. Refinements focused on terminology, metadata, permissions, and report identification. The experience was being deployed for launch when I left; I can’t confirm the launch itself, so no production impact is claimed.
Read outcome details
Strategic exploration
I also questioned whether Report Library should remain the top-level destination as the analytics platform evolved, or become one layer within a broader insights experience.
I raised the question, discussed it, and sketched around a broader hub model rather than protecting the Report Library direction because I had invested in it.
This was strategic exploration—not an approved organizational strategy. It was neither endorsed nor built before I left the team.
Lessons
- Investigate the workaround behind a feature request.
- Design for discovery, reuse, scheduling, retrieval, and maintenance together.
- Connect research to priorities through clear experience principles.
Read more reflections
What I took from this work
- Investigate the behavior behind the request. New-report creation could signal a discovery and confidence problem, not simply demand for more creation tools.
- Design for the lifecycle when content accumulates. Discovery, reuse, scheduling, retrieval, maintenance, and governance are connected.
- Use principles to connect evidence to priorities. They helped the group protect user value while deciding what belonged in the MVP.
- A prototype becomes delivery evidence when paired with criteria and priorities. The handoff connected the validated experience to implementation decisions.
- Questioning scope can be more valuable than defending a solution. Strong design judgment includes reconsidering the level at which the problem should be solved.