LeadDyno Purchases reporting dashboard with an Export to CSV panel, on a soft blue and mint glass background

Redesigning reporting to reduce churn

When managers couldn’t see how their affiliate programs were performing, they stopped seeing a reason to stay, and churn crept up month over month. As the UX designer on a phased reporting overhaul, I worked with product and engineering to scope and ship an MVP that gave managers the data they needed. It eliminated the support backlog for report exports, and the team expected it to cut the churn rate by up to 11%.

Role

  • UX Design
  • UX Research
  • UI Design support

Team

  • GM/PM
  • Project manager
  • 3 engineers
  • UI designer
  • Support agent

Methods

  • User interviews
  • Survey
  • Concept testing
  • Wireframing
  • UI design

Timeline

  • Phased rollout
  • Q2'22 – Q4'23
Solution

Performance at a glance, details on demand.

One dashboard shows overall purchases alongside affiliate-specific transactions, each split by source with the change from the last period. Purchase attribution lives in a table managers can search, sort or export themselves, no ticket required.

01

Purchase summary

Two cards surface total revenue and affiliate-driven revenue side by side,  changing dynamically to the selected date range.

Close-up of the redesigned Purchases summary cards: All Purchases 7,824 and All Sales $10,916, each split into Affiliate, Campaign and Other with share bars and change since the last period

02

Trends over time

One chart overlays total purchases and sales with their affiliate-driven counterparts, so the program’s contribution is always visible in context.

Redesigned Purchases trend chart for 08/10 to 08/16/2022: lines for overall and affiliate purchases, with stacked bars for overall and affiliate sales on a second axis

03

Self-serve export

Exports used to mean a help desk ticket. Now it lives in the Purchases table and opens pre-filled with the screen’s date range.

Recent Purchases toolbar with search and an Export to CSV button, above the SKU, affiliate, source, amount and status columnsExport to CSV modal open over the Recent Purchases table, with the date range pre-filled to 08/10/2022 – 08/16/2022, Purchases and Source dropdowns set to All, 18 export fields checked, and an Export Purchases button
Impact

Better data changed things for everyone.

Program managers finally had what they needed to run their programs with confidence. Support reclaimed time that was going toward manual data pulls. And for the business, a feature that was driving cancellations became something customers pointed to as value.

For program managers

No more guessing

Managers had a clear view of how their program was performing and could pull the data they needed on their own.

For the business

Close the churn gap

Closed a top churn driver and gave support and engineering time back that was going toward manual data pulls.

For support

A cleared queue

Exports stopped routing through the help desk, freeing the team for problems that needed a person.

“This is so much more than I envisioned.”

- Affiliate program manager, beta user

Problem

Churn was creeping up month over month.

The Purchases screen gave managers a line graph and not much else. They couldn't export their data or see how individual affiliates were performing, so they kept asking support to pull it for them. The backlog grew, and managers who couldn't prove the value of the platform were the ones most likely to leave.

The legacy Purchases screen with a line graph of purchases over time and no way to export or drill into the data
Discovery‍

Where frustration was loudest: the help desk.

The support tickets told me who to talk to, the interviews helped me understand why they were frustrated and what they needed, and an in-app survey told me how widespread it was. Each step set up the next.

Help desk tickets

The support team had already noticed a pattern with reporting complaints. I filtered tickets for data and reporting issues, looked for recurring themes, and used that list to recruit interview participants.

User interviews

I designed and led five moderated interviews end to end. I wrote the script, built the screener, did outreach, scheduled sessions, and moderated with my PM taking notes. Participants were segmented by account age, support ticket history, and annual revenue generated through the platform.

In-app survey

While interviews were running, I put a single intercept survey question on the old reports page to pressure-test what I was hearing. We ran it until we hit around 100 responses. The results confirmed that reporting frustration wasn’t isolated to the users we interviewed.

“Reporting, reporting, reporting. It will change the world.”

— Matt, Affiliate program manager

Exploration

Designing around the right questions

The reporting suite spanned 8 screens. Working with the PM, I mapped each screen to a core question, pairing KPIs, metrics, and actions a user would need to be able to answer questions about their program performance.

How much revenue are my affiliates generating?

Purchases report wireframe beside its planning notes: the key question, main and supporting KPIs, supporting metrics, and user actions

Anchoring design decisions to a single question kept each screen focused and prevented scope creep. Throughout the process, I kept engineering and design counterparts in the loop, running team reviews to pressure-test the feasibility of each data point. Those reviews are where the screens took their final form.

Tradeoffs‍

Aligning on what the MVP needed to be.

Our early concepts were ambitious. Six KPIs bucketed into a configurable chart, a Top Affiliates leaderboard, and full filtering capabilities. But after working closely with engineering and product to gut-check viability and effort, we made a deliberate call: ship the version that answered the core question and roadmap the rest. Three constraints shaped what made the cut:

Engineering cost

The full feature set was too much to build and ship in a single release.

Beta Risk

Less complexity meant less that could go wrong in beta.

Scope

Shipping the core first let us validate before investing in the rest.

Original Purchases wireframe beside the shipped screen. Six KPI tiles became two summary cards, the configurable chart became a fixed purchases and sales chart, Top Affiliates moved to its own screen, and the filter panel with its applied-filter chips was deferred.

Hover or tap to Highlight

KPIs

Simplified from six options to two cards split by source

Trend chart

Fixed to purchases and sales instead of a configurable axis

Top Affiliates

Moved off the Purchases dashboard and into the Affiliates screen

Filters

Deferred to the roadmap until core usage was validated

Reflection

In hindsight

Do differently

Map data before mapping screens

I’d spend more time upfront working through what data we actually had, what was missing, and what was buildable. Information architecture for reporting isn’t just about layout. It’s about knowing what you can promise the user before you design it.

Do again

A linear process is rare

Research led directly into strategy, which led into product roadmap. That rarely happens. It did here because the team trusted the process and gave me room to shape it. That’s something I’d try to protect on every project going forward.

Do again

Keep the feedback loop

Export generation could take time depending on report size, and async delivery wasn’t feasible. So we designed a progress state that kept users oriented while they waited. Technical constraints don’t always mean a worse experience. Sometimes they just mean a different design problem.