Skip to content
Sumio

Use case

I went for quick wins instead of a redesign of the journey.

On La Ruche qui dit Oui !, each Hive sells in cycles. A sale closes, and the Hive Host has to open the next one. In between, Members can't buy anything. I led the research that explained these gaps, then turned it into product decisions shipped fast.

Company
La Ruche qui dit Oui !
Role
Senior Product Designer
Team
Data Analyst
Tools
Figma, Notion, Typeform
Period
2024

18%

more baskets created across the network

72%

conversion on those baskets

The context

Too many Hives went several days without an open sale. The Hive and the platform lost revenue. Some Members dropped off too, new ones especially, who found the Hive closed just when they wanted to buy.

With the data, I measured the problem first. On average, 32 hours went by between two sales. That’s 42 closed days per Hive per year. One Hive in four let more than a day slip.

My role

I scoped and ran a four-week study with a data analyst. I ran five interviews with Hive Hosts of all kinds, and watched one of them prepare a sale. A survey then collected 123 answers.

Launching a sale takes time, in small repetitive actions. Hosts don’t know which producers will be available. And 40% of them don’t see what a closed sale costs Members.

I shared these findings with every team before deciding anything.

The key decision

Each idea went on an effort / impact matrix, and we started with the cheapest ones.

The effort / impact matrix used to pick the first actions

Launching a sale got lighter. The platform suggests products to feature and offers message templates. Producer availability shows up in a calendar. The Statistics view now shows the revenue lost, and a new open-sales rate.

Suggested featured products while preparing a sale

What it changed

Baskets created went up 18% across the network, with 72% conversion on those baskets. No redesign, just targeted changes.