SaaS · Marketplace Hub
B2B · B2B2C
2023
SaaS · Marketplace Hub
B2B · B2B2C
2023

When information density

becomes the problem

When information density becomes
the problem

A full redesign that reduced screen scroll by 91.5% for an average client, and what I learned doing it as a junior designer.


role

Product Designer (sole designer)

timeline

~4 months, 2023

platform

Desktop SaaS — Marketplace Hub

team

PM, PO, Developers, Designer

Due to the nature of the project, some information has been omitted or modified to preserve confidentiality.
CONTEXT

A product built without design

This was my first significant redesign as a sole designer. I'm including it not because it's my most complex work, but because it shows where my thinking started, and what I'd do differently now.

The Hub had been built entirely by developers, shaped over time by client requests added one by one. It was functional. It was also bloated: features accumulated without a clear vision of what the product should be, including entire sections that nobody used. And as the product grew, it stopped scaling well.

Nobody had ever asked what the experience should feel like. I was the first designer to work on it.

It started with mapping the existing product through a full flow diagram in my first weeks at the company, understanding what existed, what was used, and what wasn't.


Two months into the company, I ran the first structured discovery process the team had ever done. I wrote the research script, recruited participants, conducted qualitative interviews with active Hub users, and worked with the PM and PO to translate those insights into the product backlog.

the problem

Too much information, no hierarchy

The product management screen had a fundamental problem: everything was visible at the same time.

Every product variation, every sales channel, every configuration field competed for attention on a single continuous scroll. For a store with multiple products, each with multiple variations listed across multiple marketplaces, that meant navigating thousands of pixels of information to complete a single task.

It wasn't just slow. It was cognitively exhausting for operators doing this repeatedly, every day.

The platform had grown by addition. Every new channel, every new field, every new requirement had been placed somewhere on the screen. Nobody had ever decided what was primary and what wasn't.

The research was scoped to the Hub as a whole, not to the product management screen specifically. As a result, some participants didn't use that flow intensively enough to surface the friction that mattered most.

The learning: when the problem is specific, the participants need to be too.

the DECISION

Primary versus secondary

The solution started with a question I hadn't been asked to answer: what does an operator actually need to see to complete this task?

Not everything on the screen was equally important. Some information was essential to the action being performed. Some was contextual. Some was secondary, rarely accessed and better kept out of the way. That distinction didn't exist in the original interface — everything was primary by default.

One option was a separate detail page for editing. It would have simplified the list view significantly, but it would have forced operators to leave context every time they needed to edit — breaking the flow of a task that required managing multiple items in sequence.

Modals kept the operator in place. That was the deciding factor.

I reorganized the screen around that hierarchy. Variations and channel information were collapsed by default, expandable when needed. Context menus replaced actions that had been permanently visible. The structure supported both individual and bulk operations from the same interface.

Below: the same product, the same channels, the same attributes. Before and after the redesign. The only difference is how much space they demand from the operator trying to manage them.
After
Before
results

What changed in numbers

The redesign introduced collapsible variations and channel information. Operators could expand only what they needed, when they needed it. The impact on screen density varied by scenario, but was consistent across all of them.

Scenario
Before
After
Reduction
1 attribute, 1 channel
524px
32px
~94%
7 attributes, 1 channel
3,740px
304px
~92%
7 attributes, 6 channels (avg. client)
22,623px
1,938px
91.5%

These are interface metrics, not behavioral ones. The platform wasn't data-driven enough at the time to measure task completion time or error rates. I'm reporting what I can measure honestly, not what would look best on a slide.

Post-launch feedback from operators highlighted the reduction in cognitive load and the ability to focus on one product or channel at a time. The bulk action functionality was specifically mentioned as something that changed how they approached repetitive tasks.

Learnings

What I would do differently

This project shaped how I work now. Three things I carry forward from it:

1

Align research scope with design scope

The interviews covered the Hub as a whole. When the redesign focused on one specific screen, some participants couldn't contribute meaningfully. When the problem is specific, the participants need to be too.

2

Define metrics before designing

I had no baseline to compare against after launch. The scroll reduction numbers came from the interface itself, not from user behavior. Defining success metrics before starting is now a non-negotiable part of how I work.

3

Validate before, not after

Usability testing happened after launch. The sprint rhythm made earlier testing difficult, but adjustments that could have been caught in prototype were caught in production instead. I now push for at least one round of testing before implementation, even if informal and fast.

Want to talk about a

product challenge?

Want to talk about a

product challenge?

Create a free website with Framer, the website builder loved by startups, designers and agencies.