The 16% Who Will Talk

In most corporate environments, you’re expected to wait for permission before talking to users. There’s a process. You submit a request. Someone in product management decides whether it’s worth the time. A stakeholder meeting gets scheduled. By the time you actually sit down with a real user, months have passed and the product has already shipped the wrong thing.

I don’t wait that long. I start looking for opportunities to run contextual inquiry sessions on my own. And here’s what I’ve found after doing this across eight industries and two decades: roughly 16% of end users are curious and driven enough to be genuinely excited that someone is asking about their pain points. They don’t need convincing. They don’t need incentives. They’ve been waiting for someone to ask.

The Adoption Curve Parallel

That 16% maps loosely to the innovators and early adopters on the technology adoption curve. These are the people who’ve felt enough pain from the current situation that they’ve already started hacking their own solutions. They have the spreadsheet that tracks what the software doesn’t. They have the script that automates the tedious step. They have the workaround that saves them twenty minutes a day.

They’re not just willing to help with your research — they’re relieved. Finally, someone is paying attention. Finally, someone who might actually do something about the problems they’ve been living with.

How to Find Them

You can spot them from the first interaction. They’re the ones who light up when you say “Could you show me how you do this?” They’re the ones with post-it notes stuck to their monitor with shortcuts and reminders. They’re the ones who pull up a custom spreadsheet and say “let me show you something.”

They respond to your follow-up emails within minutes. They introduce you to colleagues who have the same problems. They call you — unsolicited — when they discover a new issue or have an idea. They remember your name and ask how the project is going when you bump into them months later.

Contrast this with the majority of users. Most people will be polite but passive. They’ll answer your questions but won’t volunteer information. They’ll say “it’s fine” when asked how things are going, even when it isn’t fine. They’re not being dishonest — they’ve just normalized the pain. It’s background noise.

The Other 84%

The pragmatists and conservatives on the adoption curve will help you if you compensate them for their time. That’s fair. They have jobs to do and deadlines to meet, and answering your questions isn’t in their job description. So you buy them lunch, or their manager gives them permission to spend an hour with you, or you offer a gift card.

The skeptics are just not interested. They don’t see the point. They don’t believe anything will change. And honestly? They might be right based on their past experience. Don’t waste your energy trying to convert them. Focus on the people who are already leaning in.

Your Discovery Pipeline

The 16% become your continuous discovery pipeline. This is one of the most underappreciated assets in product development.

Keep a roster. I literally maintain a list of people I can call when I need to understand something, test an idea, or validate a direction. Some of them I’ve known for years across multiple projects. The relationship is mutual: they get a voice in shaping the tools they use every day, and I get the truth about what’s working and what’s broken.

Share what you’re building with them. Show them prototypes. Ask for their honest reaction. They’ll tell you when something is wrong, which is the single most valuable thing in product development. Most people will tell you what you want to hear. Your 16% will tell you what you need to hear.

The Compound Effect

Over time, your allies become your evidence base. And this is where the real power lies.

When you need to convince leadership to change direction, you don’t come with opinions. You don’t come with best practices or industry benchmarks or frameworks you read about in a book. You come with stories from real people doing real work. You come with the specifics: “Maria at Client X spends three hours every Monday doing this manually because our system can’t handle it.” “The team at Client Y built their own dashboard in Tableau because our reporting doesn’t give them what they need.”

That’s hard to argue with. Not impossible — some organizations will argue with anything — but much harder than dismissing a design recommendation or a competitive analysis. Real people with real pain, documented in their own words, from their own workplaces. That’s the compound effect of nurturing your 16%.