New: link a theme to a roadmap item and see what the next release answers.Read the release notes

Skip to content
Meridel

Research

What we learned from our first hundred teams

A hundred workspaces in, these are the four things that surprised us about how small software teams use their feedback.

Ines Varga, Co-founder, product1 min read
A grid of a hundred small squares, a few of them highlighted.

Meridel passed a hundred active workspaces this spring. Most belong to teams of five to fifty people. We looked back at how they set up, what they read and what they changed, and four things stood out.

Sales notes matter more than we expected

We built Meridel around support tickets. But the teams that connected sales-call notes found their largest themes there: requests from people who have not bought yet, which never reach support.

The weekly digest beats the dashboard

Teams open the weekly email four times as often as the dashboard. We now put more into the digest and less into the dashboard’s front page.

Small teams merge themes, larger teams split them

Teams under ten people merge themes into broad ones. Teams over thirty split them into narrow ones that match how their product is divided. Both are right for them, so both are now one click.

Nobody wants a score

We tried a single “priority score” per theme. Every team ignored it and sorted by number of accounts instead. We removed the score.

Thank you to every team that let us look at how they work. If you want to be part of the next round of interviews, get in touch.

More from the blog

All posts

One email a month

New posts and what we changed in Meridel, in one short email.

Once a month, no more. Leave at any time with one click. Privacy policy