Despite a strong product culture and widely adopted digital products, the Hellowork team faced a challenge: better understanding why users acted a certain way, and not just how. Alongside analytics data, Hellowork chose Screeb to build a qualitative feedback loop that is continuous and actionable squad by squad, with no dependence on the research team or developers.
The context
To support the growth of its job products, Hellowork wanted to build a more agile discovery practice while giving PMs more autonomy. The goal: gather actionable qualitative insights directly within user journeys, to quickly test hypotheses, refine its understanding of usage and adjust the roadmap more precisely.
The challenge: plenty of data, little user voice
Before integrating Screeb, teams relied mainly on quantitative data: analytics, KPIs, tracking events… Valuable signals, but they left a blind spot around users' intentions, blockers and deeper needs.
Qualitative feedback came mainly from app stores or customer support, channels that are useful but often imprecise, delayed, and hard to use at scale.
On top of that, quickly testing product hypotheses proved complex. The existing user research methods weren't always suited to the pace of agile cycles. As a result, some decisions were made without real field validation.
The solution: a three-step transformation with Screeb
Screeb's arrival made it possible to put a new approach in place, centered on simplicity, responsiveness and relevance.
- User listening built into key journeys. Targeted surveys were deployed directly inside the products, without involving the tech team. They capture immediate feedback, at the moment the user is going through a specific experience.
- Better-informed, faster decisions. The feedback collected is systematically used in Product rituals: pre-refinement, post-launch, scoping… It helps validate or invalidate hypotheses, and settle structuring choices within days.
- Greater autonomy for each squad. Thanks to Screeb, each team can run its own investigations, without depending on a centralized research team. This makes it easier to build a distributed discovery culture.
The results
Concrete impacts on the product organization
Since implementing Screeb, Hellowork has seen several tangible benefits:
- A better understanding of user expectations, even on mature products.
- Feedback that is immediately actionable, with no need for interpretation or complex analysis.
- Better prioritization of topics: some redesigns, such as the search engine or the listing pages, were guided by insights gathered via Screeb.
- Stronger alignment between PMs, designers and stakeholders, thanks to shared user feedback.
What Screeb changed in practices
It's not just a tool that was added, but a new way of working that took hold:
- Screeb is part of Product rituals: every cycle includes a field-learning loop.
- Decisions are grounded in evidence: user feedback is no longer anecdotal, it is structuring.
- Feedback is representative: PMs no longer rely only on weak signals, but on concrete data collected in context.
- Product culture evolves: the voice of customer becomes a pillar of strategic decisions.
Two numbers to remember
- +40%: that's the average completion rate for in-app surveys on some key products, proof of the engagement and relevance of this new way of listening.
- 15% average response rate, versus 1.5% with the previous solution.
