user research

User Research & Engineering: Better Together During Discovery

by JULIA TAN & CAROLINA ALDAS, Spotify When we think about the “Discovery” phase in the product development process, we often picture product owners, design, and researchers working to understand a problem area, the needs of end users in that area, and testing product ideas that might deliver on those needs. When no product exists yet, it can be difficult to justify Engineering’s time. As such, the Discovery phase tends to be heavily driven by product owners, designers, and insights practitioners by default, and Engineering takes a more active role when product requirements and specifications become more defined. The process looks more like a relay race than synchronized swimming. In the process of passing the baton, important context gets lost and some agility is compromised. We’ve all been there. We devote time and energy to truly understand people, their needs and motivations. We identify and user-test solutions that have a high promise to deliver user and business value, only to find out it’s not entirely feasible...

Accelerating User Research: How We Structure Insights for Speed At Spotify

What's slowing down user research? 4 speech bubbles with text: I have this amazing idea! Can we go validate it? / How's the user experience of this screen? / We are shipping next week but need to get this in from of users first! / Let's all work in lockstep like the good partners we are!
by SARA BELT, Spotify (This article is also available in Chinese) Instead of asking how we can further speed up research itself, the question becomes how we can better integrate research into the product development practice and speed up organizations’ ability to learn and iterate overall. For many years, insights was seen as peripheral to product development because of the perception that user research had low validity. I spent the first part of my career advocating for why teams should systematically listen to the people using their products, why anyone should trust qualitative insight to guide their decisions, and why research is a field of practice that requires specialized skills. Debates about validity have diminished as the research practice has gradually proven its ability to contribute value. Approaching product making from the perspective of data, evidence, and empathy is pretty much a given these days. In companies such as Spotify, the pendulum has swung the other way, where growth in demand for research has pushed...

Mattresses & Moneyboxes: Cultural Affordances for Microfinance in Jordan

ZACH HYMAN EPAM Continuum Case Study—This case study will present how a multicultural and multidisciplinary team from EPAM Continuum, the global innovation design firm, gathered, analyzed, and presented back different forms of “evidence” to satisfy the complex set of client and customer needs for a Jordanian microfinance bank with 30 branches and 65,000 clients. The team navigated cultural and linguistic barriers as they sought to provide stakeholders and their customers the evidence they needed to confidently design a new “mobile payment service” for their microloan customers. Over the course of the engagement, the firm's team strove not only to research, design, and prototype a new service to hand off to a local development team, but also to (1) use a combination of deliverables and in-field accompaniment to train microfinance bank staff in their process; (2) present evidence demonstrating the deep customer understanding that can result from pairing ethnographic research and human-centered design; and (3) create evidence...