All work

Finding the Right Problems to Solve

Choosing small enhancements for big impacts.

Company

Movable Ink

Role

Senior product designer

focus

Product discovery, UX research, product strategy, interaction design

year

2022

Movable Ink data-source index and detail screens arranged on a light background.

At Movable Ink, I worked on improving how internal teams monitored and understood the data sources powering personalized marketing campaigns.

At the time, information about data-source performance was largely hidden in backend systems. When something went wrong, customer-facing teams often lacked the context to investigate independently and had to rely on technical specialists.

The opportunity was to make that information more accessible, helping teams move from reactive troubleshooting toward more informed conversations with clients.

But with limited engineering resources and no dedicated product manager, we couldn't solve everything at once.

I partnered closely with our engineering lead to drive discovery, define priorities, and design a focused MVP.

The challenge wasn't figuring out everything we could improve. It was identifying which improvements would create the most value with the resources we had.

The opportunity: Making hidden information accessible

Movable Ink helps brands create personalized marketing experiences using data from connected sources such as APIs and CSV files.

But once those sources were connected, information about their usage and performance wasn't readily available in the product.

When an API connection failed or a campaign stopped receiving expected data, Customer Experience (CX) teams were often the first to hear about it.

Without access to technical performance information, they had limited ability to understand what had happened or which campaigns were affected. Investigating issues frequently required escalating to the Solutions team.

This created friction for internal teams and made it harder to provide clients with timely, informed answers.

Our design challenge: How might we give customer-facing teams the information they need to understand data-source issues without requiring technical expertise?

Leading discovery without a product manager

At the start of the project, we had a broad vision: give teams visibility into data-source performance and alert them when something went wrong.

But we didn't yet know which information mattered most or how much of the experience we could realistically deliver.

With no dedicated PM, I partnered with our engineering lead to structure discovery and establish a shared understanding of the problem.

We started by documenting our assumptions, then conducted 7 moderated interviews with internal stakeholders across Customer Experience and Solutions.

I led the interviews while engineering partners observed, helping us develop a shared understanding of the user needs and technical constraints.

What we learned

1. "Healthy" meant different things to different people.

Stakeholders had different expectations for what constituted a healthy API connection. Introducing health statuses or alerts would require more investigation before we could confidently define the right behavior.

2. Visibility was more valuable than we initially realized.

Users wanted to know where data sources were being used, when they were last updated, and how they were performing.

3. Technical information needed to be accessible to non-technical users.

CX teams needed enough context to answer client questions and escalate issues more effectively without relying entirely on Solutions.

These findings challenged our initial assumptions about what we needed to build first.


Audit to uncover all the existing painpoints

Decision 1: Prioritize visibility before automation

Our original vision included monitoring, reporting, and alerting.

But the research revealed that we didn't yet have a shared understanding of what should trigger an alert.

Rather than introduce potentially misleading health indicators, we narrowed the scope to something more foundational: making existing data-source information visible and understandable.

We focused on real-time monitoring using data the Solutions team already had access to, without attempting to define health thresholds or historical reporting.

This allowed us to address an immediate user need while reducing engineering complexity.

The decision also gave us a clearer foundation for future capabilities, including reporting and alerting.

The shift: From building a comprehensive monitoring system to making the most valuable information accessible first.

Exploring the experience

With a more focused direction, I began exploring how to improve the existing Data Sources interface.

The original experience relied on a dense table containing multiple data-source types. Users could see basic information, but it was difficult to understand performance or identify where a source was being used.

I explored ways to introduce additional context without overwhelming the page.

This included:

  • Surfacing campaigns associated with each data source.

  • Introducing API performance metrics.

  • Showing when sources were last updated.

  • Improving how users navigated between the list and individual source details.

I also explored expandable rows and drawers as ways to reveal more information when users needed it.

The goal was to balance quick scanning with the deeper context required for troubleshooting.


Early exploration

Decision 2: Learning that simpler isn't always better

I tested the initial concepts with four CX directors, evaluating both usability and satisfaction.

The first iteration received:

70% usability · 84% satisfaction

Stakeholders were excited about having greater visibility into API performance and understanding which campaigns depended on each data source.

But the usability score revealed that some of the technical metrics were difficult for non-technical users to interpret.

I responded by simplifying the experience, removing API performance metrics and focusing on active campaigns and recent updates.

When I tested the second iteration with four additional stakeholders, the results surprised me.

65% usability · 76% satisfaction

Despite removing complexity, both scores declined.

This challenged my assumption that reducing the amount of information would automatically make the experience easier to use.

After revisiting the feedback, I realized that while campaign visibility was valuable, it wasn't enough on its own.

Users needed to understand both where a data source was being used and how it was performing to make informed decisions.

By removing the metrics, I had simplified the interface but also removed part of the context that made it useful.


Finding the right balance

The research helped clarify which capabilities were essential for the MVP.

We aligned around three priorities:

Active campaigns

Help users understand which marketing experiences depend on a particular data source.

Last updated

Provide visibility into recent changes so teams have more context when investigating issues.

API performance metrics

Give CX teams access to information that helps them understand performance and communicate more effectively with clients and Solutions.

Other improvements, including advanced filtering, historical reporting, and automated alerts, remained opportunities for future iterations.

This wasn't simply about reducing scope. It was about preserving the information users needed to accomplish their goals while removing functionality that wasn't yet essential.

The refined experience

The final design direction introduced a clearer Data Sources index and a dedicated details experience.

The index made it easier to scan data sources, identify relevant information, and navigate into a specific source.

The details page brought together source information, performance metrics, usage, and configuration details in one place.

Rather than asking users to interpret technical information scattered across different tools, the experience aimed to give them a more complete picture of what was happening and where to investigate.


What we validated and what's next

Through discovery and two rounds of usability testing, we narrowed a broad product vision into a focused MVP informed by actual stakeholder needs.

The research established that visibility into active campaigns, recent updates, and API performance was valuable to customer-facing teams.

It also revealed an important tradeoff: reducing information doesn't necessarily improve usability if that information provides essential context.

At the time of this case study, the experience was moving toward development. The next step was to validate its impact through real usage, including whether it reduced unnecessary escalations, helped CX teams troubleshoot more independently, and supported stronger client relationships.

These were intended outcomes, not yet measured results.

What I took away

This project reinforced that good product design isn't about solving every problem at once.

Working without a PM pushed me to take greater ownership of discovery, collaborate closely with engineering, and make thoughtful decisions about what belonged in the first release.

But my biggest learning came from the iteration that performed worse.

Simplifying an interface isn't the same as simplifying a user's job.

The goal isn't always to show less. It's to understand which information matters, why it matters, and how to make it easier for people to use.

That lesson continues to shape how I approach complex product problems today.