Show notes
Hey all,This topic could prove controversial, but I've had a couple of conversations recently that make me think this is a subject worth discussing. It's about the role of user researchers in organizations.Be Careful What You Wish ForNow, I know a lot of you reading this will be thinking to yourself that you'd kill to work somewhere willing to invest in hiring a dedicated user researcher. But be careful what you wish for, because I'm not sure it's always a good idea. Especially if it ends up creating a gatekeeper between stakeholders and users.The Separation of RolesYou see, I've worked with a few companies over the last year or so where the roles of user researcher and user experience designer have been separated. On the surface, this looks like a good idea. After all, generally speaking, the more specialized you are, the better job you'll do in a particular niche. And that's true for user researchers. There are many nuances to carrying out user research that a more generalist user experience designer may overlook.However, by separating the roles, you can create a couple of problems that I've witnessed recently.The Time-Consuming Nature of In-Depth ResearchFirst, precisely because of their expertise, some user researchers carry out such in-depth research that it doesn't always sit comfortably with the timescales allocated to projects internally. The result is that user research can become time-consuming and so only happens once or twice during the project. Instead of facilitating a culture of testing and iteration, you end up with a piece of upfront research and a sanity check towards the end when it's too late to change things.Although in theory, this kind of in-depth user research should provide benefits, in my experience at least, a leaner, more iterative approach tends to win out. Put another way, I favor a series of lightweight research and testing exercises throughout the project over more in-depth research at the beginning and end.If this is an approach you are interested in learning more about, I have a workshop that I can run in your organization.Reduced Designer-User InteractionSecond, and probably even more significantly, the involvement of a user researcher reduces the interactions that the UX designer has with users. Instead of running user testing themselves, they get back a report from the user researcher and often don't experience the user frustrations firsthand.Admittedly, the user researcher's observations may well be more in-depth and insightful because of their experience and expertise. However, I believe you lose something when the UX designer isn't observing and interacting with users firsthand. They'll learn a lot more this way than from reading a report.The Exception, Not the RuleOf course, this won't always be the case. In some organizations, the user researchers will go out of their way to involve the designer. However, in my experience, this is the exception and not the rule. That's not because of reluctance on either the part of the designer or researcher, but instead for the sake of efficiency. The pressure to deliver will often mean it's seen as excessive to have the designer involved in testing when it's seen as the job of the user researcher.Not a Criticism, But a ConcernNone of this is meant as a criticism of user researchers. Neither am I suggesting that there isn't a place for separate user researchers.However, I see the role of user researchers to be focused on the bigger picture. They should be gathering insights that apply to the wider organization, while project-specific testing should be done primarily by UX designers.See Also: Rethinking The Role Of Your UX Teams And Move Beyond FirefightingUser researchers can support them by providing training and advice, but I think it's dangerous to centralize all user research with the user researcher. Doing so, in my experience, results in less research and testing for the reasons I've given.What's Your Experience?That said, I recognize that I'm drawing on my own experience here, and maybe things are different where you work. I'd therefore love to hear from you on this one. Do you have separate user researchers, and if so, does that still allow for lots of lightweight research and testing to refine ideas and answer questions throughout the project?