Most product teams treat research like a checkpoint. Ask once, build for months, ask again. In financial services, where trust is the product, that gap is where relevance quietly dies.

The challenge

Our team needed to stay close to real user needs throughout the entire product lifecycle, not just at the start of it. The existing research setup relied on scattered, one-off methods. What was missing was a system that made listening to users a constant, not an event.

The approach

I designed and built a research and testing workflow that combined multiple feedback channels into one continuous loop. A dedicated feedback form captured input as it happened. Regular user testing sessions kept design decisions honest. Both were woven together with the methods already in place, user research and data tracking, into a single discovery process running alongside every sprint.

The principle behind it was simple. No iteration ships without being grounded in something a real user actually said, did, or struggled with.

The outcome

The team stopped guessing and started knowing. Every design decision could be traced back to real user behavior, not assumptions. The result was a product that felt functional and genuinely relevant at the same time, built by a team that stayed agile, responsive, and close to the people it was designing for.