Why can’t I rely on user research from other departments?

Why can’t I rely on user research from other departments?

Here’s a question I was asked recently:

Hi Jock,

In my company, I’m working on a workflow product that will replace a bunch of manual / paper processes used by internal users in regional offices. At the moment, I’m not allowed to do user research with the regional users directly. Instead I have to go through both the Operations and the Process tracks – they’re the gatekeepers.

You talk about doing user research directly with users – does it matter that the Operations and Process tracks are telling me what their users want instead?



Hi M,

Your product or service may have multiple, distinct user groups. Each user group has differing needs, priorities and motivation. To be successful with each group, your product has to address their respective needs or solve their respective problems.

You need to have the confidence that you understand the needs of each user group before attempting to create a product and take it to market. Your goal is to achieve product-market fit with each group of users.

The only way to reassure yourself that you understand their needs is by having direct access to each group of users, and to meet with them regularly to check that you’re not going off track in either your understanding their problem, or your implementation of a solution for them.

In your case, you have the operations and process tracks as two stakeholder groups. These groups are proxies to the actual users. The danger of relying on a proxy to a particular group of users is that they act as a filter both in terms of the information they gather, and the information they then pass on to you. And because the operations and process tracks also have a vested interest in what you build, you have to assume the information they pass on to you is partisan (biased to their own interests).

If there are objections to you and your team establishing a direct link to the members for the purposes of user research, then you need to overcome, work around or ignore those objections. The likelihood of delivering a successful product is significantly reduced if you can’t research and validate your prototypes with each of your user groups directly. You might get lucky, in the same way as you might hit a dartboard blindfolded, but you probably won’t :-)

Here are a few articles that elaborate on the topic, which you might find helpful:

Fast Path to a Great UX – Increased Exposure Hours – Jared Spool

How do you keep user needs front and centre? – I Manage Products

How UK government digital services gather and use evidence – I Manage Products



Get articles when they’re published

My articles get published irregularly (erratically, some might say). Never miss an article again by getting them delivered direct to your inbox as soon as they go live.  

Read more from Jock

The Practitioner's Guide to Product Management book cover

The Practitioner's Guide To Product Management

by Jock Busuttil

“This is a great book for Product Managers or those considering a career in Product Management.”

— Lyndsay Denton

Jock Busuttil is a product management and leadership coach, product leader and author. He has spent over two decades working with technology companies to improve their product management practices, from startups to multinationals. In 2012 Jock founded Product People Limited, which provides product management consultancy, coaching and training. Its clients include BBC, University of Cambridge, Ometria, Prolific and the UK’s Ministry of Justice and Government Digital Service (GDS). Jock holds a master’s degree in Classics from the University of Cambridge. He is the author of the popular book The Practitioner’s Guide To Product Management, which was published in January 2015 by Grand Central Publishing in the US and Piatkus in the UK. He writes the blog I Manage Products and weekly product management newsletter PRODUCTHEAD. You can find him on Mastodon, X (formerly Twitter) and LinkedIn.

Leave a Reply

Your email address will not be published. Required fields are marked *