knab

Turning UX research into a weekly decision-making engine

Overview

Knab set out to become a truly customer-driven bank.
The ambition was there—but the way research was used didn’t yet match the speed of product development.

To close that gap, we redesigned how UX research worked inside the organization—transforming it from a supporting activity into a core operating system for product decisions.

The goal

Create a scalable research approach that:

  • delivers insights continuously

  • directly influences product decisions

  • is visible and accessible across the company

The objective wasn’t to “do more research”— but to make research actually drive what gets built.

The challenge

Like many product organizations, Knab faced three core challenges:

  • Research insights were not reaching the full organization

  • Product decisions were still partly driven by assumptions

  • There was no consistent rhythm to validate MVPs quickly

At the same time, teams were moving fast.
Research needed to keep up—or become irrelevant.

our Approach

Instead of running isolated studies, we introduced a continuous research loop embedded in the weekly workflow.

A fixed weekly rhythm

  • Thursday → Research sessions (max. 5 users)

  • Friday → Company-wide insight sharing via a podcast

This created a predictable system where:

  • research was always happening

  • insights were always fresh

  • teams could iterate immediately

Making research visible

To truly influence decisions, research had to be experienced—not just reported.

We lowered the barrier to zero by:

  • live-streaming user interviews across the company

  • enabling teams to join sessions instantly

  • making real user behavior visible to everyone

This shifted research from:
→ something you read
to
→ something you see and feel

the Outcome

The biggest shift wasn’t just better insights—
it was a new way of working.

  • Research became a weekly habit

  • Teams iterated faster with real user feedback

  • Decisions became evidence-based

  • The organization built a shared understanding of users

Most importantly:
Research moved from supporting decisions to driving them

the signal

What happens when research isn’t a phase—but a system?

You stop relying on opinions and start seeing what’s actually going on with your users.
It becomes easier to make decisions, because you’re not debating assumptions anymore, instead you’re reacting to real behavior.

Teams move faster because they’re more certain and know the STORY.

Priorities become clearer and teams spend less time building things that don’t land.

In the end, it’s simple:
you replace guesswork with clarity and that shows up in every product decision you make.

Next

IKEA